Page 9 - Upgrading to ExtendSim 10
P. 9

 It is best to convert all your models to ES10 at the same time and to use the same libraries. If that isn’t possible or practical, save copies of whichever libraries you used to convert models and “freeze” those copies without making changes. Then use the “frozen” libraries when you later convert prior-release models. Using libraries that are as close as possible to what was used to build the models will give the best conversion results.
 If you have saved a hierarchical block (HBlock) in a library, and the HBlock contains blocks from a release prior to 7, and those blocks are not from the v6 Legacy libraries (Generic, Discrete Event, and Mfg):
1. 2.
If those blocks have not been properly compiled in ExtendSim 7, 8, or 9, ES10 will not be able to properly convert them to the new format. Instead, it will give a warning message when you open that library or open a model that uses that HBlock.
To fix the problem, do the following:
o o o o o o
o o
In your prior release (7, 8, or 9) and using your original (non-Legacy) library:
Open the library that gave the warning message
Open that library’s Library Window
Use the Library > Library Tools > Compile Open Library Windows command to compile the library
Drag each HBlock that got a warning message onto a blank model worksheet in your prior release
Open the HBlock’s structure and make some insignificant change so that the block needs to be saved
Close the structure window and choose Also Save to Library
Launch ES10
Open the fixed original library (.lix, not .lbr) in ES10 to convert the library to the ES10 format.
If you’ve already converted that original library in ES10 (.lbr) you’ll get a warning message. Just click OK
on that message to continue the conversion, replacing the previously converted library.
Repeat for each HBlock that has prior release blocks in it, and for each library that contains those HBlocks.
 The above process DOES NOT convert blocks from the v6 Legacy libraries (Generic, Discrete Event, and Mfg)! ES 10 does not ship with the v6 Legacy libraries because it is not compatible those libraries and does not support them. See page 10 for more information about Legacy libraries.
Verifying Models: Automating the Process
ExtendSim 10 ships with an automated test environment so you can verify models between releases and between changes you make to your models. There are two components to the test environment. They are used differently depending on whether you want to test several models at a time or only one model:
 The Compare Results application located at Program Files/ExtendSim10 is for testing multiple models
 The Model Compare block (Utilities library) is useful for testing a single model These tools help identify any differences in two situations:
Verifying that models will generate the same results when there is a new release of ExtendSim. The test environment
simplifies the process of comparing simulation results between two ExtendSim releases – looking for any differences
between models that were saved in a previous release and the same models run in the new release.
Determining if changes made to a model affect the results. In the same manner as verifying between releases, you can
compare copies of the model saved before and after you’ve made changes.
For complete information on how to use these tools for model verification, see the section “Automated test environment” in the
User Reference.

   7   8   9   10   11