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

Create a PCS 7 CMT Interface for a Valve Shared by Production and CIP

Create a PCS 7 CMT Interface for a Valve Shared by Production and CIP

Use a shared-resource block to arbitrate command ownership before commands reach a valve used by production and CIP. Siemens documents this architecture and the CMT technological-interface construction method. However, a complete ShrdResL valve implementation requires the actual APL and valve block versions and their connection definitions. The documented interface steps below provide a starting point; the exact command and feedback mapping remains a project-specific item requiring review.

Table of Contents

Documented Shared-Resource Architecture

Siemens' V9.1 compendium, section 8.9, describes switching a CM's command inputs between requesting equipment modules and managing assignment. It identifies ShrdResL and ShrdResS for supported Drive and Dose blocks. This supports shared-resource arbitration; it does not provide the wiring for a particular valve type. Compendium Part C.

For a production/CIP arrangement, identify the existing valve block, its library release and the two requesting sequences before choosing the type interface. An allocation indication and a physical valve feedback are different evidence.

Build the Technological Interface

The following is the documented CMT interface construction method, adapted to a shared-resource design rather than a verified ready-made ShrdResL example:

  1. In a development copy, open the CMT's CFC and place the required blocks. Name them meaningfully.
  2. Establish the project-specific internal connections using the applicable block manuals. Do not connect two independent command writers directly to one valve input.
  3. Drag the relevant parameters and signals into the "Technological I/Os" field. Siemens documents that this creates and assigns the interface objects.
  4. Inspect the "Attributes" area to confirm each exposed object maps to the intended internal connection.
  5. Represent commands and status explicitly; the CMT model provides Command and Status objects for sequence interaction.
  6. Route additional inter-instance wiring through technological I/Os so it remains represented in the abstraction model.

These actions create an inspectable type interface. They do not establish the missing release-specific ShrdResL pin map. Engineering with CMT, sections 3.1 and 5.4.

Define Commands and Feedback Without Confusing Ownership

Prepare a connection specification with separate entries for production requests, CIP requests, arbitration results, valve commands and valve feedback. For each entry, record its real block I/O, direction, data type and purpose from the installed documentation.

An engineering adaptation must establish what happens when one sequence requests movement while another stops or aborts. Do not assume that an abort command relinquishes ownership or closes every valve. Confirm that behavior in the sequence design and the actual block release.

Keep feedback readable for diagnostics while preserving a single resolved command path. Exactly which feedback and commands should be exposed remains project-specific; a universal port list is not established here.

Verification

Use a controlled test configuration to check these proposed acceptance cases:

  1. Request the valve from production alone, then CIP alone. Inspect allocation and the actual valve response separately.
  2. Request both at once. Confirm the documented arbitration policy and record the selected owner.
  3. Stop, hold and abort each sequence while the other requests access. Check the specified handover and safe-state behavior.
  4. Check actual position feedback and interlocks, not just the allocation display.

For APL V8.2, the ShrdResL standard view identifies assignment, active channel and resource status; channel previews distinguish requests from active assignment. These are useful ownership observations, not proof of mechanical position. APL Operator Guide, sections 2.6.2–2.6.3. These tests are proposed; no test results are claimed.

Limitations and Operational Precautions

PCS 7, CFC, APL and the valve block version are not specified. The exact ShrdResL command/feedback connections and allocation policy therefore remain unresolved. The interface method is documented, while its application to this valve requires project engineering and review.

Preserve the project and existing type definitions before changes. Assess the effect of type synchronization on existing instances. Test conflicting production/CIP commands and recovery before any approved production download; an ownership mistake can actuate the wrong process path.

Engineer FAQ

Must the shared valve have two direct command sources? Use an arbitration design rather than independent writers to the same command input.

Does an active channel prove that the valve moved? No; inspect the valve's actual feedback separately.

Can one control strategy replace sharing? Only if the equipment design can place the required operations under one controlling module; that alternative is not established for every plant.

Technical References

Related Articles

Related Tags

20 respuestas