Test Setup Manual ================= Finally we got what we wanted to have. Test Setup in Counting House is assembled and working. It includes all type of crates what we use for DAQ in the Hall B: VXI, VME, FASTBUS, CAMAC, NIM. This Test Setup has almost the same hardware modules and timing issue between essential control signals: TDC Common START, TDC Common STOP, ADC GATE, FE Busy. Fast Clear feature is also implemented. Test Setup emulates Logic and Analog signals to check data taking electronics, particularly FASTBUS ADCs and TDCs. All FASTBUS boards installed in test setup will report data in form of histograms, ROOT-based presenter is using to visualize, monitor and analyze data from testing boards. Of course Test Setup will be continuously improving and modifying, but even now we can use it for several tests: a) efficiency of all FASTBUS modules; b) channel to channel uniformity for FASTBUS ADCs and TDCs; c) behavior in real data taking; d) level 2 test (pass, fail, late fail). How to use Test Setup: ~~~~~~~~~~~~~~~~~~~~~~ I. Hardware setup. 1. Normally all crates (CAMAC, NIM, FASTBUS, VME and combined VXI/VME) behind the glass in the Counting House should be ON. 2. Test Setup has bunch of test cables ending by 34-pin ECL connector, 8 of them coming from CAMAC Discriminators and 1 (one) from Linear Fan-In/Fan-out. 3. Place testing FASTBUS board in any empty slots from 6 to 25. ( For FASTBUS you could pool-in/pool-out with power ON !!! ) 4. Connect test cables to the pooled in board: - for ADC right now we have only one cable coming from Linear Fan-In/Fan-out, so to test whole ADC you have to do several RUNs with reconnecting cable over all ADC connectors; - for TDC 1877 and 1877S use 6 flat cables coming from CAMAC Discriminators; - for TDC 1872 and 1875 use 4 flat cables coming from CAMAC Discriminators; II. CODA start. FASTBUS modules could have different levels of problem. Sometimes even installation of bad module in FASTBUS crate leads to incorrect work of FASTBUS: unresetable front end busy, data read problem, module identification problem and so on. Another set of problem is a problem with bad module by itself. In our case we can classify these problems by the levels of difficulties of their determination. In order to go through all possible tests you have to start DAQ for session "clastest" and check it status after each step. 1. DAQ could be already in use, to check this use from clon10 "ps -ef | grep clastest"; 2. If there is no anything belongs to clastest or there are some processes active but you sure that nobody uses DAQ, you could use "testsetup_exit" script to cleanup all runaway processes. Wait until "testsetup_exit" will be done. 3. Use "testsetup_start" script to run up all necessary processes for correct execution DAQ for session "clastest". Five xterms and Runcontrol GUI will be opened. 4. Runcontrol GUI opened and has only one active button "Connect", press it. Runcontrol should do right connections with "clastest" session name. 5. Click "Configure" and choose RunType: "test_setup". 6. Then "Download", "Prestart", "Go", all necessary scripts will be started automatically. On each step have a look on xterms and Runcontrol itself, there could be some informative ERROR messages. If no error occurred, run started and you see nonzero Event Rate, you can go further and start histograming tests. III. Histogram Presenter. 1. ROOT is now using to present activity in your testing board, to start it type "root" on clon10. 2. To start Histogram Presenter type ".x testsetup.C" on ROOT prompt. 3. Use "Board Chooser" button to select slot number where you install testing FASTBUS board. 4. Click "Download", "Prestart", "Go". After "Go" ROOT started to accumulate histograms from ET system and after several seconds you will see one page with 8 histograms. You can go through all pages using buttons "Previous View" and "Next View" Each module connector presented by two pages. On the top of each histogram you can see slot number and channel number. 5. To look histograms from another board click "End", then repeat step 3 and 4. 6. To exit form ROOT. First of all click "End". Then on top menu click "File" and on pop up menu choose "Quit ROOT". NOTE: To test another FUSTBUS board. ==== - do "End Run" on Runcontrol GUI; - install another testing board in FUSTBUS crate; - do "Reset" on Runcontrol GUI, then repeat all steps from II.5.