Skip to main content

CODESYS Control for Raspberry Pi SL

CODESYS logo

The 64-bit IEC 61131-3 PLC runtime for Raspberry Pi boards.

Category: CODESYS

This is the CODESYS runtime built for the Raspberry Pi. You write the logic in the CODESYS Development System, download it to the runtime on the Pi, and the runtime executes it. EmberNet packages version 4.22.0.0 as its own chart.

Home users only

This runtime is for home users. For any commercial or customer arm64 node, Raspberry Pi class boards included, use CODESYS Control for Linux ARM64 SL, the arm64 build of CODESYS Control for Linux SL. The Raspberry Pi SL card stays visible in the App Store to every tenant, but it is not what we recommend for commercial work.

What it does​

  • Runs IEC 61131-3 logic (ladder, structured text, function blocks) on a Pi.
  • Listens on 11740 for the Development System and 4840 for OPC UA.
  • Serves no web page until a downloaded project carries a WebVisu.
  • Exposes the Pi's GPIO, I2C, and SPI devices to your application when it runs privileged.

When to use it​

Use it on a Raspberry Pi in a home setup, where you want a CODESYS runtime on the board itself. It is not the same product as Control for Linux ARM64 SL with a different name. At boot it asks the Pi's firmware for the board revision, and on any other hardware it exits. If the node is not a Raspberry Pi, or the work is commercial, deploy CODESYS Control for Linux SL instead.

Running on EmberNet​

  • Raspberry Pi hardware only. Deploy it to a Pi node. The image is built for arm64 and the chart always schedules it on arm64 nodes.
  • One runtime owns its state. The chart runs a single replica.
  • Your application survives restarts. The chart puts a 2 Gi volume under the runtime's working directory (the boot application, retain data, certificates, users, and log), so a pod restart keeps the downloaded application.
  • Privileged by default. The runtime has to open the Pi's firmware device to identify the board, and that needs a privileged container. An unprivileged mode, off by default, hands the runtime only the devices you list.
  • Host network is off by default. Turn it on for a single runtime on the node when the Development System, running outside the cluster, has to scan for the Pi or reach it at the node's LAN address.
  • Connect through the Edge Gateway. Deploy the Edge Gateway on the same node so the Development System can reach the runtime. See Connect the CODESYS IDE.
  • Sized small by default. It requests 250m of CPU and 256 MiB of memory.

Learn more​

EmberNet packages and deploys this application; it is developed by CODESYS Group. Product names and logos are trademarks of their respective owners.