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

Troubleshooting QBAD=1 and Simulation Lock (Yellow Hand) on Analog Channel Drivers in SIMATIC PCS 7

Troubleshooting QBAD=1 and Simulation Lock (Yellow Hand) on Analog Channel Drivers in SIMATIC PCS 7

In SIMATIC PCS 7, an analog channel driver displaying QBAD = 1 and a yellow hand simulation icon indicates bad signal quality and active simulation. QBAD = 1 occurs when the MODE parameter is uninitialized (16#00000000) due to omitted module driver generation, when field current drops below 3.6 mA (wire break/NAMUR underflow), or when scaling mismatches occur. Clear QBAD by compiling module drivers, restoring healthy 4-20 mA current, and deactivating SimOn.

Table of Contents

Diagnostic Overview and Faceplate Visual Indicators

During plant operation or commissioning of an analog measurement loop (such as a vessel weighing scale, flowmeter, or pressure transmitter) in SIMATIC PCS 7:
* On the WinCC Operator Station screen, the process value (PV) for the instrument is greyed out and fails to display dynamic field values.
* An icon depicting a yellow hand (or simulation indicator) is superimposed on the block icon and faceplate.
* The automation engineer inspects the Continuous Function Chart (CFC) and observes that the channel driver block (Pcs7AnIn or Classic CH_AI) has its digital output asserted: QBAD = 1 (or Bad = 1).
* The engineer verifies that the physical I/O card in the cabinet shows healthy green status LEDs and field cable wiring appears intact.

Because physical cabinet hardware appears functional, engineers struggle to identify why the channel driver continues asserting QBAD = 1 and why the block is locked in simulation mode.

Root Cause Analysis: Why Channel Drivers Assert QBAD=1

In SIMATIC PCS 7 channel blocks, QBAD = 1 is the master quality assertion indicating that the raw signal cannot be validated for process control. It is triggered by four distinct conditions:

  1. Uninitialized or Unlinked MODE Parameter:
    * The channel driver does not read raw hardware directly; it interprets peripheral counts based on its MODE input word.
    * If CFC charts were compiled without checking 'Generate module drivers', or if the I/O card was integrated via an unmapped GSD file, the MODE parameter remains default 16#00000000.
    * An uninitialized MODE tells the driver that the hardware subsystem has not validated the channel, forcing QBAD = 1 immediately.

  2. NAMUR NE 43 Measuring Range Violations (Wire Break / Overflow):
    * For standard 4-20 mA analog inputs, peripheral counts range from 0 to 27648.
    * Standard industrial transmitters adhere to NAMUR NE 43:

    • Normal Range: 3.8 mA to 20.5 mA (-345 to 28512 counts).
    • Undershoot: 3.6 mA to 3.8 mA.
    • Wire Break / Failure: Current drops below 3.6 mA (counts < -691 or -4864).
    • Short Circuit / Overflow: Current exceeds 21.0 mA (counts > 29376).
    • If a field transmitter is unpowered, if a terminal wire is loose, or if instrument calibration outputs 3.2 mA, the channel driver detects a wire break and asserts QBAD = 1.

  3. Missing Load Power to Analog Module:
    * If external 24V DC auxiliary load voltage to the analog module front connector (e.g. terminals 1 and 20 on SM 331) is disconnected, the module ADCs shut down, forcing raw counts to 16#7FFF (Overflow) and asserting QBAD = 1.

The Interplay Between QBAD and Simulation Mode (Yellow Hand)

The appearance of the yellow hand represents a secondary condition:

  • Simulation Mode (SimOn = 1):
  • In PCS 7 APL, when QBAD = 1 disrupts plant operation during commissioning, engineers frequently enable Simulation Mode on the faceplate or force input parameter SimOn = 1 in CFC.
  • In simulation mode, the channel driver bypasses the bad field input and accepts a manually entered simulation value (SimPV_In), allowing downstream technological blocks (MonAnL, PIDConL) to continue operating.
  • The yellow hand is an explicit operator alert warning that the displayed value is synthetic and does not reflect physical field conditions.
  • Simulation mode does not clear QBAD; it merely decouples downstream logic from the fault.

Step-by-Step Diagnostic and Troubleshooting Workflow

1. Inspect Raw Peripheral Counts in CFC Test Mode

  1. Open the CFC chart containing Pcs7AnIn (or CH_AI).
  2. Activate Test Mode (glasses icon).
  3. Inspect input pin PV_In:
    * If PV_In = 16#7FFF (+32767): Hardware detects overflow, short circuit, or missing load power.
    * If PV_In = 16#8000 (-32768): Hardware detects underflow, wire break, or open loop.
    * If PV_In is between 0 and 27648: The raw signal is physically healthy.

2. Verify and Re-link the MODE Parameter

  1. In CFC Test Mode, inspect input pin MODE:
    * If MODE = 16#00000000, module driver generation has failed.
  2. Select Chart > Compile > Charts as Program.
  3. CHECK the box: Generate module drivers, select Scope: Entire program, and compile.
  4. After compilation, verify MODE evaluates to 16#80000203 (for 4-20 mA 2-wire) or 16#80000204 (for 4-wire).

3. Measure Field Current with a Multimeter

  1. Insert a calibrated digital multimeter in series with the 4-20 mA current loop at the cabinet terminal strip.
  2. Measure the physical current:
    * Current must measure strictly between 4.0 mA and 20.0 mA.
    * If current is below 3.6 mA, inspect the field transmitter power supply, check loop isolators, or re-zero the weighing scale transmitter.

4. Deactivate Simulation Mode

  1. In CFC, locate input pin SimOn on Pcs7AnIn.
  2. Ensure SimOn = 0 (FALSE).
  3. If simulation was locked from WinCC: open the WinCC faceplate, navigate to the Parameter View, and uncheck the Simulation box.
  4. Once field current is valid and simulation is off:
    * QBAD transitions from 1 to 0.
    * Signal status ST updates to 16#80 (Good).
    * The yellow hand icon disappears from the WinCC faceplate.

Channel Driver Signal Quality and QBAD Status Matrix

Loop StatePhysical CurrentRaw Counts (PV_In)Driver Output Bad / QBADSignal Status (ST)WinCC Visual RepresentationHealthy 50% Span12.0 mA138240 (FALSE)16#80 (Good)Normal value display; green statusWire Break / Open Loop0.0 mA< -4864 / 16#80001 (TRUE)16#00 (Bad)Greyed out value; red cross iconNAMUR Underrange3.7 mA-4350 (FALSE)16#68 (Uncertain)Valid scaled value; yellow warningSimulation Mode ActiveAny valueBypassed by SimPV_InDependent on field16#60 (Simulated)Yellow hand icon displayedUnlinked MODE = 012.0 mA138241 (TRUE)16#00 (Bad)Greyed out value; uninitialized driver

Verification

  1. Measure 12.0 mA at the field terminal strip.
  2. In CFC, confirm Pcs7AnIn.PV_In reads approximately 13824 counts.
  3. Confirm parameter MODE evaluates to 16#80000203.
  4. Confirm Pcs7AnIn.SimOn = 0.
  5. Observe block outputs: verify Bad = 0 (or QBAD = 0) and PV_Out.ST = 16#80.
  6. In WinCC Runtime, confirm the scale weight displays live decimal units with zero yellow hand or warning icons.

Limitations and Operational Precautions

  • Never Leave Production Loops in Simulation: Operating plant processes with simulation mode active masks physical sensor failures and can lead to tank overflows or equipment overpressurization. Always clear simulation flags before production handover.
  • Transmitter Fault Current Settings: Ensure field transmitters are configured to drive NAMUR NE 43 fault currents (typically 3.6 mA on low fault or 21.5 mA on high fault) matching PCS 7 driver thresholds.
  • Scale Calibration Coordination: Zero-point calibration of load cells must be coordinated with the channel driver's Scale.Low and Scale.High parameters to maintain measurement linearity.

Engineer FAQ

What is the difference between QBAD and Bad?

QBAD is the parameter name on Classic driver blocks (CH_AI, CH_DI). Bad is the parameter name on modern Advanced Process Library blocks (Pcs7AnIn, Pcs7DiIn). Both represent the identical signal quality failure.

Why did the yellow hand appear without an operator turning simulation on?

If an engineer set SimOn = 1 in the CFC chart during earlier testing and downloaded changes, the simulation setting remains permanently latched in CPU memory until explicitly reset to 0.

Can I force QBAD to 0 while the field loop is disconnected?

You can force QBAD = 0 by activating simulation mode (SimOn = 1) and entering a simulated value. You cannot force QBAD = 0 in normal mode if the physical counts violate measuring range limits.

Technical References

Related Articles

Related Tags

  • QBAD
  • Bad=1
  • Pcs7AnIn
  • Simulation Mode
  • Yellow Hand
  • MODE Parameter
6 respuestas