Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84851members
354313posts

SAGE RTU - Secure Firmware and Config Process Question

Power Monitoring and Energy Automation NAM

This forum is created for the exchange of information and open dialogue regarding electrical power monitoring and energy automation products and services. Participants will have access to downloadable material as well as chat opportunities with subject matter experts.

Solved
SAGErtu_user
Cadet
0 Likes
2
963

SAGE RTU - Secure Firmware and Config Process Question

When updating my SAGE RTU to the latest firmware version, when do I need to use the initial installer and config converter programs?  

 

@DeanLopez

Tags (1)

Accepted Solutions
DeanLopez
Crewman Crewman
Crewman
0 Likes
0
959

Re: SAGE RTU - Secure Firmware and Config Process Question

INITIAL INSTALLER

The Initial Installer utility is only used when converting an existing, "red CPU" card based SAGE RTU running non-secure firmware to the Secure Firmware, (J0 and beyond - current Rev is C3414-500-S02K5_P2).

The utility updates the existing configuration in place on the compact flash, but also modifies the directory structure on the Compact Flash to that needed by the secure firmware. 

Initial Installer utility only needs to be performed once.  


CONFIG CONVERTER

If you download a secure firmware update package (J0 or later) from the sage-rtu.com website, it comes with a Config Converter that will update an existing secure firmware configuration from an earlier revision to the firmware update package revision. It is located in the Update/Secure/updateGen folder.

 

However, there is a multi-step process required to convert a non-secure configuration to secure, depending on the hardware it is from, either 2200 or 2300/2400 (both non-secure).

 

2300 and 2400 non-secure to Secure Firmware config (offline version):

All non-secure firmware configuration must be at the G3 revision for any Secure Firmware Config Converter to be able to convert it properly.  You can download the G3 Firmware Update package to obtain the G3 Config Converter utility.  Once your configuration is converted to G3, the Secure Firmware Config converter can import it and create the equivalent secure firmware configuration package to be uploaded directly to the RTU.

 

2200 config to Secure Firmware:

Convert to B6, using the config converter supplied with the secure firmware package. (Update/Secure/config_converters/S2200/Convert_to_B6_1.6.exe)

Convert the B6 config to G3, using the config converter supplied with the  (Update//Secure/config_converters/C3414/Convert_to_G3_6.4.exe)

Finally, use the secure config converter to create the secure config (Update/Secure/updateGen/Config_Converter_K5.exe)

See Answer In Context

Tags (1)
2 Replies 2
DeanLopez
Crewman Crewman
Crewman
0 Likes
0
960

Re: SAGE RTU - Secure Firmware and Config Process Question

INITIAL INSTALLER

The Initial Installer utility is only used when converting an existing, "red CPU" card based SAGE RTU running non-secure firmware to the Secure Firmware, (J0 and beyond - current Rev is C3414-500-S02K5_P2).

The utility updates the existing configuration in place on the compact flash, but also modifies the directory structure on the Compact Flash to that needed by the secure firmware. 

Initial Installer utility only needs to be performed once.  


CONFIG CONVERTER

If you download a secure firmware update package (J0 or later) from the sage-rtu.com website, it comes with a Config Converter that will update an existing secure firmware configuration from an earlier revision to the firmware update package revision. It is located in the Update/Secure/updateGen folder.

 

However, there is a multi-step process required to convert a non-secure configuration to secure, depending on the hardware it is from, either 2200 or 2300/2400 (both non-secure).

 

2300 and 2400 non-secure to Secure Firmware config (offline version):

All non-secure firmware configuration must be at the G3 revision for any Secure Firmware Config Converter to be able to convert it properly.  You can download the G3 Firmware Update package to obtain the G3 Config Converter utility.  Once your configuration is converted to G3, the Secure Firmware Config converter can import it and create the equivalent secure firmware configuration package to be uploaded directly to the RTU.

 

2200 config to Secure Firmware:

Convert to B6, using the config converter supplied with the secure firmware package. (Update/Secure/config_converters/S2200/Convert_to_B6_1.6.exe)

Convert the B6 config to G3, using the config converter supplied with the  (Update//Secure/config_converters/C3414/Convert_to_G3_6.4.exe)

Finally, use the secure config converter to create the secure config (Update/Secure/updateGen/Config_Converter_K5.exe)

Tags (1)
Chris_Kerr
Ensign Ensign
Ensign
0 Likes
0
846

Re: SAGE RTU - Secure Firmware and Config Process Question

We recently held a webinar which goes in depth on this topic, including how to perform config updates when performing CPU upgrades from SAGE 2200, SAGE 2300 to the latest secure firmware.

 

We also covered converting from non-secure 2400's to the latest firmware as well as secure to secure configuration updates. 

 

You can watch the session here under the 2021 -> Week 3 folder. 

Or use the direct link here.

 

I hope that helps to clarify when and how to migrate from any previous CPU to the latest firmware to take advantage of the cool features we have implemented recently (an explanation also included in the webinar).

Tags (1)