I recently acquired a Zeiss AxioZoom. A device adapter has been developed by Nenad Amodaj for the Exploratorium (San Francisco) and has been recently added to the nightly build. It seems to be a modification of the ZeissCan29 device adapter.
The system is connected to a Windows 10 64-bits computer with a RS232 null-modem cable and a USB adapter.
It works well enough (control of zoom and focus, aperture, fluo revolver and fluo shutter), but there are some issues:
- There is a freeze/timeout issue when I click on the field to change the focus, zoom, or aperture, from the device property browser. Micro-manager freezes for a few seconds if I click on one of these fields and then press enter without changing the value, or if I click on another one of these fields without changing the value. It throws a timeout error (“wait for device “OpticsUnit” timed out after 5000ms”) and gets back to normal. However, if I click on one of these fields and change its value, it works smoothly. If I click on one of these fields, I don’t change the value, and then I click anywhere else (but not on the other fields), then it works fine as well. I reproduce the same behaviour from the main window when I set a group with any of these fields.
- I would love to make the camera keep running while I change the zoom. In the current configuration, the ‘live’ window freezes until the move is completed.
- The system came with a light source CL 6000 LED, which doesn’t have any ZeissCAN port, but only a USB. I can see it from the MTB Config software. Is there any chance micro-manager could control it?
- The system has two lenses, mounted on a nosepiece. The nosepiece is not motorized, but it is coded. If I manually switch lenses by spinning the nosepiece, it should be able to tell micro-manager the lens has changed. It does work this way on my system with Matlab/MTB. Could the device adapter be updated to include the nosepiece position information?