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

ScanImage 4.x users can upgrade to SI5.1 using their existing scanner hardware and much of their electronics hardware 

To upgrade, the core SI5.1 Acquisition & Control Hardware must still be purchased separately 

Steps to integrate a Thorlabs ECU1 or ECU2 (BScope 2) into a ScanImage 5 system:

  1. Wire the Thor ECU and the ScanImage 5 system. Use the image below as a guide. Items in black apply to both ECU1 and ECU2/BScope 2 while items in red apply only to the ECU2/BScope 2.
    • Loop the ECU's line clock output terminal back to the ECU's line clock input terminal
    • Connect the Thor ECU to the scanner system
      • For ECU1, connect the single DVI connector to the resonant/galvo scanner assembly
      • For ECU2/BScope 2, connect all cables for PMT and scanner controls. There will be a 25 pin D-sub for each of the two parallel scan paths and two round cables for each PMT
    • If using a BScope 2, connect the MCM5000 controller. For each stage axis (X, Y, fine Z, coarse Z, rotation) there will be two D-sub cables, one for the motor and one for the encoder. There will also be three round mirror control cables
    • Connect the 68pin DAQ connector to the scanner control DAQ board of the ScanImage 5 system
    • Connect the ECU's USB cable to the ScanImage 5 PC. Windows will automatically download the drivers (requires an Internet connection) and register a USB serial port.
    • If using a BScope 2, also connect the USB cable to the MCM5000 controller. An unknown device should appear in the device manager. Use device manager to update the device driver and choose the option to manually select driver location. Locate the BScope_ControlV3 driver package from Thorlabs. After installing, a second USB serial port should appear in the device manager.
       
     
  2. Start ScanImage 5 and create a new machine data file.
     
  3. As sections are added to the machine data file, modify them appropriately, save the file, then click ok at the prompt. Use the following settings under the specified headings. Populate the rest of the machine data file according to your acquisition hardware setup.

    1. %% ScanImage
      • scannerHardwareType: 'ecu1' or 'bscope' depending on your hardware
      • primaryPxiChassisNum: Number of the PXI chassis with the FPGA and DAQ boards. This can be found in NI MAX.
      • digitalIODeviceName: The name of the DAQ device where triggers are wired. Since the scanner control DAQ board is wired directly to the Thorlabs ECU, another board must be used. This can be found in NI MAX. (ex: 'PXI1Slot4')

    2. %% ResonantAcq
      • pathToBitfile: Appropriate FPGA bitfile for your FPGA/digitizer combination.
      • rioDeviceID: FPGA device name. This can be found in NI MAX. (ex: 'RIO0')
         
    3. %% ResScanCtrl
      • scanCtrlDeviceName: Name of the DAQ device where Thorlabs ECU is plugged in. This can be found in NI MAX. (ex: 'PXI1Slot3')
      • resonantZoomAOChanID = 0;
      • galvoAOChanID = 1;
      • chanCtrMeasResPeriod = 0;

      • galvoVoltsPerOpticalDegree = 1.0;

      • rScanVoltsPerOpticalDegree = 0.33;
      • refAngularRange = 15;
      • resonantScannerSettleTime = 0;
         
    4. %% Thor ECU1 (this section only appears is you chose 'ecu1' in the %% ScanImage section)
      • comPort: Numeric ID of COM port (ie "1" for COM1) of USB to serial adapter that installs when USB cord was plugged in. Use the device manager to determine this.
         
    5. %% Thor BScope (this section only appears is you chose 'bscope' in the %% ScanImage section)
      • ecu2ComPort: Numeric ID of COM port (ie "1" for COM1) of USB to serial adapter that installs when USB cord was plugged in from ECU. Use the device manager to determine this.
      • mcm5000ComPort: Numeric ID of COM port (ie "1" for COM1) of USB to serial adapter that installs when USB cord was plugged in from MCM5000 controller. Use the device manager to determine this.
      • hasRotation: Set to true if your BScope stage controller includes the rotation axis. Otherwise set to false.
      • acqStatusUpdateInterval: Rate at which PMT statuses are polled during an ongoing acquisition. Change if the default value causes performance issues.

Legacy FPGA digital trigger support

Since the Thorlabs ECU plugs directly into the 68 pin connector of the scanner control DAQ board, the pins for other trigger terminals are not accessible for use. Instead, the trigger terminals must be accessed from the breakout of another DAQ board inserted in the same PXI chassis. Some ScanImage 4 systems, however, do not have a second DAQ board in the PXI chassis. To work around this, ScanImage 5.1 includes legacy support for digital triggers wired to an SCB-19 connector block attached directly to the FlexRIO FPGA. To configure your system for this setup follow the directions below. This strategy is not recommended for new ScanImage 5.x setups, as it may be deprecated in the future.

  1. Connect SCB-19 connector block to the FlexRIO FPGA. Wire the required trigger signals from the appropriate terminals.

    Signal
    Description
    FPGA Terminal
    Beam ClockA TTL pulse generated on each line that controls when waveforms driving the Pockels cells begin.

    DIO1.0

    Frame Clock

    A TTL pulse generated at the start of each frame.

    DIO1.1

    Acq Trigger

    A TTL pulse generated when an acquisition starts. Useful for responding to software-triggered acquisitions.

    DIO1.2
    ShutterA TTL level that opens/closes an external shutter in the beam's path

    DIO1.3

                               

  2. Configure machine data file to route digital triggers from FPGA terminal block. Under the %% ScanImage section, change digitalIODeviceName to the RIO device name of your FlexRIO FPGA. This name can be found in MAX

 

  • No labels