.
Development status:
Released,
Release: Release_1_0
Information status: New
Repository:
http://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Acquisition/1D/OceanOpticsQEPRO
Contact:
Class Description
Tango device server for OceanOptics QE-PRO spectrometer
Families: Acquisition
Key words:
Platform: Unix Like
Language: Cpp
License: GPL
Contact:
Hardware
Manufacturer: https://www.oceaninsight.com
Product:
Bus: USB
Class interface
Attributes:
| Name | Description |
|---|---|
| TriggerModeScalar: DevLong | Set trigger mode, 0 = normal 1 = software 2 = synchronization 3 = external hardware There may be more, check your particular spectrometer`s data sheet Unfortunately there`s no way to find the state of the trigger from the device (the library does only provide a set_trigger_state call, but not a get_trigger_call). To remedy this the server will set the trigger to 0 at server start; this means you have to change that after server start if necessary. |
| IntegrationTimeScalar: DevULong | Integration time in microseconds. Unfortunately there`s no way to find the set integration time from the device. The server will set the time to the minimum value at start, change it if needed. |
| LampScalar: DevBoolean | Enable ( =true ) or disable ( = false) lamp. Unfortunately there`s no way to find the set lamp state from the device. The server will set the lamp state to disabled at start, change it if needed. |
| TecTemperatureScalar: DevDouble | Read / write temperature of Thermoelectric cooler |
| TECScalar: DevBoolean | Enable ( =true ) or disable ( = false) cooler. Unfortunately there`s no way to find the set cooler state from the device. The server will set the cooler state to enabled at start, change it if needed. |
| FileDirScalar: DevString | directory path to store spectra files in - the directory must exist - the server will check if the user running the server has write permissions for this directory, if not, the device will go to state fault / throw an exception - the attribute is memorized (last written value stored in tango db and read from there at server startup) |
| FilePrefixScalar: DevString | String prefixed to file names (memorized attribute). Only supported format is hdf5, files will have extension 'h5'. |
| FileStartNumScalar: DevULong | Start number for files: - incremented after every file - range 0 - 999999 |
| FileSavingScalar: DevBoolean | if set to true, acquired spectra will be saved to files. Can be set / reset during acquisition. |
| SpectraPerFileScalar: DevULong | Max. number of spectra written to one file. A new file will be created whenever this value is surpassed. 0 means all frames go into one file. |
| SpectraToAcquireScalar: DevULong | Number of spectra to acquire. After this many spectra were acquired the acquisition will stop. 0 means acquire continuously until StopAcquisition is called. |
| DarkSpectrumFileScalar: DevString | — |
| BrightSpectrumFileScalar: DevString | — |
Commands:
| Name | Description |
|---|---|
| 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. |
| StartAcquisitionInput: DevVoid Output: DevVoid |
Start acquiring spectra. Depending on the set integration time it may take a while until you see valid data in attribute Spectrum. |
| StopAcquisitionInput: DevVoid Output: DevVoid |
Stop acquiring spectra. Depending on the set integration time it may take a while until the device goes from state MOVING ( = acquiring) to state ON, since it will only go to ON after the current spectrum has been read. |
| GetDarkSpectrumInput: DevVoid Output: DevVoid |
read dark spectrum and store it in file set in DarkSpectrumFile |
| GetBrightSpectrumInput: DevVoid Output: DevVoid |
read bright spectrum and store it in file set in BrightSpectrumFile |
Pipes:
Properties:
| Name | Description |
|---|---|
| SerialNumberDevString | Serial number of device, used for identification. If you do not know it, plug the device into a linux box and check the output of dmesg. You should find something like this: [17370053.227300] usb 6-2: new full-speed USB device number 2 using uhci_hcd [17370053.416349] usb 6-2: New USB device found, idVendor=2457, idProduct 4004, bcdDevice= 0.67 [17370053.416352] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [17370053.416354] usb 6-2: Product: QE-PRO [17370053.416356] usb 6-2: Manufacturer: Ocean Optics [17370053.416358] usb 6-2: SerialNumber: QEP03366 |
| TriggerDeviceAttributeDevString | Name of device attribute which generates triggers (if you want to use triggers). Requirement: a value of 1 means trigger high, 0 means trigger low, If you cannot provide something like this, leave this property at ````. You will then, if you run acquisition with TriggerMode 1 or 3, have to make sure that the trigger line is high before you call StopAcquisition. Otherwise acquisition will not stop. At the time of writing these datatypes are suppoted for TriggerDeviceAttribute: - Tango::DevLong - Tango::DevULong - Tango::DevBoolean Can be extended on request |
Please log in to comment.
13 Nov 2021, DS Admin
Created:
The device class has been added to catalogue.
Created:
The device class has been added to catalogue.
Added by:dadmin
on:13 Nov 2021, 2:58 a.m.