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 eight CODESYS apps, one per vendor product, so the card you deploy is the product you are licensing.

The eight apps​

AppWhat 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.22.0.0
CODESYS Edge Gateway for LinuxThe gateway the Development System connects throughamd64, arm644.22.0.0
CODESYS Virtual Safe Control SLA SIL-rated safety soft PLCi3864.22.0.0
CODESYS Safe Time Provider for LinuxThe independent time base Safe Control needsamd644.22.0.0
CODESYS 4The browser based development environment, served from a podamd64, arm641.0.0.0
CODESYS Automation ServerCODESYS Automation Server On-Prem, the whole stackamd641.38.0.0

What each one needs​

CODESYS Control for Linux SL​

  • Includes the OPC UA server, and WebVisu once a downloaded application includes one, which then opens in EmberCORE.
  • The runtime does not include a CODESYS Gateway. Deploy the Edge Gateway on the same node so the Development System can reach it. See Connect the CODESYS IDE.
  • Your application, retain data, certificates, and users are kept across restarts.
  • Without a license, the runtime restarts about every two hours.

CODESYS Control for Raspberry Pi SL​

  • Runs only on Raspberry Pi hardware. It checks the board at boot and exits on anything else, so deploy it to a Pi node.
  • Includes the OPC UA server. It serves no web page until a downloaded project carries a WebVisu.
  • Runs with access to the Pi's GPIO, I2C, and SPI devices by default, so your application can use them. A restricted mode that hands the runtime only the devices you list is available as an 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.
  • It has no web interface, so its card offers a shell instead of a page.

CODESYS Edge Gateway for Linux​

  • It has no web interface; its card offers a shell.
  • It is the one address the Development System connects to, over Flux or the overlay network. It reaches the runtimes on its own node itself, so run one next to every runtime you program. See Connect the CODESYS IDE.
  • Keeps its configuration and enrolled identity across restarts.

CODESYS Virtual Safe Control SL​

  • Pairs with a PLC runtime on the same node, so it must run on the node of the runtime it pairs with.
  • Receives time-sync telegrams from the Safe Time Provider.
  • The vendor ships Safe Control for i386 only.

CODESYS Safe Time Provider for Linux​

  • Sends time-sync telegrams to a Safe Control release. 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 4​

  • The IEC 61131-3 development environment itself, so engineers write and download logic from a browser tab instead of installing the Development System on a PC.
  • Open it from its card in Running Apps. EmberCORE signs engineers in for you, and the password never reaches your browser. Anyone below Engineer gets the app's own login page.
  • Projects and settings are kept across restarts.
  • It has no gateway of its own. To reach a runtime, add the Edge Gateway as a gateway in the project's Communication Settings, then scan for the runtime on the same node. Its card lists the Edge Gateways it can use, or says there is none on its node. See Connect the CODESYS IDE.

CODESYS Automation Server​

  • Installs the complete CODESYS Automation Server On-Prem stack, then creates the first cluster and tenant for you, and its card opens that tenant's web interface.
  • One per cluster. 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 EmberNet runs for you unless you point it at your own.

Running on EmberNet​

  • Several per node. Every CODESYS app except Automation Server can be deployed more than once to the same node, so you can run several runtimes on one machine.
  • On your plant network when it can be. The first CODESYS install on a node is reachable at the node's own address on your plant network, so the Development System and your PLCs can reach it. If a later install on that node would collide, it is placed on the internal network instead, and the App Store tells you why when it installs.
  • Hardware access. The PLC runtimes, the Edge Gateway, and the safety apps get the access to the node's hardware that a runtime driving fieldbus devices needs. They are the only App Store apps that run this way 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.