This is historical information of device classes implemented in FPS3010LCtrl device server.

Use this link to find the valid information.

Development status: Released
Information status: Updated

Class Description

Tango device server for Attocube FPS3010 interferometer

Families: MeasureInstruments

Key words:

Platform: Unix Like

Language: Cpp

License: GPL



Manufacturer: Attocube


Bus: Not Applicable

Class interface


Name Description
DeviceFeaturesScalar: DevLong Bitfield: 0x01: Ethernet enabled 0x02: Angular measurement 0x04: Digital inputs 0x08: Environmental compensation
CollectDataUpdateTimeScalar: DevULong Logarithmic time distance of two subsequent position measurements. The actual sample time can be varied only in powers of two: sample time = 10.24us * (2 ^ lbSmpTime). Allowed range is 0 ... 24 (10.24us ... 172s) . The sample time directly affects the data rate!
CollectDataMaxSizeScalar: DevULong The maximum number of position data elements the CollectDataStart / CollectDataTime are allowed to collect. Once this value is exceeded data collection will be stopped. This is just a precaution tp prevent the program from eating up all the memory if someone forgets to call CollectDataStop or runs CollectDataTime with a too high setting.
FileDirScalar: DevString
FilePrefixScalar: DevString
FileStartNumScalar: DevLong
FilePostfixScalar: DevString
FileSavingScalar: DevBoolean
TemperatureScalar: DevDouble
AirPressureScalar: DevDouble
HumidityScalar: DevDouble
RefractionScalar: DevDouble
PositionsSpectrum: DevDouble


Name Description
ResetAxisInput: DevULong
axis number (0-2)
Output: DevVoid
SignalQualityInput: DevULong
Axis number (0-2)
Output: DevULong
signal quality (the higher the better)
StateInput: DevVoid
Output: State
Device state
This command gets the device state (stored in its device_state data member) and returns it to the caller.
StatusInput: DevVoid
Output: ConstDevString
Device status
This command gets the device status (stored in its device_status data member) and returns it to the caller.
AxisStatusInput: DevULong
axis number
Output: DevLong
0: axis is successfully aligned, signal quality is sufficient 1: axis is successfully aligned, signal quality is insufficient 2: axis is not successfully aligned, signal quality is sufficient 3: axis is not successfully aligned, signal quality is insufficient
AdjustInput: DevVoid
Output: DevVoid
start the adjustment procedure
RecalibrateInput: DevVoid
Output: DevVoid
Start the recalibration procedure.
SetPollTimeInput: DevVarULongArray
arg[0] : axis number arg[1] : poll time (= 80ns * (2 ^ arg[1]), range 0->31
Output: DevVoid
GetPollTimeInput: DevULong
axis number
Output: DevULong
poll time (= 80ns * (2 ^ arg[1]), range 0->31
get poll time for axis
CollectDataTimeInput: DevULong
time to run position data collection in ms
Output: DevVoid
time to run position data collection in ms
GetMeanDevInput: DevULong
Output: DevVarDoubleArray
0: average value 1: standard deviation
Get results per axis after a CollectData call
RunCallBackInput: DevVarUShortArray
0:true: start callback function 0:false: stop callback function 1:true routine ran ok 1:false: routine hit datasize limit
Output: DevVoid
for internal use only, never call from client
CollectDataStartInput: DevVoid
start position data collection
Output: DevVoid
CollectDataStopInput: DevVoid
stop position data collection
Output: DevVoid
GetCollectDataInput: DevULong
Axis number
Output: DevVarDoubleArray



Name Description
DeviceIDDevLong ID of device, if no IpAdress is set or ConnectType is empty or set to `usb`, the ID is used to identify the device.
ConnectTypeDevString Connection method, may be `net` for tcp/ip or `usb` for usb. If empty / not set, devices will be searched on both types.
HostNameDevString IP Address or hostname If set, device will be identified by this name/address, otherwise identification will be done by DeviceID.
TriggerSourceDevString Device/Attribute which emits trigger signal to start data collection
UseTriggerDevBoolean whether to use trigger (true) or not (false)

23 Feb 2017, Piotr Goryl
The device class has been updated.
You are looking at this version now.

19 Jan 2017, Piotr Goryl
The device server has been updated.
You can see previous version here .

2 Jan 2017, Piotr Goryl
The device server has been added to catalogue.
Added by:pgoryl2 on:23 Feb 2017, 11:21 a.m.