This is historical information of device classes implemented in TangoCA device server.
Use this link to find the valid information.
Development status:
Released,
Release: release_1_1_1
Information status: Updated
Repository:
http://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Communication/TangoCA
Contact:
Class Description
This is the tango channel access device server using ezCA
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. |
ReadDoublePVInput: DevString Output: DevDouble |
Read a double PV on a EPICS CAS / IOC |
WriteDoublePVInput: DevVarDoubleStringArray Output: DevVoid |
Write on a double PV on a EPICS CAS / IOC |
ReadLongPVInput: DevString Output: DevLong |
Read a value on a Long PV |
WriteLongPVInput: DevVarLongStringArray Output: DevVoid |
Write on a Long PV on a EPICS CAS / IOC |
ReadStringPVInput: DevString Output: DevString |
Read a String value from an EPICS CAS / IOC PV |
WriteStringPVInput: DevVarStringArray Output: DevVoid |
Write a String value on an EPICS CAS / IOC PV |
SetDoubleMonitorInput: DevString Output: DevVoid |
Put a monitor on the wanted Double PV |
ClearDoubleMonitorInput: DevString Output: DevVoid |
Clear the monitor of the wanted Double PV |
SetLongMonitorInput: DevString Output: DevVoid |
Set a Monitor on a Long PV |
ClearLongMonitorInput: DevString Output: DevVoid |
Clear the monitor on a Long PV |
IsNewMonitorValueInput: DevString Output: DevLong |
Indicate if the Monitor value has change |
MonitorDelayInput: DevFloat Output: DevVoid |
Make a tempo of Argin sec. Used for not losing changes of the PV |
Pipes:
Properties:
Name | Description |
---|---|
EzTimeoutDevFloat | Timeout of the ezca internally calls (not the Tango device server timeout |
EzRetryCountDevLong | Retry count of the ezca internal calls |
TangoRetryCountDevShort | Number of retry in the TangoEZCA Device Server commands |
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===============\nTangoEZCA2.cpp: Source code for the TangoEZCA2 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 TangoEZCA2 are implemented in this file.\n\nTangoEZCA2.h: Include for the TangoEZCA2 class.\n Server class prototypes and descriptions.\n\nTangoEZCA2Class.cpp: A singleton class derived fromTangoEZCA2.\n It implements the command list and all properties\n and methods required by the TangoEZCA2 once per process\n\nTangoEZCA2Class.h:\tInclude for the TangoEZCA2Class root class.\n This class is represents the singleton class for\n the TangoEZCA2 device class.\n It contains all properties and methods which the \n TangoEZCA2 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 are looking at this version now.
20 Apr 2017, Piotr Goryl
Updated:
The device class has been updated.
You can see previous version here .
23 Feb 2017, Piotr Goryl
Created:
The device class has been added to catalogue.