OPC Time Monitor
Condition Summary Tags
Home Product
Details Server
Consolidator Free 
Demo Pricing &
Ordering Support About Us

For every OPC Item that you connect the OPC Time Monitor to in one of your OPC Servers, the OPC Time Monitor will calculate and expose a set of tags upstream to any OPC client that is interested. This page lists the summary tags that are exposed for each state an item can be in - In Condition, Out of Condition, and Stable.

Condition Summary Tags

For each OPC item you connect you, you can specify a condition - from that setup, the OPC Time Monitor calculates a number of items for when the item is In Condition, Out Of Condition, and Stable.

The first items exposed are a set of summary tags for the selected condition - in this example "$InCondition" is chosen.

Name

Access Rights

Canonical (Default) Data Type

Description

Readable

Writeable

PreviousValue

Yes

No

VT_EMPTY *

The value that the source item had at the beginning of the previous cycle. This item appears separately for every measurement type.

ClientTime

Yes

No

VT_DATE

Returns the measured time, as seen on the client (receiving) end and measured by operating system ticks.

ClientTime!TimeFormat

Yes

No

depends on TimeFormat

Same value as ClientTime, but expressed in a different way (converted), as given by TimeFormat.

PreviousClientTime

Yes

No

VT_DATE

The previous value of the client time, i.e. the client time value reached in previous cycle.

PreviousClientTime!Tim eFormat

Yes

No

depends on TimeFormat

Same value as PreviousClientTime, but expressed in a different way (converted), as given by TimeFormat.

ServerTime

Yes

No

VT_DATE

Returns the measured time, as seen on the server (transmitting) end and measured by timestamps provided with the values.

ServerTime!TimeFormat

Yes

No

depends on TimeFormat

Same value as ServerTime, but expressed in a different way (converted), as given by TimeFormat.

PreviousServerTime

Yes

No

VT_DATE

The previous value of the server time, i.e. the server time value reached in previous cycle.

PreviousServerTime!Ti meFormat

Yes

No

depends on TimeFormat

Same value as PreviousServerTime, but expressed in a different way (converted), as given by TimeFormat

Time Format Items - these items are available for any OPC item provided by the OPC Time Monitor in VT_DATE Format. 

For each item, the time in the condition is available in different time formats based on the client needs - i.e. in days, hours, seconds, minutes, etc.

In the listings below "TimeBranch" refers to the particular summary value - for example, ServerTime is a "TimeBranch", meaning you could access ServerTime in seconds by using the item name YourItem!$InCondition!ServerTime!Seconds

Name

Access Rights

Canonical (Default) Data Type

Description

Readable

Writeable

TimeBranch!Date

Yes

same as TimeBranch

VT_DATE

Same as TimeBranch - value of the TimeBranch as a VT_DATE data type.

TimeBranch!Days

Yes

same as TimeBranch

VT_R8

Time value, expressed in days and a fraction of a day.

TimeBranch!Hours

Yes

same as TimeBranch

VT_R8

Time value, expressed in hours and a fraction of an hour.

TimeBranch!Microseco nds

Yes

same as TimeBranch

VT_R8

Time value, expressed in microseconds and a fraction of a microsecond.

TimeBranch!Millisecon ds

Yes

same as TimeBranch

VT_R8

Time value, expressed in milliseconds and a fraction of a millisecond.

TimeBranch!Minutes

Yes

same as TimeBranch

VT_R8

Time value, expressed in minutes and a fraction of a minute.

TimeBranch!Seconds

Yes

same as TimeBranch

VT_R8

Time value, expressed in seconds and a fraction of a second.

TimeBranch!Str

Yes

same as TimeBranch

VT_BSTR

Time value converted to string, such as "01:45:58". Uses the system default locale settings (not the custom locale settings). Note that the typical resolution of the converted string is up to seconds; no fraction of a second is provided.

* Note: The server reports VT_EMPTY as a canonical data type for CurrentValue and PreviousValue items. This is a common OPC way to express that the canonical data type of a value is unknown at the moment. The actual values returned by the OPC Time Monitor server have the same data type as the underlying server that provides them.  Some OPC Client applications require that the OPC server present a data type.  For that reason, the OPC Time Monitor allows you to set force a data type for each item instead of presenting VT_EMPTY.

 

Software Toolbox Inc.
Copyright Software Toolbox, Inc., 1996-2003, All Rights Reserved Worldwide.
148A East Charles Street, Matthews, North Carolina, USA 28105
Phone: 704-849-2773 or 1-888-665-3678 (US), Fax: 704-849-6388
Email:
tools@softwaretoolbox.com