Resolving S7-1200 CB 1241 RS485 Error 16#8280

1. Problem Overview

The CB 1241 RS485 signal board mounted beneath an S7-1200 CPU (firmware V4.x and later) is one of the most-used serial options for Modbus RTU master/slave communication against third-party controllers such as Schneider Modicon M340, M221, M241, or ATV drives. Field reports repeatedly describe the same symptom: at CPU power-on the CB 1241 LED flashes green once, then goes dark, while MB_COMM_LOAD never reaches DONE and MB_SLAVE returns STATUS = 16#8280.

This article consolidates the diagnostic path for that exact failure mode, ties the symptoms back to hardware and TIA Portal configuration layers, and verifies each fix against the CB 1241 RS485 wiring specification in the official S7-1200 manual collection.

2. CB 1241 Hardware Identification

The single green blink observed during CPU power-up is the LED self-test — it indicates that the CPU detected the CB on the backplane and performed a power-on check. After that pulse the LED is no longer meaningful for traffic; status must be read from the Modbus instruction output bits.

3. Decoding the LED Behavior

Unlike the CM 1241 communication modules (which have TxD and RxD LEDs that pulse with traffic), the CB 1241 has no continuous diagnostic LEDs. The "blink once, then off" behavior is therefore expected hardware behavior and not a fault indicator. The real status is obtained from:

1. The DONE bit of MB_COMM_LOAD.
2. The ERROR and STATUS outputs of MB_SLAVE / MB_MASTER.
3. The PLC tag table constant <CB1241>_RS485 (e.g., Local~CB_1241_RS485).

Use the PLC tag table → System Constants to pick the symbolic name instead of a hard-coded hardware identifier such as 269. Hard-coded IDs frequently survive a hardware reconfiguration and silently produce 16#8280.

4. Error Code 16#8280 Root Causes

STATUS 16#8280 is defined in the TIA Portal Modbus library documentation as "Invalid port ID or Modbus instruction was started on the wrong port type." It is one of the most common startup errors and almost always maps to one of the following:

5. RS485 Wiring Requirements per Siemens Manual

The CB 1241 RS485 wiring section of the S7-1200 manual collection states explicitly that termination must only be applied at the two physical end nodes of the RS485 segment. Pull TA and TB to the bus and use shielded twisted-pair cable, with the shield bonded to ground at one end minimum.

The on-board termination on the CB 1241 is implemented by closing jumpers TA↔A and TB↔B on the 6-pin plug. It is a 390 Ω / 220 Ω / 390 Ω divider per the Siemens reference design (effective ~120 Ω between A and B). Activate it only when the CPU is at one end of the bus; if the bus is daisy-chained through the CPU, leave it open.

6. TIA Portal Configuration of the CB 1241

1. Open Device Configuration and verify the CB 1241 appears under the CPU signal board slot. If it is missing, drag it from the hardware catalog (Communication → Signal Boards → CB 1241 RS485).
2. Right-click the CB 1241 → Properties → confirm the catalog order number matches the physically installed board (e.g., 6ES7241-1CH30-1XB0).
3. Open Device View → Properties → System Constants and confirm the symbolic port name (e.g., Local~CB_1241_RS485) is visible. If it is greyed out, the project was built for a CPU that does not have a CB in the signal board slot.
4. Compile the project (Project → Compile → Hardware and Software) and download the hardware configuration to the PLC. A red comparison error in the device view after download indicates the configured CB does not match what the CPU sees on the backplane.

7. MB_COMM_LOAD and MB_SLAVE Block Setup

Two instructions are mandatory for Modbus RTU on the CB 1241. The most common field error is calling MB_SLAVE without first calling MB_COMM_LOAD in the same cycle, or vice-versa.

7.1 MB_COMM_LOAD parameters

7.2 MB_SLAVE parameters

7.3 Execution order rules

1. Call MB_COMM_LOAD first in OB1 and wait until DONE = TRUE or ERROR = FALSE before relying on its result.
2. Call MB_SLAVE after MB_COMM_LOAD in the same cycle; it must not start until MB_COMM_LOAD has finished at least once.
3. If MB_SLAVE.STATUS = 16#8280 while MB_COMM_LOAD.DONE = TRUE, the port is open but the slave cannot bind to it — re-check the symbolic port name and ensure the CB matches the catalog number.

8. Termination Resistor Strategy

Termination is not optional on RS485 — without it, reflected edges corrupt the differential signal at higher baud rates and cause framing errors. The signal board integrates the termination, but the activation is your decision.

• If the S7-1200 is at one end of the bus (typical setup with one Schneider device): close TA and TB on the CB 1241 terminal plug, and enable the Schneider device's internal termination (often a DIP switch or jumper — consult the Modicon hardware manual).
• If the S7-1200 is mid-bus between two end devices: leave TA/TB open on the CB and enable termination only at the two physical end nodes.
• If only the S7-1200 and one Schneider device exist: both ends terminated, both jumpers closed.

9. Diagnostics Buffer Analysis

The S7-1200 diagnostics buffer does not generate a hardware interrupt for the CB 1241 during normal serial traffic. Absence of buffer entries is expected and is not a fault indicator. What the buffer will show, and what to look for:

10. Step-by-Step Troubleshooting Procedure

1. Verify the physical CB matches the project. Open Device View in TIA Portal, compare the order number against the label on the board. Mismatched order numbers (e.g., RS232 board configured but RS485 board fitted) silently produce 16#8280.
2. Replace any literal PORT input with the system constant. Open MB_COMM_LOAD and MB_SLAVE in the program editor, click the small symbol next to the PORT input, and pick the system constant for the CB 1241. Recompile and download.
3. Cold-restart the CPU. Stop the CPU, power-cycle, and power up again. A warm restart after a parameter change can leave the CB in an undefined state until the next STOP→RUN transition.
4. Confirm MB_COMM_LOAD reaches DONE. Monitor the DONE bit in a watch table. If DONE stays FALSE, the port parameter is rejected — go back to step 2.
5. Check parity and baud against the Schneider device. Default Modbus RTU on Schneider controllers is 19200 8E1 (1 start, 8 data, even parity, 1 stop). Match these on the S7-1200 side exactly.
6. Verify RS485 wiring. Use a multimeter between A and B: with all nodes powered, you should read approximately 60 to 120 Ω across the segment with both terminators engaged, or ~600 Ω with none. Anything outside this range suggests a missing or double termination.
7. Isolate the bus. Disconnect the Schneider device, terminate the S7-1200 end, and run a single-node loopback test (connect A↔A and B↔B at the remote end, or use a freeport loopback). If MB_SLAVE now reports DONE without error, the wiring or remote device is at fault, not the CB.
8. Re-engage the Schneider device with correct termination. Reconnect, ensure termination only at end nodes, and observe MB_SLAVE.STATUS dropping to 0.

11. Verification Checklist

• Device view shows green check on the CB 1241 entry after download.
• MB_COMM_LOAD.DONE = TRUE within one scan of REQ rising edge.
• MB_COMM_LOAD.ERROR = FALSE and STATUS = 16#0000.
• MB_SLAVE.ERROR = FALSE.
• Modbus poll from the Schneider master reads the configured holding registers (e.g., MW100..MW110).
• Wiring resistance A↔B between 60 Ω and 120 Ω with both terminators active.
• Diagnostics buffer contains no new error entries after 10 minutes of traffic.

12. Troubleshooting Matrix

FAQ