micro-manager / triggerscopemm

Micro-Manager-specific firmware for the TriggerScope

Micro-Manager

Micro-Manager is an application to control microscope hardware, such as cameras, xy-stages, filter wheels, etc. It includes a hardware abstraction layer written in C++ and a user interface written in Java (Swing).

Go to micro-manager.org for documentation and binary downloads.

For support, see Micro-Manager Community.

The Micro-Manager community welcomes you! For our governance structures, go here

Source code

This repository contains the Java projects that make up the Micro-Manager "MMStudio" GUI application. The device control layer is written in C++ and found in a separate repository, mmCoreAndDevices, which is currently a git submodule of this repository.

To checkout both repositories together:

git clone --recurse-submodules https://github.com/micro-manager/micro-manager.git

If you will be making changes to the code, make sure to enable pre-commit hooks as described in doc/pre-commit.md.

Branches

• main - the main branch of development (Micro-Manager 2.x)
• svn-mirror - git-svn mirror of the Micro-Manager 1.4 Subversion repository

Other branches are not official.

Developer information

For license information, please see doc/copyright.txt.

For build instructions, please see the doc/how-to-build.md.

Additional information is available on the Micro-Manager website at https://micro-manager.org

Contributing

Start here: https://micro-manager.org/Building_and_debugging_Micro-Manager_source_code

triggerscopemm's Issues

DAC Sequencing does not work

Sequenced acquisition based on the DAC State property does not work - the camera is not run in sequence mode (judging from the Exposure OUT signal). The acquisition is set up in the MM MDA window with two Channels (State = 0 and State = 1) and 50 time points with 0 s internal.

The same happens when DAC Volts is used to define channels (0V, 1V, 2V, etc.). Are both properties supposed to be sequenceable? That would certainly be nice.

(note: sequencing based on TTL1-8-State works well)

Changing TTL Shutter State does not work as expected on TriggerScope 4

TriggerScope 4 has two digital output devices, each controlling 8 TTL outputs. The TTL output can be controlled by (1) setting the State of the parent output device or (2) toggling the state of each output individually.

When the state of TTL-1 is changed to 1, the state of the parent output device is correctly changed to 1. When TTL-2 is also set to 1, the state of the parent output device is correctly changed to 3. When TTL-2 is then set to 0, the state of the parent output device is incorrectly set to 0.

I would expect TTL-1 to remain ON, even if TTL-2 is turned off. In the above case, the state of the parent output device should be changed to 1 after TTL-2 is set to 0.

Add delays to triggered sequences.

For both TTLs and DACs, make it possible to set a delay between the trigger and actually changing output. Work on this was started in the pulsedTriggers branch.

TTL Signal Delay with TriggerScope 4 does not work

TTL outputs on TriggerScope 4 can be used as TTL shutters by linking the TriggerScope digital output device to a State Device Shutter. During setup of the config, a delay can be added to the State Device Shutter. Adding a delay to the State Device Shutter does not lead to delay of the TTL pulse relative to the camera trigger.

TriggerScope 4 DAC control does not work as expected

TriggerScope 4 provides 16 DAC output. The State and Voltage of each output can be set through MicroManager.

When the State of a DAC output is 0 and Volts is changed to, e.g. 1 V, the line outputs 1V and the reported State in MM remains at 0. The expected behavior is that setting the voltage should not result in output on the line. The output should be toggles by the State property.

In addition, changing the State from 1 to 0 also changes the Voltage to 0. The voltage should remain at the pre-set value, such that at a later point the output device can be set to the same voltage when State is changed from 0 to 1.

@nicost we're happy to lend you our TriggerScope 4 for troubleshooting if you'd like.