Resolving CM 1241 RS422/485 Modbus 16#8281 Negative Acknowledge

Resolving CM 1241 RS422/485 Modbus 16#8281 Negative Acknowledge Error

The Modbus RTU error code 16#8281 on an S7-1200 station equipped with a CM 1241 RS422/485 (6ES7241-1CH32-0XB0) almost always points to a configuration or wiring defect rather than a slave-side fault. The error word 16#8281 is generated by the MB_MASTER or MB_COMM_LOAD instance when the module cannot successfully complete a transaction and the slave returns a non-acknowledgement response or the master itself times out before any response is received.

This article consolidates the field-proven remediation steps for the most common 16#8281 scenarios: incorrect DB9 pinout, missing or wrong hardware identifier in the MB_COMM_LOAD block, wrong MODE value for half-duplex 2-wire RS485, mismatched data block array length, and the MB_COMM_LOAD placement (OB1 vs. startup OB). Every recommendation is anchored to the official SIMATIC S7-1200 manual collection.

1. Problem Definition: Decoding 16#8281

The Modbus communication blocks in TIA Portal use standardized status words in the DONE, BUSY, and ERROR outputs. The error word 16#8281 maps as follows when read from the STATUS output of MB_MASTER:

Because 16#8281 can be produced by either a physical layer defect or a project-side configuration error, the troubleshooting procedure starts at the connector and walks up through TIA Portal configuration.

2. Hardware Identification and Module Variants

The module discussed in the source is the CM 1241 RS422/485 with order number 6ES7241-1CH32-0XB0. This is the current production variant (firmware V2.x) supported by TIA Portal V15 and later. The article also covers the older legacy variant 6ES7241-1CH30-0XB0 where relevant. Key parameters from the S7-1200 manual collection:

For the official spec sheet, refer to the CM 1241 RS422/485 specification page in the SIMATIC S7-1200 manual collection.

3. Root Cause Analysis: Six Failure Pathways to 16#8281

Six independent root causes have been documented for the 16#8281 error on a CM 1241 RS422/485 in 2-wire RS485 mode. All six must be ruled out in sequence during commissioning.

1. Incorrect DB9 wiring polarity – pins 3 and 8 reversed on the master, or A/B labelling mismatch between vendor conventions and Siemens convention.
2. Missing hardware identifier – HW_ID input on MB_COMM_LOAD left at default zero or pointing at the wrong module instance.
3. Wrong MODE parameter – Mode 0 (full duplex RS422) used when the physical network is 2-wire RS485.
4. Wrong LINE_PER (line polarity) – must be set to 2 for RS485 2-wire to invert the transmit/receive path on pin 8.
5. Data block array under-sized – slave quantity exceeds the declared DATA_PTR length on MB_MASTER.
6. MB_COMM_LOAD execution context – block placed in a startup OB or called cyclically with a clock pulse instead of a single-shot on first scan.

4. CM 1241 DB9 Pinout and 2-Wire RS485 Wiring

The DB9 male connector on the CM 1241 module uses the Siemens-specific pinout shown below. Only two signal pins are required for 2-wire RS485, plus a 5 V reference for the bias network.

The recommended Siemens termination and bias network for the master end of the RS485 bus is illustrated in the official Siemens knowledge article 109736665. Components are wired between the DB9 pins as follows:

The Thevenin equivalent gives an idle-state bias of approximately 200 mV differential between pins 3 and 8, holding the bus in a stable MARK state and preventing noise-induced false-start bits. A 120 Ω termination resistor across pins 3 and 8 should be installed only at the two physical ends of the trunk – never on stub drops. If the CM 1241 is the only device or the master is the bus end, install the full Siemens network at the DB9. If the master is in the middle of the trunk, omit the 120 Ω termination and keep only the bias network, or omit the bias as well and let the bus ends terminate.

5. TIA Portal Device Configuration

Before any Modbus block can communicate, the CM 1241 module must be correctly added to the device configuration and its system clock tag must be enabled.

1. In the project tree, open Devices & Networks and drag the CM 1241 RS422/485 from the catalog onto the S7-1200 rack next to the CPU. Confirm the order number matches the installed module: 6ES7241-1CH32-0XB0.
2. Right-click the module, open Properties > System and clock memory. Tick Enable the use of system clock memory byte and set the system memory byte (default byte 1000) and clock memory byte (default byte 1001). This exposes the FirstScan edge bit required to call MB_COMM_LOAD exactly once.
3. Open Properties > Port configuration and select RS485 (2-wire). Half-duplex is implicit. Note the Hardware identifier shown in the properties – this is the value that must be entered in MB_COMM_LOAD.HW_ID. By convention the first CM 1241 receives HW identifier 271 (decimal), the second 272, and so on. The exact value can also be read from the system constants (PLC tags > Show all tags > System constants).
4. Note that the port parameters (baud rate, parity, stop bits) are not set here for Modbus RTU – they are set at runtime by the MB_COMM_LOAD block. The hardware port only needs the electrical mode set correctly (RS485, not RS232).

6. MB_COMM_LOAD Block Configuration

The MB_COMM_LOAD instruction (FB 1080 in the Modbus_Comm_Load library, supplied with every TIA Portal installation) initialises the port and must execute exactly once after each CPU restart or module re-plug.

Placement of MB_COMM_LOAD: Place the call in OB1 (Main), not in OB100 (Startup). Several field reports of 16#8281 have been traced to MB_COMM_LOAD being placed in a startup OB, where the module is not yet fully initialised by the system. The trigger REQ must be tied to the FirstScan system memory bit (%M1000.0 by default), not to a clock pulse or a button. A clock pulse re-initialises the port every cycle and prevents the first Modbus transaction from ever completing.

7. MB_MASTER Block Configuration

Once MB_COMM_LOAD has been successfully called, the MB_MASTER block (FB 1081) issues each Modbus request. The slave-side MB_SLAVE block (FB 1082) is required only if the S7-1200 is acting as a slave – it is not used in the master scenario described here.

The error STATUS 16#8281 from MB_MASTER indicates that the master did not receive an acknowledgement from the slave. The slave either did not decode the request (wiring/baud/address mismatch) or it is wired in a way that suppresses its transmit driver (terminator/bias issue).

8. Data Block Array Sizing Rule

One of the most often missed requirements: the DATA_PTR array must be at least as long as DATA_LEN. If the function code is 16 (write multiple holding registers) and DATA_LEN = 10, the target array must be declared ARRAY[0..9] OF WORD (10 elements). If the array is smaller, the Modbus master will issue the request but the slave firmware may reject the response with a framing error or simply not respond – either of which the master reports as 16#8281.

Rule of thumb:

• DATA_LEN = number of registers = ARRAY_HIGH - ARRAY_LOW + 1
• The array may be larger than required, but never smaller.
• The array must be a standard-access (non-optimised) data block. Optimised data blocks are not supported by the Modbus library.

9. Step-by-Step Commissioning Procedure

1. Power down the S7-1200 and verify the CM 1241 module is firmly seated on the rack. Record the order number from the module label.
2. Wire the DB9 connector per Section 4. Use the Siemens 390/220 Ω bias network at the master end. Confirm pin 3 = D+ and pin 8 = D- with a continuity tester.
3. Connect the slave A-to-A and B-to-B first. If the master returns 16#8281 within 5 seconds, swap A/B at the slave end only and retry.
4. Add the CM 1241 in TIA Portal device configuration. Verify the hardware identifier under Properties > System constants. Note the decimal value (typically 271).
5. Enable system clock memory byte in the CPU properties. Record the system memory byte number and bit for FirstScan.
6. Create a global data block for the Modbus holding register buffer. Declare, for example, mb_data : ARRAY[0..9] OF WORD;. Ensure Optimised block access is unchecked.
7. Insert MB_COMM_LOAD in OB1. Wire REQ to the FirstScan system memory bit, PORT to the CM 1241 HW identifier, MODE = 4, LINE_PER = 2, BAUD = 9600, PARITY = 2, RESP_TO = 1000.
8. Insert MB_MASTER in OB1. Wire REQ to a 100 ms clock memory bit, MB_ADDR to the slave address, MODE = 1 (read holding registers), DATA_ADDR = 0, DATA_LEN = 10, DATA_PTR to the global DB array.
9. Compile and download the project. Switch the CPU to RUN.
10. Monitor MB_COMM_LOAD.DONE in a watch table. It should pulse TRUE once on the first scan and stay FALSE thereafter. If DONE never goes TRUE or STATUS = 16#8181, the HW identifier is wrong.
11. Monitor MB_MASTER.STATUS. A value of 0000 while BUSY is FALSE indicates a healthy idle state. A persistent 16#8281 points to wiring or slave address.

10. Verification and Diagnostics

Once communication is established, validate the link with the following checks:

• Oscilloscope check: Probe between CM 1241 pin 3 and pin 8 with a differential probe. With no traffic you should see a positive bias of approximately 200 mV. During a transaction you should see a clean differential signal of at least ±1.5 V with rise times under 1 µs.
• Loopback test: Temporarily short pins 3 and 8 to pins 7 and 9 of the same DB9 to create an internal loopback. If MB_MASTER now reports DONE = TRUE and STATUS = 0, the CM 1241 and the TIA Portal configuration are sound; the fault lies in the physical wiring or the slave.
• Slave echo test: Use a Modbus master tool (such as Modbus Poll or the TIA Portal Modbus RTU library simulator) on a laptop to verify that the slave responds correctly to a known query. This isolates whether the slave itself is functional.
• Online diagnostics: In TIA Portal, open Online & Diagnostics > Diagnostic buffer on the CPU. Look for module-insert/remove events or communication-error entries that may indicate intermittent contact issues on the CM 1241 backplane connector.

11. Troubleshooting Matrix

12. Field-Proven Caveats

13. Frequently Asked Questions