.

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/Pco
Contact:



Class Description


The Tango PCO ccd class uses the software development kid (SDK) for Windows

from PCO to access the ccd devices.

http://www.pco.de/software/

The SDK is capable to handle a series of different ccd cameras. The server was tested with a Pco4000 camera but should work also for the other cameras supported by the SDK.

The camera dependent parameters like the maximum image size for example is read directly from the hardware via the camera description structure of the SDK. These parameters are displayed in the status text.

Actually the server works only with one camera. To handle several cameras on the same PC, some extension is necessary.

Device server for PCO ccd cameras Device Description Pco Class

Revision: - Author:

The Tango PCO ccd class uses the software development kid (SDK) for Windows from PCO to access the ccd devices.

http://www.pco.de/software/

The SDK is capable to handle a series of different ccd cameras. The server was tested with a Pco4000 camera but should work also for the other cameras supported by the SDK.

Families: Acquisition

Key words: 2D

Language: Cpp

License:

Contact:

Class interface


Attributes:

Name Description
ImageScalar: DevEncoded
ExposureTimeScalar: DevDouble
DelayTimeScalar: DevDouble
TriggerModeScalar: DevShort
FileSavingScalar: DevBoolean
FileDirScalar: DevString
FilePrefixScalar: DevString
FileStartNumScalar: DevLong
FilePostfixScalar: DevString
WidthScalar: DevLong
HeigthScalar: DevLong
ImageCounterScalar: DevLong
Binning_xScalar: DevShort
Binning_yScalar: DevShort
ROI_x_minScalar: DevLong
ROI_x_maxScalar: DevLong
ROI_y_minScalar: DevLong
ROI_y_maxScalar: DevLong
PixelrateScalar: DevLong
ADCsScalar: DevShort
CoolingTempSetScalar: DevShort
CoolingTempScalar: DevDouble
ImageTimeStampScalar: DevBoolean

Commands:

Name Description
StateInput: DevVoid
Output: State
This command gets the device state (stored in its device_state data member) and returns it to the caller.
StatusInput: DevVoid
Output: DevString
This command gets the device status (stored in its device_status data member) and returns it to the caller.
ResetInput: DevVoid
Output: DevVoid
Reset a FAULT state and set the binning to 1 and the ROI to the full image size.
StopInput: DevVoid
Output: DevVoid
Stop the current acquisition.
StartStandardAcqInput: DevVoid
Output: DevVoid
Start an acquisition with the prepositioned parameters
LiveInput: DevVoid
Output: DevVoid
Start a live acquisition. Image are aquired in an endless loop with the prepositioned parameters. The Stop command ends the live acquisition.

Pipes:

Properties:


Please log in to comment.

Generated

PDF generated from POGO



README

b'Before compiling, you will have to install:\n- The pco.sdk, available from http://www.pco.de/de/software/\n The Tango server was tested using SW_PCOSDKWIN_114_0002.zip:\n other releases should also work.\n- The Silicon Software Runtime Environment from\n http://www.silicon-software.com/download.html (eg\n RuntimeSetup_v5.1.4_IA32.exe or RuntimeSetup_v5.1.4_AMD64.exe, depending\n whether you want to compile a 32- or 64-bit application).\n- ImageMagick headers and libraries, available from\n http://www.imagemagick.org/script/binary-releases.php\n The Tango server was tested using\n ImageMagick-6.7.3-3-Q16-windows-x64-dll.exe (32-bit) and\n ImageMagick-6.7.3-3-Q16-windows-x64-dll.exe (64-bit): other releases should\n also work, but you will have to change the headers and libraries path in\n MAKEFILE.\n- HDF5 headers and libraries, available from http://www.hdfgroup.org/HDF5/\n The Tango server was tested using HDF5-1.8.7_win_x86.zip (32-bit) and\n HDF5-1.8.7_win_x64.zip (64-bit); they were unzipped and moved respectively\n to "C:\Program Files (x86)" and "C:\Program Files". Other releases should\n also work, but you will have to change the headers and libraries path in\n MAKEFILE.\n- There is data type incompatibility between ImageMagick and HDF5 on Windows\n 32-bit. This might be solved by future releases of the packages. See below,\n "Known problems (and solutions)"\n- Tango must be installed. As of today, Tango for 64-bit windows only has lib,\n bin and headers. MAKEFILE assumes Tango has been unzipped in\n "C:\Program Files\tango-win-x64-bin-dist-msvc-2010". This may change in\n future.\n- The Tango server can be compiled using Visual Studio. As of today Tango\n 32-bit ships libraries for Visual C++ 2005 (VC8) and 2008 (VC9). This may\n change in future, in this case the MAKEFILE will need to be changed.\n\nHow to compile:\n- To compile a 64-bit executable Pco.exe, you will need the also MS Windows\n SDK. Open the "Windows SDK Command Prompt", go to the directory containing\n the Pco source files and then run "nmake win64".\n- To compile a 32-bit version of the Pco.exe, use Visual Studio C++ 2005 (VC8)\n or 2008 (VC9).\n Open e.g. the "Visual Studio 2008 Command Prompt", go to the source directory\n and then run "nmake win32".\n\nHow to run Pco.exe:\n- First of all, the pco.sdk\bin (or pco.sdk\bin64 for a 64-bit executable)\n directory must be in the path. This also applies to ImageMagick and HDF5 bin\n directories.\n- Open a command prompt, go to the directory containing the Pco.exe, and run\n the command "Pco.exe <device name>"\n\nKnown problems (and solutions):\n\n With currently used versions of ImageMagick (ImageMagick-6.7.3-3-Q16) and \n HDF5 (HDF5-1.8.7) there is a data type incompatibility on Windows 32-bit. \n The first package defines ssize_t as type "long", whereas the latter as type \n "int". Even if the data types have the same size (sizeof(int) == \n sizeof(long) == 4) they are incompatible. On Windows 64-bit both packages \n define ssize_t to be "long long". The solution is to replace to follwing\n lines of "C:\Program Files (x86)\HDF5-1.8.7_win_x86\include\H5public.h":\n\n#if H5_SIZEOF_SSIZE_T==0\n/ Undefine this size, we will re-define it in one of the sections below\n/\n#undef H5_SIZEOF_SSIZE_T\n#if H5_SIZEOF_SIZE_T==H5_SIZEOF_INT\ntypedef int ssize_t;\n# define H5_SIZEOF_SSIZE_T H5_SIZEOF_INT\n#elif H5_SIZEOF_SIZE_T==H5_SIZEOF_LONG\ntypedef long ssize_t;\n# define H5_SIZEOF_SSIZE_T H5_SIZEOF_LONG\n#elif H5_SIZEOF_SIZE_T==H5_SIZEOF_LONG_LONG\ntypedef long long ssize_t;\n# define H5_SIZEOF_SSIZE_T H5_SIZEOF_LONG_LONG\n#else / Can\'t find matching type for ssize_t /\n# error "nothing appropriate for ssize_t"\n#endif\n#endif\n\n with\n\n/ Define the ssize_t type if it not is defined /\n#if H5_SIZEOF_SSIZE_T==0\n#undef H5_SIZEOF_SSIZE_T\n#if H5_SIZEOF_SIZE_T==H5_SIZEOF_LONG_LONG\ntypedef long long ssize_t;\n# define H5_SIZEOF_SSIZE_T H5_SIZEOF_LONG_LONG\n#elif H5_SIZEOF_SIZE_T==H5_SIZEOF_LONG\ntypedef long ssize_t;\n# define H5_SIZEOF_SSIZE_T H5_SIZEOF_LONG\n#elif H5_SIZEOF_SIZE_T==H5_SIZEOF_INT\ntypedef int ssize_t;\n# define H5_SIZEOF_SSIZE_T H5_SIZEOF_INT\n#else / Can\'t find matching type for ssize_t /\n# error "nothing appropriate for ssize_t"\n#endif\n#endif\n\n (This trick solves the conflict between ImageMagick and HDF5, but may \n introduce conflicts with other packages!)\n\n There is also a problem with the pixel rate on pco.edge, on which the server \n was tested. Currently images cannot be acquired with a pixel rate of 286 MHz \n and full image size (2560 x 2160 pixels). The images will be corrupted, and \n moreover the camera will not be accessible any more and need to be switched \n off and on. For a full image size a pixel rate of 95 MHz must be used \n (leading to a maximum framerate of about 30 Hz). The 286 MHz pixel rate can \n only be used with 4 megapixels or less.\n\nA. Parenti\nHamburg, 20.01.2012 '

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



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



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



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



23 Feb 2017, Piotr Goryl
Created:
The device class has been added to catalogue.
Added by:pgoryl2 on:23 Feb 2017, 9:17 a.m.