|
<< Click to Display Table of Contents >>
Reading Event Buffers from GE PAC RX7 Controllers |
Event buffers can be read using Event-reported Tags, Event-reported Tags by point, and Real-time Tags.
Event-reported Tags return, at each reading operation, all events stored in this Driver's internal buffer, and they can be configured by Strings or numerically.
•Device: "<slave id>:"
•Item: "gesoe0.<base address of an event stack>"
To read event buffers from GE PAC RX7 controllers using numerical configuration, users must define, on this Driver's configuration window, an operation that uses as its reading function the special GE SOE function. Its data type must be defined as GE_events.
•B1: Slave ID
•B2: Code of the operation defined with GE SOE function
•B3: 0 (zero)
•B4: Base address of the stack of events in a device
At each scan on this Tag, this Driver checks if there are events on the buffer of a controller. If there are events, this Driver starts an event-reading thread, which is executed in background, not blocking the scan of all other Tags. After finishing the reading of that buffer by this Driver, this event-reported Tag returns the set of events read on that scan.
Returned events generate a sequence of OnRead events on this Tag. For each event read, Elipse E3, Elipse Power, or Elipse Water updates Tag fields, Element values, and timestamps with values from a certain event, and calls an OnRead event once. The script of the executed event must be defined by users, and it is generally used to insert data from a Tag into a Historic.
Each event is represented by a Block with 2 (two) Elements, with its Timestamp field read from a device. Fields from the respective reading Block Tag are displayed on the next table.
Block Tag fields
Offset |
Meaning |
Data Type |
Range of Values |
|---|---|---|---|
0 |
Point identification |
Byte |
Between 0 (zero) and 15 |
1 |
Point status |
Byte |
Between 0 (zero) and 1 (one) |
For more information about event-reported Tags, please check the specific topic on Elipse E3 User's Manual.
IMPORTANT |
When reading mass memory events in event-reported Tags in Elipse E3, in Elipse Power, or in Elipse Water, disable the dead band of a Tag, that is, the EnableDeadBand property configured as False, and also the linked Historic object, that is, configure the DeadBand property to 0 (zero), to avoid losing events with near values. It is also important to disable historic by scan, that is, in Elipse E3, in Elipse Power, or in Elipse Water configure the ScanTime property as 0 (zero). This ensures that new events are only stored using the WriteRecord method, executed on the OnRead event of a Tag, avoiding duplication of events. |
Starting with version 2.5 of this Driver, users can use a new Tag to download events from a specific point.
This Tags works as the previous one, except that it returns only events from a specific point.
Different from the previous event, the returned value only contains only 1 (one) Element with the value of the status of a point, so that only one Tag can be used. This Tag must be configured as follows:
•Device: "<Slave Id>:"
•Item: "gesoe<200 + Index of a point>.<base address of the stack of events>"
•N1: Slave ID
•N2: Code of the operation defined with the GE SOE function
•N3: 200 + Index of a point, such as configuring the N3 parameter as 202 for point 2 (two)
•N4: Base address of the stack of events in a device
For more information about event-reported Tags, please check the specific topic on Elipse E3 User's Manual.
These Tags return the most recent event already read for a specific point. These events are stored on this Driver's internal memory for each event reading from a device, with their respective timestamps read from that device. This Tag uses the following parameters:
•Device: "<Slave Id>:"
•Item: "gesoe<100 + Index of a point>.<base address of the stack of events>"
•N1: Slave ID
•N2: Code of an operation
•N3: 100 + Index of a point
•N4: Base address of the stack of events in a device
•Value: Status of a point