Runtime status

Runtime Status answers two questions about the device you are connected to: what it is, and how it is running. It also holds the one action that needs a device rather than a project, changing the runtime version installed on it.

It lives under the Device branch of the project tree.

The Runtime Status screen for vPLC 01 on the SLM-RP4 Device. A header reading "Runtime Status" with the Device and vPLC names beneath it, and a grid of fields: Runtime version v4.2.2, Device Agent v1.7.1, Host SLM-RP4, Operating system Linux 6.8.0-64-generic, Kernel 6.8.0-64-generic, Architecture not reported, CPU cores 4, Memory 3.8 GB. Below the header, the Scan Cycle Statistics table for TASK0 with zero overruns, and the EtherCAT Bus Statistics table

If you have used the statistics before, this is where they went. The scan-cycle, EtherCAT and plugin tables used to sit at the bottom of the Edge Devices screen in the web editor, and at the bottom of the Device Configuration screen in the desktop editor. They were never configuration, and on the desktop you had to scroll past a pin-mapping table to reach them. They are unchanged; they simply have their own screen now.

When the screen appears

Everything here is read from a live device, so the leaf appears while you are connected to one. Opening it otherwise shows: "Connect to a runtime to see its status."

What the device tells you about itself

The header describes the machine your program is running on.

FieldWhat it is
Runtime versionThe OpenPLC runtime currently installed
BootloaderThe version of the bootloader on the device, when it has one
Device AgentShown instead of Bootloader on a vPLC, which has no bootloader: the version of the Device Agent on the machine the vPLC runs on
HostThe device's hostname
Operating systemFor example Debian GNU/Linux 12 (bookworm)
KernelThe kernel release, which is where you can see whether it is a real-time kernel
ArchitectureFor example aarch64
CPU coresWorth knowing when you are sizing tasks: the core count is the budget your scan tasks share
MemoryTotal system memory

On a vPLC, the header describes the Device the vPLC runs on, as reported by its Device Agent, not the container itself. The agent does not report the architecture, so that field stays empty.

If some of these are empty on a physical device, it is a native install, or an installation old enough to predate the bootloader. It is not a fault, and nothing is wrong with the device. You simply see fewer details about it.

The statistics

Below the header are the same tables as before, refreshed while the screen is open.

Scan Cycle Statistics, per task, in microseconds. Each cell shows a moving average with the minimum and maximum beneath it.

ColumnMeaning
Scan CountHow many scans the task has completed since it started
Scan TimeHow long the task's logic takes to execute
Cycle TimeThe interval between scan starts, which should track the task's configured period
LatencyHow late the scan started relative to when it was due
OverrunsScans that did not finish before the next was due. This is the number to watch. Anything other than zero means the task is not keeping up

EtherCAT Bus Statistics appear when the project has an EtherCAT segment, reporting master state, slave and cycle counts, bus timings and error counters.

Plugin statistics appear when the board provides them. On an SLM-RP4 board, for example, the SLM-RP4 Backplane panel reports its fault state, SPI clock, configured slots and bus timings. What you see here depends on the hardware: the vPLC in the screenshot above has no such panel.

Changing the runtime version

The Change runtime version button installs a different OpenPLC runtime on the device.

The button appears only on devices that can do it, that is, when a bootloader is present. A native install, a vPLC managed by a Device, or an installation old enough to predate the bootloader, has no way to swap the runtime, so the button is not shown rather than being offered and then failing.

Picking a version

The Change Runtime Version dialog. It explains that the device downloads the version you choose and restarts its runtime, and that installing an older version is supported. A Version dropdown is open, listing v4.2.2 (installed), v4.2.1, v4.2.0, v4.1.10, v4.1.9, v4.1.8, v4.1.7 and v4.1.6

The list is populated from the published runtime releases, newest first. The version already on the device is marked (installed) and cannot be chosen, since installing what is already there would do nothing.

Upgrading and downgrading are the same action. There is no separate direction and no lower limit on what you can install: pairing an older runtime with an older editor is a legitimate thing to want, and the bootloader stays reachable either way.

If the release list cannot be fetched, the dropdown is replaced by a field you can type a version into, so a device that is offline but holding an image you side-loaded is still installable.

While it installs

The same dialog mid-install. The Version field shows v4.2.1 with "Currently running v4.2.2" beneath it, a progress bar reads "Downloading v4.2.1 — Downloading" at 38%, and a note says the device continues on its own if you close the editor and that on a slow connection this can take several minutes. The buttons read Cancel and Installing…

The device does the work: it downloads the image, replaces the runtime and then waits to confirm the new one starts. The dialog follows along and reports the stage it has reached:

ShownWhat is happening
Downloading <version>Fetching the image. The download's own phase appears beside it, and a percentage where one is available
Replacing the runtimeSwapping the running runtime for the new one
Waiting for the new runtime to startConfirming the new version comes up healthy
Installed <version>Done
The update failedShown with the reason the device gave

Closing the editor does not stop it. The device continues on its own, and on a slow connection the whole thing can take several minutes. The dialog cannot be dismissed while an install is in flight, so you will not close it by accident partway through.

Expect the PLC to stop and restart as part of this. Plan it the way you would any other runtime restart on a live machine.

If the device is in recovery

When the runtime is not running, the screen shows a warning at the top of the header saying the device is in recovery, with the reason the device reported and the advice to install a different version to recover it.

This is what the version change is for as much as upgrading: a runtime that will not start can be replaced with one that does, from the same dialog, without physical access to the machine.