Skip to main content

CODESYS

CODESYS logo

IEC 61131-3 PLC runtimes and the tools around them, on your own edge hardware.

Category: CODESYS

CODESYS turns an edge node into a programmable controller. You write the logic in the CODESYS Development System (ladder, structured text, function blocks), download it to a runtime on the node, and the runtime executes it. The App Store carries seven CODESYS charts, one per vendor product, so the card you deploy is the product you are licensing.

The seven charts​

ChartWhat it isArchitecturesVersion
CODESYS Control for Linux SLThe PLC runtime, with OPC UA and WebVisuamd64, arm644.22.0.0
CODESYS Control for Raspberry Pi SLThe 64-bit PLC runtime for Raspberry Pi boardsarm64 (Pi hardware only)4.22.0.0
CODESYS Virtual Control for Linux SLThe containerized PLC runtimeamd64, arm644.21.0.0
CODESYS Edge Gateway for LinuxThe gateway the Development System connects throughamd64, arm644.21.0.0
CODESYS Virtual Safe Control SLA SIL-rated safety soft PLCi3864.21.0.0
CODESYS Safe Time Provider for LinuxThe independent time base Safe Control needsamd644.21.0.0
CODESYS Automation ServerCODESYS Automation Server On-Prem, the whole stackamd641.38.0.0

What each one needs​

CODESYS Control for Linux SL​

  • The Development System connects on port 11740. The OPC UA server listens on 4840. WebVisu serves on 8080 once a downloaded application includes one, and then it opens in EmberCORE.
  • The runtime does not include a CODESYS Gateway. Deploy the Edge Gateway alongside it when the Development System needs one.
  • Its working directory (the boot application, retain data, certificates, and users) lives on a 5 GiB volume, so a restart keeps the application.
  • Without a license, the runtime restarts about every two hours.

CODESYS Control for Raspberry Pi SL​

  • Runs only on Raspberry Pi hardware. At boot it checks the board through the Pi's firmware and exits on anything else, so deploy it to a Pi node.
  • Listens on 11740 for the Development System and 4840 for OPC UA. It serves no web page until a downloaded project carries a WebVisu.
  • Runs privileged by default, which also exposes the Pi's GPIO, I2C, and SPI devices to your application. An unprivileged mode that hands the runtime only the devices you list is available as a chart option.

CODESYS Virtual Control for Linux SL​

  • A different product from Control for Linux SL, not a variant of it. Its OPC UA node IDs carry its own product name, so tags browsed from one product do not resolve against the other. Point your clients at the product you browsed.
  • Listens on 11740 and 4840 only. It has no web interface, so its card offers a shell instead of a page.

CODESYS Edge Gateway for Linux​

  • Listens on 1217/tcp for the Development System and 1743/udp for its block driver. It has no web interface; its card offers a shell.
  • Keeps its configuration and enrolled identity on a 2 GiB volume.

CODESYS Virtual Safe Control SL​

  • Pairs with a PLC runtime over shared memory, not the network. It must run on the same node as the runtime it pairs with, and it runs in the host's IPC namespace to reach it.
  • Its one network port is 60000/udp, where time-sync telegrams from the Safe Time Provider arrive.
  • The vendor ships Safe Control for i386 only.

CODESYS Safe Time Provider for Linux​

  • Sends time-sync telegrams to a Safe Control release on 60000/udp. When you install it, the App Store lists the Safe Control releases it can send to, and by default it targets the Safe Control on its own node.
  • The CODESYS manual treats a time provider on the same host as Safe Control as a commissioning and test setup. For production, point it at a Safe Control on a different node, so the safety PLC has a genuinely independent clock.

CODESYS Automation Server​

  • Installs the complete CODESYS Automation Server On-Prem stack: the Manager, its PostgreSQL and Vault, and the Automation Server services. It then creates the first cluster and tenant for you, and its card opens that tenant's web interface.
  • One per cluster. The vendor's software owns fixed namespaces, so a second install on the same cluster cannot work, and the App Store does not offer one.
  • amd64 only, because that is all CODESYS ships. The version it packages is the vendor's 1.38 beta release.
  • Licenses come from a CodeMeter license server, which the chart runs in the cluster unless you point it at your own.

Running on EmberNet​

  • Several per node. Every CODESYS chart except Automation Server can be deployed more than once to the same node, so you can run several runtimes on one machine.
  • Host networking when it is free. The first CODESYS install on a node gets the node's own network, so the Development System and your PLCs can reach it at the node's LAN address. If another CODESYS install on that node already holds one of its ports, the new one goes on the pod network instead, and the App Store tells you why when it installs.
  • Privileged. The PLC runtimes, the Edge Gateway, and the safety charts run privileged, because a runtime that drives fieldbus hardware needs the host's device nodes. These CODESYS charts are the only App Store apps that run privileged by default.
  • Licensing is with CODESYS. Runtime licenses are CODESYS licenses, and an unlicensed runtime runs in the vendor's demo mode.

Learn more​

EmberNet packages and deploys these applications; they are developed by CODESYS Group. Product names and logos are trademarks of their respective owners.