What is the process for updating versions?

[Leeable]

Hi~

I want to know How to update vPLC version for example from 25.0 to 26.0? and any details process?

./DEINSTALL.sh then choose not to remove volumes?
podman load -i vplcnext26.0.tar to load a new image?
UPDATE.sh to maintain volumes?
I feel a little confused about whether need to add some warnings in certain places. Or give users some guidance?

Thanks a lot

[OWarneke]

Hello Leeable,

In the best case a update can be executed as follows.

./INSTALL.sh -i Image_Version_2025.0.tar

./DEINSTALL.sh -n my_vplcnext_1
Delete Volumes?:
- No

./INSTALL.sh -i Image_Version_2025.6.tar

The new version should then be running with the same project and configuration.

Additionally there is an UPDATE.sh script that can be used to update the state of the volumes.
This is usually not necessary but might be neccessary in the future when mayor changes or new features are added to the PLCnext Firmware.

e.g. Feature_A is added in version_26.0 and needs new config files at /opt/plcnext/config/Services/Feature_A/File.config

When reusing volumes this file will not be present and thus a Sync of the Image state and current Volume State has to be executed.
Thats what the UPDATE.sh does.

[Leeable]

Hello Leeable,

In the best case a update can be executed as follows.

./INSTALL.sh -i Image_Version_2025.0.tar

./DEINSTALL.sh -n my_vplcnext_1
Delete Volumes?:

• No

./INSTALL.sh -i Image_Version_2025.6.tar
The new version should then be running with the same project and configuration.

Additionally there is an UPDATE.sh script that can be used to update the state of the volumes. This is usually not necessary but might be neccessary in the future when mayor changes or new features are added to the PLCnext Firmware.

e.g. Feature_A is added in version_26.0 and needs new config files at /opt/plcnext/config/Services/Feature_A/File.config

When reusing volumes this file will not be present and thus a Sync of the Image state and current Volume State has to be executed. Thats what the UPDATE.sh does.

Thanks! @OWarneke