Troubleshoot a PCS 7 Analog Channel Block in PLCSIM Without I/O Hardware

If a PCS 7 analog channel block does not produce the expected value in PLCSIM after module-driver-generated interconnections were removed, identify the exact block and Advanced Process Library (APL) version before changing Mode or DataXchg. Siemens documents that channel-block behavior depends on whether “Generate module driver” and the DataXchg1 connection are used; the reported values 16#80000203, 16#4, and 16#14 are not established as universal settings by the available version-unspecified source.

Symptoms and applicability

The discussion describes a PLCSIM test after removing green interconnections and manually setting Mode to 16#80000203, without a satisfactory result. A suggested change to the first DataXchg parameter to 16#4 reportedly helped one test environment. A later reply says that when an analog address is used for a channel absent from the hardware configuration, set DataXchg to 16#4 for the first parameter or 16#14 for the second parameter. The source does not identify the exact channel block, APL release, driver-generation state, or explain the field meanings for these constants.

Why manually set values may not resolve the channel

PCS 7 channel blocks ordinarily receive driver and diagnostic interconnections through module-driver generation. Siemens' APL V9.1 SP1 Readme documents behavior changes when module drivers are not generated, when third-party diagnostic blocks are used, or when a channel block lacks a DataXchg1 connection to PCS 7 Basis Library blocks. For those stated cases it instructs users to set Feature.Bit27 (the “Initial execution identifier of the diagnostic blocks”) to 1 at the relevant channel blocks. That release-specific instruction does not prove that a particular value on DataXchg, DataXchg1, or Mode is right for an unidentified version or block.

Method: determine which configuration path applies

Record the channel block name and block type/version from the actual CFC chart, and identify the installed PCS 7/APL version. Do not assume a block is Pcs7AnIn solely from the symptom.
Determine whether the analog channel exists in HW Config and whether the relevant module driver was generated. Inspect the actual CFC connections to the block's driver/diagnostic inputs, including Mode, DataXchg, and DataXchg1 where present.
If the hardware channel exists and its module driver should supply those signals, restore and verify the intended generated connections using the project's normal compile workflow rather than leaving conflicting manual values. The source does not specify hardware or driver settings, so no precise menu or compile options beyond the cited documentation can be prescribed here.
If module-driver generation is intentionally not used, consult the Readme/help for the exact installed APL version. For APL V9.1 SP1, Siemens says to set Feature.Bit27 to 1 when there is no DataXchg1 connection to PCS 7 Basis Library function blocks, or where the stated third-party-diagnostic condition applies.
Treat the source's DataXchg=16#4 / 16#14 suggestion as an environment-specific report. Before using either constant, verify its meaning and expected behavior in the block help for the exact version and hardware path. Do not transplant these values to another block or release based only on the forum result.

Interpret the reported Mode and DataXchg values cautiously

The ticket says Mode was set to 16#80000203, but it does not provide enough block/version context to explain or validate that encoding. The first response suggesting DataXchg=16#4 reports one successful test; the later answer distinguishes first versus second DataXchg parameter as 16#4 versus 16#14 when a channel address is absent from hardware. Siemens' APL V9.1 SP1 Readme corroborates the importance of DataXchg1 connectivity and Feature.Bit27 in specific no-driver/third-party conditions, but the opened reference does not validate the ticket's hexadecimal constants. Keep the reported values scoped to the original test context.

Verification

With a controlled PLCSIM configuration, observe the channel block's value and relevant status/diagnostic outputs after applying a version-appropriate configuration. Confirm that the signal source actually supplies a value, the block's driver/diagnostic inputs have the intended connections or documented manual setup, and no contradictory generated connections remain. Record whether the CPU stays in RUN and whether the expected output changes. Do not infer correct real-I/O diagnostics or hardware behavior from a simulator result without testing against the actual supported hardware configuration.

Limitations and Operational Precautions

The original thread was split from another discussion and omits the attached image, exact block type, APL/PCS 7 versions, hardware module, CFC driver-generation choices, and full parameter values. The reported successful 16#4 test is not a universal Siemens guarantee. The version-matched APL V9.1 SP1 Readme provides a conditional instruction about Feature.Bit27, but the ticket's release is unknown. Manual changes to channel diagnostic and value-quality inputs can change what the block evaluates; confirm the effect in the exact block documentation and project design, particularly before using the pattern outside simulation.

Engineer FAQ

Does Mode=16#80000203 fix every analog-channel simulation issue? No. The source gives the value without identifying the block revision or configuration, so applicability must be checked against the installed block help and driver setup.

Is DataXchg=16#4 a generally valid replacement for module-driver connections? No. It is a reported workaround for one test, not a verified general instruction. Siemens' APL V9.1 SP1 guidance instead identifies a conditional Feature.Bit27 setting for specified cases without DataXchg1 or using third-party diagnostics.

What should be checked when analog hardware is not present? Confirm whether the channel block is intentionally configured without a generated module driver, inspect its relevant input connections, and follow documentation for the exact library release. Do not assume the simulation should be configured as though a physical module were present.

Technical References

Siemens, PCS 7 Advanced Process Library Readme V9.1 SP1 (Online), A5E51158325-AA11, §4.1, “What's New in Version 9.1?” The release note documents the behavior-change conditions involving “Generate module driver,” third-party diagnostic blocks, and DataXchg1, and specifies the conditional Feature.Bit27 setting. The Siemens attachment URL returned HTTP 403 in this research session; its indexed official Siemens text was reviewed, but the PDF itself could not be opened: https://support.industry.siemens.com/cs/attachments/109781735/AdvLib-Readme-Online_en-US.pdf
Siemens Industry Online Support forum, “Analogue Scaling with PCS7 AP Library,” Topic 227622, source-reported discussion of Pcs7AnIn (FB1869), Mode, module-driver interconnections, Feature.bit27, and DataXchg1. This is a forum exchange, not a manufacturer specification: https://support.industry.siemens.com/forum/ww/cs/post/900947/

Related Tags

PCS 7, PLCSIM, APL, analog channel

Troubleshoot a PCS 7 Analog Channel Block in PLCSIM Without I/O Hardware