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

Use this link to find the valid information.

Development status: Released, Release: Release_2_2
Information status: Updated
Repository: http://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Acquisition/2D/TangoVimba
Contact:



Class Description


Tango device server for genicam compatible GigE cameras

Families: Acquisition

Key words:

Platform: Unix Like

Language: Cpp

License:

Contact:

Hardware


Manufacturer: none

Bus: Ethernet

Class interface


Attributes:

Name Description
FileDirScalar: DevString Directory to store image files in
FilePrefixScalar: DevString String prefixed to file names
FileStartNumScalar: DevULong Start number for files
FilePostfixScalar: DevString file postfix (determines file format). Supported file formats at time of writing are: bmp jpg/jpeg png ppm pbm pgm tif/tiff xbm xpm bin: raw data from camera mbin : raw data from camera + header containing some meta information: byte 0-1: header size byte 2-9: recording time in us since 1.1.1970 byte 10-13: Image width byte 14-17: Image heigth byte 18-21: Horizontal offset byte 22-25: Vertical offset byte 26-29: BinningX (if supported by camera) byte 30-33: BinningY (if supported by camera) byte 34-37: PixelFormat (cf. vimba doc) byte 38-39: length of serial number( = X) byte 40-40+X: serial number of camera as string after serial number: 2 bytes containing length of comment for file type mbin, cf. Attribute BinComment after length of comment: comment as string after comment: image data Format mbin is not supported on some older cameras due to missing timestamp feature (sometimes a camera firmware update helps). nx: nexus hdf5 files (see also property XMLTemplate)
FileSavingScalar: DevBoolean if set to true, acquired images will be saved to files
ReadModeScalar: DevString How image data are processed before being written to Image attribute - flat : pixel = pixel - log10 : pixel = log10(pixel) - sqrt : pixel = sqrt(pixel) This has no effect when reading to RawImage.
FramesProcessedScalar: DevULong Number of frames processed
TuneModeScalar: DevUShort Mode for adjusting camera frame rate: 0 = no adjustment 1 = frame rate will be set the maximum number of frames the server can process (may produce high cpu loads) 2 = frame rate will be set so that the server will consume max. MaxLoad % cpu time
MaxLoadScalar: DevDouble Max. allowed cpu load if TuneMode is set to 2
ViewingModeScalar: DevShort How camera data are written to attributes: 0 : nothing is written to any attributes 1: data are converted to 8-bit greyscale and written to Image8 2: data are converted to 16-bit greyscale and written to Image16 3: data are not converted and written to ImageRaw (ImageRaw dimensions will always be ImageSize (in bytes) x 1). Note 1: not all pixel formats can be converted to 16-bit greyscale. An exception will be thrown if the current camera pxel format cannot be converted. Note 2: if you change the viewing mode while acquisition is running the acquisition has to be restarted in the server process. This means that a file which is in the process of being written will be closed.
BinCommentScalar: DevString This goes as a comment into files of type mbin (c.f FilePostfix). Max. length 256 chars.
Image8Image: DevUChar Array of unsigned char representing the acquired image(s). Pixel data will be converted to 8-bit greyscale.
Image16Image: DevUShort Array of unsigned short representing the acquired image(s). Pixel data will be converted to 16-bit greyscale.
ImageRawImage: DevUChar Array of unsigned char representing the acquired image(s). Pixel data will be converted to 8-bit greyscale to maximize transfer speed.

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 continous image acquisition
StopAcquisitionInput: DevVoid
Output: DevVoid
Stop continous image acquisition
StartSingleAcquisitionInput: DevVoid
Output: DevVoid
Acquire single image

Pipes:

Properties:

Name Description
HostNameDevString host name or ip address of camera
DynAttrListArray of DevString for internal use only
VisibleAttributesArray of DevString Since different cameras support different features (and the same feature may even have different names on a different camera), camera features are dynamically converted into device attributes. Converting all available camera features into attributes will create a quite lengthy and cluttered list, so you can put those features you want to see as device attributes into this list. Only the features mentioned here will be shown as attributes. To find out about the available features of a camera either use a program like VimbaViewer or leave this list empty. Then all features will be shown as attributes. For features which are of type enumeration (e.g. PixelFormat) an additional read-only attribute <FeatureName>#Values will be created. This shows the possible values for this feature on this camera.
FrameBuffersDevUShort Number of frame buffers for image acquistion (defaults to 4)
GainFeatureNameDevString Depending on the camera type the name of the Gain feature differs(e,g. `Gain`, `GainRaw`). Please check for the camera you are using and enter the appropriate string here.
DeviceIDDevString - the IP address - the mac address - the ID as reported by Vimba (DEV_XXXXXXXXX) - the serial number If given, property Hostname will be ignored.
XMLTemplateDevString Here you can give the name of an xml file which you can use to add static data e.g about your insxtrument to nexus files. The file has at least to look like this: ----------------------------------------------------------- <group name=``/`` type=``NXroot``> <group name=``entry`` type=``NXentry``> <group name=``instrument`` type=``NXinstrument``> <group name=``detector`` type=``NXdetector``> <field name=``description`` type=``string``> </field> <field name=``serial_number`` type=``string``> </field> <field name=``comment`` type=``string``> </field> <field name=``source_pixelformat`` type=``string``> </field> <field name=``data_pixelformat`` type=``string``> </field> <field name=``width`` type=``uint32``> </field> <field name=``heigth`` type=``uint32``> </field> <field name=``xoffset`` type=``uint32``> </field> <field name=``yoffset`` type=``uint32``> </field> <field name=``xbinning`` type=``uint32``> </field> <field name=``ybinning`` type=``uint32``> </field> <field name=``framerate`` type=``float32``> </field> <field name=``gain_setting`` type=``{{GAIN_TYPE}}``> </field> <field name=``exposure`` type=``float32``> </field> <field name=``bits_per_pixel`` type=``uint32``> </field> <field name=``bits_used`` type=``uint32``> </field> <field name=``timestamps`` type=``uint64``> <dimensions rank=``2``> <dim index=``0`` value=``0``/> <dim index=``1`` value=``1``/> </dimensions> </field> <field name=``data`` type=``{{PIXEL_TYPE}}`` units=``a.u.``> <dimensions rank=``3``> <dim index=``0`` value=``0``/> <dim index=``1`` value=``{{NX}}``/> <dim index=``2`` value=``{{NY}}``/> </dimensions> </field> </group> </group> </group> </group> ----------------------------------------------------------- If the property is not set or empty a default template will be used.

March 9, 2019, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



Dec. 1, 2018, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



April 21, 2018, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



April 7, 2018, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



Oct. 7, 2017, Piotr Goryl
Updated:
The device class has been updated.
You can see previous version here .



Aug. 26, 2017, Piotr Goryl
Updated:
The device class has been updated.
You are looking at this version now.



April 29, 2017, Piotr Goryl
Updated:
The device class has been updated.
You can see previous version here .



April 20, 2017, Piotr Goryl
Updated:
The device class has been updated.
You can see previous version here .



Feb. 23, 2017, Piotr Goryl
Updated:
The device class has been updated.
You can see previous version here .



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



Jan. 2, 2017, Piotr Goryl
Created:
The device server has been added to catalogue.
Added by:pgoryl2 on:26 Aug 2017, 5:01 a.m.