SB2SL (SB2SL)

SB2SL

Limitations

No translator can completely convert an optimally designed SystemBuild model into a optimally designed Simulink model. There are subtle differences in the way that the two tools work that prevent faithful translation of all capabilities. However, this tool does the job of converting basic blocks and hierarchy from one tool to the other in a form that can be simulated. The following are limitations of SB2SL:

Data types are not supported.
Write to Variable and Read from Variable blocks do not support the element- or bit-addressing option.
The SystemBuild simulation parameter cdelay is not supported.
The timing of triggered subsystems with the "as soon as finished" output posting requirement differs from the SystemBuild implementation:
- SystemBuild updates the outputs at the beginning of the next minor numerical integration step.
- In Simulink, the outputs are available immediately.
Simulink models obtained from SB2SL conversions of SuperBlocks containing any triggered SuperBlocks with both of the following attributes will not run:
- The output posting is selected as "at timing requirement."
- The triggered SuperBlock is nested within another triggered SuperBlock.

File Formats

SB2SL cannot read SystemBuild files stored in the binary file format.

Blocks Not Converted to Simulink

SB2SL converts the following SystemBuild blocks into blocks that are not directly usable with Simulink:

State Transition Diagrams
MathScript blocks
UserCode blocks
Interactive Animation blocks

These blocks are converted into blocks labeled Unconverted. To view a complete listing of the blocks not translated, select Unconverted blocks from the Build menu.

Suggestions for Handling Unconverted Blocks

You can implement all of the SystemBuild operations represented by the Unconverted blocks on your Simulink diagram using MATLAB, Simulink, and, in some cases, other related products. Here are some suggestions for replacing the Unconverted blocks with ones usable for simulation with Simulink:

You can replace MathScript blocks with MATLAB Fcn blocks. These blocks are used to run M-files. You must write your own M-files to execute the equivalent MathScript.
You can replace UserCode blocks with S-Function blocks. These are blocks you can use to run C code or Fortran.
You can use a variety of blocks in the Simulink Sinks library to replace Interactive Animation blocks, depending on the function of that block.
You can replace State Transition Diagrams with Stateflow^® models. This requires you to purchase Stateflow in addition to MATLAB and Simulink.

To replace an Unconverted block in your Simulink model with the correct Simulink block:

1.: Open an Unconverted block in the Simulink model by double-clicking on it.

: This opens a window listing the SystemBuild component that caused the Unconverted block to be created.

2.: Either:

Delete the Unconverted block and copy an appropriate standard Simulink block into its place.
Use the Simulink function replace_block to replace the Unconverted block in the Simulink model.

[ Previous | Help Desk ]