Upgrade logiccloud Control
logiccloud Control is the runtime that executes your PLC project on a device. Older runtime versions miss bug fixes, protocol features, and security updates, so the portal flags any device whose installed version is below the current minimum supported version.
When you see the warning
Section titled “When you see the warning”When a device runs an outdated logiccloud Control version, the portal shows a warning on the device card and in the device header:
You are running an old version of logiccloud-control. Please update to the latest version.
A device that cannot report a valid version at all is also treated as outdated — it predates version reporting and should be upgraded. The remediation depends on the device type, shown directly in the warning and detailed below.
On a physical edge device (Raspberry Pi, industrial gateway, IPC, …) logiccloud Control runs as a container. Restarting the container keeps the old image, so to pick up the latest version you must remove the existing container and install a fresh one. Do it in two steps: remove the current installation (Step 1), then install the latest container from the device binding dialog (Step 2).
The quickest route on most devices is the Management Commands section of the binding dialog, which can run the container upgrade for you — see Edge troubleshooting and maintenance. The manual steps below give the same result and let you choose whether to keep your data.
Step 1 — Remove the current installation
Section titled “Step 1 — Remove the current installation”The logiccloud-storage volume holds everything that makes the device yours: the installed PLC project, retained values, connector configuration, and the cloud binding / license activation. You can remove the container with or without that volume:
- Keep storage (recommended for a version upgrade) — only the container and image are replaced; the device comes back already bound and licensed, running the same project.
- Remove storage (clean slate) — also wipes the project, retained values, and binding. After reinstalling you must re-bind and re-activate the device from the binding dialog. Use this only if you intend to start fresh.
Docker
# Stop and remove the running container + the old image (keeps your data volume)docker stop logiccloud-controldocker rm logiccloud-controldocker rmi logiccloud/logiccloud-control:4.68.11
# Optional — ALSO delete the stored project / retained values / binding (clean slate):docker volume rm logiccloud-storagePodman
# Stop and remove the running container + the old image (keeps your data volume)podman stop logiccloud-controlpodman rm logiccloud-controlpodman rmi logiccloud/logiccloud-control:4.68.11
# Optional — ALSO delete the stored project / retained values / binding (clean slate):podman volume rm logiccloud-storageThe first three commands replace only the runtime container and image. Run the
volume rmline only if you want to discard the device’s data and binding — skip it for a normal version upgrade.
Step 2 — Install the latest container via the binding dialog
Section titled “Step 2 — Install the latest container via the binding dialog”- In the logiccloud portal, open the device and bring up its binding dialog (the installation panel) — see Setting up the device.
- Follow the installation steps shown there. The Quick Install one-liner (
curl/wget) downloads and starts the latest logiccloud Control image — this is what installs the new version. The dialog also offers a Manual Installation variant that uses a temporarydocker/podmancontainer whencurl/wgetare unavailable. - If you kept the storage volume, the device reconnects automatically with the same project and license — no re-activation needed. If you removed the storage volume, copy the activation token from the binding dialog and paste it into the device’s edge interface to re-bind and re-activate — see Activation and connecting the device.
Once the new container is running and reports its version, the outdated-version warning clears automatically.
Device-specific (FLECS, Portainer, device UI)
Section titled “Device-specific (FLECS, Portainer, device UI)”Some devices install containers through their own interface (a built-in app store such as FLECS, a pre-installed Portainer, or a vendor device UI) rather than the command line. To upgrade on these:
- Open the device’s container UI and locate the logiccloud-control app/container.
- Update the image tag to the latest
logiccloud/logiccloud-controlversion (or use the UI’s update/recreate action), keeping the existinglogiccloud-storagevolume mounted. - Recreate/restart the container from the new image.
See Alternative installation possibilities for the per-UI field names (image, volume, ports) that must be carried over.
A vPLC (a cloud-hosted soft PLC — types S1, S2, S3, S4, and Development) does not run a container you manage directly. To pick up the latest logiccloud Control version the device only needs to be restarted — there is nothing to reinstall.
- Open the device and go to the Actions section.
- Use Restart (or Stop then Start). On restart the vPLC comes back on the latest runtime version while keeping the same installed project — see Stop and restart a runtime.
After upgrading
Section titled “After upgrading”Once the device reports a version at or above the current minimum, the outdated-version warning clears automatically on its next status update. If the warning persists, confirm the container was recreated from a freshly pulled image (edge) or that the runtime actually restarted (vPLC).