Input Events

The 5034-UB8F and 5034-UB8FXT modules can be configured with four input event definitions.
To use Input Events, select the “Data with Events” connection type in the Device definition dialog while configuring the module.
The following conditions can trigger events:
  • An input state change
  • A counting input done bit change
  • A pattern of input state changes on multiple module inputs
When the module reports an input 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.
IMPORTANT:
No input event is generated, if any of the participating channel is in fault condition.

Independent Point Trigger

An input state change or a counting input bit done change that triggers an event is known as an independent point trigger.
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.

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 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.
  • An event is recognized only when it maintains the same state for the minimum duration that is determined by the input filter time specified.
  • 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.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal