Pattern Match Trigger; Input Event Latching; Additional Event Considerations; Use Cip Sync Time - Rockwell Automation Allen-Bradley ArmorBlock 5000 Series User Manual

Chapter 2 Module Features

Use CIP Sync Time

20

Pattern Match Trigger

When a pattern of input state changes triggers an event, multiple points participate in the
event trigger. To use this type of trigger, you must disable the Independent Point Trigger
option in the event definition. Set the EO.Eventxx.IndependentConditionTriggerEn tag to 0.
Every point that participates in an event trigger is configured separately. Depending on the
event definition, the collective status of all points that matches the pattern triggers the event.

Input Event Latching

To use input event latching, you must select the Latch Event checkbox for that input event. Set
the EO.Eventxx.LatchEn tag to 1.
When input event latching is used, the event in the input data must be acknowledged before a
new event is sent out.
To acknowledge the current event in the input data, set the EO.Eventxx.EventNumberAck tag to
the event number (EI.Eventxx.EventNumber tag) in the input data.
If the current event is not acknowledged, subsequent events are stored in a queue. The queue
can store up to four events. If the queue is full, excess events are dropped.

Additional Event Considerations

When you use the Input Events feature, also consider the following:
• An Event task only actuates if an event occurs.
IMPORTANT Make sure that you link the Event task to the Event Input tag, not
• An event is recognized only when it maintains the same state for the minimum duration
that is determined by the input filter time specified.
For example, if the input filter time is set at 2 ms, and the input filter time accuracy is
-50...+400 µs (except for 0 µs filter time setting), this means that:
- A pulse width that is shorter than 1.95 ms is not detected.
- A pulse width that is longer than 2.4 ms is detected.
- A pulse width that is between 1.95...2.4 ms may or may not be detected.
• When you configure the RPI of the input event connection, consider that the minimum
interval between two input data packets of event connection is one quarter of the RPI
connection.
• After the event task executes, it does not execute again until the event occurs again.
• When the input event connection is reopened, the EI.Eventxx.PtxxData tag is reset to 0.
CIP Sync is a CIP implementation of the IEEE 1588 PTP (Precision Time Protocol). CIP Sync
provides accurate real-time (Real-World Time) or Universal Coordinated Time (UTC)
synchronization of controllers and devices that are connected over CIP networks. This
technology supports highly distributed applications that require timestamping, sequence of
events recording, distributed motion control, and increased control coordination.
The ArmorBlock 5000 8-channel IO-Link master module is a CIP Sync slave-only device. There
must be another module on the network that functions as a master clock. For more
information on how to use CIP Sync technology, see the Integrated Architecture® and CIP Sync
Configuration Application Technique, publication IA-AT003.
Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
the Input tag.
Keep in mind that when the Event task executes, the input tag
data can have the same data that was sent at the last RPI.