How to Add Additional Messages to APL MotL Faceplates Using EventTS
To add more alarms to an APL MotL block when all built-in and external message inputs are exhausted, connect the companion message block EventTS (FB 1212) or Event (FB 1211) to the motor block in CFC. EventTS monitors up to eight discrete binary signals with high-precision time stamping. Interconnecting the structured output EventTS.EventTsOut to the input pin MotL.EventTsIn (or EventTs2In) integrates all additional messages directly into the motor faceplate's alarm view, allowing operators to view and acknowledge up to 16 extra alarms.
Table of Contents
- Architecture of APL Message Expansion and the EventTS Block
- Step-by-Step CFC Interconnection and Configuration Workflow
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Architecture of APL Message Expansion and the EventTS Block
In SIMATIC PCS 7 Advanced Process Library (APL), the large motor block MotL (FB 1850) provides built-in alarm monitoring for standard drive faults:
* Dynamic feedback errors (MonDynErr), static feedback errors (MonStaErr), thermal protection trips (Trip), and interlock violations (LockAct).
* It also includes general external message inputs (ExtMsg1 through ExtMsg3).
However, complex heavy industrial drives (such as mining slurry pumps, ball mills, or variable frequency drives) often monitor dozens of auxiliary status signals:
* Winding temperature high, drive cooling fan failure, vibration warning, lubrication oil low pressure, and local isolator trips.
When built-in message pins are exhausted, modifying the compiled internal code of MotL is strictly prohibited. Instead, APL provides the EventTS (FB 1212) and Event (FB 1211) companion blocks. EventTS captures up to eight discrete Boolean signals (In1 to In8), assigns millisecond-precise time stamps (Sequence of Events - SOE), and routes alarm states into technological blocks via dedicated structure pins.
Step-by-Step CFC Interconnection and Configuration Workflow
Follow this procedure to expand motor faceplate alarms:
- Instantiate EventTS in the Motor CFC Chart:
* Open the CFC chart containing theMotLinstance.
* From the APL library catalog, drag and dropEventTS(FB 1212) onto the chart.
* PlaceEventTSin the same cyclic runtime group and execution sequence slice immediately precedingMotL. - Interconnect Additional Alarm Signals:
* Connect auxiliary digital input channel blocks (Pcs7DiIn) to inputsEventTS.In1throughEventTS.In8.
* Double-clickEventTS, open the Messages configuration dialog, and configure custom alarm texts (e.g.,Bearing DE Vibration High) and message classes (Alarm, Warning, Tolerance). - Link EventTS to MotL:
* Interconnect output pinEventTS.EventTsOutto input pinMotL.EventTsIn.
* If eight additional messages are still insufficient, instantiate a secondEventTSblock and connect its output toMotL.EventTs2In, providing a total of 16 additional faceplate alarms. - Compile AS and OS:
* Compile CFC charts with Changes only.
* Execute an OS compilation to transfer the new message descriptors to the WinCC Alarm Logging database.
Verification
- In WinCC Runtime, open the faceplate for the configured motor.
- Click on the Alarm View tab in the faceplate header.
- In the field or via CFC test mode, force an auxiliary fault on
EventTS.In1. - Verify that:
- The motor block icon on the process screen indicates an active alarm.
- Opening the
MotLfaceplate displays the new alarm text (Bearing DE Vibration High) directly within the motor's alarm list. - Acknowledging the alarm from the
MotLfaceplate acknowledges theEventTSmessage simultaneously.
Limitations and Operational Precautions
- Strict 1:1 Relationship: An
EventTSblock can be interconnected to only one technological block. SplittingEventTsOutacross multiple motor or valve blocks is strictly forbidden and causes compiler errors. - For time-stamping to achieve 1 ms Sequence of Events precision, the digital input hardware modules must support hardware time-stamping (e.g., ET 200SP HA DI 16x24VDC with SOE enabled in HW Config).
- Ensure that the
EventTSblock'sMsgLockpin is linked to the master plant message lock signal to ensure unified suppression during maintenance.
Engineer FAQ
- What is the difference between Event and EventTS?
Event(FB 1211) generates standard alarms with controller cycle time resolution.EventTS(FB 1212) supports high-precision 1 ms hardware Sequence of Events time stamping from distributed I/O racks. - Can I link EventTS to blocks other than MotL?
Yes. All major APL technological blocks—includingVlvL,VlvMotL,PIDConL, andMonAnL—featureEventTsInpins for alarm expansion. - Will the additional alarms sound the operator alarm horn?
Yes. Because the messages are registered in WinCC Alarm Logging with standard message classes, they trigger horn annunciators according to the plant's WinCC Horn configuration.
Technical References
- SIMATIC PCS 7 Advanced Process Library (APL) Function Manual: EventTS Block (A5E43360408-AA).
- SIMATIC PCS 7 High-Precision Time Stamping System Manual.
- Siemens Industry Online Support Entry ID 109801081: Expanding Technological Block Alarms in PCS 7.
Related Articles
- Configuring 1 ms Sequence of Events (SOE) Time Stamping with ET 200SP HA and EventTS.
- Designing Standard Control Module Types (CMT) with Extended Alarm Handling.
Related Tags
PCS 7, APL, MotL, EventTS, Alarm Logging, Faceplates, SOE, Function Blocks