.

Average: 0
Rating Count: 0

Development status: New development
Information status: Updated
Repository: http://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Acquisition/2D/TangoDALSA
Contact:



Class Description


Tango Device server for GigEVision cameras from teledyne dalsa

Remarks:

  • if you want to use atk panel (or other java programs) to view the ImageXX attributes make sure to start java with a sufficiently big -mx<memsize> switch

Families: Acquisition

Key words:

Platform: Unix Like

Language: Cpp

License: GPL

Contact:

Hardware


Manufacturer: https://www.teledynedalsa.com/

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.
ThrashedBuffersScalar: DevLong Number of buffers which were discarded due to no free buffers available. This number should not change while an acquisition is running. If it does, try increasing property FrameBuffers and restart the server.
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 alway be ImageSize (in bytes) x 1). 4: data are converted to RGB-JPEG and written to ImageEnc 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 format Mono8 will not be converted at all when ViewingMode is 1. Data are written to the attribute `as is`, lower cpu load - pixel formats Mono10/12/14/16 will not be converted at all when ViewingMode is 2. Data are written to the attribute `as is`, lower cpuload
ImageEncScalar: DevEncoded JPEG encoded representation of the acquired image(s). Attribute is written if ViewingMode is set to 4.
TurboModeScalar: DevBoolean
BinCommentScalar: DevString This goes as a comment into files of type nx (c.f FilePostfix). Max. length 256 chars.
NXFileCompressionScalar: DevShort aveat utilitor ! This works, but CPU load and memory usage might increase a lot. And if you collect files with compression enabled for a long time the OS might kill the server. It all depends on PixelFomat, ImageSize and FrameRate. So: test before using this in experiment setups.
FramesPerNXFileScalar: DevULong Max. number of frames written to one file if file format is nx. A new file will be created whenever this value is surpassed.
FrameRateScalar: DevDouble The camera I'm using for development cannot give us the framerate. So this is calculated form the time elapsing from the arrival of one frame to the next (and thus only gives a value when Acquistion is running). Might need some code fixing for other camera types.
FramesReceivedScalar: DevULong64 Number of frames received from camera and stored in internal queue.
FramesProcessedScalar: DevULong64 Number of frames processed (i.e. removed from the internal queue)
FileSavingScalar: DevBoolean f set to true, acquired images will be saved to files. Can be set / reset during acquisition.
FilePostfixScalar: DevString file postfix (determines file format). Supported file formats at time of writing are: tif/tiff nx: nexus hdf5 files
FileStartNumScalar: DevULong start number for files: - not initialized - incremented after every file - range 0 - 999999
FilePrefixScalar: DevString String prefixed to file names (memorized attribute). Strings containing any of ` .,\/` are considered invalid.
FileDirScalar: DevString directory path to store image files in - strings containing any of ' .,\': are considered invalid. - 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)

Commands:

Name Description
DeviceResetInput: DevVoid
Output: DevVoid
StartSingleAcquisitionInput: DevVoid
Output: DevVoid
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
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
DeviceIDDevString Identifier of camera, this can be: - the mac address - the serial number


Please log in to comment.

23 May 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



16 May 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



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



2 May 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



25 Apr 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



18 Apr 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



11 Apr 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



4 Apr 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



28 Mar 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



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



14 Mar 2020, DS Admin
Updated:
The device class has been updated.
You can see previous version here .



7 Mar 2020, DS Admin
Created:
The device class has been added to catalogue.
Added by:dadmin on:7 Mar 2020, 4:06 a.m.