Migration from previous FESA3 versions
FESA3 3.0.0 3.1.0
Basic migration steps
To migrate existing FESA software from the previous FESA3 version 3.0.0 to the latest version FESA3 3.1.0 perform the following steps:
- Open the FESA class design
- Press 'Update FESA Version'
- Press 'Synchronize Source Code'
- Open the FESA deploy-unit
- Press 'Update FESA Version'
- Press 'Synchronize Source Code'
- Open the FESA instance-file
- Press 'Update FESA Version'
- Press 'Promote Instances'
- 'Update FESA Version' will increase the FESA version number of classes and deploy-units, copy your file to *.backup and then run a python script to automatically modify the XML design if required. Please check the Eclipse console output for details.
- 'Synchronize Source Code' will update the generated C++ code and the XML design of the deploy-unit and/or instantiation file according to the changes in the current XML design.
- 'Promote Instances' will modify the FESA instantiation file if required according to the updated XML schema
The following issues are performed by the migration tool:
- class design: Description items will be added to GSI's standard properties such as Version, Init, Reset, Power, etc
- class design: The used structure type of the GSI-specific value-item "acquisitionContext" changed together with the value-item itself.
- instance-file: Renameing of the GSI-specific "MainMultiplexingCriterion" SEQ --> SEQUENCE, BP --> PROCESS
- Adaption of links in /common/export/nfsinit/<FEC>
FESA Version |
Initialization Script |
SAFTlib |
FESA3 2.3.2, 3.0.0 |
fesa_64bit, e.g. ../global/fesa_64bit |
saftlib_fesa232, e.g. ../global/saftlib_fesa232 |
FESA3 3.1.0 |
fesa310_64bit, e.g. ../global/fesa310_64bit |
saftlib_fesa310, e.g. ../global/saftlib_fesa310 |
Older FESA versions
If you want to migrate from an older FESA version to 3.1.0, please follow
the previous migration-steps to bring your software to
FESA3 3.0.0 .