This post explains how to update EtherCAT slave firmware in a CODESYS system.
Firmware
EtherCAT stations split into masters (controllers) and slaves (drives, and so on). Update methods differ.
| Kind | How | Who runs it |
|---|---|---|
Master application (.app) |
IDE download, or replace the boot application | CODESYS runtime |
| Slave firmware | FoE / vendor tools over EtherCAT | Master + slave |
FoE upgrade states
Idle → FoE connect → Transfer firmware → Checksum verify → Reboot / apply.
Three-party sequence
Master/IDE, controller, and slave coordinate the transfer and restart.
Controller-side state machine
IDLE → PREPARE → TRANSFER → VALIDATE → APPLY.
Notes
- Match firmware to the exact slave model
- Keep the bus stable during transfer
- Plan for reboot: axes will drop until the slave returns




Top comments (0)