What the Trace Viewer can show you

Depending on the license you purchased with VTS, up to four sources of information are available to the trace viewer.

Driver Messages for running applications (always available while an application is running)

Information collected includes:

•      Timestamp, accurate to the nearest thousandth of a second

•      Direction (Sent or Received from the driver)

•      Service name

•      Driver name as entered in the tag

•      Driver area as entered in the tag

•      Driver description as entered in the tag

•      Port name that the driver is attached to

•      Data included in the communication to/from the driver (a string of hexadecimal values)

RPC Diagnostics (always available)

Information collected for remote procedure calls includes:

•      Timestamp, accurate to the nearest thousandth of a second

•      Identification of internal events

•      The message’s routing flag

•      Sequence number of the message

•      Direction (To or From the server identified by the IP address)

•      IP address of the message source or destination

•      Name of the application sending or receiving the message

•      Name of the service or machine

•      Data and parameters of the message

SOAP Messages (available only if you have a license for VTS Web Services)

Information collected includes:

•      Timestamp, accurate to the nearest thousandth of a second

•      Message number (large messages might be split across more than one line)

•      Message status (an HTML error code indicating success or failure)

•      Source IP address and Port number

•      Destination IP address and Port number

•      Indication of whether the message is incoming or outgoing.

•      The SOAP action (the function call being made)

•      Message size measured in bytes.

•      The SOAP-encoded XML message

OPC Server Trace Messages (available only if you have a license for the VTS OPC Server and a running application is using that server)

Information collected includes:

•      Timestamp, accurate to the nearest thousandth of a second

•      Event description

•      Textual OPC item ID being read from or written to. (Often includes the tag name.)

•      Numeric ID of the OPC property

•      Write Value – the value being written to the tag

•      Result – depending on the nature of the read or write operation, may be one or more of the following:

•      the value being read or written,

•      the quality of the data transfer

•      the number of child nodes

•      the name of the tag

•      access rights

•      type

•      timestamp

Items such as quality, access rights, type, etc are numeric codes. Please refer to the OPC Server Setup chapter in the Developer's Guide for relevant information.