Configuring HART Field Devices on AI 8x16Bit HART Modules (6ES7331-7TF01-0AB0) via SIMATIC PDM V8.2 - Routing and HW Config Download Prerequisites

In SIMATIC PCS 7 and STEP 7, connecting to a HART field instrument (such as a VEGA DIFF 65) via an AI 8x16Bit HART module (6ES7331-7TF01-0AB0) in SIMATIC PDM V8.2 requires downloading the hardware configuration to the controller with HART mode enabled and the channels unassigned prior to device identification. If an engineer assigns field devices in HW Config and attempts 'Device Identification' without an initial HW Config download, PDM aborts with 'Action failed: The device was not found or could not be identified - OM: Parameter invalid' because the S7-400 CPU and ET 200M interface module lack the acyclic data routing records (DS131-138) required for HART communication.

Acyclic HART Communication Mechanics Over PROFIBUS DP

In SIMATIC PCS 7 distributed I/O architectures, HART (Highway Addressable Remote Transducer) field communication enables bidirectional digital data exchange superimposed over standard 4–20 mA analog wiring:
- Cyclic vs Acyclic Data Streams:
* Cyclic Data: The analog process variable (4–20 mA) is digitized by the module (6ES7331-7TF01-0AB0) and transferred cyclically to the controller's process image for standard control logic.
* Acyclic Data: Digital HART commands (Universal, Common Practice, and Device-Specific) are transmitted asynchronously between SIMATIC PDM on the Engineering Station and the field instrument.
- Data Record Routing (S7-Routing):
* PDM communicates with field devices using S7 data record routing (via SFB 52 / SFB 53 or internal communication blocks).
* The telegrams travel from ES $\rightarrow$ Industrial Ethernet $\rightarrow$ S7-400 CPU $\rightarrow$ PROFIBUS DP Master $\rightarrow$ ET 200M IM 153-2 $\rightarrow$ AI module backplane $\rightarrow$ HART field loop.
* For this route to exist, the S7-400 operating system must generate internal system data blocks (SDBs) defining the routing endpoints.

Root Cause of 'Action Failed - OM: Parameter Invalid'

When an engineer installs an IM 153-2 (6ES7153-2BA02-0XB0) and an AI 8x16Bit HART card (6ES7331-7TF01-0AB0), the following trap frequently occurs:
1. The Un-downloaded Routing Trap:
- The engineer places the card in HW Config, enables HART mode on Channel 0, and immediately assigns the field instrument (e.g. VEGA DIFF 65 Rev 7.0).
- In HW Config, double-clicking the channel opens the PDM assignment window. Clicking Device Identification triggers:
text Action failed: the device was not found or could not be identified. OM: parameter invalid.
2. Missing Controller Data Records:
- Because HW Config was never compiled and downloaded to the physical S7-400 CPU, the CPU has no knowledge of the HART module's presence or channel mapping.
- The Object Manager (OM) attempts to send acyclic HART data records (DS131 for Channel 0) across a non-existent routing path, causing the controller to return a parameter invalid error.

Step-by-Step Configuration and PDM Identification Workflow

To successfully configure HART devices and eliminate the OM error:

Configure Hardware in STEP 7 HW Config:
- Insert an IM 153-2 interface module (6ES7153-2BA02-0XB0 or successor 6ES7153-2BA10-0XB0) onto the PROFIBUS DP master line.
- Insert the SM 331 AI 8x16Bit HART module (6ES7331-7TF01-0AB0) into the ET 200M rack.
- Double-click the SM 331 module:
- Navigate to the Inputs tab.
- Set measuring type to 4DMU (4-wire) or 2DMU (2-wire transmitter).
- Check HART Mode for all active channels.
- Crucial Step: Do NOT assign any field devices to the channels yet!
Save, Compile, and Download HW Config:
- In HW Config, select Station > Save and Compile.
- Download the hardware configuration to the S7-400 CPU (PLC > Download).
- The CPU initializes the ET 200M rack, parameterizes the SM 331 module, and creates the internal acyclic HART data routing tables.
Assign and Identify Field Device in PDM:
- Return to HW Config.
- Double-click Channel 0 on the SM 331 module.
- In the device selection dialog, select the device description: VEGA > Level > VEGA DIFF 65 > Rev 7.0.
- Click Device Identification.
- PDM transmits HART Command 0 via the established routing path; the field transmitter responds with its unique device ID.
- Click Assign.
Upload Parameters to PG/PC:
- Save and compile HW Config.
- Open SIMATIC Manager Process Device Plant View, double-click the VEGA instrument to launch PDM online mode, and execute Device > Upload to PG/PC.

ET 200M HART Analog Module Configuration Parameter Table

The following table details configuration requirements for the SM 331 HART module:

Module ParameterRequired SettingFunctional ImpactCommon Error If MisconfiguredMeasuring Type2DMU or 4DMUDefines loop power supply from card vs externalReversed polarity, blown card fuse, or 0 mA raw inputMeasuring Range4..20 mA HARTEnables FSK Bell 202 modem modulationStandard 4–20 mA works, but PDM cannot communicateHART Repetitions3 to 5Number of communication retries on noisy loops'Remote IO channel constantly busy' or timeoutHW Config DownloadCompleted prior to PDMGenerates S7 routing records in controller SDBs'Action failed: OM parameter invalid'Field Wiring ImpedanceMinimum 250 ohmsRequired loop resistance for HART FSK voltage dropCommunication fails if loop load resistance is < 230 ohms

Verification

To confirm that the HART field device is properly communicating with PDM:
1. In HW Config, verify that Channel 0 displays the VEGA DIFF 65 object.
2. In SIMATIC Manager Process Device View, double-click the transmitter to open SIMATIC PDM.
3. Verify that the communication indicator in the PDM status bar displays Online (HART).
4. Execute View > Process Variables: confirm that the Primary Variable (PV - Differential Pressure), Secondary Variable (SV), and Percent Range track live sensor inputs.
5. In CFC, connect the module peripheral address (PIW xxx) to channel driver block FbAnIn or Pcs7AnIn. Verify that the process value reads cleanly with Quality = 16#80 (Good).

Limitations and Operational Precautions

When configuring HART instruments in PCS 7:
1. Loop Resistance Prerequisites: HART communication requires a minimum loop impedance of 250 ohms (maximum 1100 ohms) for the FSK frequency-shift keying modem to detect voltage fluctuations. If loop resistance is below 230 ohms, install a series resistor.
2. Channel SDB Memory Limits: Enabling HART on all 8 channels across dozens of SM 331 modules increases controller communication load. Monitor CPU communication connection resources in Module Information.
3. Avoid Unshielded Cable Runs: Unshielded signal cables run alongside high-power variable frequency drive (VFD) cables introduce electromagnetic noise that corrupts HART packets, leading to intermittent PDM disconnects.

Engineer FAQ

Why did PDM throw 'OM: parameter invalid' before the HW Config download?

Because the S7-400 CPU had not yet received the hardware configuration enabling the HART routing tables. PDM attempted to communicate across a routing path that did not exist in the controller's active memory.

Can I configure HART devices in HW Config while the CPU is in RUN?

Yes, if the ET 200M station is configured on an active bus module supporting Configuration in RUN (CiR). Otherwise, downloading HW Config to the S7-400 requires a momentary CPU STOP.

What does the 6ES7331-7TF01-0AB0 module do if a HART transmitter fails?

The analog input drops below 3.6 mA (triggering underflow / wire-break detection in the driver block), and the module logs a HART diagnostic interrupt in the CPU diagnostic buffer.

Does SIMATIC PDM support multi-drop HART configurations on SM 331?

No. The SM 331 AI 8x16Bit HART module supports point-to-point connections exclusively (one field instrument per physical channel). Multi-drop HART (polling addresses 1-15) is not supported.