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

Troubleshooting Frozen Analog Channel Drivers and RTD Measurements After PCS 7 V9.1 Upgrades

Troubleshooting Frozen Analog Channel Drivers and RTD Measurements After PCS 7 V9.1 Upgrades

Following an upgrade from PCS 7 V8.0 to V9.1 SP2, analog channel drivers freezing with PV_Out unchanging (despite valid PV_In) and Pt100 RTD measurements failing completely occurs because legacy channel blocks (CH_AI) were not updated to APL V9.1 block types (Pcs7AnIn, FB 1869) or the hardware module is missing from the PCS 7 V9.1 released modules catalog. Furthermore, Pt100 RTDs fail when the driver is parameterized for 4-20mA linear scaling instead of RTD temperature linearization, or when the Module Driver Generator fails to link diagnostic MODE parameters during compilation.

Table of Contents

Root Causes of Frozen Channel Drivers After Major Upgrades

Migrating an automated facility across multiple PCS 7 generations—such as upgrading from PCS 7 V8.0 Upd 1 to PCS 7 V9.1 SP2 UC1—introduces significant updates to the driver block abstraction layer and hardware diagnostic mechanisms:
1. Block Type Signature Discrepancies: In PCS 7 V8.0, older projects frequently utilized classic Standard Library drivers (CH_AI, FB 34) or early APL drivers (FB 1869). If the project was migrated without executing Block Types -> New Version / Clean up, the CFC runtime database retains obsolete internal memory offsets, causing the driver algorithm to freeze and fail to transfer PV_In to PV_Out.
2. Unreleased Hardware Modules: PCS 7 V9.1 includes an updated Released Modules Catalog. If legacy ET 200M or ET 200S analog modules installed in the field were discontinued and omitted from the V9.1 catalog, the Module Driver Generator (Generate module drivers) skips the module, leaving diagnostic and mode interconnection pins (MODE, DataXchg, MS) unconnected.
3. Pt100 RTD Measurement Scaling Failure:
* Standard 4-20mA current loops supply raw integers from $0$ to $27648$, which Pcs7AnIn scales linearly to physical engineering units (Scale.Low to Scale.High).
* Pt100 RTD temperature modules transmit temperature directly as an integer multiplied by 10 or 100 (e.g., 25.4 deg C = 254).
* If a Pt100 input is connected to Pcs7AnIn with standard 4-20mA scaling (0 to 100%), the block clamps or outputs incorrect values. The driver requires configuring the hardware module in HW Config for RTD and ensuring the driver block operating mode matches RTD processing (MODE parameter set to temperature mode).

Step-by-Step Diagnostic and Remediation Procedure

Follow this procedure to restore analog channel processing and RTD measurements.

Prerequisites

  • SIMATIC Manager open with write access to the migrated PCS 7 V9.1 project.
  • Hardware catalog confirmed against the PCS 7 Released Modules manual.

Step 1: Verify Hardware Module Release Status in HW Config

  1. In SIMATIC Manager, open HW Config.
  2. Locate the analog input module in the rack (e.g., ET 200M 6ES7 331-7KF02-0AB0 or RTD module 6ES7 331-7PF01-0AB0).
  3. Check the module catalog tree:
    * Verify that the module is selected from the PCS7_V91 profile catalog rather than the generic Standard catalog.
    * If the module appears with a red line or missing description, update the module order number (MLFB) or replace with a released hardware variant.
  4. Double-click the RTD module to open Properties:
    * Under the Inputs tab, verify that measurement type is set to RTD and sensor type to Pt 100 standard (or Pt 100 climate).
  5. Execute Station -> Save and Compile.

Step 2: Update Block Types from APL V9.1 Library

  1. In SIMATIC Manager, open the Master Data Library.
  2. Copy the latest version of Pcs7AnIn (FB 1869) from the PCS 7 APL V9.1 library into the project library.
  3. Open any CFC chart and select Options -> Block Types....
  4. In the Block Types dialog, select Pcs7AnIn in the Master Data Library and transfer it to the Chart folder.
  5. Select New Version and confirm updating all instances across the project.

Step 3: Configure Pt100 Channel Parameters in CFC

  1. Open the CFC chart containing the RTD temperature channel.
  2. Ensure the input pin PV_In is symbolically connected to the hardware address (e.g., IW 256).
  3. Set the scaling parameters on Pcs7AnIn:
    * For standard Pt100 modules operating with 1 decimal place (0.1 deg C resolution), verify whether the raw signal requires linear conversion or if the module driver handles temperature mode via MODE.
    * If using MODE = 16#202 (standard RTD mode generated by module drivers), set Scale.High = 850.0 and Scale.Low = -200.0 (matching the Pt100 measurement range).
  4. Verify that SimOn = 0 (Simulation mode disabled) and SubsOn = 0 (Substitute value disabled).

Step 4: Recompile Entire Program with Generate Module Drivers

  1. In CFC, select Chart -> Compile -> Entire Program.
  2. Check the box for Generate module drivers.
  3. Execute compilation.
  4. Review the compiler log: verify that module drivers (MOD_D1, RACK) are created and interconnected to the MODE and DataXchg pins of Pcs7AnIn without warnings.

Verification

  • In CFC dynamic test mode, inspect Pcs7AnIn:
  • Confirm that PV_In reflects raw field integer counts.
  • Confirm that PV_Out dynamically fluctuates in real time with temperature changes.
  • Verify that output Bad = 0 and quality code PV_Out.ST = 16#80 (Good).
  • On the WinCC OS faceplate, confirm that the analog temperature indicator displays the correct engineering value (e.g., 24.5 °C) without warning icons.

Limitations and Operational Precautions

  • Avoid Mixing Standard and APL Drivers: Do not mix legacy CH_AI and modern Pcs7AnIn blocks within the same automation station; standard and APL drivers utilize conflicting diagnostic driver chains.
  • CPU Download Requirements: Updating block types across hundreds of charts requires a Changes Only download in RUN mode if interfaces are backward compatible, but significant library updates may necessitate a CPU STOP if instance memory layout shifts.
  • ET 200S vs. ET 200SP: Legacy ET 200S serial/analog modules have different diagnostic architectures than modern ET 200SP modules; ensure correct driver families are applied.

Engineer FAQ

  • Why did PV_Out freeze even though Bad remained 0?
    When a block type is replaced without updating instance DB structures or when the block execution sequence is corrupted, the block algorithm exits early, leaving output variables frozen at their last calculated value without asserting the Bad fault output.
  • What does the MODE parameter on Pcs7AnIn do?
    The MODE parameter defines the operating mode of the hardware channel (e.g., 4-20mA, 0-10V, Pt100 standard). It is automatically populated by the Generate module drivers compiler task.
  • Can Pt100 RTD values be read directly without Pcs7AnIn?
    Yes, but using Pcs7AnIn is mandatory in PCS 7 to integrate module failure diagnostics, wire-break detection, operator simulation, and OS faceplate alarming.
  • Why does Pt100 read 254 instead of 25.4?
    Siemens analog input modules in RTD mode transmit temperature in tenths of a degree (0.1 deg C). If raw integer 254 is not scaled with a factor of 0.1, the value displays as 254.
  • Where do I find the list of released modules for PCS 7 V9.1?
    Consult the official Siemens manual: SIMATIC PCS 7 - Released Modules for PCS 7 V9.1 (SIOS Entry ID 109801081).

Technical References

  • Siemens Industry Online Support Entry ID 109801081: SIMATIC PCS 7 Advanced Process Library (APL) Function Manual.
  • Siemens System Manual: Process Control System PCS 7 - Released Modules V9.1 SP2.
  • Siemens Technical Guide: Channel Driver Architecture and Module Driver Generator in PCS 7.

Related Articles

Related Tags

  • PCS 7
  • APL
  • Pcs7AnIn
  • Channel Driver
  • Analog Input
  • Pt100
  • RTD
  • Troubleshooting
20 respuestas