Icon
This documentation is for a legacy ScanImage version. The current documentation is ScanImage 2019.
Skip to end of metadata
Go to start of metadata
Icon

To use the LinScan Imaging System it has to be enabled in the ScanImage section of the Machine Data File.

Machine Data File
Icon

If you have questions about using existing ScanImage 3.8 hardware with ScanImage 2015, review the article ScanImage 3.x upgrade guide. If you need general support with wiring your system, please write an email to support@vidriotech.com

 

ScanImage 2015 supports galvo/galvo scanning through the module 'LinScan'. LinScan replicates most of the features (triggering, timestamping) of the resonant scanning subsystem (ResScan), but utilizes National Instruments multifunction DAQ boards instead of the FlexRIO platform to acquire data and control the microscope. The recommended hardware for LinScan is a simultaneously sampled NI X-series DAQ board (e.g. NI PXIe/PCIe/USB-6356). For backward compatibility to ScanImage 3.x, legacy hardware (e.g. NI-6110) is supported as well.

The LinScan module is subdivided into three logical devices. The settings 'deviceNameAcq', 'deviceNameGalvo' and 'deviceNameAux' in the Machine Data File the logical devices can be mapped onto physical DAQ devices available in the computer. Multiple logical devices can be mapped onto the same physical. If the logical devices are mapped to separate physical devices, these devices need to be connected to each other via either a RTSI cable or they all need to be installed in the same PXI chassis.

Icon

Please review the NI-knowledgebase What is RTSI and How is it Configured? to learn the correct configuration of a RTSI bus in NI-MAX.

Logical DeviceCommentDAQ Requirements
Acquisition deviceUses analog inputs to acquire image data from the PMTsFor multi-channel input, analog inputs need to be simultaneously sampled. Sample rate ideally >= 1.25MHz
Galvo deviceUses analog outputs to control the positions of the X/Y GalvosRequires at least two analog outputs
Auxiliary deviceUtilizes trigger lines and counters to generate clocks, register triggers and generate hardware timestampsNeeds to be an NI X-series DAQ board (63xx)

Example 1: NI-PCIe 6356

 Dev1 (6356)
Acquisition device: AIs simultaneously sampled, sample rate >= 1.25MHzyes
Galvo device: has two analog outputsyes
Auxiliary device: is NI X-series (63xx)yes

Since the NI-6356 fulfills the requirements for all the virtual devices, no additional hardware is required for LinScan in the Machine Data File:

%% LinScan
deviceNameAcq = 'Dev1';
deviceNameGalvo = 'Dev1';
deviceNameAux = 'Dev1';

Example 1

Wiring diagram for a NI PCIe-6356.

Example 2: NI-6110 in combination with NI-6321

Icon

To exchange timing signals, the NI-6110 and NI-6321 DAQ boards need to be connected with a RTSI bus cable.
Please review the NI-knowledgebase What is RTSI and How is it Configured? to learn the correct configuration of a RTSI bus in NI-MAX.

If you connect PCI-611x board with one or multiple X-series boards (PCIe-63xx), make sure to use the 'Extended Length RTSI Bus Cables' to bridge the gap between the long and short boards (RTSI Bus Cable, Product Number 777562-05)

 Dev1 (6110)Dev2 (6321)
Acquisition device: AIs simultaneously sampled, sample rate >= 1.25MHzyesno
Galvo device: has two analog outputsyesyes
Auxiliary device: is NI X-series (63xx)noyes

 

This allows two possible configurations in the Machine Data File

Configuration 1Configuration 2
%% LinScan
deviceNameAcq = 'Dev1';
deviceNameGalvo = 'Dev1';
deviceNameAux = 'Dev2';

deviceNameAcq = 'Dev1';
deviceNameGalvo = 'Dev2';
deviceNameAux = 'Dev2';

In Configuration 1, the analog inputs and analog outputs of Dev2 are unused by LinScan, so that Dev2 can also be used as the Beams or FastZ device.

 

Example 2

Wiring diagram for configuration 1. Since the analog inputs and analog ouputs of Dev2 (NI-6321) are unused, they can be configured to control a Pockels cell. See section 'Pockels Control'. 

LinScan Pinout

Acquisition Device

The standard PMT inputs for the Acquisition Device are channel AI 0-3. This configuration can be changed in the Machine Data File

Icon

Please review the article Wiring ScanImage analog input terminals if you are using a NI screw terminal (SCB-68(A) or USB DAQ device) as the breakout box for the Acquisition Device.

Galvo Device

The control output for the X / Y Galvos can be configured in the Machine Data File:

Icon

For Photostimulation Monitoring and Logging, the x,y mirror signals and one beam signal can be looped back to AI 5,6 and 7 of the Galvo Device.

Icon

Please review the article Wiring ScanImage analog input terminals if you are using a NI screw terminal (SCB-68(A) or USB DAQ device) as the breakout box for Photostimulation Monitoring and Logging.

Auxiliary Device

Outputs

Outputs
Frame ClockPFI10
10MHz Reference ClockPFI14*

*If the MDF setting referenceClockIn = 'PFI14' is set, PFI14 acts as an input

Inputs
Start TriggerPFI0 -> port0/line0*
Stop Triggerport0/line1
Next Triggerport0/line2

*PFI0 and port0/line0 need to be bridged to ensure proper time stamping of the start trigger

Shutter Control

To configure a shutter for LinScan, review the article Shutter Configuration. If using the Auxiliary DAQ to control the shutter, PFI12 is recommended for the digital output.

Pockels Control

Automatic Trigger Routing

No external trigger wiring between LinScan and the Beams DAQ board is required in the following cases

  1. The LinScan Auxiliary device and the Beams device are configured to operate on the same DAQ
  2. The LinScan Auxiliary DAQ and the Beams DAQ are installed in the same PXI chassis
  3. The LinScan Auxiliary DAQ and the Beams DAQ are connected via a RTSI bus, and the RTSI bus is correctly set up in NI-MAX

For the three cases above, all triggers are routed automatically so that the Beams section in the Machine Data File can be configured as follows:

Icon

Please review the NI-knowledgebase What is RTSI and How is it Configured? to learn the correct configuration of a RTSI bus in NI-MAX.

Automatic Beams Trigger Routing

Trigger Routing via RTSI bus: frame clock and reference clock are automatically routed over RTSI

Icon

Please review the article Wiring ScanImage analog input terminals if you are using a NI screw terminal (SCB-68(A) or USB DAQ device) as the breakout box for the Acquisition Device.

Manual Trigger Wiring

In case the LinScan Auxiliary device and the Beams device are not connected via the PXI/RTSI bus, the LinScan frame clock and reference clock need to be wired to the Beams device:

TriggerSourceDestination
LinScan Frame ClockLinScan Auxiliary board PFI10Beams board any free PFI (e.g. PFI12)
LinScan Reference ClockLinScan Auxiliary board PFI14Beams board any free PFI (e.g. PFI0)

The trigger destination terminals need to be configured in the Machine Data File accordingly:

Manual Beams Trigger Wiring

External Trigger Wiring for Pockels Control

Icon

Please review the article Wiring ScanImage analog input terminals if you are using a NI screw terminal (SCB-68(A) or USB DAQ device) as the breakout box for the Acquisition Device.

FastZ (Piezo) Control

Automatic Trigger Routing

No external trigger wiring between LinScan and the FastZ DAQ board is required in the following cases

  1. The LinScan Auxiliary device and the FastZ device are configured to operate on the same DAQ
  2. The LinScan Auxiliary DAQ and the FastZ DAQ are installed in the same PXI chassis
  3. The LinScan Auxiliary DAQ and the FastZ DAQ are connected via a RTSI bus, and the RTSI bus is correctly set up in NI-MAX

For the three cases above, all triggers are routed automatically so that the FastZ section in the Machine Data File can be configured as follows:

Icon

Please review the NI-knowledgebase What is RTSI and How is it Configured? to learn the correct configuration of a RTSI bus in NI-MAX.

Automatic FastZ Trigger Routing

Automatic Trigger Routing for Piezo Control

Icon

Please review the article Wiring ScanImage analog input terminals if you are using a NI screw terminal (SCB-68(A) or USB DAQ device) as the breakout box for the Acquisition Device.

Manual Trigger Wiring

In case the LinScan Auxiliary device and the FastZ device are not connected via the PXI/RTSI bus, the LinScan frame clock needs to be wired to the FastZ device:

TriggerSourceDestination
LinScan Frame ClockLinScan Auxiliary board PFI10FastZ board any free PFI (e.g. PFI0)

The trigger destination terminals need to be configured in the Machine Data File accordingly:

Manual FastZ Trigger Wiring

External Trigger Wiring for Piezo Control

Icon

Please review the article Wiring ScanImage analog input terminals if you are using a NI screw terminal (SCB-68(A) or USB DAQ device) as the breakout box for the Acquisition Device.

  • No labels