Before Migration

Prepare to Migrate a Model

The seupdate function overwrites the model that it is updating. Before beginning the update, the function completely backs up the model and associated custom libraries. The software stores this backup in a new folder, in the same directory as the model. The new folder uses the naming convention seupdate_for_sys.

Before you start the migration:

  • Ensure that you have no unsaved changes in the model.

  • Ensure that you have write permission for the model and associated libraries.

  • Ensure that the model compiles without warnings or errors.

Expected Changes to Model Contents

SimEvents® models cannot simultaneously contain blocks from releases prior to R2011b and the current release. After you update your model, you cannot use blocks from previously released SimEvents libraries.

The seupdate command:

  • Replaces SimEvents and Simulink® blocks with the latest versions.

  • Replaces instances of the Discrete Event Subsystem block with the Simulink Atomic Subsystem block.

      Note:   seupdate might convert a Discrete Event Subsystem block to a virtual subsystem that contains an Atomic Subsystem block and possibly Event Filter or gateway blocks. In these cases, the name of the virtual subsystem might still contain the string, Discrete Event Subsystem. However, the underlying subsystem has been converted.

  • Inserts new gateway blocks to delineate the boundaries between event-based portions and time-based portions of the model.

For information on using the seupdate function to migrate your model, see Run seupdate.

Was this topic helpful?