Integrating Endress+Hauser Waterpilot FMX167 Level Transmitters into SIMATIC PDM V8.2

In SIMATIC PDM V8.2 utilizing a Viator USB HART modem (7MF4997-1DB), connecting to an Endress+Hauser Waterpilot FMX167 hydrostatic level transmitter using the newer FMX21 device description fails because PDM strictly enforces HART Manufacturer ID and Device Type Code validation. Attempting to force an incompatible Electronic Device Description (EDD) causes PDM to reject the communication handshake. To establish online communication, engineers must either import the exact Waterpilot FMX167 EDD device description package into PDM using the Device Integration Manager (DIM) or configure the device under the generic 'HART Universal / Common Practice' profile. The generic profile provides full access to primary process variables, loop current, and standard zero/span calibration.

HART Device Identification and PDM EDD Verification Architecture

SIMATIC Process Device Manager (PDM) is an open, vendor-neutral tool used to configure, parameterize, and diagnose intelligent field instrumentation conforming to the Electronic Device Description (EDD / EDDL) standard (IEC 61804). When PDM communicates with a field instrument over HART (via a physical modem such as the Viator USB modem 7MF4997-1DB):

PDM issues universal HART Command 0 (Read Unique Identifier).
The field device replies with its 24-bit hardware header, containing:
- Manufacturer Code: E.g., 17 (16#11) for Endress+Hauser.
- Device Type Code: Unique identifier assigned per transmitter model.
- Device Revision: Firmware generation.

PDM queries its internal Device Catalog. If the configured object in the project tree does not match the physical device type code returned in Command 0, PDM aborts the connection with a device type mismatch warning.

Why Device Descriptions Cannot Be Substituted Across Product Generations

Engineers facing missing legacy EDD files often attempt to bind a newer model's description (e.g. selecting Waterpilot FMX21 to configure legacy Waterpilot FMX167). This substitution invariably fails:

Instrument ModelHardware GenerationHART Device Type CodeEDD Compatibility in PDM V8.2Waterpilot FMX167Legacy hydrostatic level sensor16#1136 (Model Specific)Requires dedicated FMX167 EDD or Generic HARTWaterpilot FMX21Modern replacement generation16#1158 (Updated ASIC)Rejects FMX167 due to Device Type mismatchGeneric HART ModuleUniversal HART standard profileUniversal Commands (0, 1, 2, 3)Universal Compatibility (Reads PV, Current, Zero/Span)

Because the FMX21 uses updated HART command sets, menu structures, and diagnostic registers, PDM's interpreter prevents cross-binding to prevent writing corrupt configuration records to the transmitter's non-volatile memory.

Step-by-Step Device Integration and Generic HART Fallback Workflow

To establish reliable communication with the Waterpilot FMX167 in SIMATIC PDM V8.2, execute the following technical procedure:

Option A: Import Official FMX167 EDD via Device Integration Manager (DIM):
- Download the official Waterpilot FMX167 EDD package (.zip / .edd) from the Endress+Hauser online download portal or from the Siemens PDM Device Library DVD (DVD 2/2 - Device Integration Library).
- Open Device Integration Manager (DIM) (Start -> Siemens Automation -> SIMATIC PDM -> Device Integration Manager).
- Select File -> Add Device Descriptions.... Browse to the unzipped EDD folder.
- Select Endress+Hauser -> Level -> Hydrostatic -> Waterpilot FMX167 and click Integrate.
- Once integration completes, close DIM and restart SIMATIC Manager.
Option B: Deploy Generic HART Device Profile (Immediate Field Fallback):
- If the manufacturer's proprietary EDD is unobtainable, open SIMATIC Manager in Process Device Network View.
- Insert a generic network object under the HART modem: HART Communication -> HART -> Generic Device -> HART Universal.
- Open the object. PDM bypasses the strict proprietary model check and queries the transmitter using standard HART Universal Commands (Commands 1, 2, 3, 6, 15).
Configure Viator USB Modem (7MF4997-1DB):
- Connect the Viator modem between the PC USB port and the 4–20 mA loop (ensure minimum 250-ohm loop resistance exists).
- In Windows Device Manager, verify the COM port assigned to the USB modem (e.g. COM3).
- In PDM, set the communication interface to HART on COM3.

Verification

Verify live online communication and instrument parameterization through these diagnostic checks:

LifeList Scan: In PDM Network View, right-click the COM port network object and select Start LifeList. Confirm that the Waterpilot responds at polling address 0 with manufacturer Endress+Hauser.
Online Parameter Read: Double-click the instrument object to launch PDM. Confirm that the status bar displays Online and that live process values (PV = Level, Loop Current = 12.0 mA) update dynamically.
Range Calibration Check: Open the calibration view. Confirm that Lower Range Value (LRV / 4 mA) and Upper Range Value (URV / 20 mA) reflect physical tank depth parameters.

Limitations and Operational Precautions

When servicing legacy HART instrumentation with PDM, observe these operational safeguards:

250-Ohm Loop Resistor Mandatory: HART communication modulates a high-frequency AC frequency-shift keying (FSK) signal onto the 4–20 mA DC loop. If loop resistance is below 230 ohms, the FSK voltage is attenuated, resulting in communication timeouts. Insert an external 250-ohm precision resistor in series if needed.
Generic Profile Functional Limits: While the Generic HART profile allows zero/span adjustment and damping changes, advanced proprietary features (such as sensor linearization tables, density compensation, and echo curve diagnostics) require the manufacturer's official EDD.
Safe Loop Handling in Hazardous Areas: Ensure the Viator modem model utilized matches hazardous area classifications if connecting directly to intrinsically safe loops in the field.

Engineer FAQ

Why did PDM connect to FMX21 on another skid but fail on FMX167?

FMX21 is a newer generation transmitter with a different Device Type Code. The FMX21 EDD only accepts connections from physical FMX21 devices; it strictly rejects older FMX167 transmitters.

Can I update PDM V8.2 device library without upgrading PCS 7?

Yes. Siemens releases updated 'Device Integration DVDs' for SIMATIC PDM periodically that can be imported into existing PDM installations using the Device Integration Manager.

What does 'Device Type Mismatch' mean when opening an online connection in PDM?

It means the physical device connected to the HART loop reported a different manufacturer code or device type identifier than the device description assigned to that object in the project tree.