User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
80
Tx Event Logs
No longer supported. Please use Tx Update Event Logs block.
Tx Update Event Logs
This block is designed to update event logs in a standby master RTU. It also updates the event log pointers
for the remote RTUs in the standby master. The block checks if new logs need to be transmitted to the
destination RTU and then sends them 10 at a time until it has sent the maximum limit of event logs or until
the end of the event log list is reached. Requires driver TXUPDATE.Dxx. Care must be taken to initiate only
one Tx or Rx Update block at a time otherwise unpredictable results may occur. The pending flag detailed
below can be used to determine when the Tx Update block has finished.
Destination RTU: (1-249) The target RTU to send event logs to.
Event Log Pointer: (#R) The local register which the RTU uses to remember where it is up to in the event
log list. It is automatically updated after the TX Update block is successfully completed.
Status Register: (#R) A local register used to indicate the status of the block as follows:
• Channel 1: Pending Flag. Channel 1 is set ON when the block is activated and set OFF when the block
is finished.
• Channel 2: Status Flag. Channel 2 is written to after the block is finished. Channel 2 is set OFF if the
update was successful or is set ON if the update failed (due to communications failure).
• Channel 3: Finished Flag. Channel 3 indicates whether the Event Log list contains any more entries and
is written to after a block of event logs has been successfully transferred. Channel 3 is set ON if all the
event logs have been sent or is set OFF if there are more logs.
Max. number of logs: (0-65535) The maximum number of logs to transmit each time the Tx Update Event
Logs block is activated.