Troubleshooting Persistent Analog Input (AI) Channel Faults (QBAD / Bad Signal) in PCS 7

Troubleshooting Persistent Analog Input (AI) Channel Faults (QBAD / Bad Signal) in PCS 7

Persistent bad signal quality (QBAD = 1, ST = 16#00) on SIMATIC PCS 7 analog input channels—causing PID controllers to display 's' (substitute value)—is primarily caused by open/unwired spare channels on multi-channel AI modules, missing active bus modules on distributed ET 200 racks, or diagnostic latches in module driver blocks (MOD_D8_PN / MOD_1). On high-resolution AI modules, unshielded or floating spare channels trigger internal ADC group diagnostic errors that passivate entire channel groups. To resolve this without stopping the plant, deactivate unused channels in HW Config or short-circuit open terminals, toggle the ACC_MODE parameter on the module driver block, and ensure distributed racks utilize active bus modules with proper shield connections.

Table of Contents

Mechanism of Analog Channel Passivation and Quality Code Evaluation

In SIMATIC PCS 7 (V8.0 through V9.0), analog signal acquisition adheres to strict NAMUR NE43 and IEEE 754 quality code standards. When an analog input module (e.g. ET 200M AI 8x16-bit 6ES7331-7NF00-0AB0 or ET 200SP AI 8xI 2-wire 6ES7134-6TD00-0CA1) detects a hardware malfunction, channel wire break, or ADC out-of-range condition, it triggers an asynchronous diagnostic interrupt (OB82) to the S7-400 CPU.

The PCS 7 Basis Library diagnostic driver (MOD_1 or MOD_D8_PN) processes the diagnostic data record and updates the channel driver Pcs7AnIn (FB1869). If a fault is confirmed, Pcs7AnIn sets output QBAD = 1 and assigns Quality Code ST = 16#00 (Bad). Downstream Advanced Process Library (APL) technological blocks, such as PID controller PIDConL (FB1874), detect bad signal quality and automatically switch into safety substitute mode, displaying a prominent yellow 's' symbol on the WinCC faceplate to warn operators that closed-loop control is operating on frozen substitute data.

Root Causes of Persistent QBAD and 's' Indications in PCS 7

Commissioning engineers frequently struggle with cases where channel faults persist even after disabling diagnostics in HW Config. Investigation typically reveals three root causes:

  1. Floating / Open Unused Channels: High-resolution multi-channel analog modules evaluate channels in paired ADC groups (e.g. channels 0/1, 2/3). If an unused spare channel is parameterized as active (e.g., 4-20mA or 2-wire RTD) but has no physical wires connected, electromagnetic noise induces a floating potential that exceeds the common-mode voltage limit ($U_{CM}$). The ADC flags a group diagnostic error, passivating the adjacent connected channel!
  2. Passive Bus Connectors vs Active Backplane Bus: Standard ET 200M racks utilizing passive U-shaped bus connectors lack hot-swap bus isolation. Electrical noise, backplane contact oxidation, or loose module seating triggers sporadic I/O access errors (OB122), causing driver blocks to latch in a faulted state. Racks must utilize Active Bus Modules (6ES7195-7HD10-0XA0) on a DIN rail for hot swapping (6ES7195-1GA00-0XA0).
  3. Diagnostic Record Lock and ACC_MODE: On PROFINET ET 200 stations, driver block MOD_D8_PN reads diagnostic records using parameter ACC_MODE. If a transient wire break occurred during loop testing, the driver may fail to re-read the cleared diagnostic record. Toggling ACC_MODE from 1 to 0 and back to 1 forces an acyclic record re-read (RDREC), clearing the stale latch.

Comparison of Hardware and Driver Diagnostic Fault Triggers

The following table compares different triggers of analog channel passivation and their specific remediations:

Diagnostic TriggerPhysical SymptomDriver Block ReactionResolution MethodFloating Spare ChannelChannel unwired; module SF LED activeEntire 2-channel ADC group passivated (QBAD = 1)Deactivate channel in HW Config or jumper terminals (short circuit)Excessive Common Mode ($U_{CM}$)Potential difference between M- and chassisSporadic channel overflow (16#7FFF)Connect M- terminals of all channels to central analog groundStale Diagnostic RecordField wiring repaired, but QBAD remains 1MOD_D8_PN holds latched fault stateToggle input ACC_MODE from 1 -> 0 -> 1 on MOD_D8_PN blockPassive Backplane NoiseRandom channels drop across entire rackCPU reports OB122 (I/O access error)Replace passive U-connectors with Active Bus Modules (6ES7195-7HD10-0XA0)Missing Shield Connection50/60 Hz noise on 4-20mA signalSignal oscillates out of measuring rangeInstall Siemens shield connection element (6ES7390-5AA00-0AA0)

Step-by-Step Procedure to Diagnose and Eliminate AI Channel Faults

Follow this procedure to locate and eliminate persistent analog channel faults online:

  1. Identify Module Fault Status in HW Config:
    - In HW Config, switch to Online view (Target System -> Open Online).
    - Double-click the faulted AI module and open the Diagnostic Interrupt tab.
    - Read the exact hardware error: check whether 'Wire break', 'Underflow', or 'Common mode fault' is reported on specific channels.

  2. Deactivate or Terminate Unused Spare Channels:
    - In HW Config offline, open Module Properties -> Inputs tab.
    - For all unused spare channels, change the Measurement Type from 4-20mA to Deactivated.
    - If deactivating in HW Config requires a CPU STOP that cannot be scheduled immediately, physically short-circuit the unused positive and negative terminal screws (jumper terminal M+ to M-) or place a 250-ohm resistor across the loop terminals.

  3. Toggle ACC_MODE on the Module Driver Block:
    - In the CFC chart containing the module driver (located in the system chart @... generated by the Driver Generator), locate MOD_D8_PN or MOD_1.
    - Locate parameter ACC_MODE (Diagnostic Access Mode).
    - Change ACC_MODE from 1 to 0, wait 5 seconds, and change back to 1.
    - This reinitializes acyclic diagnostic reading, clearing any stale latch in the driver memory.

  4. Verify Active Bus Module Installation:
    - Inspect the physical ET 200M / ET 200SP rack. Ensure active bus units are securely snapped onto the DIN rail with the grounding spring making solid contact with the metal rail.

Verification

Verify channel fault elimination in CFC and WinCC Runtime:
1. In the CFC Editor, open the chart containing Pcs7AnIn and switch to Online test mode (Test -> Watch on).
2. Confirm that Pcs7AnIn.QBAD = 0 (False) and output PV_Out.ST = 16#80 (Good).
3. Open the downstream PIDConL faceplate in WinCC Runtime. Verify that the yellow 's' substitute value indicator is completely cleared.
4. Confirm that the PID controller operates normally in Automatic mode without unexpected setpoint or output freezes.

Limitations and Operational Precautions

  1. HW Config Download Restrictions: Downloading modified channel parameters in HW Config requires a CPU STOP unless the automation system is an S7-400H / CPU 410-5H configured for Configuration in RUN (CiR). If CiR is not available, use physical terminal jumpers until a planned shutdown.
  2. Safety Module Passivation: On fail-safe analog modules (e.g. ET 200M F-AI 6ES7336-4GE00-0AB0), clearing a channel fault requires a fail-safe reintegration command via F_QUICK_I or faceplate acknowledgment.
  3. Transmitter Power Supply: Verify 2-wire vs 4-wire transmitter wiring. Configuring a 2-wire transmitter module for a 4-wire active transmitter sends 24V loop power into an active output, destroying the input channel.

Engineer FAQ

Why does my PID controller show an 's' symbol in WinCC?

The 's' symbol on APL faceplates indicates that the block is receiving a substitute value (SubstPV) because the interconnected channel driver (Pcs7AnIn) has detected bad signal quality (QBAD = 1 / ST = 16#00).

Why do open spare channels affect connected working channels?

Multi-channel analog cards share internal analog-to-digital converters (ADCs) across channel pairs. An open, floating spare channel can float to a high common-mode voltage, causing the shared ADC to report group diagnostic errors that passivate all channels in that pair.

What does the ACC_MODE parameter do on MOD_D8_PN?

ACC_MODE configures how the PCS 7 Basis Library diagnostic driver accesses peripheral diagnostic data. Toggling ACC_MODE forces the driver to execute an acyclic diagnostic re-read, clearing stale latched errors after wiring faults have been repaired.

Technical References

Related Articles

Related Tags

  • Analog Input Fault
  • QBAD
  • Pcs7AnIn
  • PIDConL Substitute Value
  • ACC_MODE
  • ET 200M Active Bus
6 respuestas