From: John David Richardson [JDRichardson@lbl.gov]
Sent: Saturday, June 12, 2004 3:30 AM
To: Aldo F. Saavedra; Polina Netchaeva; Claudia Gemme; Giovanni Darbo;
Roberto Beccherle; Kevin Einsweiler; John Richardson; Paolo Morettini;
Susanne Kersten; Christian Grah; Peter Gerlach; Rusty Boyd; Attilio
Andreazza; patrick breugnon; Clemens Jean-Claude; Joachim Schultes;
Martin Mass; Reiner Klingenberg; Joern Grosse-Knetter; Tobias Flick;
Johannes Muelmenstaedt; Maurice Garcia-Sciveres; Amanda Deisher; Fabian
Huegging; Thorsten Stahl; Wolfgang Walkowiak; Daniel Dobos; Sven Vahsen;
Joseph Virzi; Tobias Stockmanns; Dirk Hoffmann; Hans Christian Kaestli
Subject: TurboDAQ 5.9


Dear users,
the current release has now become 5.9. Changes w.r.t. 5.8 are:

Keithley 2410:
---------------
Keithley GPIB problem, the *CLS fix wasn't included for all of the instances of GPIB read operations in 5.8, it is in 5.9.

Keithley 237
-------------
Siegen provided some upgrade code for the control of their Keithley 237 so I have included this.

In the case that multiple modules are being operated via the same TPLL/TPCC and you wish to send triggers to all of them in order to exercise the 
readout
logic (the "XCK+Cal/Trig to All" TPCC MUX option) while making a threshold scan on one of them:
--------------------------------------------------------
 From version 3.7 up to 5.8 the TPCC was only being put into DCI-broadcast mode during CAL and TRIGGER issuance. I was wrongly assuming that the strobes and LV1 pulses would still be issued to the FEs for the modules not being read out, even though their MCCs were not being held in DATA mode. I now understand that this is incorrect and all fast commands are simply 
ignored
by the MCC when not in DATA mode (with the one exception of ECR). In v. 5.9 therefore I put the TPCC into DCI-broadcast mode before 
issuing the
final EN-DATA-TAKE command which is routinely sent prior to issuing the 
CAL-TRIGGER
sequences. When you hit SEND MODULE CONFIGURATION, as a last step the MCC is prepared for triggers with respect to it's configuration 
registers
(CAL, LV1B etc.), so perform this in turn for all modules before 
scanning the module
under study. Then when the 'other' modules see the EN-DATA-TAKE command they will fully behave as if they are being scanned. To guarantee that 
the 'other' modules
are generating hits, set the static VCAL in the CONFIG CONSOLE to something above threshold when initially configuring them via 'SEND MODULE 
CONFIGURATION'.
You should also ensure they are in analog inject mode. I recommend the 
following example sequence
to prepare three modules:
Set the assembly type to 'Multi-chip module' (or read in a module cfg file) Read the threshold scan .scn file (e.g. MCM, Internal, Concurrent) Set the static VCAL to 250. Set the TPCC MUX mode to 'XCK+Cal/Trig to All' Read in module-0 .cfg file Issue 'SEND MODULE CONFIGURATION' Read in module-1 cfg Issue 'SEND MODULE CONFIGURATION' Read in module-2 cfg Issue 'SEND MODULE CONFIGURATION' Switch back to TPCC channel-0 and start the scan.

John.

-- 
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
  \_ Dr. John Richardson  \_ John.Richardson@cern.ch            \_
   \_ Lawrence Berkeley Lab\_ JDRichardson@lbl.gov               \_
    \_ One Cyclotron Road   \_ http://www-physics.lbl.gov/~jrich  \_
     \_ Berkeley             \_ Tel: +1 510 486 4156               \_
      \_ California 94720 USA \_ Fax: +1 510 486 5101               \_
       \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_