top bar


Revision as of 05:50, 7 November 2011 by P.nanda (Talk | contribs)

Summary: Interfaces with Andor cameras
Authors: Nenad Amodaj (Windows)
Karl Bellvé (Linux port)
Jizhen Zhao, Daigang Wen, Francis McCloy (Andor contributors)
Maintainers: David Gault (Andor)
Arthur Edelstein
Karl Bellvé (Linux port)
Pariksheet Nanda (Andor) this document
License: BSD
Platforms: Windows and Linux (No Mac driver available)
Devices: iXon, iXon+, iXon3
Luca-S, Luca-R
Clara, Clara-E


Andor SDK

You must install the Andor SDK, or Andor camera application software (Solis or iQ), since it contains the necessary files to recognize the camera. If you need to download a copy of the Andor SDK, since is not publicly available, request Andor support to gain access to it, stating in the support request form you need the drivers for µManager.

Disable power savings

Commercial computers like Dell, HP, etc shipped in the US and Europe are legally required by environmental regulations to ship with all power savings turned on. These must be disabled in the BIOS.

Additionally for Windows 7, turn off PCI power management and USB suspend settings

Test communication

The Andor SDK installs test programs that can be used to get live images:

     C:\Program Files\Andor SOLIS\Drivers\Examples\C\

Fixing computer bus speed bottlenecks


iXon PCIe cameras can have their live stream stops after 2 or 3 images or not start at all. The reason for this is PC motherboards throttle the PCIe speed depending on the daughter boards populated. Make sure you plug the PCIe card into a fast enough bus.

For example the Dell XPS desktop 1x PCIe bus will not run at the rated speed when the PCIe 16x graphics card is populated, so you have to instead connect the Andor PCIe card to 8x PCIe slot


iXon 885 PCI cameras can have their live stream not start at all, but will work if you bin the image 2x2 or slow the horizontal clock speed from 35MHz to 13MHz. The reason for this is a small set of PC motherboards may not fully comply with the PCI standard bandwidth, so try another motherboard (or more conveniently another computer)


USB cameras using high bandwidth such as the Clara must be plugged into the computer to be its own USB bus:

Windows OS

You need to use a utility like UVCview.

UVCview on Windows showing the Clara by itself, i.e. with no other devices sharing the USB bus:

Good Clara USB Connection cropped.JPG

Linux OS

You can easily check USB bus position with lsusb -t. The shell output below shows that the Clara (Vendor 0x136e Product 0x000e) has been correctly plugged into its own USB bus (Bus# 1):

     $ lsusb -t
     Bus#  5
     `-Dev#   1 Vendor 0x1d6b Product 0x0001
     Bus#  4
     `-Dev#   1 Vendor 0x1d6b Product 0x0001
       |-Dev#   2 Vendor 0x046d Product 0xc045
       `-Dev#   3 Vendor 0x2341 Product 0x0001
     Bus#  3
     `-Dev#   1 Vendor 0x1d6b Product 0x0001
       `-Dev#   2 Vendor 0x03f9 Product 0x0100
     Bus#  2
     `-Dev#   1 Vendor 0x1d6b Product 0x0001
     Bus#  1
     `-Dev#   1 Vendor 0x1d6b Product 0x0002
       `-Dev#   6 Vendor 0x136e Product 0x000e
     $ lsusb
     Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
     Bus 004 Device 002: ID 046d:c045 Logitech, Inc. Optical Mouse
     Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
     Bus 003 Device 002: ID 03f9:0100 KeyTronic Corp. Keyboard
     Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
     Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
     Bus 001 Device 006: ID 136e:000e  
     Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Device Configuration

  1. Open Micromanager.
  2. You will be prompted to load a configuration file. To create a new configuration file use "Tools" > "Hardware Configuration Wizard..." to manually add the device.

Device Settings

Set camera properties under "Tools" > "Device/Property Browser..." Micromanager does not offer every feature available in Andor Cameras. TODO: List camera features not available in Micro-Manager. However for the Clara overlap mode, Extended NIR and the variable pre amp gains are available.


  • iXon cameras MUST be cooled to the specified temperature: at least -60 C for DV models and -70 C for DU models.
  • Offset ("Baseline") is optimal at this setting. If the camera is not cooled, the offset can be display as 0 data counts.
  • Some blemishes are compensated at the specified temperature setting and will be more visible at warmer temperatures.
  • No need to warm up cameras before shutdown of software and computer (since condensation does not occur).
  • Full gain will not be achievable without cooling.
  • EMgain is temperature compensated for RealGain cameras.
  • Clara must be cooled to the specified temperature: -45 C with fan, -15 C without. The Clara-E is fixed at cooling to -20 C, so no action is needed to set its temperature

Electron Multiplying Gain (EM Gain)

EMgain range

  • EMgain does not start at 1 for all cameras. The start level is tuned for each EMCCD chip.
  • The actual EM gain range depends on the model of your camera: it can be from 0 to 255 (non-linear), 4096 (non-linear), or RealGain 1000 (linear)

EMgain slew rate

Warning: Typically EM gain levels should not be made to change during an experiment.

The software and camera has no problem in changing the level, but there is a 1-3 second delay for the new gain value to come into effect which affects data.

e.g. if you are imaging confocal fluorescence data and DIC, and you need lower or no EM gain for DIC, one would need a 3 second delay before and after the DIC image to allow for EM gain to slew.

  • iXon, iXon+, Luca-R and Luca-S
  • EM gain circuitry is powered by a high +53V voltage rail and the gain applied to the EM readout register is proportional to this voltage.
  • Thus when you increase or decrease the EM gain on the camera, you have to wait for the voltage slew to stabilize at the new set value.
  • This is typically about 1-2 seconds, the maximum time being from setting EM gain from 0 to the maximum value of 1000.
  • Thus it is much better to vary exposure times or excitation signal intensity rather than switching EM gain levels in a multi-channel acquisition (unless you know what you are doing)

Pre-Amplifier Gain (PAG)

  • Pre-Amplifier Gain is a historical name since this feature predated EMCCD cameras. The "Pre-" is in relation to the Analog-to-Digital (A2D) convertor, so PAG refers to the opamp between the sensor and the A2D convertor.
Note: On EMCCDs it is confusing to talk of PAG since one may think this "pre-" amplification happens before EM gain amplification. However EM amplification happens on sensor, and PAG happens "post-" readout of your sensor.
  • PAG multipliers like 1x, 2x, 4x can vary between cameras since they are tuned for each sensor.
  • PAG can affect the saturation limit of your image. To determine the expected digital saturation limit, consult your camera performance sheet of your camera. Divide the "Saturation Signal per Pixel (Electrons/pixel)" by the "CCD Sensitivity (Electrons/A2D count)" to get saturation signal in digital counts.
Warning: Always set PAG to maximum when using EM gain. PAG is useful in Life Sciences only in Conventional mode

Conventional CCD or EM-CCD mode

  • With the exception of the 885, you can switch between CCD and EMCCD modes via the Output_Amplifier setting
  • EMCCD readout without EM gain is more noisy (~40e read noise) so Conventional readout (~6e read noise) is beneficial if light levels do not require EM gain.
  • Benefits of EM gain combating the EMCCD readout register noise of ~40e can be seen from 45x onward, i.e it is better to use 45x EM gain and upward.



iXon: PCI/PCIe card not found on Windows 2000/XP

If the iXon PCI/PCIe board is plugged in before you first install the

and plug in your camera and Windows tries to recognize it, choose:
   Install from a list or specific location (Advanced) >
   Search for the best driver in these locations >
   Include this location in the search >
   C:\Program Files\Andor SOLIS\Drivers\

Clara: error code 22

The camera cannot be seen because the Andor SDK version is too old, i.e. the Andor SDK Micromananger bundled needs to be updated to the current version Andor is using to use the cameras newer firmware.

To update the Andor SDK used by Micromanager, copy the library file from your Andor installation to your Micro-Manager directory. If you have the Andor SDK installed, copy and overwrite:

     C:\Program Files\Andor SOLIS\Drivers\atmcd32d.dll


     C:\Program Files\Micro-Manager-1.4\atmcd32d.dll

64-bit users should copy the library atmcd64d.dll instead

Clara: Java exception using Live, Overlap mode with Clara-Output_Amplifier in "Extended NIR" mode

This is a bug with the DeviceAdapter.

The camera hardware does not support Extended NIR with overlap; the option should not be populated in the drop-down list.


Development support

Please liaison with Micro-Manager developers to contact the Andor software team

Click here to search for Andor on the Micro-Manager mailing list archive.

Andor support

For contacting Andor product support regarding any questions, see under "Support" for your location -

P.nanda 04:40, 7 November 2011 (PST)

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