User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
79
Ladder Logic - Event Logging
Event logs allow the RTU to record time and date stamped data. An event log can be created periodically,
after data changes or on any configurable event.
Event logs are kept in a circular buffer that is "max. number of logs" long (as detailed by the Memory
configuration, Check memory usage button). When the buffer is full, the oldest logs are overwritten. The
RTU uses an internal "current pointer" which always points to the latest log added to the buffer.
Accumulating Event Logs From Other RTUs
Event logs received from other RTUs are all stored in one event log buffer. To keep track of which logs have
been received, a master RTU uses a local log pointer for each outstation RTU. Each of these pointers is then
used to point to the last log polled from the outstation RTU. For greater flexibility, a local log pointer can be
set to point to the latest log in an outstation RTU or it can be set to point to a log that occurred a number of
minutes ago in the outstation RTU.
RTU Communications
Most of the event log blocks initiate messages and should be used in a similar way to other communication
blocks by first checking if the port is available before sending a message. For an example of using event log
blocks, please see the topic Example - Polling Event Logs.
Event Log
Logs the value or state of a variable along with the user type and priority of the event log. Please see the
topic Example - Event Logging. Note: a maximum of 250 Event Log blocks can be used per RTU.
Comment: A 12-character description.
Ref: No longer used.
Variable: Bit, 16-bit register, Long (#L) or Float (#F).
User Type: (0-31) Used to group similar types of logs. For example, analog inputs could be type 1, digital
status signals type 2, digital alarm signals type 3 and so on. Only logs matching a certain User Type can
then be uploaded instead of uploading all the logs.
Priority: (0-7) Allows separation of logs within each User Type category. 0 is used for the highest priority
logs.