Skip to main content

HotLoop for CODESYS

HotLoop logo

The screens and alarms for a CODESYS PLC, running beside the runtime.

Category: HotLoop

Current release: 0.3.5, which installs HotLoop 4.20.2 and the provisioner. See the release notes.

HotLoop for CODESYS installs HotLoop Edge and a small provisioner on the same node as a CODESYS runtime. It reads the PLC's variables through the runtime's own OPC UA server, shows them on dashboards that work on a panel PC, a phone, or a wall, raises alarms on them, and keeps their history. Nothing is installed in the CODESYS runtime, and nothing is written to the PLC.

What it needs​

  • A CODESYS runtime on the same node that publishes its OPC UA server. The provisioner finds the runtime on its own node and connects to it.
  • A Symbol Configuration in the PLC program with OPC UA support on, listing the variables to show. This is the only change the PLC project needs.
  • A profile. One JSON file naming the device, the variables to keep, the alarms, and one dashboard. It is stored securely for your organization, and the App Store writes it when the app is installed.

Installing it from the App Store​

  1. Choose HotLoop for CODESYS in the App Store and pick the node the runtime is on. The app is pinned to that node, so the dashboard and the runtime stay together.
  2. The App Store writes the profile and ties the app to your organization. Sign-in uses the same EmberCORE sign-in as the other HotLoop apps.
  3. HotLoop starts on SQLite on the node's local storage, with no separate database. The provisioner waits for HotLoop and the runtime, then sets up the device, variables, alarms, and dashboard, and checks again every five minutes.

This app is marked for staff in the App Store, so EmberNet staff install it onto your tenant. Nothing needs doing on your side afterward.

What it won't do​

  • It won't write to your PLC. Every tag it sets up is read-only, and the profile cannot mark one writable.
  • It won't change what a person edited. The dashboard and alarms are replaced only when a newer profile revision is shipped on purpose.

Running on EmberNet​

  • One instance per node.
  • A node that loses its link to the platform keeps it running. That has not been tested on a real node yet.
  • The OPC UA server, the embedded broker, edge publishing, and backups are off.
  • If the runtime restarts, every tag reads bad with the reason and recovers on its own.

What has been proven​

It has been run against a CODESYS Control for Linux SL 4.22.0.0 runtime in a container, on a lab cluster. It has not been run from the real App Store page, on a physical controller.

Licensing​

HotLoop for CODESYS installs HotLoop Edge and a provisioner, and it is under the EmberNet Source License 1.0, like every HotLoop product. You can copy, modify, and redistribute it, and any non-production use is allowed. Production use is allowed three ways: at home or in a lab, by schools, nonprofits, and government bodies for their own mission, and anything run through EmberNet, business use included, where signing up is free. A systems integrator can run it under its own EmberNet account for a customer and charge for its services, never for the software. Each version becomes available under AGPL-3.0-or-later four years after it's first made public. See the license and Using HotLoop in a business. There's no license key.

Learn more​

EmberNet packages and deploys this application; HotLoop for CODESYS is developed by HotLoop. CODESYS and other product names and logos are trademarks of their respective owners.