This is historical information of device classes implemented in OPCaccess device server.
Use this link to find the valid information.
Development status:
Released
Information status: New
Contact:
Class Description
- The OPCaccess class maps data items from an OPC server to Tango
attributes. For every OPCaccess device the attibute data type has to be specified. Tango can handle only double, long and short attributes. All OPC data items are casted to the requested data type. If an OPC item is an array (uses the ,lxx) extension in the item name, the tango attribute is created as a spectrum attibute.
For OPC servers which cannot handle array types, the property "array_handling" must be set to false to trigger correct data conversion.
Families: Communication
Key words:
Language: Cpp
Contact:
Class interface
Attributes:
Commands:
Name | Description |
---|---|
StateInput: DevVoid Output: State |
This command gets the device state (stored in its device_state data member) and returns it to the caller. |
StatusInput: DevVoid Output: DevString |
This command gets the device status (stored in its device_status data member) and returns it to the caller. |
ReadCacheInput: DevVoid Output: DevVoid |
Triggers reading of data from the OPC data cache. |
ReadDirectInput: DevVoid Output: DevVoid |
Triggers reading of data directly from the OPC item. |
Pipes:
Properties:
Name | Description |
---|---|
DataFromCacheDevShort | Triggers data reading from the OPC cache or directly from the OPC item. Set to 1 -> cache reading is enabled. Set to 0 -> direct access is enabled. |
Server_nameDevString | Specifies the name of the OPC server to be used. |
Path_nameDevString | Specifies the path of the OPC item to be addressed on the OPC server. |
Item_namesString[]Type | Specifies the OPC item names to be read from the OPC server via the given path. |
Data_typeDevString | This is set as the requested data type for the OPC items to be read. The possible data types are ``double``, ``long`` or ``short``. |
Array_handlingDevString | Specifies whether the OPC server used is capable to handle arrays or only scalar data types. array_handling = ``true`` , array data types are handled. array_handling = ``false``, only scalar data types are handled. |
README
b'//-============================================================\n//\n// This class has been generated by POGO\n// (Program Obviously used to Generate tango Object)\n//\n// (c) - Software Engineering Group - ESRF\n//=============================================================\n\n\nFiles generated:\n===============\nOPCaccess.cpp: Source code for the OPCaccess class and its commands.\n This class is derived from DeviceImpl_2 class.\n It represents the CORBA servant obbject which\n will be accessed from the network.\n All commands which can be executed on the\n OPCaccess are implemented in this file.\n\nOPCaccess.h: Include for the OPCaccess class.\n Server class prototypes and descriptions.\n\nOPCaccessClass.cpp: A singleton class derived fromOPCaccess.\n It implements the command list and all properties\n and methods required by the OPCaccess once per process\n\nOPCaccessClass.h:\tInclude for the OPCaccessClass root class.\n This class is represents the singleton class for\n the OPCaccess device class.\n It contains all properties and methods which the \n OPCaccess requires only once e.g. the commands.\n\nmain.cpp:\t\tC++ source for a TANGO device server main.\n The main rule is to initialise (and create) the Tango\n system and to create the DServerClass singleton.\n The main should be the same for every Tango device server.\n\nClassFactory.cpp:\tC++ source for the class_factory method of the DServer\n device class. This method is responsible to create\n all class singletin for a device server. It is called\n at device server startup\n'
Updated:
The device class has been updated.
You can see previous version here .
20 Apr 2017, Piotr Goryl
Updated:
The device class has been updated.
You are looking at this version now.
23 Feb 2017, Piotr Goryl
Created:
The device class has been added to catalogue.