Changes which will be done by the migration-script:

The script will ...
  • the silecsdeploy folder 'generated' will be named 'generated-silecs' (old generated folder will be removed)
  • re-structure the silces deploy-document to provide more configuration-options
    • disconnect fesa-device-name from silecs-device-name ( now they can be different! )
    • possibility to specify FESA FEC name --> needed to automatically deliver .paramter files to FEC
  • remove the config field 'parameterFile' fom FESA class and from instance-file
    • now the plugin provides a button to deliver the 'parameterFile' to the FEC

What do I need to do ?

  • Install the SILECS Eclipse-Plugin for SILECS v2.1.x
    • If there is some error, first uninstall the old silecs-eclipse-plugin !
  • Right click on a silecs-file, select SILECS --> Update SILECS version. This will launch the migration-sript ( a backup of the old doc will be done).
  • Optionally, for pretty xml formatting: click somewhere into the new xml-code + press STRG(Control)+Shift+F
  • Validate the new xml (if there are errors, please let me know!)
  • Re-Generate the code in Silecs
  • Validate related FESA-files and as well re-generate the code in FESA
  • Check that the new Makefile.specific are fine ( the old Makefile.specific got renamed to Makefile.specific.backup since the silecs-version to link changed )
  • Clean & Make first the FESA-class, than the FESA-DU
  • Release the new FESA binary, make sure that the new .silecsparam files are used !
  • You dont need to upload the new PLC-controller-code to the PLC, this part did not change
  • Take a try ! If there are problems, please let me know!

Dont forget to check the changelog to see how you can profit from the fixes!
Topic revision: r1 - 31 Jan 2018, AlexanderSchwinn
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback