Welcome to the home of TurboDAQ!


What is TurboDAQ?

TurboDAQ is the software used to perform automated electrical test of ATLAS Pixel Detector Modules during the production phase. TurboDAQ runs under Windows. It's based on Native Instruments's Lab Windows developement suite. TurboDAQ speaks to the Pixel Modules via a combination of custom electronics ("TPCC", "TPLL") and a generic PC-to-VME interface from National Instruments.


What is it not?

TurboDAQ is not the DAQ software that will be used with the final Pixel Detector. Each TurboDAQ setup can only receive data from one Pixel Module at a time, and TurboDAQ cannot talk to a ROD (Read Out Drive).


Who's developing / maintaining it?

Developement of TurboDAQ has stopped. TurboDAQ version 6.6 is stable and able to carry out the tasks needed for production testing. If you need help, please try asking an expert user at your institution first. The program is not exactly intuitive, and it takes a while to learn all the features. If there's a problem that you still cannot resolve, you can try emailing me (Sven). I have moved on to other tasks, but of course I'll try to help resolve any showstoppers.

TurboDAQ was originally written by John Richardson (then at LBNL). Starting with version 6.0, Sven Vahsen (LBNL) took over development of the program. There have also been valuable contributions from Bob Ely (help with SURF support) and Daniel Dobos (implemented controls for dortmund specific hardware). Thanks!


Downloads: Main program, Scanfiles & Release Notes

TurboDAQ version .zip file Release notes
6.6 (07/28/2005) download View
6.5 (05/22/2005) download View
6.4 (03/30/2005) download View
6.3 (03/26/2005) download View
6.2 (03/18/2005) download View
6.0 (12/23/2004) download View
5.9 (06/12/2004) download View

Installation from scratch


Putting together and configuring a new test station can be tricky. The main steps are outlined below, but we recommend that you have an expert assist you with your first installation.
  1. Install National Instruments hardware (VME-crate and GPIB-interface pci cards) + software (Labwindows, GPIB drivers etc) on a PC computer. Note that it matters wheather you install the drivers or the pci-cards first. Consult the manuals that come with the National Instruments products for the correct procedure. Link to National Instruments VME crate controller. 
  2. Install and connect the remaining hardware: TPLL, TPCC, MAC card or SURF board, power supplies.
  3. Use the "National Instruments Measurement & Automation Explorer" (MAX) to configure VME communication with the TPLL
  4. Create a TurboDAQ_files directory where test data will be stored, make sure it contains the scan files (see downloads section above).
  5. Download the latest TurboDAQ release (see download section above) and follow "Installation of new version" below

Installation of new version
  1. Download and unpack .zip file
  2. Edit the file Local_setup.dat, which tells TurboDAQ where to find your TurboDAQ_files directory
  3. Edit the file preferences.h to reflect your desired program behavior. Current choices are
    1. Default VDDD, VDDA for SURF boards channels
    2. SURF or MAC mode upon startup
    3. Writing of badfit files ON/OFF
    4. Logging of primlist execution ON/OFF
  4. If you made changes to preferences.h, then recompile TurboDAQ.exe (in release mode)

Tips & Tricks
  1. The Module Connectivity Test is described in detail in the TurboDAQ 6.5 release notes.
  2. Manual (power point format) for the SURF panel. The SURF panel layout has changed slightly since the manual was written, but it's still useful.
  3. Example primitive lists that show how to perform module burn-in, LOAD and STAVE tests with the SURF panel.
  4. Example primitive list that automatically masks stuck-on and hot pixels. This primlist runs the stuck-on pixel scan and a short 1000-hit source scan four times. Each times stuck-on and hot pixels are masked. At the end, the configuration is written out with the name MODULEID_STATUS_SOURCE01.cfg
  5. Tired of setting the same power supply (or other) settings every time you start up TurboDAQ? If you create a primlist called turbodaq_startup.primlist in your primlist directory, it will get executed everytime you start TurboDAQ. Load your power configuration and other settings in that primlist.
  6. You can force the SURF panel to update the list of .cfg files for a given modules by chosing "remove" module, and then re-entering the module ID in the designated field.

Known problems
  1. Latest releases with SURF panel: In SURF mode, during scans only, logging of I,V,T to the "ambush" file is is intermittent.
  2.  "Wait Primitive": If you run this primitive for a long time, you may notice the each wait unit actually lasts slightly longer than a second.