Just as you add groups to the server's OPCGroup object, you add items to a group object. Items must be valid fields in the DeltaV database. The ItemID is the DeltaV path to the item (area name is not included). An example path note "OPCSAMPLE/STEP_COUNT.CV". The same item may exist in multiple groups. There are a few settings that are changed at the item level. They are:
RequestedDataType - This is the data type of the item that the client application would like to receive. For example, to request the String representation of a Named Set use a requested data type of string (VT_BSTR) instead an integer value (VT_I4).
ClientHandle - This value is any unsigned 32-bit integer. The DeltaV OPC Data Access Server will provide this handle when returning data in an asynchronous connection. This allows the client application to identify the item to which the data refers.
IsActive - The client application can change the active state of an item at any time using the SetActiveState command. If an item is not active the DeltaV OPC Data Access Server will not keep its value up to date. The client application will not be notified of changes. Read requests to cache will return successfully however, the data value will be stale and the quality status will be "bad" (for a detailed description of statuses, refer to Appendix B). Read requests to "device" always return the current value if no errors are encountered.
AccessPaths and Blobs are defined in the OPC specification but are not required for the DeltaV system. These variables are ignored.
The DeltaV OPC Data Access Server returns the following information about the item:
Canonical Data Type - This is the native data type of the item.
Server Handle - This is an unsigned 32-bit integer. Clients give this handle to the DeltaV OPC Data Access Server to identify an item. The DeltaV OPC Data Access Server uses the group server handle with the item server handle to identify the item.
AccessRights - This is the access rights allowed to a given item. The return values are Read only, Write only or Read/Write.
The DeltaV OPC Data Access Server assumes that all items are read/write. If a client application attempts to write to a parameter that is in fact read only in the DeltaV system, the write will fail, and the DeltaV OPC Data Access Server will return an error to the client.