I’m excited to announce the release of the newest Triggerscope model the 3-B. This version replaces the V3, and is packed with improvements for practical laboratory use, including:
DAC Software Range Selection
Range selection is now software controllable for each channel. This means you can get a full 16 Bit resolution delivered to your device in any range from -2.5/+2.5V, to -10V/+10V, as well as -5/+5V, 0-5V, and 0-10V. A demo video of this feature is available below.
LED Status Indication
When integrating or first using any TTL controlled system, it’s difficult to determine whether the controller is properly firing trigger signals, and whether the device is properly outputting changes on the TTL and DAC lines. New LED’s on the Triggerscope 3B indicate an active sequence, TTL status, DAC output status, and input trigger status, all from the face of the device. In addition, these signals can be disabled or enabled for compatibility with ultra low light acquisition environments.
High Current TTL Drivers
When driving Lasers, the 50 Ohm impedance used can cause a tough voltage drop problem. This has been addressed by now sourcing up to 500mA per line on TTL lines 1-4. In addition, lines 5-8 now source 200mA per channel. While most systems should work great at 200mA, the higher current channels may also optionally be used to drive low intensity LEDs if needed, for applications such as transmitted illumination, powered directly from the Triggerscope.
An External DC Power switch is now included for simple restarts.
How fast can a typical imaging system really run? What factors affect this? While most research might not require rapid sequential capture, almost all experiments can benefiet from tight exposure/illumination timing, yet few microscope users are aware of timing delays injected into experiments by the control software they are using. So how much delay is caused by software? I’ve long wanted to look into this, and finally got the chance!
In order to accomplish this, I programmed a microcontroller to accept commands from the Lumencor Spectra-X. This high power/high speed LED engine is popular for fluorescent excitation, as a result, almost every available software application can control it. I set up my code to measure the time in which a known shutter, or known wavelength command was received on the serial line (well, USB serial).
The team at Technical instruments were kind enough to loan me the use of their equipment, so a generous thanks to Reese Allen and the entire Technical instrument staff!
Experimental conditions were as follows:
All software packages were installed on a clean OS install of Win7/x64
Test machine was a Dell Precision series
Tests were performed by configuring the camera to run ~100fps. This was accomplished using a 4×4 binning, and an exposure of 9.8mS.
All software applications were set to send at minimum one shutter and one wavelength change per acquisition cycle. (i.e. 1 picture from the camera, + 1 wavelength change + open shutter, then switch wavelength and cycle shutter).
All applications were first tested in a “free run” mode, to confirm the camera configuration was capable of 100fps at minimum.
No other devices were installed for these tests.
The results were quite interesting:
Software
NIS Elements V4.30
Micro-Manager V1.4.22
Metamorph V7.8.12
Metamorph Streaming
Average Overhead
60mS
71mS
65mS
11mS
Max FPS
16
14
15
90
Here are some videos showing each of the programs performing. You can see some timing variation (likely caused by my capture device) but the averages are easy to resolve, and they correlate to the speed seen on the captured image stacks.
NIS Elements
Micro-Manager
MetaMorph
What becomes quickly apparent is the influence of asynchronous device control using metamorph’s “Stream” function. This is making use of a patented computer-based device sequencing technique. This technique waits for a camera “event flag” (interrupt) to fire, and when it does, a pre-defined set of events occur which control devices. This is similar to what many external trigger devices do, such as a configured national instruments card , or a pulse oscillator, or the triggerscope. The key difference here is that an external card and/or device isn’t needed, this occurs within the PC itself.
Some further thoughts:
Micromanager is a great open-source competitor to other pay-for solutions. Good speed performance for a low up-front cost! (the cost of setting it up!)
It’s interesting that this never really seems to come up for 90% of customers who purchase “high speed” devices. Either the exposure times needed for acquisition of dim signal are so long as to never reach the speed thresholds shown here, or the capture frequency needed for a given study doesn’t require these speeds, or some other cause, but in my experience this is rarely a complaint on behalf of clients. Why isn’t this a bigger problem?
Many, many devices can’t reach the speeds shown here. In my tests I was using an LED driver. LED’s should have a switch time in the <5mS range. The slowest components usually found on a common automated microscope are the filter wheels and turrets, which usually run at the 50ms range when fully loaded with filters. (that’s on the fast side). So is this the reason the problem isn’t exposed more often?
By far, the slowest components you’ll find for microscopy are found on automated microscopes. Shutter open/close times on a common scope (i.e. big 4 name brand scope) can be in the upwards of 100ms! Moving a big filter turret usually takes 200mS. Again, this begs the question of how important speed really is for the common researcher….
For those who want the fastest possible speeds, have no fear! I’ll be announcing some major improvements to my triggerscope soon, to include programmable high speed sequencing capability!
NIS Elements, MetaMorph and a host of other programs rely on XML files to save settings that are user-adjusted inside the program. XML files are like mini databases that can be easily set up, modified and read by a host of programs. The tough part comes when you may need to manually edit one of these files. Viewing an XL file is difficult in IE, and editing it is even more difficult using wordpad or notepad! So Microsoft came up with a handy editor, which can be downloaded here – XML Notepad. I highly recommend keeping this tool handy!