Stateflow

DLL Files

If you have a Simulink model named mymodel.mdl, which contains two Stateflow blocks named chart1 and chart2, this means that you have a machine named mymodel that parents two charts named chart1 and chart2.

When you simulate the Stateflow chart for mymodel.mdl, you actually generate code for mymodel.mdl that is compiled into an S-function DLL file known as a simulation target. On Windows PC platforms this file is named mymodel_sfun.dll. On UNIX platforms the DLL file is named mymodel_sfun.$mexext$ where $mexext$ is sol2 on Solaris, mexsg on SGI, mexlx on Linux, and so on.

Generated Files

Code Files