Canberra Industries RMSA7070822 Manual De Usuario
5.4.2 Extended State of Health (ESOH) Request
For an extended SOH request, enter the hexadecimal seal address (from 1 to FFFFFFFF) and
use the Request Type down arrow to select ESOH. The message ID text box is not activated as
a message number is not required for an ESOH request. Once the seal address has been
entered, click OK to continue. Click Cancel to abort the request.
use the Request Type down arrow to select ESOH. The message ID text box is not activated as
a message number is not required for an ESOH request. Once the seal address has been
entered, click OK to continue. Click Cancel to abort the request.
Within 15 seconds, an extended SOH report from the specified seal, using the next available
message number, should appear in the GUI’s main display. The extended SOH report includes
entries in the Further Information column for the number of watchdog resets and the transmission
count for the seal.0
message number, should appear in the GUI’s main display. The extended SOH report includes
entries in the Further Information column for the number of watchdog resets and the transmission
count for the seal.0
5.4.3 Send Message (SNDM) Request
To request a particular archived message, enter the hexadecimal seal address (from 1 to
FFFFFFFF) and use the Request Type down arrow to select SNDM. Once the SNDM request
type is selected, the Message ID text box is activated. Enter a valid message number for this
seal as a decimal value.
FFFFFFFF) and use the Request Type down arrow to select SNDM. Once the SNDM request
type is selected, the Message ID text box is activated. Enter a valid message number for this
seal as a decimal value.
Message numbers start with 1. The maximum valid message number should be available in the
main display within the most recent autonomous State of Health message.
main display within the most recent autonomous State of Health message.
Click OK to send the request. Click Cancel to abort the request.
Within 15 seconds, the requested message number from the requested seal should appear
within the GUI window. Note that in default review mode, messages are sorted chronologically in
order of the log timestamp on the translator. Since the translator has no access to the TLV
contents of the message (due to encryption), it has no way of inserting the data in a day file log
based on the message number or time it was originally sent. Therefore, if interrogating a seal
that has been running for some time for message ID 1, the translator will log the event in the
current day file, not in the day file of the original transmission attempt. Similarly, the GUI will
present the new message (Message Number 1) at the end of the currently displayed data set.
within the GUI window. Note that in default review mode, messages are sorted chronologically in
order of the log timestamp on the translator. Since the translator has no access to the TLV
contents of the message (due to encryption), it has no way of inserting the data in a day file log
based on the message number or time it was originally sent. Therefore, if interrogating a seal
that has been running for some time for message ID 1, the translator will log the event in the
current day file, not in the day file of the original transmission attempt. Similarly, the GUI will
present the new message (Message Number 1) at the end of the currently displayed data set.
5.4.4 Send Fiber History (HIST) Request
To request a history of all fiber optic event messages generated (up to a limit of ~383), enter the
hexadecimal seal address (from 1 to FFFFFFF) and use the Request Type down arrow to select
HIST. Once the seal address has been entered, click OK to continue. Click Cancel to abort the
request.
hexadecimal seal address (from 1 to FFFFFFF) and use the Request Type down arrow to select
HIST. Once the seal address has been entered, click OK to continue. Click Cancel to abort the
request.
Within 15 seconds, a list of the seal’s fiber optic event messages should appear in the GUI’s
main display.
main display.
5.4.5 Send RMSA To Translator Associate(RTTA) and RMSA To Translator
Disassociate(RTTD) Request
The RMSA To Translator Associate (RTTA) and Disassociate (RTTD) commands were created
for seals that do not provide translator addresses during personality programming. The address
of the Translator that is connected to the GUI will be used by the seal after successfully sending
this message. Before receiving the RTTA command, the seal will buffer but not transmit
messages. Upon receiving RTTA command, the seal will check a list of all messages buffered
and send those to the associated translator all at once. Upon receiving the RTTD command, the
for seals that do not provide translator addresses during personality programming. The address
of the Translator that is connected to the GUI will be used by the seal after successfully sending
this message. Before receiving the RTTA command, the seal will buffer but not transmit
messages. Upon receiving RTTA command, the seal will check a list of all messages buffered
and send those to the associated translator all at once. Upon receiving the RTTD command, the
REMOTELY MONITORED SEAL ARRAY(RMSA)
SFG-MAN-001
REVISION: 1.7
2016 CANBERRA
54