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

How to Diagnose and Resolve QBAD Faults on Digital Input Channels in PCS 7

How to Diagnose and Resolve QBAD Faults on Digital Input Channels in PCS 7

To resolve a QBAD = 1 (or Bad = 1) fault on a digital input channel driver block (Pcs7DiIn or F_CH_DI) connected to a field level switch (LSH) in SIMATIC PCS 7, inspect the physical field loop for wire breaks and verify the channel diagnostics configuration in HW Config. In PCS 7, a digital channel driver asserts QBAD = 1 when the underlying hardware module detects a physical loop disruption (such as an open circuit or sensor power loss), when the channel address is mapped to an un-updated Process Image Partition, or when the Driver Generator detects a diagnostic interrupt (OB82). Immediate resolution requires checking the CPU diagnostic buffer, verifying the terminal loop resistance on wire-break-enabled digital input cards, and ensuring the driver's Mode parameter matches the hardware configuration.

Table of Contents

Mechanics of Quality Evaluation (QBAD and Signal Status) in PCS 7

In the SIMATIC PCS 7 Advanced Process Library (APL) and S7 F Systems:
- The Role of the Channel Driver (Pcs7DiIn / F_CH_DI): Decouples physical controller I/O from technological process logic (MotL, VlvL, interlocks).
- Quality Status Bit (Bad / QBAD): When hardware diagnostics detect a channel fault, the driver asserts Bad = 1 (APL) or QBAD = 1 (F-Systems).
- Signal Status (Out.ST): In standard APL, the output structure's status byte changes from 16#80 (Good) to 16#00 (Bad).
- Process Safety Substitution: The driver substitutes a pre-configured safe value (typically 0 or the last valid state), forcing downstream interlocks into a safe trip state to prevent equipment damage.

Root Causes: Physical Loop Disruption vs. Hardware Diagnostic Faults

When a digital input channel connected to a critical level switch (LSH) reports QBAD:

Failure CategorySpecific MechanismDiagnostic IndicatorPhysical Field Loop OpenHigh-vibration level switch contacts, loose terminal block screws, or a severed field cable.Card channel LED unlit; CPU diagnostic buffer reports Wire break (Event ID 16#3842).Missing End-of-Line ResistorsHardware card has "Wire break check" enabled in HW Config, but the mechanical switch contact lacks a parallel/series resistor network to pass supervisory current.Input module red SF (System Fault) LED illuminated; channel asserts QBAD continuously.Process Image Partition MismatchThe I/O address of the DI channel is assigned to Process Image Partition 0 (OB1), but the channel driver runs in OB35 (100 ms).Driver reports Bad signal status due to asynchronous process image updates.Driver Generator InconsistencyHardware configuration was modified, but CFC was compiled without "Generate module drivers".Driver block disconnected from @ diagnostic driver blocks.

Wire Break and Diagnostic Interrupt Settings in HW Config

Standard digital input modules (e.g., SM 321, ET 200M, ET 200SP HA) offer selectable diagnostic capabilities:
* Dry Contact vs. NAMUR Sensors: A standard mechanical dry contact switch (open/closed) passes 0 mA when open. If the engineer checks "Wire break" on a standard DI module, the module interprets an open switch contact as a severed cable, triggering a false QBAD whenever the tank level is low!
* NAMUR Sensor Profiles: For genuine wire break monitoring on dry contacts, engineers must install an End-of-Line (EOL) resistor network (typically a 1 k$\Omega$ series and 10 k$\Omega$ parallel resistor) or use NAMUR proximity switches conforming to EN 60947-5-6.
* HW Config Setting: If using simple mechanical dry contacts without resistors, open HW Config for the digital input module, select the channel group properties, and uncheck the "Enable Wire Break Diagnostics" checkbox.

Method: Step-by-Step Diagnostic and Channel Recovery Workflow

Follow this procedure to identify and clear the QBAD condition:

Step 1: Inspect Controller and Module Diagnostics in STEP 7

  1. In SIMATIC Manager, select the AS station and open HW Config.
  2. Go online (Station -> Open Online).
  3. Look for modules displaying a red slash (fault indicator).
  4. Double-click the digital input module and select the Diagnostic Interrupt tab:
    - Identify the exact channel reporting Wire break, Short circuit to M, or External power supply missing.

Step 2: Test Physical Field Wiring with a Multimeter

  1. Disconnect field loop wires at the marshaling cabinet terminal block.
  2. Measure the loop voltage across the terminals:
    - For 24V DC discrete inputs: confirm presence of +24V DC sensor supply.
  3. Measure loop resistance:
    - With switch closed: confirm near-zero resistance ($< 10\ \Omega$ or matching series resistor).
    - With switch open: confirm loop resistance matches the parallel resistor ($\approx 10\ \text{k}\Omega$). If reading $\infty$ (open loop) on a wire-break-monitored channel, the field loop is severed.

Step 3: Reconfigure Channel Settings in HW Config

  1. If the field device is a standard mechanical switch without an EOL resistor pack:
    - Open module properties in HW Config.
    - Set the operating mode to Standard Digital Input (disable diagnostic interrupts and wire break monitoring).
  2. Verify the Process Image Partition (PIP):
    - Set the I/O address partition to PIP1 (or the partition matching your cyclic OB35 execution).
  3. Save, compile, and download HW Config to the CPU.

Step 4: Recompile Module Drivers in CFC

  1. In SIMATIC Manager, select the chart folder and execute Chart -> Compile -> Charts as Program.
  2. Ensure the checkbox Generate module drivers is checked.
  3. Select Changes Only and compile.
  4. Download changes to the AS CPU in RUN mode.

Verification

To verify that the channel is healthy and QBAD has cleared:
- Open the CFC chart hosting Pcs7DiIn in online Test Mode.
- Confirm that:
- Parameter Bad.Value = 0 (or QBAD = 0).
- Output signal status Out.ST reads 16#80 (Good).
- Parameter Out.Value accurately tracks the physical float switch position.
- Physically toggle the level switch float: verify that the channel transitions between 0 and 1 smoothly without triggering diagnostic alarms.
- Inspect the physical I/O card: confirm that the red SF (System Fault) LED is extinguished and the channel status LED illuminates green.

Limitations and Operational Precautions

  • Fail-Safe SIL Systems (F_CH_DI): On fail-safe digital inputs (F_CH_DI), safety regulations (IEC 61508) mandate wire break monitoring. You cannot simply uncheck wire break diagnostics on safety interlocks; physical loop integrity with approved resistor networks or fail-safe sensors is legally required.
  • Depassivation Requirements in F-Systems: Clearing the physical fault on an F_CH_DI channel will not automatically clear QBAD. S7 F Systems enforces safety latching; the channel requires an explicit acknowledgment pulse via input pin ACK_REI.
  • Process Simulation Caution: While troubleshooting, an engineer can set SimOn = 1 on Pcs7DiIn to temporarily force a good signal to avoid tripping active plant processes. Ensure simulation is deactivated immediately after wiring repairs.

Engineer FAQ

Why did QBAD appear only when the level switch was not actuated?

If wire break monitoring is enabled on an I/O card connected to a bare dry contact without parallel resistors, opening the contact drops loop current to zero, which the card misinterprets as a broken wire.

What is the difference between Bad on Pcs7DiIn and QBAD on F_CH_DI?

Bad is the boolean error flag in standard PCS 7 Advanced Process Library (APL) blocks. QBAD is the standardized fail-safe passivation output on S7 F Systems safety channel drivers.

How does the Driver Generator connect diagnostic data to the channel driver?

The Driver Generator automatically wires internal interconnect pointers between parameter Mode on Pcs7DiIn and the @ diagnostic blocks (MOD_D1, MOD_D2) during CFC compilation.

What happens if I replace an I/O card with a different revision?

If a replacement digital input card has a different part number or hardware revision, update the catalog entry in HW Config, recompile module drivers in CFC, and perform a download to ensure diagnostic telegrams align.

Technical References

  • Siemens Industry Online Support: SIMATIC PCS 7 Advanced Process Library (APL) Manual.
  • SIOS Entry 109742323: PCS 7 Compendium Part A - Configuration Guidelines (Section: Channel Drivers and Diagnostics).
  • SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Released Modules.
  • Siemens System Manual: Automation System S7-400 Module Specifications (Digital Input Modules).

Related Articles

Related Tags

  • QBAD
  • Pcs7DiIn
  • Channel Drivers
  • Level Switch
  • Diagnostics
  • APL
  • Industrial Automation
20 respuestas