WAGO
DIN-rail automation controllers and spring-cage terminals — the standard KNX/Modbus gateway platform for European panel builders.
WAGO Kontakttechnik GmbH & Co. KG (Minden, Germany — founded 1951) is the inventor of the spring-cage terminal block and a leading manufacturer of DIN-rail automation controllers, field-bus I/O systems and panel wiring components. The WAGO 750 series modular I/O system — with the PFC100 (750-893) and PFC200 (750-8100) Linux-based programmable controllers at its core — has become the de-facto KNX/Modbus gateway platform for European panel builders. The PFC100 runs CODESYS 3.5 (IEC 61131-3) and carries an integrated KNX TP bus coupler, making it possible to implement complex KNX-to-Modbus bridging, demand response logic and energy management without any additional gateway hardware. WAGO TOPJOB S and JUMPFLEX push-in terminals are specified across the full range of panel types — from residential KNX panels to industrial MCC switchgear — for their tool-free, time-saving spring-cage wiring technology.
Role in our panels
How we use WAGO
The WAGO 750-893 PFC100 controller (36mm DIN-rail footprint, 24V DC supply) integrates: RJ45 Ethernet port (Modbus TCP master/slave, web server), integrated KNX TP bus coupler (physical address configurable in e!COCKPIT IDE), RS-485 via the 750-653 expansion module (Modbus RTU, 300-38400 baud, 2-wire). The CODESYS 3.5 runtime runs on embedded Linux — program tasks execute with deterministic cycle times (10ms typical). The WAGO KNX library (installed in e!COCKPIT) exposes each KNX group address as a CODESYS variable typed with DPT: write to the variable to send a KNX telegram, read it to receive incoming telegrams. Modbus TCP polling is implemented as a CODESYS function block (WAGO Modbus TCP library): configure IP address, slave ID, register start, register count, cycle the FB.Execute input — read results land in an array. For Modbus RTU via 750-653: same approach but using the SerialMaster FB with port parameters (baud rate, parity, stop bits) matching the energy meter configuration. WAGO PFC200 (750-8100) adds a second Ethernet port, 512MB RAM and a WLAN adapter slot — used when simultaneous Modbus TCP, KNX and BACnet gateway functions are required on a single controller.
KNX panel wiring for WAGO PFC100/PFC200: 24V DC from KNX panel PSU (Schneider ELUT or ABB SU/S) to WAGO 750-893 power terminals on DIN-rail. KNX TP bus: standard KNX green/yellow 2-core cable to KNX TP terminals on the 750-893 DIN-rail body — no additional bus coupler module needed. Modbus RTU RS-485: 750-653 module latches onto the 750-893 via the WAGO expansion connector (no tooling) — RS-485 A/B/GND terminals wire to the Modbus RTU daisy chain bus of energy meters. RJ45 Ethernet: patch cable to panel-mounted RJ45 keystone jack (for structured cabling) or direct to building LAN switch. TOPJOB S QUATTRO terminals (2270/2273 series) distribute 24V DC power and 230V AC circuits to KNX actuators throughout the panel — colour coding: grey body for AC/DC power, blue for neutral, green/yellow for PE. KNX TP cable (0.8mm solid core): spring-cage accepts solid conductors without tools. For 2.5mm² stranded power cables: crimp ferrules for secure spring contact.
Used in these project types
WAGO products
Key components we install
WAGO PFC100 Controller
Linux-based programmable controller with integrated KNX TP bus coupler, RJ45 Ethernet (Modbus TCP master/slave, web server), 256MB RAM, 36mm DIN-rail body. CODESYS 3.5 IEC 61131-3 programming via WAGO e!COCKPIT IDE (Windows). KNX library: each group address mapped to a CODESYS variable with DPT type. Modbus TCP master: polls up to 32 slave devices per task cycle. Expandable with 750-series I/O modules (DI, DO, AI, AO, RS-485). Typical KNX/Modbus gateway project: 750-893 + 750-653 RS-485 module reading Modbus RTU energy meters, publishing kWh and power values to KNX group addresses for EcoStruxure or Gira X1 visualisation. 24V DC supply, UL 508 and CE marked, -20°C to +55°C operating range.
WAGO RS-485 Serial Module
DIN-rail expansion module for 750-893/8100 PFC controllers — adds RS-485 Modbus RTU master capability. Supports baud rates 300 to 38400 (9600 default for most energy meters), 2-wire RS-485, configurable parity and stop bits. Up to 247 Modbus slave devices on one RS-485 bus (limited by cable length and line load — typically 32 unit loads per segment without repeater). In CODESYS: SerialMaster function block, configure port parameters, poll slave registers on each task cycle. Used with Carlo Gavazzi EM340 energy meters: 9600 baud, 8N1, 2-wire RS-485, slave addresses 1-8 per bus. Also compatible with Siemens PAC energy meters, Finder 7M series and all standard Modbus RTU RS-485 devices. Single DIN-rail slot width (12mm), 24V DC from 750-series bus.
WAGO PFC200 Controller
Enhanced CODESYS controller with dual RJ45 Ethernet ports (independent network segments — isolate Modbus TCP network from building LAN), 512MB RAM (larger CODESYS projects, more gateway variables), WLAN adapter option (750-652 WLAN module). Integrated KNX TP bus coupler identical to PFC100. Runs Modbus TCP, KNX and BACnet IP simultaneously as independent CODESYS tasks — each task has independent cycle time and priority. Typical use: Modbus TCP master on port 1 (energy meters, VRF controllers, EV chargers), BACnet IP on port 2 (BMS integration), KNX TP on integrated bus coupler (room controllers, actuators). Used in hotel energy management hubs, commercial building gateway panels, and Modbus/KNX/BACnet aggregation for EMS platforms.
WAGO TOPJOB S Rail-Mount Terminal
Standard TOPJOB S DIN-rail terminal block, 2.5mm² cross-section, 17.5A rated current, 800V rated voltage. Push-in spring cage: solid conductor and ferrule-terminated stranded conductor inserted tool-free. Accepts solid wire 0.2-4mm² and stranded wire with ferrule 0.14-2.5mm² (standard, no slim ferrule needed). JUMPFLEX actuator (orange lever) available for fine-stranded without ferrule. Colour coded: grey body for power, blue for neutral, green/yellow for PE. Pitch-compatible with Phoenix Contact PT and Weidmuller WDU series for mixed-manufacturer panels. Used throughout KNX panel power distribution wiring — faster than screw terminals in panel build, no re-tightening needed after commissioning, vibration-resistant spring contact.
WAGO TOPJOB S 8-Wire Terminal
8-conductor distribution terminal block on a single DIN-rail section — equivalent to 8 individual 2270-201 terminals in less than half the DIN-rail space. 2.5mm² maximum cross-section per connection, 17.5A, 800V. All 8 conductors internally bridged — ideal for distributing 24V DC supply to multiple KNX devices from a single PSU output, or for distributing neutral (N) conductor to multiple circuit MCBs without a separate bus bar. Push-in spring cage on all 8 positions, tool-free for solid conductors. Reduces panel wiring time significantly where one supply feeds multiple devices. Common in KNX panel designs: one 2273-208 for 24V positive rail, one for 0V/GND, eliminates point-to-point wiring from PSU to each device.
WAGO FAQ
How does WAGO 750-893 connect to KNX TP?
The 750-893 has an integrated KNX TP bus coupler on the main board — no additional module is required. In CODESYS e!COCKPIT: add a KNX device to the project, configure the physical address (e.g. 1.2.100), then add group addresses as I/O variables with DPT mapping. The WAGO KNX library exposes each group address as a typed CODESYS variable — write to the variable to send a KNX telegram, read it to receive incoming telegrams from the KNX bus. KNX TP bus connection: standard KNX TP green/yellow 2-core cable to the KNX TP terminals on the 750-893 DIN-rail body. The bus coupler draws its power from the KNX TP bus — the 750-893 24V DC supply powers only the controller and I/O expansion. Ensure the KNX power supply (e.g. MDT STC-0640.01 or Schneider MTN684064) has sufficient current budget — each bus coupler typically draws 10-15mA from the KNX TP line.
Can WAGO 750-893 run Modbus TCP and KNX simultaneously?
Yes — the 750-893 CODESYS program runs multiple independent tasks simultaneously: a Modbus TCP master task (polling energy meters every 10 seconds), a KNX publish task (writing to group addresses every 60 seconds or on value change above a threshold), and a local logic task (demand response alerts, peak shaving logic). The Linux OS and CODESYS runtime handle task scheduling and multitasking. Typical performance: 8 Modbus TCP meters polled in under 5 seconds per cycle, KNX telegram rate under 1 telegram per second (well within KNX bus capacity of approximately 50 telegrams per second). Task priorities are configurable in e!COCKPIT — set Modbus polling at medium priority, KNX publish at low priority, local protection logic at high priority. Watchdog timer in CODESYS restarts the runtime automatically if a task exceeds its configured timeout.
Are WAGO TOPJOB S terminals compatible with standard DIN-rail busbar systems?
Yes — TOPJOB S 2270 and 2273 series terminals are pitch-compatible with Phoenix Contact PT and Weidmuller WDU DIN-rail terminal systems, allowing mixed-manufacturer terminal strips in the same panel. Standard colour coding applies: grey body for AC/DC power circuits, blue for neutral conductor, green/yellow for protective earth. JUMPFLEX actuators (orange push-in tool) are available for fine-stranded cable without ferrules. For KNX TP cable (0.8mm solid core): the standard push-in spring cage accepts solid conductors without any tool — insert directly. For 2.5mm² stranded power cables: use insulated wire end ferrules (DIN 46228 end sleeve) for secure spring contact and to prevent strand splaying inside the terminal. WAGO also offers cross-connection bridges and end brackets for the 2270/2273 series, compatible with the DIN EN 60947-7-1 system.
Need a panel with WAGO components?
We select, procure, assemble and certify. Free initial consultation.
Request consultation →