Overview
This note walks through the common protocols and what to check when comms drop.
Modbus RTU/TCP Configuration
Modbus is the one you'll hit most often. For Modbus RTU over serial, the baud rate, parity, and stop bits all have to match on the panel and the PLC. For Modbus TCP, set the PLC IP address and port (502 by default):
- Modbus RTU: Match baud rate (9600/19200/38400/115200), 8 data bits, parity, 1 stop bit
- Modbus TCP: Set PLC IP address, port 502, unit ID if using gateway
- Address format: 0x (coils), 1x (discrete inputs), 3x (input registers), 4x (holding registers)
- Test with the built-in System Register communication monitor
Ethernet/IP for Allen-Bradley
For Allen-Bradley CompactLogix and ControlLogix, use the Ethernet/IP driver. The panel reads tag names directly, so there's no address mapping to do. Set the PLC IP address and keep the panel on the same subnet. If the tag database is large, import it instead of typing every tag by hand.
Communication Troubleshooting
When comms fail, work through it in order: the physical cable or network first, then the protocol parameters, then the PLC addresses, then firewall and security settings. EasyBuilder Pro's "System Parameter Settings → Communication" page shows live status and error counts right on the panel.
Typical applications
- New HMI installations
- PLC retrofit projects
- Multi-protocol gateway applications
- Communication troubleshooting
Related products
All Weintek cMT and eMT series. See them on the Weintek USA page or ask us for a quote.