Wago PFC Controllers: An Open Architecture Ideal for Remote Access
Wago stands out from traditional PLC manufacturers with its resolutely open approach: the PFC100 and PFC200 run on embedded Linux (Debian), which gives them unique IoT integration capabilities. Where other PLCs require third-party gateways for MQTT or Node-RED, the Wago PFC natively integrates these technologies.
This architecture makes the PFC200 both a control PLC and an IIoT gateway capable of:
- Running the control program (CODESYS V3 via e!COCKPIT)
- Publish process data via MQTT
- Host Node-RED flows for data processing
- Provide a web-based monitoring interface
- Expose an OPC UA server for SCADA systems
PFC100 vs. PFC200: Which One Should You Choose for Remote Access?
| Feature | PFC100 | PFC200 |
|---|---|---|
| Ethernet interfaces | 1 × 10/100 Mbit/s | 2 × independent 10/100 Mbit/s |
| Processor | 600 MHz ARM | 600 MHz dual-core ARM |
| RAM | 256 MB | 512 MB |
| OT/IT Segregation | No (1 port only) | Yes (2 independent ports) |
| Node-RED | Yes | Yes |
| MQTT client | Yes | Yes |
| OPC UA Server | Yes (FW 3.5+) | Yes (FW 3.5+) |
| Recommended for remote access | Simple sites | Sites with network segregation |
For deployments with high security requirements (OT network isolated from the VPN), the PFC200 is recommended: its second Ethernet port allows you to connect the OT network to eth0 and the 4G VPN router to eth1.
Protocols Available on Wago PFC for Remote Access
The PFC100/PFC200 are among the most versatile controllers in terms of protocols:
Field Protocols (Machine Side):
- Modbus RTU (RS-232/RS-485 via serial module)
- Modbus TCP (native Ethernet)
- PROFIBUS DP (via module)
- CANopen (via module)
- BACnet MS/TP and BACnet/IP (for building automation)
Cloud/Monitoring Protocols:
- MQTT (native client, TLS supported)
- OPC UA Server (FW 3.5+)
- REST API via Node-RED
- SNMP
- HTTP/HTTPS Web Services
Node-RED on Wago PFC: Remote Access and IoT Integration
Node-RED is the key differentiator of Wago PFCs for remote access. Here are a few practical use cases:
Remote Web Dashboard: Node-RED Dashboard creates a responsive web interface that can be accessed from a browser via VPN. The PLC’s variables are displayed in real time using gauges, graphs, and indicator lights.
Modbus-to-MQTT Gateway: A Node-RED flow reads the Modbus registers of field devices and publishes them to an MQTT broker. The data is accessible from the cloud without the need to deploy a separate gateway.
Alerts and Notifications: Node-RED nodes can send emails or text messages (via the Twilio/Vonage API) when a threshold is reached, without going through a centralized monitoring system.
Configuring Remote Access via e!COCKPIT
To configure remote access to a Wago PFC via e!COCKPIT:
- Check the IP address of the PFC (default 192.168.1.17, can be changed via WBM)
- Enable the VPN on your device and make sure you can ping the PFC’s IP address
- Launch e!COCKPIT and create a new project or open an existing one
- Scan the network (Device > Scan Network) or enter the IP address directly
- Connect: e!COCKPIT uses TCP port 1217 (CODESYS runtime)
- Online Mode: You can monitor variables, force values, and modify the program
Safety and Best Practices
- Change the default credentials: The PFC ships with the default credentials "admin/wago" — change them immediately
- Disable unnecessary services: FTP, Telnet, HTTP (enforce HTTPS) via the WBM
- Enable the firewall built into the PFC to restrict access based on source IP
- Encrypt MQTT: Use MQTT over TLS (port 8883) for cloud communications
- Update the firmware: Wago updates regularly address vulnerabilities