-- PierreAlainLoizeau - 01 Oct 2010

This page is mean as a user guide for the different daqs used during the test Beam at GSI in October 09 for the CBM readout chain & HDRPC test.

RIO list and corresponding boards

  • R3-22 (Main setup)
    • RIO3 + Triva
    • Vulom3 loaded with the HDRPC modified version of Triglog
    • 2 Caen v1290A TDC boards (32 channels each, board a = time & board b = tot)
    • 1 NIM-ECL conversion board
    • SAM3 board for Tacquila
    • 2 DL702 boards for the SSDs

  • R3-42 (Secondary setup)
    • RIO3 + Triva
    • 1 Vulom4 loaded with the normal version of Triglog
    • 2 modified Vulom4 loaded with the FPGA TDC version 1.0

DAQ list and characteristics

Every daq is located in the ~/nxm/hdrpc/Sept10 folder from the RIO prompt.

  • "Caen RPC, no SSD, no Tacquila":
    • Located in the "rpc" folder
    • Version of the MBS with Caen RPCs and Trilog: Vulom3 + v1290a/b
    • This is the main DAQ, which should be used until the SSD are debugged
  • "all RPCs, no SSD":
    • Located in the "rpc_all" folder
    • Version of the MBS with all RPCs and Trilog: tacquila/Sam3 + Vulom3 + v1290a/b
    • This can be used to get comparison of Tacquila VS Caen, should be used until the SSD are debugged

  • "all RPCs, 0-supp SSD"
    • Located in the "hd" folder
    • Version of the MBS with RPCs, Trilog and the 4 double side silicon detectors : tacquila/Sam3 + DL702#1/#2 + Vulom3 + v1290a/b
    • The SSD are read in the hardware zero-supp mode, the pedestal update method will have to be defined
      • => Expected ?k events per 1 GO
      • This is the main DAQ in case the SSD are ready

  • "0-supp SSD"
    • Located in the "ssd" folder
    • Version of the MBS with Trilog and the 4 double side silicon detectors : DL702#1/#2 + Vulom3
    • The SSD are read in the hardware zero-supp mode, the pedestal update method will have to be defined
      • => Expected ?k events per 1 GO
      • This is a debug DAQ for the SSD

  • "FPGA TDC"
    • Located in the "fpga" folder
    • Version of the MBS with Trilog and the 2 FPGA TDC : Vulom4 (Triglog) + 2*Vulom4 (fpgaTdc_a/b)
    • Each FPGA TDC is set to take time on channels 1-8 & Tot on channels 9-16, 1 channel should be used for synchronization
    • This is a debug DAQ for the FPGA TDC

Operating the MBS DAQ system (main)

  1. Go to the HD-RPC computer and login as fopiuser if it's not already the case
  2. Launch 5 RIO windows (our RIO is r3-22), either via the telnet r3-22 command or via the out r3-22 command. In the first case you will need to login as "fopi" with the normal fopi password. In the second case the login is automatic. It is better if you do it in the first desktop ("1" in the bottom left)
  3. Prepare your windows on the screen so that you have 2 windows on one side and 3 on the other
  4. In each console, enter mbslogin v50 to switch to the MBS system version we are using.
  5. In the big console, enter cd nxm/hdrpc/Sept10/__the_daq_you_want_to_run___ with "__the_daq_you_want_to_run___" replaced by one of the folders listed in previous part. Let's call this windows 'MAIN'.
  6. IF USING THE TACQUILA SYSTEM: In the upper small console, enter cd nxm/hdrpc/dsp, and then fopideb 4. You can then resize this console to the size of the printout if you want. Let's call this windows 'A'.
  7. IF USING THE TACQUILA SYSTEM: In one of the two remaining console on the right, enter cd nxm/hdrpc/dsp. Let's call this windows 'B'.
  8. In the last console, enter cd nxm/hdrpc/triglog. Let's call this windows 'C'.
  9. In 'MAIN', enter resl to reset the daq system and then mbs to start it again.
  10. In 'MAIN',on the MBS prompt, enter @startup and wait until all message appear.
  11. In the bottom left window, just enter rate XX with XX a number to the rate all XX seconds (default = all seconds). Let's call this windows 'D'.
  12. IF USING THE TACQUILA SYSTEM: In 'B', enter startrpc and wait until the prompt come back.
  13. In 'C', enter triglog -f=triglog.txt to reload the trigger setup in the trigger box board.
  14. In 'MAIN' :
    1. Enter con rfio lxg0204 -disk
    2. If you want to take all events from the first one, enter open file /data.local2/rpcaug09/__filename__.lmd -rfio size=__wanted_Size__ , replacing "__filename__" by the name of your file (usually DAQname_date_runXXX) and "__wanted_Size__" by the maximal size in MO you want for your raw data file. This will start you first data file. This is the advised way of doing in case of high rate (~100-200 Hz).
    3. If you don't care of the first event, enter directly sta acq to start the acquisition. Then wait until the MBS prompt come back before going on with the next step.
  15. In 'MAIN' : (letters correspond to previous step)
    1. Once the MBS prompt is back, enter sta acq to start the acquisition.
    2. Enter open file /data.local2/rpcaug09/__filename__.lmd -disk size=__wanted_Size__ , replacing "__filename__" by the name of your file (usually DAQname_date_runXXX) and "__wanted_Size__" by the maximal size in MO you want for your raw data file. This will start you first data file.
      This step can be a bit tricky because of the scalers slow control output which flush the screen quite quickly in high rate case.
  16. In 'B', enter rate to see get an actualized printout of the last second rate/file status/event number status.
  17. If you want to close a file before its end (or if you started a file without size limit), just enter close file in 'MAIN'.
  18. To stop the acquisition, enter sto acq in 'MAIN'.
  19. To close the connection to the rfio file server, enter disc rfio in 'MAIN'.
  20. If you want to change the MBS version, in 'MAIN', enter @shutdown, then once no message comes anymore (should be 5-7 lines), enter quit, kill any rate/scaler windows and go back to step 3 .

Operating the MBS DAQ system (secondary or FPGA setup)

  1. Go to the HD-RPC computer and login as fopiuser if it's not already the case
  2. Launch 5 RIO windows (our RIO is r3-42), either via the telnet r3-42 command or via the out r3-42 command. In the first case you will need to login as "fopi" with the normal fopi password. In the second case the login is automatic. It is better if you do it in the first desktop ("1" in the bottom left)
  3. To be continued....

Special cases

  1. To print an hexadecimal dump of 1 event (mainly to test if a change in setup parameters is working on the data size side), enter type event -v in 'MAIN'.
  2. To recompile the daq program, just enter make after step 3. You should do this ONLY AFTER speaking with Norbert or me (Pierre-Alain).
  3. The source file is "f_user.c". Please ALWAYS speak with me (Pierre-Alain) before ANY modification!!!!
  4. The trigger file is triglog.txt. If you want a different trigger, ask Ingo or me.
  5. To convert a "*.ntu" file (NTuple) to a "*.root" file (TTree), you can either use :
    1. The command h2root filename.ntu filename.root 1 1 16384 (replacing filename by the name of your file) => Convert a single file!!!
    2. The "ntuple_conv" script that you can find in "/lynx/Lynx/fopi/usr/fopi/nxm/hdrpc/April09". For this copy the file in the folder where your .ntu files are. Then just enter ./ntuple_conv and the conversion will start => Convert all .ntu file in a folder!!!
    3. If a message appear saying that "h2root" is a unknown program/command, enter ". rootlogin new" to reload current GSI root version.
  6. In case error messages like vXXXXa DREADY not zero after read! appear more than once in the same spill
    1. Try to stop/restart acquisition
    2. If it does not solve the problem, try to shutdown, go out of MBS and restart everything
    3. Still not working? Enter cave, switch of the crate, wait a bit, switch on and restart everything
    4. If it still appear and I am around or it is between 8:00 and 24:00, just call me, otherwise => Go to bed !!!!!!
Topic revision: r1 - 2010-10-01, PierreAlainLoizeau
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding GSI Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)