Skip to main content

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 it
  • it provides free academic license
  • there are thousands of youtube videos with detailed tutorials by enthusiasts
  • easy 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 free (good job, Thorlabs!). For example, a 100-mm mounted achromat model can be downloaded as STEP file and imported directly into Inventor. It takes a few clicks in the Inventor to add an optical axis and a focal plane of the lens:

Mirrors, lasers, cameras can all be imported as STEP files (if available), or their scale mock-up models can be created in the Inventor. 

Autodesk has excellent rendering system, so you can make your parts look as realistic as you wish, by selecting surfaces and their colors (such as Aluminum, Polished).

You can make your own 3D models of anything, for example a tiny zebrafish larva in a plastic holder:

Individual parts (including optical table and breadboards) can be combined into assemblies with specified geometrical constrains. A finished microscope project can look like this.

A 3D assembly of system can be a BIG saver of time and money - it's better to know whether you parts fit together before buying them.

3D printing

Making 3D models is a lot of fun, and there are only few basic tools of Inventor you need to start modeling:
  • 2D sketch,
  • Extrude,
  • Revolve,
  • Make holes.
For a demo, check how to model a scooter tire in less than 6 min.
Once you created your new shiny 3D model and saved it in .ipt file for posterity (.ipt is Inventor format), re-save it as STL file: Export > CAD Format > STL files (.stl)

The STL is a standard format for 3D models recognized across different software platforms. Open the STL in a software specific for your 3D printer, such as Cura (Makerbot), or PreForm (Formlabs), set the printing parameters and save in printer-specific file format which your printer recognizes. Then print!

Here are some recent examples of stuff I modeled and printed for the lab. The modeling typically required 15-20 min, so it's a no brainer once you know basic steps.

Happy printing!


Popular posts from this blog

Programming NI DAQmx board in Python: easier than you think!

For my DIY microscope I had a task - generate a train of digital pulses which simulate camera trigger, so that other devices (galvo and laser) are synched. I wanted to do it in Python, so that it seamlessly integrates in my data acquisition and analysis Jupyter notebook.

After some quick search I found a PyDAQmx library which seemed mature and had good examples to begin with.

Installation was smooth: download, unzip, open Anaconda prompt,
python install

After only 30 min fiddling, I was able to solve my problem in just a few lines of code:

Holy crap, it just works, out of the box. Oscilloscope shows nice digital pulses every 100 ms, each 1 ms long. The code is much shorter and cleaner than would be in C, C#, or LabView.

PyDAQmx appears to be a full-power wrapper around native NI DAQmx drivers (yes, they need to be installed), so presumably it can do all that can be done in C or even LabView (this statement needs to be tested).

One can use PyDAQmx to control galvos with fast ana…

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…

Shack-Hartmann sensor resolution - how much is good?

If you are new to adaptive optics (AO) like me, the selection of right hardware can be daunting. Starting with a wavefront sensor - they range in price, resolution, and many options which are not obvious. By practical trial and error I learned something about resolution, which wasn't obvious to me a year ago.

The Shack-Hartmann wavefront sensor (WFS) is essentially a camera with a lenslet array instead of an objective.
 There are sensors with 15x15 lenses, 30x30 and higher. Naively, you might think "the more the better" - we are digital age kids used to get high-res for cheap.

However, there is a catch. High-res sensor, say, 30x30 lenslets, divides your photon count by 900 per spot. Roughly speaking, when you image a fluorescent bead (or another point source) by a camera with "normal lens" (not a lenslet array), and your peak intensity is 2000, this makes a very nice, high SNR bead image. However, is you switch to Fourier (pupil) plane and image the wavefront u…