Managing twenty controllers in four buildings, from four vendors means keeping track of their status and applications. The CODESYS Automation Server registers every device, watches their health from one browser dashboard, and pushes application updates over the air, including queued updates for devices that are currently offline. Deploy a new app to the fleet below to follow the rollout.
Four CODESYS targets from four vendors are registered to one Automation Server. Each reports online status, its running app version and health information. Press Deploy v1.3.0 to send the new boot application to every device. Online devices show their update progress, while the offline Eaton is queued to update the moment it reconnects.
| Device | Status | App version | Deploy | Health |
|---|
The Automation Server keeps the boot application and source for every device. You can update the fleet in one action instead of carrying twenty USB sticks between controllers. For an offline device, the update stays queued until it reconnects, then gets applied. The common CODESYS runtime lets you manage a WAGO, a Raspberry Pi, a Festo and an Eaton side by side from the same dashboard.
☁️ Central registry. Each controller enrols once and appears in a shared browser console, so you can manage it without separate VPN connections to each panel. Group devices by line, site or customer.
📦 OTA application deployment. Send a tested boot application to one device or a group, either immediately or on a schedule. Version history and rollback are available, and how long a rollout takes depends on the number of devices and their network connections.
💚 Monitoring & alerts. Check online/offline state, runtime metrics and trends. Automatic notifications warn you about potential problems with a device, giving you an operations view alongside your engineering tools.
🔐 Connection security. Devices connect outbound to the server over TLS, with no inbound ports to open. User roles and audit logging control and record access. The server is an optional add-on to the runtime already on your devices.
The Development System builds and tests the application; the Automation Server operates the devices after deployment. You manage the fleet from one place instead of logging into each PLC separately, much as DevOps tools bring individual servers under shared management.
You deploy a new app version to the fleet, but one controller is powered down for maintenance. What does the Automation Server do with it?