Up: TPC Testing

Handling MicroDAQ Data

25-May-1999 updates on daqman and rcf:


The MicroDAQ test system reads out one TPC production-version readout board (MiniDAQ's Rosie receiver cards are not guaranteed to handle the higher transfer rate). However, MicroDAQ lacks support for multiple readout boards, pedestal subtraction and zero suppression, which are supported by translating DAQ's Raw Tape Format to the MiniDAQ-like tables used by the tpm Pad Monitor and analysis codes. ttm could be extended to handle multiple input and/or output formats, but only supports MicroDAQ-format input and MiniDAQ-format output for a single TPC sector now. There is also a version of the Pad Monitor with a built-in ttm.

Assuming certain basic requirements are met, the usual procedure is:


MicroDAQ instructions are provided by DAQ. The system is not robust, so MDAQ reboots are not rare. The usual commands are:

Note 1: Repeat mdaqReset and rstFE until rstFE returns 0x1.

Note 2: Another reset command is sbMzClearAll (a subset of mdaqReset, I believe).

The trigger word for either an MDAQ1 or MDAQ2 event is that loaded into MDAQ1's CSR (Control Status Register). When taking data with MDAQ1, the CSR is automatically loaded appropriately; when taking data with MDAQ2, it must be loaded by hand. The values commonly used now are:

To load the CSR with 4 for pedestal or cosmic data:

m 0x23000002 [cr]
0x23000002 - 0000: 4 [cr]
0x23000004 - 0000: . [cr]

where [cr] is a carriage return and the period "." exits the memory poking tool.


To connect to daqman.star.bnl.gov from another Unix box: enable the display of X Windows from daqman, then log in to complete the setup:

% xhost +daqman.star.bnl.gov
daqman.star.bnl.gov being added to access control list

% rlogin -l bossingh daqman.star.bnl.gov
Password: [Ask Roy Bossingham or Fred Bieser]
(daqman) ~ %

(daqman) ~ % setenv DISPLAY Your_Workstation_Name:0.0
(daqman) ~ % cd rdo_test

Running the ttm Translator

There are five example .kumac's on daqman and rcf in ~bossingh/rdo_test/ :

The ttm_par parameters are used to specify options in .kumac's; in general, the user will have to modify these to achieve his/her goals --- e.g., specifying a sector ID (instead of taking the first one found) or adjusting thresholds and other zero-suppression criteria.

NOTE: Entries in the pedestal means and widths tables are scaled by a factor of eight, allowing +/- 1/16 ADC count precision with integers; recent tpm's rescale them to plot correctly.

To make ttm and run the ped.kumac example:

(daqman) ~/rdo_test % staf
Workstation type (?=HELP) =1: 0

staf > make trn
staf > exec ped

Enter the input file, such as:
Macro : infile ? (=) DAQ_FILE_NAME

Enter the output file, such as
Macro : outfile ? (=) OUTPUT_FILE_NAME

staf > exit

Running the tpm_old Pad Monitor after ttm translation.

Start the tpm_old V3.3 Pad Monitor as usual, except, for displaying a translated MicroDAQ file, set the data-table types in the data file to those in ttm's output before selecting the input source:

(daqman) ~/rdo_test % tpm_old &

In the control window:

  1. Select Data Tables for a pedestal run:
  1. OR Select Data Tables for a geometry run:

  2. Select Input Sources; under Files, supply the DataFile name and hit CR (carriage return).

  3. Unselect Input Sources.

  4. Click Get Event

  5. Have fun!!!

More Information

For more information on:

Written: Roy Bossingham (LBNL)   Maintenance