Where HotLoop for CODESYS stands
This page is what is published, and how far HotLoop for CODESYS has been run.
What is out
Section titled “What is out”- The chart.
hotloop-codesys0.3.5 is in the index athttps://hotloop.io/hotloop-codesys/, published on 2026-11-16, with every earlier version still there beside it. It wraps HotLoop 4.20.2. Install 0.3.5: the release notes say what each chart changed. - The provisioner image.
ghcr.io/hotloop-io/hotloop-provisionat 0.3.1 pulls with no login, and the chart runs it. - The App Store listing. The EmberCORE Store lists it for EmberNet staff, who put it on a tenant.
How far it has been run
Section titled “How far it has been run”The chart on a k3s node with Store-shaped values, a real CODESYS Control for Linux SL 4.22.0.0 runtime on the same node running a demo program, and a HotLoop Edge image.
- The device, its tags (none writable), its alarm, and its screen appeared with no hand step.
- Every value read good and moved.
- The pods came back after a pod delete.
- The install read bad with the reason “the PLC’s runtime is not answering” through a runtime restart, and came back by itself about 88 seconds after.
- A signed sign-in from the dashboard signed a person in as an operator or an admin, and a wrong app, a wrong tenant, an expired one, a wrong issuer, and a tampered one were each refused.
- The published chart renders from the live index with Helm.
The connector under it, HotLoop core’s CODESYS driver, is verified live against a CODESYS Control for Linux SL 4.22.0.0 runtime, for reads and writes, and on bare metal (2026-11-17). Writes are there in the connector, and this product never turns them on.
All of it has also been run on bare metal (2026-11-17).
What a profile can’t do yet
Section titled “What a profile can’t do yet”A profile makes one screen. It makes one device from device, or several of any protocol from devices, and there is no way to mark a variable writable from it, on purpose.