.

Average: 0
Rating Count: 0

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



Class Description


Tango device server for Allied Vision GigE cameras

Families: Acquisition

Key words:

Platform: Unix Like

Language: Cpp

License: GPL

Contact:

Hardware


Manufacturer: Allied Vision

Product:

Bus: Ethernet

Class interface


Attributes:

Name Description
ImageRawImage: DevUChar Array of unsigned char representing the acquired raw image date. ImageRaw dimensions will always be ImageSize (in bytes) x 1) Attribute is written if ViewingMode is set to 3.
Image16Image: DevUShort Array of unsigned short representing the acquired image(s). Pixel data will be converted to 16-bit greyscale. Attribute is written if ViewingMode is set to 2.
Image8Image: DevUChar Array of unsigned char representing the acquired image(s). Pixel data are converted to 8-bit greyscale. Attribute is written if ViewingMode is set to 1.
BinCommentScalar: DevString This goes as a comment into files of type mbin or nx (c.f FilePostfix). Max. length 256 chars.
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: - not all pixel formats can be converted to 16-bit greyscale. An exception will be thrown if the current camera pixel format cannot be converted. - pixel formats Mono10/12/14 (unpacked) will not be converted at all when ViewingMode is 2. Data are written to the attribute 'as is'.
MaxLoadScalar: DevDouble Max. allowed cpu load if TuneMode is set to 2
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
FramesProcessedScalar: DevULong Number of frames processed
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. Modified values are not written to files.
FileSavingScalar: DevBoolean if set to true, acquired images will be saved to files. Can be set / reset during acquisition.
FilePostfixScalar: DevString file postfix (determins file format). Supported file formats at time of writing are: bmp jpg/jpeg png ppm pbm pgm tif/tiff xbm xpm nx 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)
FileStartNumScalar: DevULong Start number for files: - not initialized - incremented after every file - range 0 - 999999
FilePrefixScalar: DevString String prefixed to file names (memorized attribute)
FileDirScalar: DevString directory path to store image 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 to state fault - the attribute is memorized (last written value stored in tango db and read from there at server startup)

Commands:

Name Description
StartSingleAcquisitionInput: DevVoid
Output: DevVoid
Acquire single image
StopAcquisitionInput: DevVoid
Output: DevVoid
Stop continous image acquisition
StartAcquisitionInput: DevVoid
Output: DevVoid
Start continous image acquisition
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.
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.

Pipes:

Properties:

Name Description
XMLTemplateDevString Here you can give the name of an xml file which you can use to add static data e.g about your instrument 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=``model`` type=``string``> </field> <field name=``serialnumber`` type=``string``> </field> <field name=``comment`` type=``string``> </field> <field name=``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`` type=``{{GAIN_TYPE}}``> </field> <field name=``exposure`` type=``float32``> </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}}``> <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.
DeviceIDDevString Identifier of camera, this can be: - the mac address (notation e.g. 000F3101C94A, no `-` or `:` between digits) - the ID as reported by Vimba (e.g. DEV_000F3101C94A) - the serial number (e.g. 02-2110A-07625) (use of ip address as identifier is not supported - hot plugging won`t work with ip address)
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.
FrameBuffersDevUShort Number of frame buffers for image acquistion (defaults to 4)
VisibleAttributesArray of DevString Since different cameras support different features (and the same feature may even have different names on different cameras), 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.
DynAttrListArray of DevString for internal use only


Please log in to comment.

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 can see previous version here .



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:2 Jan 2017, 3:46 p.m.