Below is a short video introducing the Triggerscope Mini, as well as demonstrating how to set it up in micromanager.
If you’re in a hurry, I’ve also outlined the basic steps below with screen shots.
Connect the triggerscope mini to a USB-2 compliant port, via it’s USB C connection cable (included).
Open micromanager, select the device configuration wizard, and browse to the add device page.
Scroll the device list until you see “Triggerscope-MM” expand that and select the -Hub device.
A window will appear, set the COM port to the port used by the triggerscope mini, and set the baud to 115,200, then click OK.
After a few seconds, a list of components will appear. Note this is for the full triggerscope, so we will only choose the TTL 1-8 Bank, and DAC 1 + DAC 2. Below is a basic chart showing what devices are supported on the mini vs the standard triggerscope.
When prompted for the DAC voltages, only select 0-5V (default), and click OK.
That’s it! Follow the manager to complete the install. Once done, you’ll have the common TTL output control, DAC control, blanking, sequencing and other features of a standard triggerscope!
Compact, Simplified TTL and DAC – Micromanager Native
I’m happy to share a new device I’ve been working on after encouragement from numerous clients. This new smaller version of the Triggerscope is intended to bridge the gap between large complex systems and more streamlined setups.
With the Mini you get:
4 TTL Outputs at 5V
2 DAC Outputs at 5V
1 3.3V to 5V input Trigger
Status LEDs for all connections!
A single USB-C Connection to the computer
Full supported Micromanager Triggerscope-Hub Behavior
This was a super fun project for me, as for the first time this board uses a bare MCU, which enabled my team to use any connector we wanted (hence the USB C) as well as full USB-Serial emulation on our own terms.
I’m also quite fond of the baby side-emitting LEDs on the outputs. These LED’s draw almost no current, but having them for all of the outputs makes it so easy to know whether a given control line is on or off. For the DAC LED’s, they change brightness with the output!
I tried to keep this design in-line with the current TG4, as it’s worked well for us over the years. This one is of course thinner, lighter and smaller, but in effect a truly miniaturized version of the larger model.
A few months back, I started promoting a new software application called Nebula. As I introduced it to people I realized that I’d not explained the development or release of it on my website, and so here I’ll take a minute to explain that.
The Why
20 years ago I fell into a career in the life science imaging industry, working for an integration and microscope dealer in southern California. One of my first jobs was installing a copy of software application called MetaMorph. This was an interesting thing to me, having a background in building computers from the days of ISA cards and DOS boot menus.
Metamorph could move things like a filter wheel (then a Sutter Instrument 10-2), and capture images from a camera like the then-new Photometrics 1300 YHS.
It fascinated me to watch the camera snap images with it’s mechanical shutter as the filter wheel switched positions, compiling images into a singular display. I was intrigued by this ability and also how it was used in research.
As time went on, I eventually moved from building the basic systems to maintaining them in-field, and then to offering complete hardware and software systems as a direct rep for the company who made this software, Universal Imaging Corporation.
The Need
What made MetaMorph appealing was the wide array of devices it could control at speed – from stages, to microscopes, to illuminators, basically anything. The company had no specific lockout, and would integrate device drivers for any product.
Over time, UIC was acquired by Molecular Devices, and after a long run ceased offering product sales in 2023. By that time, the industry was somewhat locked into the major microscope companies selling brand-specific products. Further, these companies would refuse support (understandably) for specific competing devices. Yet, this posed a genuine challenge for users:
Once invested into an automated microscope, I am forced to use proprietary software with restrictions, or use open-source software alternatives like MicroManager.
Now, MicroManager is an exceptional suite of software with device drivers, but for customers who want a simplified approach to control, with minimal hands-on configuration, and someone to call when things go wrong, there really aren’t many commercial applications filling the need. This situation led me to conclude that a new company was needed in the industry to:
Provide Custom Integration Support for existing microscopes
Offer hardware driver support for smaller and newer companies excluded by the major brands.
Wrap device control into a simple, easy to use interface
Provide exceptional support for products.
With this in mind, I engaged with my friend and colleague Jacob Gewerth, to launch Starlyte Imaging, and build our core product, Nebula. It’s been a long development process, but what Nebula does is something very special:
The What
We imagined, and have released, a software application geared to capture, and capture alone:
We are dedicated to controlling devices as the priority – it’s all about getting data
Our drivers are completely developed in Python, and our driver standard is open – meaning YOU or any company who wants to, can write device drivers for our software.
Our pricing is approachable and fair – no huge budget outlay for software – we offer fixed licenses, or service-based pricing.
We can support old as well as new devices – many older microscopes are perfectly suitable as a chassis to perform any modern study, they just need to be tied into the capture control scheme.
We also can support data collection and metadata recording from perfusion systems, peristaltic pumps, or any other environmental control device you want to talk to.
More than anything else, I wanted to bring the simple, fair and honest product support I’ve enjoyed providing to this industry for my career. Things fail, mistakes happen, but what makes the difference to me, is the dedication to see projects through, supporting your research, and seeing the project through.
I’m excited today to announce the release of the Triggerscope version 4. TG4 marks a major improvement in the performance and capability of the Triggerscope.
New Features
At the heart of Triggerscope 4 is a New high speed MCU running @ 600 Mhz. This is an 83x improvement over the Triggerscope 3B.
On board 1024K MCU RAM provides more than enough memory for arrays.
A new features provides access to a 16GB External SD Card, installed inside. Memory may be used for storing data for sequence access, recording of external parameters and timing events, or saving of advanced settings.
A new Real Time Clock is included for better timing over long duration experiments and delays.
DAC update rates can be overclocked, to a maximum frequency of 270kHz.
Integrated and simplified external controls for easier operation.
New Software
In addition to the release of Triggerscope 4, ARC is introducing a python-based, multi-platform compatible standalone control application. Our application can be installed on Windows, OS-X, or Linux systems. Source is also available from the GitHub Repo here. Users have two options for use – EXE and APP executables provide a small containerized version of python, so the entire application runs without any external installs required. Or, for customers who already have python installed, simply downloading and running the native python file is an option.
For debugging, all communication between the software and the triggerscope are printed for the user to view, to make diagnostics and custom driver development as simple as possible.
Light and Dark themes are provided to keep monitor glare down during imaging. This software is available for all Triggerscope 3 and up devices, and can be found on our GitHub Repo here.
New Micromanager Firmware Options
Nico Stuurman recently undertook a huge endeavor, and implemented a new approach for using MicroManager and the Triggerscope, with faster syntax, greater memory capacity, and tight integration into the Micromanager sequencing system for fast device control. ARC can install this firmware option before your triggerscope ships, just let us know which version you’d like to use!
Over the past few years, I’ve often battled the Micromanager MDA window, when needing to perform high speed triggered acquisitions. While the system works well for multi channel Z stacks, running timelapse 2 channel streams, or “Z first” streams, didn’t work well. To overcome this, I’ve written a script that pulls all of the MDA user settings out of the window, loads up the Triggerscope, and captures the sequence.
This approach gives any user of the triggerscope far greater control over how sequences are run, and offers users the ability to customize external device commands if needed.
I’ve cooked up a brief video overview here, with some example screenshots of the results on an oscilloscope below.
If you’d like to use or check the script out, it can be found on my GitHub site here.
Please note this requires updated firmware (V 600 or up)
A basic example of a Z stack in a single channel is shown below. In this configuration, 1 channel is selected in the MDA window, and a single Z stack is collected. The Yellow line indicates intensity of a laser or LED on Ch1, the pink line indicates the Z voltage output, and the blue line indicates a TTL input from the camera.
In the next example, output from a “channel first” Z capture is shown. Here Channel is prioritized, so the system runs Ch1 , then captures all Z frames, thens witches to Ch2, and captures all Z frames.
Next, is an example of a capture previously impossible in MM. In this capture we stream 3 time loops back to back, with no delay.
Next up is an example of a “Z First” capture, where all channels are acquired for a single Z position.
Finally, a multi channel example can be seen in this image, with 2 channels running in a time series.
Those are the highlights – I hope others find this useful!
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.
It appears that more and more people want to use PWM control for illumination devices from Micro-Manager and other imaging software. PWM may be used for any number of applications, from high speed pulsing of an LED, or a laser, in order to reduce phototoxicity or just to control brightness, or to drive a DC motor at a varying speed, or to drive a device like a spinning disk to set the PRM. I figured I’d address this using the Triggerscope system controllers. rIn order to support PWM drive over an external device, I wanted a few useful functions to work in MM:
PWM duty cycle should be controlled form presets
PWM should be called to “off” from a TTL or other “shutter” style command
Once off, a similar “ttl on” type command should re-enable PWM at the alst used duty cycle
multiple output lines should be supported at different duty cycles.
Version 407 of the Triggerscope firmware now supports this, and uses the existing driver available for these devices. I’ve made a short demo video showing how this works on an oscilloscope output. I’ll place an option for this on the store. Please get in touch with any questions or post here – thanks!
I made this video to show how to use both a state device shutter object and a group shutter object in micro-manager. Hopefully others can make use of it!
I wrote this for a client, but figured others could make use of it. This code simply captures a number of images as defined by the user, and saves them to the specified folder without displaying them. This is useful if you don’t want all of the images open in memory during a timelapse.
