Device Status Types
This applies for
DeviceAccess devices.
Device status types, for example
device status type GATE
of the
device GUL3VV0T
of the
device type VVC
provide a more fine grained definition of status bit meanings. This was necessary since not all bits are relevant for the use in applications. The device status types definitions were once created by FEC but then refined by SRV and APP.
Device to Status Type Mapping
A mapping of device name to status type is stored in the OperDB managed by Susi. Applications currently use a CSV export of the file
device-control-app-OperdbInfo.csv (in the DCL) since the data is not expected to be changed a lot anymore. The list might be modified and is then merged back with the database regularly.
#NOMEN,#TYP,#SUBTYP,#STATUSTYP,#XAPERTUR,#YAPERTUR,#PIKTOGRAMM
#GUL3VP1T,null,null,NONE,0,0,0
#GUL3VP2T,null,null,NONE,0,0,0
GUL3VV0T,GATE,null,GATE,0,0,11
GUL4BG1,GAPU,null,NONE,25,25,23
GUL4DT4,TRAF,NORM,NORM,37,37,75
GUL4MS1H,MAGN,STER,MG8B,50,50,2
GUL4MS1V,MAGN,STER,MG8B,50,50,3
…
Status Type Definition
A list of status types and their bit definitions can be found in the
devacc-status-lib git project. See
src/main/resources/de/gsi/cs/co/ap/cscoap_common_status_files.
Example
GATE.STATUS
:
!*GATE___
00 00000001 0 "Netz aus" "Netz aus"
00 00000001 1 "Netz ein" "Netz ein"
01 00000002 0 "manuell " "Handsteuerung"
…
Other sources of status bit definitions
- Equipment Model Documentation
- Device header files comments
- Ion Source Fx App status bit documentation
- Focused on Ion Source and manually updated (or not)
-
smb://srvfilegrp07.gsi.de/acogroup/Group_APP/Applications/IonSource/Statusbits.xls
Device Type
In order to find out the device type of a device you can query the middleware config service
Response example:
{"protocol":"devacc","deviceName":"GUL3VV0T","model":"VVC_11"}
Example
DevAcc