SV5 to SV6 online upgrade of controllers
We are performing HMI upgrade for a customer going from SV5.0 SP2 Rev B to SV6.0.3.2. The software installation and configuration for SV6 is taking place in the office. According to the upgrade manual we should be able to take the upgraded system and connect to running controllers at site.
One of the steps when upgrading the CBM project is to determine when the associated libraries are to be replaced with newer versions. Is it correct to state that this step needs to take place when we are ready to fully download the application from SV6 system to the controllers (also upgrade the firmware)?
If we are not to replace the libraries, can we still perform downloads from the SV6 system to the running controllers at the older firmware.
One of the steps when upgrading the CBM project is to determine when the associated libraries are to be replaced with newer versions. Is it correct to state that this step needs to take place when we are ready to fully download the application from SV6 system to the controllers (also upgrade the firmware)?
If we are not to replace the libraries, can we still perform downloads from the SV6 system to the running controllers at the older firmware.
Asked 1 year ago
Voted best answer
2
Hi,
If you are using redundant controllers (and/or CI), you can perform "Online Upgrade", without shutting down production, while upgrading firmware.
There are a couple of if's & but's, for instance check your slave settings on handling bus errors, if you are using ProfiBus etc.
Single controllers you have to delete application in the controller before firmware upgrade.
Could also be useful to check ISP/OSP-settings, document status of outputs, forces etc of your I/O.
Also useful is to check hardware types and revisions before roll-out, some PM's or CI's are not supported by SV6 (coming from SV5.0).
BR
If you are using redundant controllers (and/or CI), you can perform "Online Upgrade", without shutting down production, while upgrading firmware.
There are a couple of if's & but's, for instance check your slave settings on handling bus errors, if you are using ProfiBus etc.
Single controllers you have to delete application in the controller before firmware upgrade.
Could also be useful to check ISP/OSP-settings, document status of outputs, forces etc of your I/O.
Also useful is to check hardware types and revisions before roll-out, some PM's or CI's are not supported by SV6 (coming from SV5.0).
BR
Answered 1 year ago
Answers
1
As part of the upgrade the older application libraries will be replaced by newer versions. Updated hardware libraries (firmware), will be added, but the old hardware libraries will remain. When you open up a project in CBM, the application libraries will automatically update. You can not go online until the updated, recompiled, applications have been downloaded. During our upgrade a month or two ago, we ran without downloading for a day or two, since we experienced process shutdowns when we tried the first controller. We took precautions and forced a lot of outputs in manual mode while downloading the subsequent 10 or 12 controllers.
Hardware libraries (firmware) was successfully upgraded online several weeks later.
Hardware libraries (firmware) was successfully upgraded online several weeks later.
Answered 1 year ago
0
In some cases firmwares has backward compatibility but the recompiled application has to be downloaded
Answered 1 year ago
Add new comment