TurboDAQ6.0

 

Known problems (with current release or all previous releases)

 

·  All TurboDAQ versions: TurboDAQ occasionally freezes during fitting of T0 scans. We finally manage to trace this problem to a National Instruments routine, so we hope to create a work-around in the next release.

·  On one of LBL’s computers, TurboDAQ will only run if it’s installed on the same hard drive as the National Instruments libraries. It’s not clear what is special about this computer.

 

Bugfixes, version 5.9 to 6.0

 

·  Proper naming convention is followed for VDDA min and max scans, so that Module analysis now finds all FLEX test scans files automatically. (Previously released as patch to TurboDAQ5.9)

·  During scans that returned invalid pixel addresses, TurboDAQ would previously sometimes write the time-histogram values outside the histogram boundaries in memory.

·  Power supply patch for Keithley 273 HV supply used at Siegen (code for this written by Siegen)

·  Phase adjust primitive now works properly for new TPLL. Previously it only adjusted the first of the two phases.

·  Socket that talks to mtest would sometimes write to an un-initialized pointer

·  TDAC-tuning with more than 32 TDAC values produced unpredictable results, due to an array size bug.

 

New features / changed program behavior

 

·  Startup primitive: If you create the primlist “primlists/turbodaq_startup.primlist”, then it will be automatically executed when TurboDAQ starts. This is a handy way to automatically load the power configuration, set power supply types, initialize the PLL etc.

·  Timewalk and intime threshold scans: The Timewalk primitive has an improved T0 calibration. If the maximum MCC strobe delay with delay line 5 (the default) is not sufficient for the timewalk scan, delay line 6 or higher are automatically used. The T0 calibration is attempted with trigger delay 250, 251, and 252, and the best two values are used to calibrated the MCC delay line. The Timewalk primitive now always runs the intime threshold scan with trigger delay of 251, while the Timewalk scan still uses trigger delay 252. [The standard scans have not been changed, only the primitive.] (Previously released as patch to TurboDAQ5.9)

·  Timewalk primitive has a new, 4th option, that allows the same T0 calibration to be used with the Intime threshold and timewalk scans. This saves a little bit of scan time, and reduced the likelihood of freezes, which occasionally occur during T0 scans.

·  Wait (time inverval) primitive: Paused for specified number of second. If you hit stop, the primlist will be aborted. (Note that if you instead want to pause until the user responds, there is already a “pause” primitive for that.)

·  Windows can now be closed by clicking upper-right corners

·  Windows in background can be moved to front by re-selecting them in the master panel

·  TurboDAQ gives a warning if the current program version is to old to properly interpret a module configuration (.cfg) file

·  Test Set in data panel is now 01 by default, rather than 00

·  XCKR phase is now a scan variable. Can be used as outer or inner scan variable, with DFIFO and SRAM scans. The recommended usage (because it is the fastest) is to use it as an inner scan variable with binned SRAM scans. After users get a chance to play with this a little, we plan to introduce a production test. Module Analysis is already clever enough to display the results of these scans.

·  New option (in static configuration panel): user chooses whether column pairs with bad pixels automatically get turned off or not. The default is to not turn them off, as this can get annoying during production testing, leading to scans that need to be repeated.

·  FE-register test primitive. Finally a register test that produces output files. This is intended to eventually become a production scan. It’s based on Aldo’s code for the register tests run during wafer probing, so the .txt file output format is the same. I haven’t had time to extensively test this, but it seems to work well.

·  Stop button (for aborting scans) now also works during module configuration.

 

Please address TurboDAQ comments, complaints, and requests to Sven Vahsen.