DataServerStatistics
The
DataServerStatistics
item returns a detailed description of each configured data server conversation and each conversation’s status.This table shows the input and output formats for this item.
Input Format | Request: DataServerStatistics | ||
Output Format | The DataServerStatistics item returns in this format: | ||
<Statistics> | is | <NullList> | <ServerList> | |
<ServerList> | is | <ServerRecord> | <ServerRecord> <ServerList> | |
<ServerRecord> | is | <ServerName> \t <ConfigString1> \t <ConfigString2> \t <ConversationStatus> \t <WatchDog> \crlf | |
where <ServerRecord> is: | |||
Field Name | Format | Description | |
<ServerName> | ASCII - String | Data server name. | |
<ConfigString1> | ASCII - String | Protocol-specific configuration string exposed: OPC: Data Server brand name from DSDF file. CIP: The string constant "FactoryTalk Linx". FTD:The Area Path used in establishing a connection to the FactoryTalk Live Data server. | |
<ConfigString2> | ASCII - String | Protocol-specific configuration string exposed: OPC: Data server’s configured watchdog read item access path. CIP: Controller path FTD: Data server’s configured watchdog read item access path. | |
<Conversation Status> | ASCII – String | Language-specific word for the current conversation status between the FactoryTalk Batch Server and the data server:Good, Bad, Suspect, or Lost | |
<WatchDog> | ASCII – String | Protocol-specific configuration string exposed: OPC: Data server’s configured watchdog read item name. CIP: Unused (<sp>) FTD: Data server’s configured watchdog read item name. |
This table shows an example of the return on this request.
TIP:
A request on the
object.GetItem(DataServerStatistics)
could return this for two servers:OPC_SIM \t \t PHASES \t GOOD \t WATCHDOG \crlf
INSTRUCTIONBASEDSERVER \t \t INSTRUCTIONS \t GOOD \t WATCHDOG \crlf
Provide Feedback