Migration from previous FESA3 versions

FESA3 2.x.2 -> 3.0.0

Basic migration steps

To migrate existing FESA software from the previous FESA3 version 2.x.2 to the current version FESA3 3.0.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'

Changes in the GSI-Template

If your migrated class uses the GSI-Template, be aware that:

• Now there is a new GSI-Specific acquisition property, called "ModuleStatus". You need to fill it's related fields with infomation! The most easy approach is, to set the field together with all status-related fields in the RT-Action:

...
// Per default the modules "myModule1" and "myModule2" are defined. 
// Please modify the list of modules, according to your hardware/software module-configuration in the configuration-field "moduleStatus_labels"!
device->moduleStatus.set("myModule1",MODULE_STATUS::OK, context);
device->moduleStatus.set("myModule2",MODULE_STATUS::NOT_AVAILABLE, context);
...

• The GSI-Status-Property got a new boolean value-item, called "modulesReady-item". It is used to signal that all required 3rd party hardware and software modules are ready to be used. A value needs to be set to this item, or the related field, so that client are able to use the property ! Again, the most easy approach is, to set the field together with all other status-related fields in the RT-Action:

...
device->modulesReady.set(true, context);
...

Detailed information

• '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: new GSI-specific acquisition property "ModuleStatus" and all its dependencies will be added if the GSI-template is ued.
  • Check this link for more information !
• class design: new element builtin-types will hold notification-update-enum and diag-fwk-topic
• class design: fault-severity element is introduced
• class design: instead of state-enum elements the GSI specific properties use normal enums
• class design: power state unknown (=0) is added to the list if it is missing
• instance: fec-name element is inserted before server-name element

Older FESA versions

If you want to migrate from an older FESA version to 3.0.0, please follow the previous migration-steps to bring your software to FESA3 2.x.2