Path to MATLAB executable

Specify the full path of the MATLAB executable (e.g. matlab.exe) that you would like to use with Syndeia. If empty, the default MATLAB configured on your computer will be used. This setting allows you to select a specific MATLAB/Simulink version to be used for Syndeia if you have multiple versions installed on your machine.

Use MATLAB Engine API

If this setting is set to true, then Syndeia will use an API-based approach to interact with MATLAB which was introduced in R2016b. This approach provides a much faster access to MATLAB session and execution of MATLAB commands from Syndeia. Select this mode if you have MATLAB 2016b and above. Otherwise, set this to false, and specify the path to MATLAB executable in the first setting above.

Use existing MATLAB session

If this setting is set to true, then Syndeia will use an existing MATLAB session if you have MATLAB running your computer. Otherwise, Syndeia will create its own MATLAB session in no-graphics mode. Note that Syndeia can use an existing MATLAB session only if the user has shared the session. This setting is used only when using the MATLAB Engine API (setting above).

Generate executable wrapper model

If true, Syndeia will generate an executable wrapper model for the given Simulink model, with name <SimulinkModelName> _RUN.slx. This wrapper model can use input values from the MATLAB workspace, execute the Simulink model, and return output results to the MATLAB workspace. This functionality is currently only available for MATLAB versions 2012a and above.

SysML port type when generating from Simulink

Select the type of SysML port that will be created when generating SysML block structure from Simulink model structure.

Use library blocks when generating from Simulink

Set true if Simulink library blocks should be used when generating SysML models from Simulink models. By default, Simulink library blocks will be ignored.

Generate/compare state and transition behaviors

Set true if you want to generate and compare state behaviors (e.g. entry, do, exit) and transitions behaviors (e.g. trigger, guard, effect) from SysML → Stateflow, or vice versa.

Synchronize state and transition behaviors

Set true if you want to synchronize state behaviors (e.g. entry, do, exit) and transitions behaviors (e.g. trigger, guard, effect) from SysML → Stateflow, or vice versa.

Browser not supported