Skip to main content

Unpacking deformable Mirror Mirao52e: first impressions

Mirao52e 

from Imagine Optic is probably one of the best known high-stroke deformable mirrors (DMs), a working horse in adaptive optics. It has 52 actuators, huge stroke (up to +/- 50 microns peak-to-value), and a hefty 15-mm clear aperture of usable mirror surface. All things look good, at a price tag of about 20K euro. After some hesitation and comparing specs/price with Alpao mirrors, I eventually chose Mirao52e for my adaptive optics project.



It is too early to speak of performance, I will do optical tests later. Today I can only share my first impressions.

Pros:
  1. Small form factor: 64x64x17.6 mm, easy to integrate if your space is tight
  2. Very easy installation (Windows 7), basically installation of USB-serial port drivers 

Cons:
  1. Mounting options are weird. There are two M3 tapped holes on each side, 20 mm apart. Does not fit any Thorlabs mount I know - they normally use M4 screws and 25-mm space between. No adapter included :(
  2. Where are LabView drivers which are industry standard for many years? Only a dll file and single Visual C/C++ library. They gotta be kidding me, such bare-bone API for a 20+K research apparatus. A full-scale API collection WaveKit in LabView/Matlab/C++ is offered for extra cost. Not cool.
  3. The cable attached to the mirror is humongous! It is 10 mm thick and stiff as a horsewhip. This is bad, because DM will be installed on a Thorlabs kinematic mount, which is a delicate mechanical piece, and it will likely drift because of residual stiffness of this huge cable. Should I call Imagine Optics engineers and break out in tears?
Update: I did some homework and wrapped the driver file mirao52e.dll in LabView code, so it can (and should!) be used in LabView: https://github.com/nvladimus/mirao-LV-driver
Will I get a paycheck from @ImagineOptic? :-)

Update 21.10.2017. Open and closed-loop control code for this mirror in Python here.

Comments

Popular posts from this blog

Machine shopping for a microscopy lab

Disclaimer: I believe that everyone who can hang a picture on the wall can work in a machine shop. However, if you are sloppy, forgetful, or messy, don't do it. Or at least read the manuals and learn safety instructions before you go.

If you are still reading this, you are not easily scared! Welcome to the world of DIY fun and creativity which a machine shop provides. Let's start with the most common myths.

Myth 1. Machine shop is for old-school dudes who like to fix their motorcycles - today one can buy online everything needed for science.
If you can buy everything - you follow mainstream, because your tools are old and popular enough that a company makes money making and selling them. If you hit an unbeaten path, or even make adjustments, you need to invent and make new tools. Of course, you can hire engineers - but research labs are rarely that rich.

Myth 2. Machine shop is a big and expensive enterprise, only big institutes can afford it. 
MS can be as big or small as you m…

Programming of DIY microscopes: MicroManager vs LabVIEW

In the flourishing field of DIY light microscopy, a decision of choosing the programming language to control the microscope is critically important. Modern microscopes are becoming increasingly intelligent. They orchestrate multiple devices (lasers, cameras, shutters, pockel cells) with ever increasing temporal precision, collect data semi-automatically following user-defined scenarios, adjust focus and illumination to follow the motion (or development) of a living organism.
So, the programming language must seamlessly communicate with hardware, allow devices be easily added or removed, have rich libraries for device drivers and image processing, and allow coding of good-looking and smooth GUIs for end users. This is a long list of requirements! So, what are the  options for DIY microscope programming?

There are currently two large schools of microscope programming - Labviewers and Micromanagers. (update: Matlab for microscope control also has a strong community, comparable to labview…

3D modeling in a lab

About once a week I am asked by my colleagues which 3D modeling software I am using - usually when I am staring at the new part being 3D printed.

I am using Autodesk Inventor for a few reasons:
it is a professional software for engineers and has huge community around itit provides freeacademic licensethere are thousands of youtube videos with detailed tutorials by enthusiastseasy to learn at a basic level, but there is always a lot of room for growth In a lab, there are two main workflows where Inventor is necessary: 3D modeling of complex assemblies (like custom-built microscope) and 3D printing. There are many youtube tutorials for beginners, so I here only review some things that Inventor can do, without any specific instructions.  3D modeling of parts and assemblies Before building a new microscope, you can create its virtual model and check dimensions, required adapters, and whether things will fit together. Luckily, Thorlabs has 3D model of nearly all its parts available for fre…