top bar

Difference between revisions of "PVCAM"

Line 6: Line 6:
<tr><td>'''Platforms:'''</td><td>Windows and Mac OS X (linux possible but not tested)</td></tr>
<tr><td>'''Platforms:'''</td><td>Windows and Mac OS X (linux possible but not tested)</td></tr>
<tr><td>'''Devices:'''</td><td>MicroMax, Camera-1, Camera-2</td></tr>
<tr><td>'''Devices:'''</td><td>PVCAM compatible cameras</td></tr>
<tr><td>'''Example Config File:'''</td><td>[[Media:MMConfig_pvcam_simple.cfg]]</td></tr>
<tr><td>'''Example Config File:'''</td><td>[[Media:MMConfig_pvcam_simple.cfg]]</td></tr>

Revision as of 13:39, 1 September 2007

Roper/Photometrics PVCAM adapter

Summary:Interfaces with Roper and Photometrics cameras that work with the PVCAM driver
Author:Nenad Amodaj, with contributions from Nico Stuurman (Mac adaptation) and Ji Yu (expose more PVCAM properties)
Platforms:Windows and Mac OS X (linux possible but not tested)
Devices:PVCAM compatible cameras
Example Config File:Media:MMConfig_pvcam_simple.cfg

This adapter should work with all PVCAM compatible camera on all platforms. To use it, you will need to have the PVCAM software (download here) installed and working. At the very least, the pvcam test application should give you an image, and preferably RSImage works with your camera (although we have seen cases where Micro-Manager works with a PVCAM camera whereas RSImage does not). We tested it with an old MicroMax, a newer Firewire CoolSnap and Cascade II cameras on Windows and a Firewire Coolsnap ES, EZ, and HQ2 on Intel Mac. Some properties are relatively hard-coded, so you will find a property for EM gain even if your camera does not have it (we are working on this). Thanks to Ji Yu, most available camera properties are exposed. To use the adapter on Mac OS X, you will need at least version 2.7.7 of the PVCAM adapter (older versions will lock up your Mac).

If you encounter the following error message on startup: Error code: 39
Line 14: Property,Core,Initialize,1
Error code: 22
Device Undefined. Duplicate property names are not allowed.
then Micro-Manager was most likely not terminated in a graceful way during the previous session. Simply quit Micro-Manager, reboot your camera (by switching it off and back on again) and try again. One way of quitting Micro-Manager non-gracefully is by using the ImageJ 'Quit' command. ImageJ does not give Micro-Manager a chance to clean up and therefore will lead to this problem. When you use the Micro-Manager File->Quite command, things will be fine.

--Nico 11:33, 31 August 2007 (PDT)

© Micro-Manager : Vale Lab, UCSF 2006-2011 | All Rights Reserved | Contact