Migration Limitations

Position of Gateway Blocks

During migration of your model, the software inserts gateway blocks where signals transition from the event-based domain to the time-based domain, or vice-versa. To insert these gateway blocks, the software inspects existing lines and connections in your model. Based on the position of these existing connections, the software calculates the best position at which to insert the required gateway blocks. However, the software might not always place gateway blocks in the ideal position, or if the software inserts multiple gateway blocks, the gateway blocks might overlap.

Once the seupdate migration process is complete, review the list of new gateway blocks that the software includes in the update report. In the model editor, inspect the positioning of these new gateway blocks. If any blocks are not positioned as you expect, reposition them manually and save your model.

Cascaded Mux or Bus Blocks

In the following model fragment, two Bus Creator blocks are connected in a cascade configuration. In this case, if you use seupdate to migrate the model, the migration fails.

Migration of a model using seupdate fails if the model contains cascaded configurations of the following Simulink® blocks:

  • Bus Creator

  • Mux

In this example, when migration of the model fails, the command window displays the following output:

If migration fails due to cascaded mux blocks, the software displays similar output. The output notifies you that as a result of the failed migration, the model might be in a partially updated state. To resolve the failure condition and successfully update the model, before rerunning seupdate, remove any cascaded bus or mux configurations from your model.

For information on using bus signals in SimEvents® models, see Working with Bus Signals.

Was this topic helpful?