How to Arbitrate a Shared Control Module Between PCS 7 Equipment Modules
To share a PCS 7 control module between equipment modules, implement an explicit, version-appropriate request and command-arbitration interface rather than assuming that EPH-to-EM acquisition also creates CM ownership logic. Siemens documents the APL ShrdResL resource multiplexer as a block-level implementation baseline. The actual EM-to-actuator wiring remains project-specific, and the available question does not identify the installed version or provide a verified generated-acquisition solution.
Table of Contents
- Define the Shared Resource
- Documented APL Implementation Baseline
- Build and Review the Project Interface
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Define the Shared Resource
The engineering question is how an EM can acquire a CM, using an approach similar to acquiring an EM from an equipment phase. Do not assume that those two ownership relationships provide the same generated logic. The affected product and library versions were not specified.
Identify the actual shared actuator and the competing upstream sequences. Define what acquiring, releasing and losing availability mean before implementing the interface.
Documented APL Implementation Baseline
For APL V9.0, Siemens documents ShrdResL as a shared-resource command multiplexer for downstream Drives or Dose technology blocks. Section 7.7.3 identifies ReadyIn, ChnEn_x, Occ_x and ActChnNo for readiness, enable, request and allocated-channel indication.
A documented allocation requires ReadyIn and the selected channel enable. The upstream request is applied through Occ_x; ActChnNo identifies the allocated channel, with zero indicating none. The configured priority and strategy govern competing requests.
This establishes a block-level mechanism. Mapping EM commands, states and release conditions into it is a project-specific adaptation, not an automatically generated CM-acquisition procedure.
Build and Review the Project Interface
Use the following engineering sequence in a project copy:
- Identify the installed APL version and verify the chosen shared-resource block against that version.
- Define one requester interface per upstream application, including request, permitted command and release conditions.
- Connect the downstream readiness and required channel enables according to the documented I/O meanings.
- Map requests to the chosen channels and inspect the allocated-channel indication before allowing commands to influence the actuator.
- Define the required contention policy, then configure and review the corresponding documented strategy and priorities.
- Review what happens when the current requester releases or becomes disabled before compiling or downloading.
No exact motor or valve command wiring is supplied because the downstream block and EM interface are unknown. Complete that mapping against the actual block interfaces rather than inventing generic command contacts.
Verification
Test one requester alone, a second requester alone, simultaneous requests, release and loss of availability. Observe the allocated-channel indication and the downstream command path together.
Compare the observations with the written contention policy. Allocation does not prove physical actuator position; verify the relevant device feedback separately. These are proposed acceptance tests rather than reported results.
Limitations and Operational Precautions
The assertion that CM acquisition is not generated automatically in the affected installation is not independently established for an identified version. The closest documented implementation is explicit APL resource arbitration.
The opened V9.0 manual contains inconsistent channel-count descriptions: its overview describes four channels, while later parameter and management descriptions refer to channels through eight. Resolve capacity against the actual installed block and current manufacturer information before sizing the design. Do not silently select either count as universally correct.
Preserve the project and library baseline. Review interlocks, release behavior and controller availability before making live ownership changes; incorrect arbitration can send the wrong command to shared equipment.
Engineer FAQ
Is an EM-to-CM acquire operation proven to work like EPH-to-EM acquisition?
No. That equivalence is not established here.
Is ShrdResL a documented alternative mechanism?
Yes, as a version-specific block-level command-arbitration baseline.
Does allocation prove the physical valve or motor state?
No. Check the actual feedback separately.
Technical References
- Siemens: Advanced Process Library V9.0, March 2017, A5E39147331-AA — sections 7.7.1 and 7.7.3, pages 1246–1255. The manufacturer PDF was downloaded and read; conflicting capacity descriptions require review.