Events

When Encoder Type is configured as HSC, the following conditions can trigger events:

Window00…Window03
Counter Load
Counter Store
Counter Hold
Counter Reset
Counter Direction
Counter Rollunder
Counter Rollover

When Encoder Type is configured as SSI, the following conditions can trigger events:

Window00…Window03
Store
Direction

You must choose a State Transition for each trigger. The State Transition defines what must occur to trigger the event.

The following State Transition choices are available:

Not in Window/In Window – Used with the Window event triggers.
Low/High – Used with the Counter/SSI event triggers.

When the module reports an event to the controller, the module can trigger an event task to execute in the controller. The event task lets you execute a section of logic immediately when an event, or receipt of new data, occurs.

For more information on event tasks, see the Logix 5000 Controllers Tasks, Programs, and Routines Programming Manual, publication 1756-PM005.

This option means that any state change that match can trigger the event.

To use this type of trigger, you must enable the Independent Point Trigger option in the event definition. Set the

EO.Eventxx.IndependentConditionTriggerEn

tag to 1.

This option means that a pattern of state changes must match to trigger the event.

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 state that participates in an event trigger is configured separately. Depending on the event definition, the collective status of all states that matches the pattern triggers the event.

An event is triggered each time a state change results in one of the following conditions:

When Rising Edge event trigger is enabled (
EO.Eventxx.EventRisingEn
= 1) – Matching the event trigger definition
When Falling Edge event trigger is enabled (
EO.Eventxx.EventFallingEn
= 1) – No longer matching the event trigger definition
Do not use the Falling Edge event trigger for the following:
Counter – Reset, Load, Store, Rollunder, and Rollover
SSI – Store

To use event latching, you must select the Latch Event checkbox for that input event. Set the

EO.Eventxx.LatchEn

tag to 1.

When 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.

You can use as many as three user-defined data values to define an event.

When Encoder Type is configured as HSC, the following data values are available:

No Additional Data
Count
Stored Count
Scaled Count
Scaled Stored Count
Revolution Count
Stored Revolution Count

When Encoder Type is configured as SSI, the following data values are available:

No Additional Data
Data
Stored Data

You define events when you define a module during module configuration in the Studio 5000 Logix Designer application. For more information, see Device Definition – Events View.

When you use the 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 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.
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.
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.<member>
tags are reset to 0.