Check the BBTK v2 using a serial communication software

Before using the python module, we recommend to check the communication between the BBTKv2 and the PC using a serial communication program, following instructions in the next section.

  1. Power on the Bbtk_v2, then link it through USB cable to your computer

    A usb-storage device BBTKV2 should be detected and mounted, and a USB ACM device /dev/ttyACM0 should have been created.

    Determine the Baud Rate:

    cat /media/*/BBTKV2/BBTK.ini
    [BaudRate]
    230400
    
  2. Launch a serial communication program (e.g. minicom if you are runnning Linux — you may have to install it with sudo apt install minicom), and open /dev/ttyACM0, set the configuration to 8bits, NoParity, and a Buda RAte equal to the one you read from the BBTK.ini file.

    minicom -8 -D /dev/ttyACM0 -b 230400

    The terminal should display something like:

    Welcome to minicom 2.7.1
    
    OPTIONS: I18n
    Compiled on Dec 23 2019, 02:06:26.
    Port /dev/ttyACM0, 17:31:53
    
    Press CTRL-A Z for help on special keys
    

    Press CTRL-A Z and select Local Echo 'on', and Add Carriage Ret, and Send a Break

  3. Run a short acquisition session:

  • Send the command CONN. In return, you should get the messgge BBTK;

  • Enter the command GEPV read the sensors’ thresholds.

  • Enter SEPV and 8 times 63 to set the sensors’ thresholds

  • Enter SPIE to erase internal memory. Check the display of the Bbtkv2.

  • Enter ICHK and create events (e.g. putting a light on/off on a photodetector), each event should generate the display of a line with 12 binary digits. Send a Break CTRL-A Z F to interupt the process;

  • To capture events for 10s:

    DSCM
    TIML 10000000
    RUDS
    
_images/bbtkv2_minicom.png

The information about the events is provided in the SDAT; and EDAT; lines. The lines containing 32 digits encode the events in the following manner: the first 12 digits reprenet the status of input ports, the next 8 digits describe the ouput ports (and should all be zero with the DSC command), and the last 12 digits indicate the time in microseconds since the start of the acquisition run.