How to Fix Modbus RTU Timeout Error 16#80C8 on Siemens S7-1200

If you connect a third-party Modbus RTU device to a Siemens S7-1200 PLC (using the CM 1241 or CB 1241 modules), the MB_MASTER instruction block frequently encounters a communication fault where the ERROR bit goes high, and the STATUS output remains locked at 16#80C8.

Block: MB_MASTER (FB 43)
REQ:   TRUE
DONE:  FALSE
ERROR: TRUE
STATUS: 16#80C8

Description: Timeout during Modbus RTU communication. The slave device did not respond within the defined RESP_TO time.

In Siemens TIA Portal, 16#80C8 strictly indicates a “Timeout”. The PLC was able to send out a Modbus request frame but did not receive any valid response from the slave device. Verify the following engineering checklist before replacing the communication module or assuming hardware failure. Most of those timeout errors (roughly 90 percent) are caused by physical layer inversions or logical polling collisions.

Step 1: The RS485 Polarity Trap (A/B Wires)

This is the leading cause of initial communication failure when bridging Siemens hardware with third-party inverters, power meters, or VFDs.

The Fix: If 16#80C8 occurs consistently and the slave’s RX/TX indicators show no activity, swap the A and B wires on the slave side (Siemens Pin 3 to positive, Pin 8 to negative). Reversing the polarity will not cause electrical damage; it merely prevents signal interpretation.

Step 2: Execution Order (MB_COMM_LOAD)

In the PLC cycle the CM 1241 serial port must be fully initialized before any polling requests can be made.

• Ensure the MB_COMM_LOAD block executes only once (typically triggered by the FirstScan system memory bit during startup).
• Do not trigger the REQ pin of the MB_MASTER block until MB_COMM_LOAD.DONE returns TRUE. Polling an uninitialized port will immediately yield an 80C8 timeout.

Step 3: Polling Collisions & Bus Decoupling

Modbus RTU is inherently a half-duplex serial protocol. Aggressively polling slave devices without allowing sufficient processing and response time will result in bus collisions.

• Check your RESP_TO parameter: In the MB_COMM_LOAD background Data Block (DB), the Response Timeout defaults to 1000 ms. When polling older legacy devices that are slower it is recommended to increase this value to 2000ms.
• Implement a State Machine: Never utilize a continuous clock pulse (e.g., a 1Hz Clock Memory bit) to trigger MB_MASTER. Instead, utilize the DONE or ERROR outputs of the block to trigger a short delay timer (e.g., 50ms), and use that timer’s completion to trigger the subsequent REQ.

No matter how you optimize the ladder logic, if you ask the S7-1200 to poll several devices over a large daisy-chain network, the half-duplex limitations of RS485 will cause collisions on the bus and random 16#80C8 timeouts, regardless of ladder logic optimization. In standard industrial architectures, engineers resolve this bottleneck by offloading the polling cycle to a transparent Modbus TCP to RTU gateway equipped with local caching. This effectively decouples the PLC from the physical serial layer, allowing it to read buffered data immediately over Ethernet without serial timeout errors.