Resolving SITRANS Library SipPS2 Valve Control Failures: QWronDev Error and Simulation Quality Code 16#60

In SIMATIC PCS 7 with SITRANS Library V6.0, the SipPS2 function block (FB2613) triggering output QWronDev = 1 ('Wrong Device' faceplate alarm) occurs when the GSD file revision configured in HW Config does not match the exact Electronic Device Description (EDD) or device profile (PA Profile 3.00 vs 3.01/3.02) parameterized in SIMATIC PDM. The second issue—receiving status 16#3F from the positioner causing the block to display quality code 16#60 (Simulation mode) instead of Local mode—results from an unaligned Status Byte mapping in the cyclic input telegram. Aligning the GSD version with the physical positioner firmware and parameterizing the PDM profile correctly resolves both defects.

SITRANS Library SipPS2 Architecture and Cyclic Telegram Mapping

The Siemens SITRANS Library provides dedicated driver and control blocks for field instruments operating on PROFIBUS DP, PROFIBUS PA, and HART. For the SIPART PS2 intelligent electropneumatic valve positioner, the standard library block is SipPS2 (FB2613 in SITRANS Library V6.0).

SipPS2 manages bidirectional communication: it cyclically commands the valve setpoint (SP) while reading actual position feedback (Rbk), valve state, operating hours, and detailed diagnostic alarms. To perform diagnostics, SipPS2 reads device identification bytes and status bytes embedded in the cyclic PROFIBUS PA telegram. If the telegram format differs from the block's internal decoding table, functional failures immediately emerge.

Root Cause 1: Device Identification Mismatch and QWronDev = 1

When the block output QWronDev transitions to 1, the WinCC APL-style faceplate displays the alarm banner 'Wrong Device' in bright red, blocking remote setpoint control. This occurs because SipPS2 performs an identity check:

During initialization, the block queries the device's diagnostic profile telegram (DIAG_VAL) or PDM identification.
If the positioner is configured in HW Config using a generic PA Profile 3.00 GSD (e.g., siem8079.gsd) while the physical instrument runs firmware requiring manufacturer-specific GSD (e.g., si018079.gsd or Profile 3.02), QWronDev asserts 1.

According to the official Siemens document Devices in the SITRANS Library V6.0 (Entry ID: 109738509), exact pairing between the hardware GSD, EDD version, and block version is mandatory.

Root Cause 2: Status Byte 16#3F and Quality Code 16#60 Simulation State

The second common defect occurs when switching the valve from remote to local mode. The SIPART PS2 transmits an IEEE 754 floating point value accompanied by an 8-bit Quality Code (Status Byte):

When in local manual mode, certain SIPART PS2 firmware versions transmit Status Byte 16#3F (which corresponds to PA Profile 'Good (cascade) - Local override').
The SipPS2 block in SITRANS Library V6.0 interprets bit combinations within 16#3F as a simulation flag if the simulation bitmask is active, mapping the block's RbkLi.ST to 16#60 (Simulation mode active).

Instead of showing that the field valve is in manual local operation, the operator faceplate misleadingly indicates that the valve is running in software simulation.

Step-by-Step Resolution Workflow: HW Config, PDM, and CFC Block Alignment

To resolve both QWronDev and the simulation status anomaly:

Identify Physical Hardware and Firmware: Open SIMATIC PDM. Connect to the SIPART PS2 and inspect Diagnostics > Device Identification. Note down the exact firmware version (e.g., FW 4.00.00, 5.00.00) and communication type (PA vs FF).
Verify Correct GSD File in HW Config: In HW Config, check which GSD file represents the SIPART PS2. Replace generic profile GSDs with the specific manufacturer GSD matching the firmware (e.g., si028079.gsd for newer units).
Update PDM Device Description: In PDM Device Integration Manager, ensure the latest certified EDD for SITRANS Library V6.0 is installed and assigned to the device object in the Process Device Plant View.
Parameterize Feature Bits in CFC: In the CFC chart, inspect the SipPS2 block's Feature input. Verify that status evaluation features match the device profile.
Compile and Download: Perform a CFC compile with 'Generate Module Drivers' checked. Download changes to the AS.
Reset Positioner: Cycle 24 VDC bus power to the SIPART PS2 to force a fresh cyclic parameter exchange.

SIPART PS2 Device Profile and Telegram Comparison

The following table summarizes GSD file types and profile behaviors for the SIPART PS2 in PCS 7:

Configuration ProfileGSD File IdentifierIdentification Byte ExpectedQWronDev Trigger ConditionLocal Mode Quality CodeStandard PA Profile 3.00pa139710.gsdGeneric 0x9710Asserts 1 if SITRANS Library expects specific EDDStatus 16#3F mapped to 16#60Manufacturer Specific FW <4.0si018079.gsdSiemens 0x8079Asserts 1 if device runs FW 5.0+Status 16#48 (Good Local)Manufacturer Specific FW >=5.0si028079.gsdSiemens 0x8079 (Rev 2)Clean 0 (Matched)Status 16#80 / 16#84 (Good Normal)SITRANS Library V6.0 TargetCertified Library TemplateExact EDD MatchClean 0Correctly resolved local state

Verification

Verify valve control and status resolution through the following steps:

Open the CFC chart online and monitor SipPS2 (FB2613). Confirm that output QWronDev = 0.
Open the WinCC faceplate for the valve. Confirm that the red 'Wrong Device' error banner has disappeared.
Move the physical valve positioner into local manual mode via its pushbuttons. Confirm that the faceplate indicates 'Local Mode' and that RbkLi.ST displays healthy status (16#80 or 16#84), not simulation code 16#60.
Switch the valve back to remote automatic mode. From the WinCC faceplate, adjust setpoint SP and verify that the valve travels smoothly to the demanded position.

Limitations and Operational Precautions

Consider these operational rules when maintaining fieldbus positioners:

Never Change GSD Configuration in HW Config While Plant Is Running: Replacing a GSD file in HW Config requires downloading the hardware configuration, which will disrupt the PROFIBUS segment and trip operating valves.
Pneumatic Calibration Requirements: When re-parameterizing a SIPART PS2 via PDM, do not initiate the automatic initialization routine (INIT) while process fluid is flowing through the valve, as the positioner will stroke 0% to 100%.
Coupler Baud Rates: Ensure AFDiSD or DP/PA links operate at supported baud rates (typically 45.45 kbit/s or 31.25 kbit/s).

Engineer FAQ

Where can I find the certified GSD file for SIPART PS2?

Certified GSD files are supplied on the SITRANS Library installation disc and on Siemens Industry Online Support under the SIPART PS2 product page.

How does SipPS2 detect valve travel deviation?

The block compares setpoint SP and readback Rbk against parameterized deadbands and tolerance times (PosMonTime), asserting alarm PosErr if the valve fails to reach position.

Can SipPS2 read internal valve diagnostics like stroke counters?

Yes, when coupled with PDM and appropriate cyclic telegram configurations, SipPS2 reads total stroke counts, direction reversals, and temperature alarms.