Resolving Modbus_Comm_Load 16#7000 and 0x8281 on S7-1200 CM1241

1. Problem Overview

The Modbus_Comm_Load instruction on a Siemens SIMATIC S7-1200 CPU paired with a CM 1241 RS485 communications module is meant to parameterize the serial port for Modbus RTU master or slave service. When commissioned through TIA Portal (V15 and later, including V16, V17, V18, V19, V20), two failure modes recur in field deployments against devices such as the Schneider Electric PM2230 power meter:

1. The instruction reports Status = 16#7000, Done = FALSE, Error = FALSE, and no characters are ever placed on the wire — no TX/RX LED activity on the CM 1241.
2. The companion Modbus_Master (or Modbus_Slave) instruction reports a status of 16#8281 with the Error output TRUE.

Both symptoms are caused by incomplete port configuration, library version mismatch, or wiring errors that prevent the underlying UART from being armed. This article consolidates the field-proven resolution steps, parameter assignments, and the diagnostic procedure needed to clear the fault and bring the CM 1241 link to PM2230 (or any Modbus RTU slave) on-line.

2. Hardware Reference: CM 1241 RS485 Modules

Siemens currently produces the following first-party RS485 point-to-point modules usable with the S7-1200 family:

Confirm the MLFB on the side label before troubleshooting. The firmware version of the S7-1200 CPU (V1.x, V2.x, V3.x, V4.x, V4.2, V4.3, V4.4, V4.5, V4.6, V4.7) determines which Modbus_Comm_Load instruction variant can be inserted. As a rule of thumb:

• Firmware V1.x–V3.x: legacy Modbus library (instruction version 2.x).
• Firmware V4.0–V4.4: MODBUS (RTU) library distributed with TIA Portal — instruction version 3.0/3.1.
• Firmware V4.5+: MODBUS (RTU) V20 library — instruction version 4.x with extended diagnostics.

3. Decoding Status 16#7000

16#7000 belongs to the IEC 61131-3 "no operation / no error" family. For the S7-1200 Modbus RTU instruction set it means:

The instruction latches Done or Error for exactly one CPU scan, then both reset. If you sample the outputs in OB1 without using a positive-edge contact on Done / Error, you will see 16#7000 forever — even after a successful run. Always route Done to a flag (MB_x) and read that flag in your HMI or next cycle.

4. Root Cause Matrix for Status 16#7000 With No LED Activity

5. The MODE Parameter — Half-Duplex 2-Wire Assignment

The MODE input selects the physical layer profile of the CM 1241's UART driver. The valid values are:

If MODE is left at 0, the CM 1241 expects four-wire operation and will never assert the transmit driver in the direction needed for a 2-wire bus. The TX LED will remain dark and the bus will be silent. The fault is silent in the sense that no error code is raised — 16#7000 simply persists because the instruction is doing exactly what it was told to do: nothing useful.

6. REQ Trigger Wiring and OB Placement

The instruction needs a single rising edge on REQ to start the configuration handshake with the module. Standard practice is to drive it from the CPU's first-scan bit, exposed in the System and clock memory byte:

Notes:

• FirstScan is bit 0 of the system memory byte configured in CPU Properties → System and Clock Memory. It is TRUE for exactly one scan after restart.
• OB100 (Startup) can be used only if the watchdog is configured to accommodate the call. The recommended practice is to call Modbus_Comm_Load from OB1 to avoid Startup OB timeouts when the CPU has a large project.
• RESP_TO is the response timeout in milliseconds. The default of 1000 ms is safe for PM2230; lower it only after validation.

7. Modbus_Master Error 0x8281 — Decoding

Once the port is armed (TX/RX LED flashes when traffic hits the bus), the next fault encountered is typically Modbus_Master status 16#8281. The high nibble (8) marks an error, and the low word decodes to a sub-cause. From the Siemens error reference the most common values are:

0x8281 is almost always "I sent a request, nobody answered within RESP_TO." The slave either cannot see the request, cannot transmit a reply, or is configured to a different station address.

8. Wiring, Biasing, and Termination for the CM 1241 ↔ PM2230 Link

The CM 1241 RS485 pinout is:

The PM2230 (Schneider Electric) is a 2-wire half-duplex device. Connect:

• CM1241 pin 3 (D+/B) → PM2230 D+ terminal
• CM1241 pin 8 (D−/A) → PM2230 D− terminal
• CM1241 pin 7 (GND) → PM2230 COM (signal ground)

For cable runs shorter than 10 m the on-module biasing is usually sufficient. For longer runs, add failsafe biasing at the master end: a 620 Ω pull-up from D+/B to +5 V and a 620 Ω pull-down from D−/A to GND, with a 120 Ω termination resistor across the bus at the far end. Do not place a second 120 Ω termination at the CM 1241 end — that produces a T-network that attenuates signals above 50 m.

9. Library Choice: MODBUS (RTU) vs Legacy Modbus

Two distinct instruction libraries ship with TIA Portal:

Mixing instructions from the two libraries in the same project is allowed but each port must use the matching pair — Modbus_Comm_Load + Modbus_Master on one port, MB_COMM_LOAD + MB_MASTER on another. If the project was migrated from a V13 SP1 source, you may inherit the legacy MB_COMM_LOAD V2.1 blocks. Open the block properties to confirm the version, then either:

1. Replace the legacy pair with the new Modbus_Comm_Load V3.1+ instructions (recommended for V4.x CPU), or
2. If the CPU firmware is older than V4.0, keep the legacy V2.1 instructions but verify they are sourced from the right library.

10. Step-by-Step Resolution Procedure

1. Verify the CPU firmware version. Open Online → Accessible Devices, select the S7-1200, and read the order number and firmware. Note both.
2. Open the device configuration of the S7-1200 station and confirm the CM 1241 is online (green check). Note the Hardware identifier under Properties → System constants.
3. Insert a single Modbus_Comm_Load instance in OB1. Pin PORT to the CM 1241's hardware identifier (typically "CM_1241_RS485_1").
4. Open the instance DB and set the start value of MODE to 4. Set BAUD, PARITY, FLOW_CONTROL matching the PM2230 configuration (default 19200, 8E1, no flow control → BAUD = 5, PARITY = 2, FLOW_CONTROL = 0).
5. Trigger REQ with a rising edge from FirstScan (%M1.0) or a one-shot coil driven by a user flag.
6. Download the project to the CPU and go online. Watch the CM 1241 LEDs. After the rising edge on REQ, the TX LED should flicker every time the bus is active.
7. Insert Modbus_Master in OB1 with the same instance DB family. Set MB_ADDR = 1 (PM2230 default), MODE = 0 (read), DATA_ADDR = 0x0000 (for V_avg on PM2230), DATA_LEN = 2 (single 32-bit float), and DATA_PTR pointing to a data block of ARRAY[0..1] OF WORD.
8. Trigger Modbus_Master.REQ with a periodic pulse (e.g. 500 ms from a clock bit or TON timer).
9. Monitor the response: Done pulses TRUE for one cycle, then resets. Route it to %M30.0 and watch online.

11. Verification Checklist

• [ ] Modbus_Comm_Load.Status returns 16#0000 for one cycle after REQ rises, then settles to 16#7000 while idle.
• [ ] Modbus_Comm_Load.Done is TRUE for exactly one scan after configuration.
• [ ] Modbus_Comm_Load.Error is FALSE.
• [ ] The CM 1241 TX LED flashes within 100 ms of a Modbus_Master REQ pulse.
• [ ] The PM2230 RX LED (if equipped) flashes on the same pulse.
• [ ] Modbus_Master.Status shows 16#0000 for one cycle, then 16#7000 while idle.
• [ ] Modbus_Master.Done is TRUE on success.
• [ ] The requested register (e.g. PM2230 V_avg at address 0x0B58) returns a non-zero value matching the live voltage.

12. Diagnostic Decision Flow

13. Field-Proven Tips

• Watch the instance DB online. With TIA Portal online, expand the instance DB and verify that MODE, BAUD, PARITY, FLOW_CONTROL show the values you configured. If the online value differs from the start value, the block is being re-initialised by code — fix the upstream logic first.
• Disable the watch dog during commissioning. If the OB1 cycle time exceeds the configured scan watchdog (default 150 ms for V4.4+), the CPU can drop the configuration and the CM 1241 will revert to 16#7000 on the next startup. Either extend the watchdog in CPU Properties → Cycle Time or optimise the OB1 cycle.
• Use the Modbus RTU library's free-port diagnostic in TIA V17+: enabling Online → Diagnostics → Modbus Trace shows the raw byte stream and is the fastest way to confirm the master is sending valid Modbus frames.
• Avoid the "Modbus_Comm_Load in OB100" anti-pattern. The Startup OB runs once at restart; placing long-running or conditional blocks there is fragile. Run everything from OB1.
• Do not re-trigger Modbus_Comm_Load.REQ on every cycle. The instruction is designed to receive a single rising edge to apply the configuration. Triggering it on every OB1 cycle wastes CPU time and may cause intermittent busy flags. The cleanest pattern is FirstScan or a manual HMI button.

14. Related Standards and Reference

The CM 1241 implements the physical layer of ANSI/TIA-485-A (often called RS485) and the data-link layer of Modbus over serial line as defined by the Modbus Organization's Modbus over Serial Line Specification and Implementation Guide V1.02. A working RS485 link is implicitly defined by the standard; the Modbus application layer then defines function codes 01–06 and 0F/10 for read/write access to coils, discrete inputs, input registers, and holding registers.