C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Loading CP 341 Modbus RTU Drivers in SIMATIC PCS 7 Without Stopping Controller - The Offline Staging and CiR Workflow

Loading CP 341 Modbus RTU Drivers in SIMATIC PCS 7 Without Stopping Controller - The Offline Staging and CiR Workflow

In SIMATIC PCS 7 running live plant production on an S7-400H or CPU 410-5H controller, installing a loadable protocol driver (such as Modbus Master RTU or Modbus Slave RTU) into a CP 341 serial communications processor cannot be performed directly across the plant bus in RUN mode, because the standard HW Config driver download routine mandates placing the controller CPU into STOP mode. However, because the Modbus driver is stored in non-volatile flash memory directly on the CP 341 hardware module and is completely retentive, engineers can bypass plant downtime by using the Offline Staging workflow: load the driver into the CP 341 on a standalone bench S7-300 rack in STOP mode, configure the ET 200M station in PCS 7 HW Config using Configuration in RUN (CiR), and hot-swap the pre-loaded CP 341 into the live production ET 200M rack without halting the CPU 410-5H.

Table of Contents

Architectural Constraint: Why Driver Download Requires CPU STOP

In industrial distributed control systems, integrating third-party serial devices (such as energy analyzers, chillers, weigh scales, and gas chromatographs) frequently utilizes the CP 341 serial communications processor installed in ET 200M distributed I/O racks.

To execute the Modbus RTU protocol, the CP 341 requires a loadable driver:
- Modbus Master (RTU)
- Modbus Slave (RTU)

When attempting to load this driver via SIMATIC Manager (HW Config > CP 341 Properties > Parameterize > Load Drivers...), the engineering software sends a low-level diagnostic command across the system bus. The firmware communication protocol between STEP 7 and the CP requires the controlling CPU to transition into STOP mode to freeze peripheral bus polling while firmware blocks are flashed into the CP's internal memory. In active 24/7 continuous process plants controlled by CPU 410-5H, stopping the CPU is unacceptable as it shuts down ongoing production.

Non-Volatile Storage Mechanism of CP 341 Protocol Drivers

A critical hardware property of the CP 341 module (6ES7341-1AH02-0AE0, 6ES7341-1CH02-0AE0) enables a non-intrusive workaround:
- The loaded protocol driver (Modbus RTU Master/Slave) is written into an internal non-volatile flash memory chip located on the CP 341 printed circuit board.
- This memory is completely retentive and persists across power interruptions, backplane disconnections, and module removal.
- Once the driver is flashed into the CP 341, the module does not need to be reloaded unless the protocol version itself is upgraded.
- Furthermore, the hardware dongle (electronic license key / software protection dongle) is inserted directly into the rear receptacle of the CP 341 module.

Methodology: The Offline Test Rack Staging Procedure

To install the driver without interrupting plant production, execute the following staging procedure in a workshop or laboratory:

Step 1: Set Up an Offline Staging Rack

  1. Assemble a simple test rack using any spare S7-300 CPU (e.g., CPU 315-2 DP) or spare ET 200M interface module with an S7 backplane bus.
  2. Insert the production CP 341 module into the test rack.
  3. Insert the Modbus hardware license dongle into the back of the CP 341.
  4. Connect an engineering laptop to the test CPU via MPI or Ethernet.

Step 2: Flash the Modbus Driver

  1. On the laptop, open STEP 7 and create a basic test project with the S7-300 CPU and CP 341.
  2. In HW Config, double-click the CP 341, click Parameter..., select Modbus Master (or Slave), and click Load Drivers....
  3. Place the test CPU in STOP mode when prompted.
  4. Execute the driver download; observe the progress bar as the firmware blocks are flashed into the CP 341.
  5. Once completed, power down the test rack and remove the CP 341 module. The driver and license dongle are now permanently stored in the hardware.

Hot-Swapping and Hardware Configuration in RUN (CiR)

Once the module is staged, integrate it into the production PCS 7 system:

Step 1: Configure HW Config via CiR

  1. In the production PCS 7 multiproject, open HW Config.
  2. Locate the active ET 200M station (equipped with active bus modules 6ES7195-7HB00-0XA0 supporting hot-swapping).
  3. Insert the CP 341 into the planned empty slot within the CiR boundary.
  4. Set communications parameters (baud rate, parity, stop bits) to match field instruments.
  5. Select PLC > Download to Module > Changes in RUN (CiR). The controller accepts the hardware configuration without stopping.

Step 2: Hot-Swap the Module into the Production Rack

  1. Approach the live ET 200M rack on the plant floor.
  2. Ensure the active backplane bus module is present in the slot.
  3. Firmly seat the pre-flashed CP 341 module (with its dongle installed) into the active slot.
  4. The ET 200M interface module detects the module insertion; the CP 341 executes an internal self-test.
  5. Within 5 seconds, the SF (System Fault) LED extinguishes and the RUN LED turns solid green, confirming driver initialization.

Operational Comparison: Driver Installation Methodologies

The table below compares the two installation pathways for CP 341 protocol drivers:

Installation PathwayPlant CPU StateDowntime RequiredSafety / Operational RiskFeasibility in ProductionStandard Online DownloadSTOP Mode RequiredYes (Full Process Shutdown)High (Loss of plant control)Unacceptable for 24/7 operationsOffline Test Rack StagingController in RUNZero DowntimeLow (Standard hot-swap)Recommended Industry Standard

Verification

To confirm that the CP 341 is operating with the loaded Modbus driver:
1. Module LED Status: Verify that the SF LED is OFF, RUN LED is steady GREEN, and TxD / RxD LEDs flash cyclically as serial telegrams are exchanged.
2. CFC Modbus Communication Blocks: Open the CFC chart containing the Modbus driver blocks (MODB_400 / P_SND_RK / P_RCV_RK); verify that the status output indicates DONE = 1 and ERROR = 0.
3. Module Information Diagnostics: In SIMATIC Manager, select the CP 341 module and press Ctrl+D; verify that the diagnostic buffer indicates 'Module operational, driver Modbus Master active'.

Limitations and Operational Precautions

Engineering teams must observe the following precautions:
- Hot-swapping is supported only if the ET 200M rack utilizes active bus modules (6ES7195-...); standard passive DIN-rail backplane connectors do not support hot-plugging under voltage.
- The hardware license dongle must remain physically inserted into the rear of the CP 341 module at all times; removing the dongle causes communication blocks to abort with licensing errors.
- Always validate final license quantities and MLFBs against the applicable Siemens catalog and authorized distributor quotation when procuring Modbus RTU driver packages.

Engineer FAQ

What happens if I hot-swap a CP 341 that does not have the driver loaded?

If inserted without the driver, the CP 341 SF LED will remain illuminated red, and calling communication blocks (P_SND_RK / P_RCV_RK) will return error code 16#0830 (Driver not loaded).

Can the Modbus driver be loaded into a CP 441 module in the central AS rack without stopping?

No. CP 441 modules installed in the central S7-400 rack also require CPU STOP for driver flashing, unless staged in a spare central rack using the same offline principle.

Does the CP 341 lose its loaded driver if power is turned off for months?

No. The driver is flashed into non-volatile Flash-EPROM memory and remains intact indefinitely without battery backup.

Technical References

Related Articles

Related Tags

  • CP 341
  • Modbus RTU
  • Configuration in RUN
  • CiR
  • Hot-Swapping
6 respuestas