Separate or Integrate ShrdResL in a PCS 7 Control Module Type

Separate or Integrate ShrdResL in a PCS 7 Control Module Type

A separate shared-resource CMT and a valve CMT containing ShrdResL are two possible project designs. Select the boundary according to interface ownership and the effect on existing instances. Siemens documents command multiplexing and technological-interface construction, but the available information does not establish a complete wiring example for either arrangement. Keep arbitration commands separate from actual valve feedback and resolve the release-specific connections before commissioning.

Table of Contents

Compare the Two Type Boundaries

Two project designs can be considered: a separate shared-resource CMT between equipment modules and the existing valve CMT, or a revised valve CMT containing the arbitration block. Neither is established here as a ready-made manufacturer template.

DesignInterface implicationEngineering decisionSeparate shared-resource CMTCommands cross an additional technological interface; valve feedback needs an explicit route.Assess whether retaining the existing valve type justifies the additional connections.Integrated valve CMTThe revised type exposes ownership, commands and valve status together.Assess the impact of changing the type on existing valve instances.

Choose by the actual interface requirements and migration impact, not by the number of visible blocks.

Documented Multiplexing Requirement

Siemens' V9.1 compendium describes switching command inputs between equipment-module sources and managing assignment. ShrdResL and ShrdResS are identified as APL options for supported Drive and Dose blocks. This establishes the arbitration architecture, not either proposed CMT boundary or its pin mapping. Compendium Part C, section 8.9.

Construct and Inspect the Selected Interface

Use the documented CMT interface method in a project copy:

  1. Open the type's CFC and place the required blocks. For integration, review the existing internal wiring before changing it.
  2. Define the project-specific connections using the installed block documentation. Preserve one resolved command path to the valve.
  3. Drag the required parameters and signals into "Technological I/Os" to create and assign interface objects.
  4. Inspect each object's "Attributes" mapping to the internal logic.
  5. Expose command and status requirements explicitly. For a separate type, identify both the requesting-module interface and the valve interface.
  6. Route inter-instance wiring through technological I/Os rather than leaving connections outside the technological model.

Siemens documents this representation and construction method. The particular ShrdResL and valve mapping must still be specified from the applicable releases. Engineering with CMT, sections 3.1 and 5.4.

Verification

Trace a command from each requesting module through the arbitration block to the valve. Trace physical feedback back to the consumers independently. Confirm that every inter-instance connection is visible in the technological model.

In a controlled test, compare single requests, conflicting requests and stop/abort handovers against the required ownership specification. Check actual valve feedback as well as allocation. For the documented V8.2 operator view, assignment and active-channel indications provide ownership evidence; they do not replace physical feedback. APL Operator Guide, section 2.6. No tests are claimed to have been performed.

Limitations and Operational Precautions

The application identifies no PCS 7, CFC, APL or valve block version. It also provides no confirmed final wiring. Consequently, neither candidate arrangement can be presented as a complete verified implementation.

Back up the project and existing types. Review affected instances before synchronizing a revised type. Do not bypass interlocks or release production changes merely because the CFC compiles. Establish the site's safe handover and recovery requirements before commissioning.

Engineer FAQ

Is the separate-CMT design mandatory? No documented requirement for that particular boundary is established here.

Is the integrated design automatically simpler? It reduces one visible boundary but can affect existing instances; assess both effects.

Where should feedback originate? Specify the actual valve status independently of arbitration ownership.

Technical References

Related Articles

Related Tags

20 respuestas