Restore PCS 7 EPH Acquisition After an EMT Interface Change

Restore PCS 7 EPH Acquisition After an EMT Interface Change

If a PCS 7 Equipment Phase (EPH) stops acquiring a modified Equipment Module Type (EMT), check the linked SFC type interfaces and block contacts, not only the displayed technological I/O assignment. Siemens' PCS 7 Compendium Part C describes updating and synchronizing changed EPH/EMT interfaces. In the reported V9.0 SP1 Update 3 case, temporarily reassigning the affected attribute to another compatible EMT and then restoring the intended instance was used as a workaround; review all pending changes before compiling or downloading.

Table of Contents

Why an EPH may stop acquiring a modified EMT

When an Equipment Module Type (EMT) is changed in the Master Data Library, its Equipment Phase Type (EPHT) and project instances may require the corresponding block types and block contacts to be updated and synchronized. Siemens' PCS 7 Compendium Part C describes block contacts and mirrored interfaces between EPH/EM structures; it notes that changed EMT interfaces require appropriate update/synchronization steps. A correctly displayed technological I/O assignment therefore does not, by itself, prove that the SFC type's block-contact interface is current.

Confirm the affected assignment

Open the EPH chart that cannot acquire the EMT and inspect its technological I/O assignment. Identify the exact EMT instance and characteristic/setpoint that fails. Check whether the EMT interface, EPHT interface and project-level assignment have been updated consistently after the MDL change. Preserve the project and identify the last known-good version before altering role assignments.

Refresh the role assignment

The reported recovery method is to remove and recreate the EPH-to-EMT role assignment so CFC rebuilds the relationship:

  1. In the affected EPH chart, open the technological I/O view for the EMT/characteristic that is not acquired.
  2. In the Assigned equipment module selection for the affected attribute, temporarily select a different compatible EMT instance. The source reports that CFC pauses while it recreates the connection; this behavior is a reported observation, not a guaranteed visual confirmation.
  3. Reopen the assignment and select the intended original EMT instance again.
  4. Review the pending changes on both the EPH and EMT. Confirm that the intended instance and characteristic are assigned before proceeding.

This instance-switch sequence is a reported workaround. Do not apply it blindly to a live project or to a different configuration where the assignment has other dependencies.

Update interfaces and block contacts when the type changed

If the EMT/EPHT SFC type or its setpoint/control interface changed, follow the release-matched PCS 7 Part C update procedure. Siemens describes updating and synchronizing the relevant SFC block types and updating block contacts in the involved EPH/EM types so the changed interface becomes available at the higher level. Do not substitute a full compile for these interface-specific update operations; compilation and block-contact synchronization are separate tasks.

Compile and download only the reviewed changes

After the assignment and interface updates are correct, review the pending CFC/SFC changes. Compile the affected charts and download only under the site's approved engineering/change procedure. The source reports compiling and downloading as the final action in its workaround, but that report does not establish a universal download sequence or prove suitability for every active process.

Verification

Confirm the intended EMT is shown as assigned to the affected EPH characteristic and that the related block contacts/interfaces match the updated type. Check for pending or inconsistent chart changes, then compile and review the resulting diagnostic log. After an authorized download, verify acquisition with the configured test procedure and Batch/engineering diagnostics before declaring the EPH ready.

Limitations and Operational Precautions

The source reports BATCH Builder V9.0 SP1 Update 3 and an EPH that stopped acquiring an updated EMT after type/interface changes. It does not name the affected EMT/EPHT types or provide a successful post-download verification. The different-instance-then-original reassignment is a field-reported workaround; the stronger documented principle is to perform the required update/synchronization and block-contact steps for the modified interface. Exact menu labels and update order must be confirmed in the documentation installed for the project's PCS 7 release. Treat chart compilation and PLC/OS downloads as controlled changes.

Engineer FAQ

Why didn't full compile and plant synchronization restore acquisition? Those actions do not necessarily replace explicit EPH/EMT interface and block-contact update steps after a type change.

Is switching to another EMT and back an official universal fix? No. It is the source-reported workaround; use it only after confirming the assignment and reviewing the resulting pending changes.

What must be updated when an EMT interface changes? The relevant SFC block types and block contacts at the linked EPHT/EMT levels, following the procedure for the installed PCS 7 release.

Should I download immediately after reassigning? First verify the intended instance/characteristic, interface consistency and pending changes; then use the approved site download procedure.

Does this apply to every EPH acquisition issue? No. The evidence applies to a case following EMT changes and does not identify a general fix for unrelated assignment or runtime faults.

Technical References

Related Articles

PCS 7 EPH EMT block contact updates

SIMATIC BATCH equipment phase types

Related Tags

SIMATIC PCS 7, SIMATIC BATCH, EPH, EMT, block contacts

20 respuestas