Table of Contents
This chapter gives an overview of how the OPC DataHub handles data and the various protocols it works with.
Each value stored in the OPC DataHub is called a point. A point has the following attributes:
Name: a character string. Currently the only limit on length is internal buffer size, about 1000 bytes by default.
Value: an integer, floating-point number, or character string.
Time: the date and time of the last significant change to the point's value, confidence, quality or other status information.
Quality: the quality of the connection, assigned by the OPC DataHub for this point, such as Good, Bad, Last known, Local override, etc.
Confidence: a value from 0 to 100 that indicates as a percentage the probability that the value shown for the point is actually its true value. This feature can be accessed and changed only by using the API. the OPC DataHub never uses confidence itself, but carries it for use by client applications.
The OPC DataHub automatically creates a point whenever a connecting program tries to read, write, or create a point that doesn't exist. When the point is created, the OPC DataHub assigns its value, time, quality, and confidence.
It is possible to have the OPC DataHub create points and assign values to them at startup. Sometimes referred to as seeding, this is done with supplemental configuration files. Please refer to Appendix B, Configuration Files for more details.
It is not possible to directly delete points from the OPC DataHub. Should a point no longer be in use by any of the participating programs, when the DataHub is shut down and restarted, the point will no longer appear.
You can view the values of all data points with the Data Browser.
The OPC DataHub itself does not limit the size of a point data message. The only limits are those imposed by the operating system, and in Windows there are no such limits. If, however, you intend to share data between with Linux or QNX computers, there is a limit of 64000 bytes for QNX and 128000 bytes for Linux. In any case, bear in mind that very large values will take some time to be transmitted over a network.
Copyright © 1995-2010 by Cogent Real-Time Systems, Inc. All rights reserved.