Custom framework migration (ION9000)

[TC]

Hi, we have multiple units of ION9000 with hyper scaler DC, all of which with fw 3.1, and heavily customized framework. A lot of modules (modbus master device 1-49, modbus master map 1-13, display 9-17, convert, modbus slave, aritmetic, pulse merge, AND/OR, data recorder, etc)

Now, there is a need to upgrade firmware to latest 4.6 (or 4.7 we are considering).

The question is how to do it "most efficiently" and "error free".

Lead to believe the "error free" method is per below, which is very crumble some, and needing advice how can we simply?

(1) Download from site each ION9k existing dcf file using ION Setup

(2) Back in office, find a unit of ION9k (temp_ION9k_v3.1) ;fw 3.1, which we struggled to get one as most of ours in lab are already v4.x

(3) Using IONsetup, load the dcf file taken from site to the temp_ION9k_v3.1.

(4) connect temp_ION9k_v3.1 to PME instance and open Designer

(5) Locate added module and save it as "added_module.fwn"

(6) find yet another ION9k (temp_ION9k_v4.6); which we have to find a way to locate second piece.

(7) connect temp_ION9k_v4.6 to PME instance and open Designer

(8) paste "added_module.fwn" into factory template (and lots of validations to make sure modules are integrated properly, not overriding factory template modules)

(9) from IONSetup, download dcf file and save as "dcf_v4.6__updated_with_added_module" 

(10) bring the dcf file generated from step 9 to site, load into ION9k after it is updated to 4.6

[RobGraham · Accepted solution]

This is a good idea to verify with one meter, as changes to the supported modules do happen occasionally.  However, in theory, you should be able to simply download the .dcf, upgrade the firmware, then reload the .dcf in one shot.  

For your information, modern ION Setup can also load full .fwn files to a meter instead of a .dcf if it's more convenient.  Just select all modules in Designer and copy to framework.  I think it can also lock-paste partial .fwn files, but I haven't worked with that myself.

[Charles_Murison]

Hello,

If there were any changes to the modules supported you would see when doing a framework paste.

One suggestion would be sure that you maintain external inputs when saving the framelet. The steps as described are the steps I would do myself.

Regards,

Charles

[Tom_Stevenson]

Please let us know how this goes - one additional thought is to maintain in the fwn format (as ION Setup supports fwn) and this opens up maintaining your framelet as a partial framework (ie. group in a customer folder and save just that folder) that can be applied to future factory frameworks in Designer.  

[TC]

Thank you @RobGraham @Charles_Murison @Tom_Stevenson for feedback. 

Now I am convinced I am not alone.

The optimization I gathered, will be on step 9 and 10, where after pasting the custom framework in Designer, I will save as .fwn file, and integrate it into single fw4.7 update zip package. For on-site one-time upgrade via IONSetup.

Any indication whether this kind of migration work can be made easier/automated near future? Via IONSetup maybe? Removing the need of very back office support.

[Tom_Stevenson]

Hi TC - you could streamline by doing a partial framework paste from Designer with your custom framelet vs. maintaining a complete template.  This would cut out steps from your process and your framelet becomes less subject to factory framework changes.