Configure S7-1200 Modbus RTU Master for Altivar ATV12 via CM1241

Overview

Pairing a SIMATIC S7-1200 CPU with a Schneider Electric Altivar ATV12 variable frequency drive over Modbus RTU is a common low-cost motion package: a CPU 1212C, 1214C, or 1215C acts as the Modbus master, an RS-485 CM1241 or CB1241 acts as the physical port, and three ATV12 drives hang off the bus as slaves. Despite the simplicity of the topology, the integration trips on a handful of repeatable failures: the wrong communication module is installed (the CM1243 is not a Modbus RTU module), the S7-1200 Modbus blocks are addressed using the application layer convention 4xxxx instead of the data link layer convention expected by MB_MASTER, and the port is used before MB_COMM_LOAD initializes it, which surfaces as status word 16#8180. This reference walks through the wiring, TIA Portal configuration, block parameters, addressing rules, and the field-proven fixes for the most common error codes.

Prerequisites

Verify the ATV12 firmware supports Modbus RTU slave mode. From the drive keypad navigate to CONF > FULL > COMM > MODBUS, confirm Modbus is enabled, and assign a unique address (1 to 247) to each drive on the bus; addresses 1, 2, and 3 are typical for a three-drive cluster.

Communication Board Selection: CM1241 vs CB1241 vs CM1243

The single most common initial question on this integration is which communication module to install. The correct answer is either CM1241 or CB1241. The CM1243 family is not the right module for Modbus RTU and will not run MB_MASTER.

CB1241 is the more compact choice: a communication board that mounts to the left side of the CPU with screw terminals for D+, D-, and GND, ideal for small panels. CM1241 is a communication module that mounts to the left of the CPU or CB1241, uses a 9-pin SUB-D connector, and is the right choice when a Profibus-style connector with integrated 120 Ω termination is required. Both modules support Modbus RTU master and slave at 1.2 to 115.2 kbps.

Hardware Wiring and Bus Topology

The ATV12 RJ45 Modbus port follows the Modbus standard pinout: pin 5 is D1 (B+), pin 4 is D0 (A-), pin 8 is common (0V/GND), and pin 7 is the 120 Ω termination jumper on the drive PCB. For multi-drop, daisy-chain D+, D-, and GND between drives, then place a 120 Ω resistor between D+ and D- at the two physical ends of the bus. If the CM1241 is one physical end, enable its internal termination via the slide switch or by inserting a jumper between pins 7 and 8 of the SUB-D connector per the CM1241 manual.

Bond the shield at one end only to avoid ground loops. If the panel has high VFD switching noise, place a small RC snubber (e.g. 100 Ω + 100 nF) across the bus at each drive terminal; the ATV12 manual documents this as a software setting under CONF > COMM > MODBUS > TER.

Port Configuration in TIA Portal

1. Open the device configuration of the S7-1200 CPU in TIA Portal.
2. Drag the CM1241 or CB1241 from the hardware catalog (under Communication modules > CM/CB) onto a free slot to the left of the CPU.
3. Open the module properties and set the port to RS-485 half-duplex, not RS-422. The ATV12 is a two-wire RS-485 device.
4. Select 9.6 kbps (or 19.2 kbps for faster polling), 8 data bits, even parity, 1 stop bit, and flow control: none. These must match the ATV12 exactly or frames will be silently dropped.
5. Confirm the diagnostic address. TIA assigns 271 to the CM by default; do not change this unless you also pass the new ID to MB_COMM_LOAD as the PORT input.

The hardware configuration is the input contract for MB_COMM_LOAD. If the slot is empty in the device view, MB_MASTER calls will return 16#8180 because there is no valid port to write to. For the broader Modbus RTU integration checklist, refer to the Siemens FAQ on S7 Modbus RTU components.

Initializing the Modbus Port: MB_COMM_LOAD

MB_COMM_LOAD is a one-shot block that runs in OB100 (startup) or OB1 on the first scan to push the port parameters into the CM/CB. Without it, every MB_MASTER call returns 16#8180 ("Invalid value for the port ID").

MB_COMM_LOAD input parameters

Sample call in OB100:

// OB100 - Startup
MB_COMM_LOAD_DB.MB_COMM_LOAD(
    REQ        := TRUE,        // execute on first scan only
    PORT       := 271,         // CM1241 default diagnostic address
    BAUD       := 9600,
    PARITY     := 2,           // 2 = even parity
    FLOW_CTRL  := 0,
    RTS_ON_DLY := 0,
    RTS_OFF_DLY:= 0,
    RESP_TO    := 1000,
    DONE       => FirstInitOK,
    ERROR      => FirstInitErr,
    STATUS     => FirstInitStatus);

If the block returns ERROR = TRUE on first execution, capture STATUS. A common value is 16#80B0 plus the slot number; this means "module does not exist or wrong ID". Verify the slot is populated in the device configuration and that PORT matches the diagnostic address.

Polling Three Slaves with MB_MASTER

With one CM1241 handling three ATV12 drives, MB_MASTER is called in a round-robin pattern. Use a cyclic OB (OB1) and a state machine that cycles through slave IDs 1, 2, and 3, requesting one or two registers per cycle. Calling MB_MASTER more than once per port at the same time will corrupt the frame; gate the call with a single instance DB per channel.

MB_MASTER input parameters

Mode values (S7-1200 Modbus block V2.x)

To read the output frequency of an ATV12, use MODE 2 (read holding registers, FC 03) and point DATA_ADDR to the data link address of the ETA/frequency register. To set the speed reference, use MODE 5 or MODE 7 with a target value, e.g. 1500 for 50.0 Hz on a 50 Hz drive (the Schneider Altivar scaling is 0..1500 for 0..50.0 Hz on most parameters; check the specific register in the ATV12 manual for the correct scaling).

Modbus Addressing: Data Link Layer vs Application Layer

This is the most common source of confusion. The S7-1200 Modbus blocks (MB_MASTER, MB_SLAVE) accept the 0-based data link layer address, not the application layer 4xxxx convention. The ATV12 manual, on the other hand, lists its registers in the 4xxxx format. Convert by subtracting 40001.

For hex-formatted addresses such as 16#FD00 (64768 decimal), MB_MASTER accepts the integer directly. Some Schneider manuals present the address in a 6-digit form (e.g. 416FD00). Whether the value to enter is the application address or the data link address depends on the manual; the simplest field test is to use a free Modbus master tool on a PC (e.g. Modscan32) against the same drive, request the documented register, and observe the raw address it sends. See the S7-1200 Modbus RTU master programming manual for the full block description.

ATV12 Holding Register Map (Working Subset)

The ATV12 exposes a virtual control word, status word, frequency setpoint, and output frequency through Modbus. The field report cited 16#FD00 (64768 decimal) as the address for output frequency and 42001 as another working read address. Treat these as example values and verify against the official ATV12 Modbus communication manual (Schneider document NVE21777 or the current equivalent) before deployment.

To read a holding register into S7-1200 data block "ATV12_FB" at offset byte 0 (Word 0):

// OB1 - Cyclic, one transaction per cycle
IF (State = 0) THEN
    // Read status from slave 1
    MB_Master_DB.MB_Master(
        REQ       := TRUE,
        MB_ADDR   := 1,
        MODE      := 2,            // 03 = read holding registers
        DATA_ADDR := 3200,         // ETA (verify against ATV12 manual)
        DATA_LEN  := 1,
        DATA_PTR  := P#DB10.DBX0.0 WORD 1,
        DONE      => DoneFlag,
        ERROR     => ErrFlag,
        STATUS    => StatusWord);
    State := 1;
END_IF;

For the 16#FD00 parameter access range, confirm whether the ATV12 manual lists the address as the application layer value (in which case use DATA_ADDR = 64767) or as the data link value (in which case use DATA_ADDR = 64768). The Modscan32 utility on a PC is the fastest way to confirm; it can scan the entire 0..65535 data link space and show which addresses return a non-exception response.

Error Code Diagnosis: 16#8180 and Other Status Words

Status word 16#8180 from MB_MASTER or MB_SLAVE means the PORT input does not match any Modbus-enabled communication module in the device configuration. This is by far the most common fault when bringing up an S7-1200/ATV12 link.

Other common status words

Verification, Commissioning, and Pitfalls

Commissioning sequence

1. Confirm the MB_COMM_LOAD DONE = TRUE on the first OB100 cycle and DONE never appears again (the block fires only on edge).
2. Trigger one MB_MASTER read with MB_ADDR = 1, MODE = 2, DATA_ADDR = 3272 (output frequency, typical), DATA_LEN = 1.
3. Watch the CM1241 Send/Receive LEDs. A healthy transaction shows alternating flashes on each direction; the receive LED should blink on every successful response.
4. Use a Modbus diagnostic tool on the bus (Modscan32 on a laptop with a USB-RS485 adapter) to confirm the slave is responding to the same address. If the drive is silent, isolate it from the bus to rule out a stuck partner.
5. Read back the output frequency in a watch table. The value should track the local HMI/keypad setpoint within one cycle.
6. Add a write test: send MODE = 5, MB_ADDR = 1, DATA_ADDR = 3252 (speed setpoint, typical), DATA_LEN = 1, data = 1000 (33.3 Hz on a 50 Hz drive). The drive should ramp and the output frequency should climb to 33.3 Hz.
7. Once one drive is healthy, extend the polling sequencer to slave IDs 2 and 3 and add fault handling per the STATUS codes above.

Polling state machine sketch

// OB1 - Polling sequencer
CASE PollState OF
    0: // Read ETA from slave 1
       MB_Master_DB.REQ := TRUE;
       MB_Master_DB.MB_ADDR := 1;
       MB_Master_DB.MODE := 2;
       MB_Master_DB.DATA_ADDR := 3200;
       MB_Master_DB.DATA_LEN := 1;
       MB_Master_DB.DATA_PTR := P#DB10.DBX0.0 WORD 1;
       PollState := 10;
    10: // Wait for done/error
       IF MB_Master_DB.DONE THEN PollState := 1; END_IF;
       IF MB_Master_DB.ERROR THEN LogFault(1, MB_Master_DB.STATUS); PollState := 1; END_IF;
    1: // Read ETA from slave 2
       MB_Master_DB.MB_ADDR := 2;
       MB_Master_DB.DATA_PTR := P#DB10.DBX2.0 WORD 1;
       PollState := 11;
    11: IF MB_Master_DB.DONE THEN PollState := 2; END_IF;
        IF MB_Master_DB.ERROR THEN LogFault(2, MB_Master_DB.STATUS); PollState := 2; END_IF;
    2: // Read ETA from slave 3
       MB_Master_DB.MB_ADDR := 3;
       MB_Master_DB.DATA_PTR := P#DB10.DBX4.0 WORD 1;
       PollState := 12;
    12: IF MB_Master_DB.DONE THEN PollState := 3; END_IF;
        IF MB_Master_DB.ERROR THEN LogFault(3, MB_Master_DB.STATUS); PollState := 3; END_IF;
    3: // Read output frequency from slave 1
       MB_Master_DB.MB_ADDR := 1;
       MB_Master_DB.DATA_ADDR := 3272;
       MB_Master_DB.DATA_PTR := P#DB10.DBX6.0 WORD 1;
       PollState := 13;
    13: IF MB_Master_DB.DONE THEN PollState := 4; END_IF;
        IF MB_Master_DB.ERROR THEN LogFault(1, MB_Master_DB.STATUS); PollState := 4; END_IF;
    4: // Send speed setpoint to slave 1
       MB_Master_DB.MODE := 5;
       MB_Master_DB.MB_ADDR := 1;
       MB_Master_DB.DATA_ADDR := 3252;
       MB_Master_DB.DATA_LEN := 1;
       MB_Master_DB.DATA_PTR := P#DB10.DBX20.0 WORD 1;
       PollState := 14;
    14: IF MB_Master_DB.DONE THEN PollState := 0; END_IF;
        IF MB_Master_DB.ERROR THEN LogFault(1, MB_Master_DB.STATUS); PollState := 0; END_IF;
ELSE
    PollState := 0;
END_CASE;

Field debugging checklist

• Measure A-B on the bus with an oscilloscope; signal should swing at least 1.5 V differential, with the bus biased by 650 Ω pull-up to +5 V and 650 Ω pull-down to GND at one master.
• Confirm 120 Ω at each physical end; the ATV12 RJ45 has a 120 Ω resistor that can be enabled with a jumper on the drive PCB (refer to ATV12 installation manual).
• Verify drive Modbus address in CONF > COMM > MODBUS > ADDR. Default is 1; ensure each drive on the bus has a unique value.
• Watch for silent slaves after a hot restart of the CPU. Some ATV12 firmware versions drop the Modbus connection if the drive sees a long inter-character gap; reduce inter-frame delay or use a 100 ms post-response recovery if needed.
• Use a watch table to confirm MB_MASTER STATUS = 0 (DONE) on success and capture the first non-zero value for the diagnostics table above.

Pitfall matrix

Frequently Asked Questions