Hardware Prerequisites and Data Record Routing for SIMATIC PDM Integrated in SIMATIC PCS 7

SIMATIC PDM integrated in SIMATIC PCS 7 requires an automation station that supports Data Record Routing (Dataset Routing) across all communication boundaries. While standalone S7-300 CPUs (such as CPU 315-2 DP) support data record routing across their integrated interfaces, standard S7-300 Ethernet modules (CP 343-1 Lean and CP 343-1 Standard) do NOT support dataset routing. Consequently, an Engineering Station cannot reach field devices (like SIMOCODE pro V) on PROFIBUS via an Ethernet CP 343-1. In SIMATIC PCS 7, certified PDM integration mandates an S7-400 or CPU 410-5H controller (with CP 443-1 or integrated PN) as the routing bridge.

Principles of Data Record Routing in SIMATIC PDM

SIMATIC Process Device Manager (PDM) is the universal tool for parameterization, commissioning, diagnostics, and maintenance of intelligent field devices (transmitters, actuators, motor management relays, and valve positioners) operating on PROFIBUS DP, PROFIBUS PA, Foundation Fieldbus, and HART protocols.

When PDM is integrated into SIMATIC PCS 7, engineers configure devices from a central Engineering Station (ES) connected to the Industrial Ethernet Plant Bus. For PDM to communicate with a field instrument connected to a downstream PROFIBUS segment, the intermediate controller must perform Data Record Routing (also known as Dataset Routing). Unlike simple cyclic I/O polling, dataset routing encapsulates acyclic read/write requests (S7 job functions for DPV1 communication) and routes them between distinct network subnets.

Hardware Limitations of S7-300 and CP 343-1 in PDM Routing

A frequent design error occurs when engineers attempt to use an S7-300 station (e.g., CPU 315-2 DP with a CP 343-1 Ethernet coprocessor) as an inexpensive gateway between the PCS 7 Engineering Station and PROFIBUS DP motor devices (such as SIMOCODE pro V):

CP 343-1 Dataset Routing Inability: Standard Ethernet communications processors for S7-300 (including CP 343-1 Lean 6GK7343-1CX10-0XE0 and standard CP 343-1 6GK7343-1EX30-0XE0) do not support data record routing. They can exchange cyclic S7 connections and ISO-on-TCP buffers, but they cannot route acyclic PDM data records from Industrial Ethernet to the CPU backplane.
S7-300 CPUs Unsupported in PCS 7: S7-300 controllers are not released or approved as AS controllers in SIMATIC PCS 7. They lack the system architecture, alarm handling (ALARM_8P), and hardware routing pathways required by PCS 7 and PDM integration.

Supported PCS 7 Architecture: S7-400, CPU 410, and CP 443-1

In official SIMATIC PCS 7 architectures, PDM data record routing is guaranteed by the following hardware platforms:

S7-400 Controllers: Standard S7-400 CPUs (CPU 414-3, CPU 416-3, CPU 417-4) support full dataset routing between their internal backplane, integrated PROFIBUS DP master interfaces, and Industrial Ethernet CPs (such as CP 443-1 6GK7443-1EX30-0XE0).
CPU 410-5H Process Automation: The flagship CPU 410-5H possesses dual integrated PROFINET ports and integrated PROFIBUS DP interfaces, natively supporting high-speed acyclic dataset routing without requiring separate communications coprocessors.
Direct PC-to-Fieldbus Interfaces: Standalone PDM can also connect directly to fieldbuses using a dedicated CP 5611, CP 5711, or IE/PB Link PN IO, bypassing the controller entirely.

Parameterizing SIMOCODE pro V and PROFIBUS Field Devices via PDM

When configuring SIMOCODE pro V motor management units under a certified PCS 7 AS:

HW Config Setup: Insert the SIMOCODE pro V (e.g., 3UF7010-1A...) into the PROFIBUS DP line of the S7-400 or CPU 410-5H. Assign it a unique PROFIBUS DP address (e.g., Address 12).
Assign PDM Device Type: Right-click the SIMOCODE device in HW Config and select Start Device Tool > SIMATIC PDM. Select the certified Electronic Device Description (EDD) from the PDM Device Integration Manager.
Dataset Routing Configuration: Ensure the Engineering Station's network connection is assigned to the Plant Bus subnet in NetPro, and that 'PG/PC Interface' is set to PC Internal.local or the active network adapter with S7ONLINE routing active.
Acyclic Parameter Upload/Download: PDM transmits motor protection parameters, trip curves, and operational limits directly across the S7-400 backplane to the SIMOCODE unit without interrupting cyclic motor control.

PDM Routing Capability Matrix Across Siemens Hardware

The following table compares dataset routing capabilities across Siemens communications processors and controllers:

Hardware ComponentMLFB / Order NumberData Record Routing SupportPDM Integration in PCS 7Suitable RoleCP 343-1 Lean6GK7343-1CX10-0XE0NOStrictly UnsupportedBasic S7 server communication onlyCP 343-1 Standard6GK7343-1EX30-0XE0NOStrictly UnsupportedStandard S7-300 Ethernet networkingCP 343-1 Advanced6GK7343-1GX31-0XE0YES (Limited, STEP 7 only)Not released for PCS 7Package unit routing in STEP 7 V5.5CP 443-1 Standard6GK7443-1EX30-0XE0YESFully SupportedStandard PCS 7 S7-400 Plant Bus interfaceCPU 410-5H6ES7410-5HX08-0AB0YES (Native PN/DP routing)Flagship Certified CoreModern PCS 7 DCS process controllerIE/PB Link PN IO6GK1411-5AB00YESFully SupportedStandalone PROFINET-to-PROFIBUS bridge

Verification

Verify PDM routing and device accessibility through the following procedure:

Open SIMATIC Manager and switch to the Process Device Plant View.
Right-click the SIMOCODE pro V or field transmitter and select Open Object to launch SIMATIC PDM.
Select Device > Read from Device. Confirm that PDM connects without routing timeout errors (0x80040154 or Connection timed out).
Verify that online measured values (current, voltage, operating hours, device status) populate live in PDM.
In PDM, execute a test diagnostic read (Diagnostics > Diagnostic Status) to confirm bidirectional acyclic communication.

Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Limitations and Operational Precautions

Consider these operational rules when implementing PDM routing:

Never Perform Firmware Updates via Routed Links During Plant Operation: Flashing field device firmware over a routed S7-400 link consumes significant backplane bandwidth and can cause cyclic communication jitter on critical control loops.
SIMOCODE Motor Control Safety: Modifying motor protection parameters (such as nominal current or class trip time) while the motor is in RUN mode can cause immediate trip activation if parameters cross the current operating point.
PDM License Tags: SIMATIC PDM licensing is based on the total number of configured field devices (TAGs, e.g., 100, 1,000, or unlimited TAGs); verify sufficient PDM tag capacity in Automation License Manager.

Engineer FAQ

What is the difference between S7 routing and Data Record Routing?

S7 routing passes standard engineering connections (such as uploading/downloading PLC blocks). Data Record Routing specifically transfers acyclic parameterization datasets (DPV1/HART) to intelligent slave devices.