Ergonomics of Sustainability, Innovation & Continuous Integration (part 4)

In the previous blog post we explained how to upgrade a zenon standalone system. This time we are going to focus on a zenon Network server-client system.

On a zenon Network server-client System we have to bear in mind that more than one operator works with the system. This makes the upgrade sequence a bit more challenging as the uptime of the whole system becomes more important.

The good news is that the whole zenon system can get upgraded step by step. There is NO need to shutdown the whole system for an extensive upgrade period. This is a crucial advantage when it comes to the step-by-step planning of an upgrade sequence.

“Client only” PCs in a zenon network can always be upgraded prior the upgrade of the Server PCs. This way, only the PC being upgraded is temporarily unavailable while the rest of the zenon network runs uninterrupted.

zenon has worked this way since zenon 7.00, based mainly on zenon’s Runtime Compatibility function. For more about Runtime Compatibility check out the zenon online help (F1) -> Manual -> Runtime -> Runtime Compatibility.

Upgrade Scenario:

In our second example, we are going to upgrade a zenon network client server system with one zenon project running, from a zenon 7.20 system to zenon 7.50.zenon_product_version_connectivity_-12 Step 1: Read back and import the Runtime files into the Editor project in the old version 7.20. Make sure that, in the Editor for the current version of the project, the settings for “RT changeable data” concerning decompilation settings are set correctly.

Step 2: Create a workspace backup in the current version 7.20.

Step 3: Install the zenon Editor of the new version 7.50 on the Engineering PC. Now both zenon Editor versions – 7.20 and 7.50 – are installed and can be used by starting them through the zenon Startup Tool.zenon_product_version_connectivity_-08zenon_product_version_connectivity_-11 Step 4: Upgrade client Runtimes (all except Server 1 of the project).

Stop the Runtime and install the new version of the Runtime.

Hint: Installation without demo projects is advisable.

After successful installation, enter the path to your project for the new 7.50 entry in the Startup Tool.

Now both zenon Runtime versions 7.20 and 7.50 are installed on the PC. In the worst case scenario, you can always go back to using the 7.20 Runtime.

Step 5: Start the new 7.50 Runtime. The same unchanged zenon project files of 7.20 will be synchronized from the process-leading server 1. Now, the Runtime version 7.50 on the clients is executing the zenon project of version 7.20.

zenon_product_version_connectivity_-13Step 6: Upgrade Server 1 just like you upgraded the clients in the previous step.

Warning: this will result in some downtime.

Stop the Runtime and install the new version of the Runtime.

Hint: Installation without demo projects is advisable.

After successful installation, enter the path to your project for the new 7.50 entry in the Startup Tool.

Now both zenon Runtime versions – 7.20 and 7.50 – are installed on the PC. In the worst case scenario, you can always go back to using the 7.20 Runtime.

zenon_product_version_connectivity_-14Step 7: On the Engineering PC load the project -> this will be converted to zenon 7.50. Compile the project for zenon 7.50.

Step 8: Transfer the zenon project files of version 7.50 to Server 1 using Remote Transport.

Step 9: Start the new 7.50 Runtime on Server 1 with the Startup Tool.

Step 10: The zenon project files will be synchronized to all clients automatically.

Hint: On very large zenon network installations, the network bandwidth can be a crucial factor to keep an eye on. This should be considered during the planning phase.

Depending on what you prefer to work with – the Startup Tool, the Remote Transport or the Network Topology – Steps 7 through 9 can vary a bit.

zenon is flexible and offers a tool for all your needs: do it your way!

Now your whole zenon system runs entirely on zenon 7.50 and you can benefit from all the new features available.

Tags: , , ,

Leave a Reply