Hardware · WAGO

The terminals stay.
The engineering moves.

WAGO ships its controllers with Linux and a Docker interface. That already satisfies the requirement for logiccloud CONTROL: the controller becomes a virtual PLC without a single change to wiring, terminals or I/O modules.

On the Compact Controller 100 we address the inputs and outputs directly — CONTROL ships a connector of its own for it.

Request trial access — we set it up and email you.

Try CONTROL for freeWatch the tutorial

What changes — and what does not

The hardware stays. The software becomes replaceable.

  • Your WAGO periphery stays

    I/O modules of the 750 and 753 series, terminals, wiring and cabinet layout are untouched. What gets swapped is the runtime on the controller, not the plant.

  • The engineering moves to the browser

    IEC 61131-3 control logic, web HMI and connectivity come together in one project — no local installation, built reproducibly and under version control.

  • The application is not stuck on the device

    The same automation app later runs on a touch panel, on an edge computer or centrally in the cloud. When a device goes end-of-life, the software moves on.

The web HMI runs on the panel, on a tablet and on a phone — one interface instead of three.

The logiccloud CONTROL tutorial for the WAGO Compact Controller 100

Compact Controller 100

The CC100 — with a connector of its own.

The 751-9301 carries eight digital inputs, four digital outputs, two analogue inputs and two analogue outputs, two resistance inputs and an RS-485 interface on the device itself — without a single terminal module attached. For compact machines, pumping stations and building services that is often the entire control system.

logiccloud CONTROL ships a dedicated connector for this device. The on-board interfaces are addressed straight from the control program, the way you are used to from the WAGO runtime.

  • Real-time Linux with the RT-Preempt patch, Docker enabled through Web-Based Management
  • ARM Cortex-A7, two Ethernet interfaces, SD card slot
  • On-board I/Os addressed straight from the program
  • Modbus RTU over RS-485, Modbus TCP, MQTT and OPC UA over Ethernet
Video: installing CONTROL on the CC100

Other WAGO devices

From the DIN-rail controller to the panel.

WAGO ships these devices with Linux and Docker support, which meets the requirement for CONTROL. Which connector serves your I/O configuration is something we work out in the project.

  • PFC200 G2

    The workhorse in the cabinet: WAGO I/O modules of the 750 and 753 series attach directly, giving you the right terminal combination for any size of plant.

    • 750-8212 through 750-8217, plus the T, XTR and 4G variants
    • Real-time Linux with the RT-Preempt patch
    • Modbus TCP and RTU, CANopen, PROFIBUS DP slave depending on variant

  • Edge Controller

    Control and data processing in one device, for applications where something else has to run alongside the logic.

    • 752-8303: ARM Cortex-A9 quad core, 2 GB RAM, 4 GB flash
    • 2 × Ethernet, 2 × USB, USB-C, HDMI, CAN, RS-232/485
    • Real-time Linux, Docker out of the box

  • Edge Computer

    The x86 industrial PC for the DIN rail — for visualisation, data storage or several applications running at once.

    • 752-9400 with 4 GB RAM, 752-9401 with 8 GB RAM
    • Intel Atom quad core, 64 GB flash, expandable by SSD
    • Debian Linux with Docker pre-installed

  • Touch Panel 600

    Control system and operator interface on one device. The CONTROL web HMI runs in the panel’s browser — and on every tablet in the plant at the same time.

    • Control Panel range 762-43xx, Docker-ready
    • From 4.3 inches to 21.5 inches
    • Modbus TCP, CANopen, EtherNet/IP

Commissioning

Four steps to a running control system.

No installation medium, no local engineering tool, no licence file on your machine.

  1. 1ENABLESwitch Docker on in WBMIn the WAGO device’s Web-Based Management, once per device.
  2. 2INSTALLOne command on the deviceThe setup script fetches the runtime and sets it up. Around 36 MB.
  3. 3CONNECTActivate the deviceThe device registers with your logiccloud account and appears in the browser.
  4. 4DEPLOYDeploy the projectControl program, HMI and connectivity go onto the device together.
  1. DOCKER ENABLED
  2. RUNTIME INSTALLED
  3. DEVICE CONNECTED
  4. APP RUNNING

For many devices at once, logiccloud ORCHESTRATE handles the rollout — staged, with automatic rollback.

Common questions about WAGO and logiccloud

What happens to my existing CODESYS project?

You program logiccloud CONTROL to IEC 61131-3 — the same standard language, the same patterns of thought. Even so, moving a project across is not simply a file import: blocks, libraries and the I/O configuration are transferred and checked. What that means for your project is something we go through together in a working session.

Does the WAGO runtime keep running alongside?

CONTROL runs as a container beside the device’s operating system. Whether you keep the existing runtime alongside it or replace it is a decision per plant — for a pilot on one machine, running both side by side is the usual route.

And real time?

The WAGO controllers run on real-time Linux with the RT-Preempt patch, and the control system stays local on the device and therefore independent of the internet connection. How hard the cycle time has to be for your application belongs in the design — we work through that together before series use.

Does my model need a release?

Not to try it out: wherever Docker runs, the runtime runs. For series use we work out which connector serves your I/O configuration — for the CC100 we ship it, and for attached terminal modules on a PFC200 we look at your configuration.

Does this affect my warranty with WAGO?

The Docker interface is a documented function of the devices, intended by WAGO itself and switched on in Web-Based Management. For a binding answer on your specific device and firmware, WAGO is the right address.

How do I manage hundreds of WAGO devices in the field?

With logiccloud ORCHESTRATE: devices, versions and rollouts centrally, across vendor boundaries too. An installed base of WAGO controllers, ctrlX devices and gateways becomes one list instead of three tools.