OPC90 Server
FILE VT_BSTR Read/Write Indicates / selects the current file name for the
captured SOE data.
NEXTFILE VT_BOOL Read/Write Flag used to sequence through the most
recent to oldest SOE capture files.
NEXTREC VT_BOOL Read/Write Flag used to sequence through the records of
the currently selected SOE capture file..
RECORD VT_I4 Read/Write Indicates / selects a record (1 – COUNT) for
the currently selected capture file.
POINT_TYPE VT_BSTR Read Point type (‘Undefined’, ‘Standard’,
‘Summary’, ‘Pre-fault’, ‘Post-fault’ and ‘Snap-
shot’) for current record of selected SOE file.
POINT_NUM VT_I4 Read Point number (0 - 511) for current record of
selected SOE file.
POINT_NAME VT_BSTR Read Point name for current record of selected
SOE file.
POINT_SCAN VT_BOOL Read Point scan state (0 on scan, 1 off scan) for
current record of selected SOE file.
POINT_DATE VT_BSTR Read Point capture date month/day/year for current
record of selected SOE file.
POINT_TIME VT_BSTR Read Point capture time
hour:minute:second.millisecond for current
record of selected SOE file.
POINT_Q VT_BOOL Read Point quality (0 good, 1 bad) for current record
of selected SOE file.
POINT_ALARM VT_BOOL Read Point alarm state (0 no, 1 yes) for current
record of selected SOE file.
POINT_VALUE VT_BOOL Read Point value (0 or 1) for current record of
selected SOE file.
Application: This block is used to monitor and retrieve sequence of events data from Bailey
function code 99 and 243 blocks. Bailey function code 99 blocks can be any block number within
the controller block range. On startup, OPC90 reads the Bailey SOE block data to determine its
type (FC 99 or 243) and based on the type setup the OPC90 SOE.BLOCK_TYPE tag. Bailey
function code 243 is the INSEM01 executive block. Its base address is always 5000 and is used
to retrieve “Standard” sequence of events. Its 5001 block address is used to retrieve “Summary”
sequence of events.
The SOE.SOE_DATA tag indicates the Bailey system is capturing an SOE event when it goes to
the one state. When this occurs, OPC90 will read the sequence of event data and store it in SOE
files automatically generated within the C:\Program Files\OPC90 Server\SOE directory. The
SOE.OFLOW tag indicates the Bailey SOE block experienced an overflow condition (when 1)
and the block buffer size must be increased to clear this condition.
SOE.SOE_DATA will reset when the SOE event capture is complete. The current capture file
can be closed and a new one opened by writing a zero to this tag. Note that a value of one can
only be written to the SOE.SOE_DATA tag when the SOE block type is ‘Summary’ requesting a
summary report to be generated. If OPC90 device simulation is enabled, a one and then zero
can be written regardless of the SOE block type. This will cause a simulated SOE log file to be
generated
By definition file names are the system address of the block (ring, node, module, block separated
with an underscore character ‘_’) followed by date of capture followed by a two digit (01 – 99)
sequence code. The capture file types are ‘STD’, ‘SUM’, ‘PRE’, ‘POS’ or ‘SNP’ which
corresponds to standard, summary, pre-fault, post-fault and snapshot type logs. Note that Bailey
blocks based on FC 243 generated by the INSEM01 module only support standard and summary
type events.
The RoviSys Company Version 7.0 Page 109
To Next Page
Loading...