Document created 01/03/03
Author: Alexei Drozdetski
E-mail: drozdetski@phys.ufl.edu
Last modification: May 28, 2016
DAQ SETUP: three custom boards (CCB, TMB, DMB) checking.
Step-by-step instruction.
Note:
some instructions here are only for “development small setup” at UF,
but it’s obvious which ones. Just don’t pay attention to them.
(These notes are written during DAQ Setup checking for different
FAST sites and will be updated up until the end of this process.
It seems that they could be useful in other cases, so, here they are…)
Preparation, common notes.
We suppose that you have working CSC chamber with all working on
chamber electronics. HV is on (3600 V). Gas flow exists and chamber was
under the flow long enough and ready for work (the level of gas gain can be
a good checking point of how good your gas is). All cables should be
connected to chamber they are (not only, but including) CFEB-to-TMB
cables, ALCT-to-TMB cables, CFEB-to-DMB cables, LVMB cable, CCB… cable.
Besides you need to have an optical cable, a 7.5V (about 15-20A) low
voltage source, VME create with custom back-plane, FAST-site-PC.
Note: switch on/off low voltage supply then switch on/off VME create
should precede all operation with boards (or on chamber) in VME or cables.
Note: it’s a good style to change board by board with pre-checking in your
already working setup until you have all-new setup in order to localize
problems if there are some.
Note: CCB and TMB have numbers on the face-side of them and DMB – on
the board itself (bottom part). It’s necessary to know this numbers for
tracking and having boards history.
Note: CCB cable is cut off at the bottom part. Put CCB cable to the top
connector of the CCB board.
Note: When an optical cable connected properly the green diode on DMB
(bottom, close to user part of the board) should be on. And all three green
diodes on the Gigabit Ethernet card in PC should be on too. Before
installation you should see on the face-side of the good TMB the “running
signal”, in which all diodes are taking place one by one. Before installation
you should see on the face-side of the good CCB three bottom diodes on
(two red and one green). Before installation you should see all four diodes
on at the face-side of DMB.
Special notes for cms-pc01: data files are in /scratch/csc_data/. There is
enough space for all tests for one chamber only. After finishing working on
data with lisas_test_manager and before going to another set of boards (or
another chamber) you will need to delete data files. For boards tests we use
there 672 channel ALCT (ME2.1).
Note: if run_control doesn’t work, do ‘telnet ucquicc’ – telnet to dynatem
OS. If telnet session failure it means, that dynatem “died” and you need
switch off VME create and then switch it on again, after about 1 minute it
will work again. If it doesn’t help, then reboot PC too, if it still doesn’t work
try to switch on/off low voltage supply (before switch off VME create).
Dynatems have arbitrary user (root, f.e.) and standard password (uclacms).
You may try ‘ps’ command in telnet session at dynatem, there shouldn’t be
any ‘d360.bin’ if you aren’t running any programs like cfeb_control,
run_control, lvmbctp an so on at the FAST PC, if there are some, you may
kill them: ‘kill ID’ (ID – corresponding number in ‘ps’ printing) or reboot
VME create (see above).
Custom boards pre-checking.
When do pre-checking it’s good to choose “no file writing” in the
run_control menu. Trigger type: DDU2 ready; any time.
Use visualization with event_display to understand if the particular board
looks OK or not. In case of “no file writing” there is no particular number
when you are trying to connect to run, there are will be words: “dummy
run”.
Use message_window to see if there critical errors or warnings during the
process, it helps.
Additional programs to use (NOTE: you may always try: “command -help”):
 lvmbctp – you may check voltages and currents with it. There is an
interactive menu for convenience in use (options in command line are
available as well).
 ‘actp --alcttype 672 --rvolt --rcurrent --rtemp --ID’ – to check main
values in ALCT. Be sure that two “id” lines have not-all-zero values
– this is corresponds to good ALCT.
 read_scalers (choose: 2, 1, 3, 0(or 1), 1, 1, 1, 1; or choose: 5 => about
2kHz for small chamber – is a good value.) It’s good to run
read_scalers and check the rate after changing CCB custom board, it
helps to be sure that the board is OK.
You may check if there are old programs are still running (“zombies”) using
command: “ps –ef | grep cfeb”. Program ddu_b_daemon will kill its
previous version when running next time, but you may kill it using
“ddu_b_daemon -k”.
Pre-checking CCB:
 test#12 (scanning by test pulse in AFEB planes) -> corresponding
picture should appear, switching between planes each 1000 events;
 test#16 (scanning by test pulse with switched off anode channels in
CFEB planes), switching between planes each 1000 events;
 test#23 (scintillator trigger) – should see tracks (choose CLCT-on in
configuration in event_display);
 test#25 (selftrigger CLCT, scanning: 1 of 1, 2 of 6, 3 of 6, 5 of 6, 6 of
6), choose CLCT-on in configuration in event_display;
 test#26 (same as #25, but for ALCT), choose CLCT-on in
configuration in event_display;
 additional: test#17a,b (choose only CLCT-on in configuration in
event_display) – scanning by delay and amplitude and by channels;
test#19.
Pre-checking DMB:
 tests#12, 16, 19 (trigger from DMB), 20, 21 (left-right), 23 or 24, 25,
26;
 lvmbctp – for checking (because LVMB on-chamber board is
connected to DMB). Use: “lvmbctp --set 0” – to switch off all onchamber boards (you may check it by looking at CFEB boards, red
diodes, and … board), “lvmbctp --set 3f” – to switch on all boards,
“lvmbctp --show” – to show current values of voltages and currents
for on-chamber boards, “lvmbctp --test” – to test operation of all low
voltage system, you will have detailed summary at the end. You may
have notes in a message window like: “ddu_b_daemon: small buffer”
and corresponding notes in xterm: “Cannot get write access to buffer”,
this notes are due to “error” in DMB which is not good actually, but
we can live now with it.
Pre-checking TMB:
 ‘actp --alcttype 672 --rvolt --rcurrent --rtemp --ID’ – to check main
values in ALCT. Be sure that two “id” lines have not-all-zero values –
this is corresponds to good ALCT.
 In all NEW (or from repair) TMB firmware should be rewritten. Run
cfeb_control, choose: config, Load proms, TMB, load TMB, then
choose file “tmb2001a_101802.svf”, push OK. If you need to rewrite
firmware in CFEBs, choose: FEB; for DMB choose: MB, load VME
ISPROM, then load control ISPROM; for ALCT choose” ALCT,
choose file from the right panel.
 Test#12, 25.
Custom boards checking.
After finishing pre-checking all custom boards in new setup one need to do
all the tests, work on data for them with lisal_test_manager, look through all
results, check if they are OK… In details:
 After each changing of TMB you need to be sure that it’s OK. Do
test#9 (“actp +v --alcttype 672 --test”, if there are errors because of
the temperature is too high – it’s OK for setup without cooling, allow
the program to do 112 WG (wire group) scanning only once, because
of the bag in dynatem. There could be a error (at least it is still exist
now - 01/05/03): “Failure 14: Error checking current 3.3V source, or
out-of-range. Operational error 0 reported.” – returned value of
current is lower than expected one (about 1.98A instead of 2.7-3.1A),
which could be due to not switched on AFEBs in this test. We already
know that current flow with working AFEBs during tests is about 17A
and about 13A before we start working with these on-chamber boards
(see above).
Then do ‘actp --alcttype 672 --rvolt --rcurrent --rtemp --ID
>>test_09_01.results’ from the data/test_results/temp directory.
Then do ‘lvmbctp --test’ from the same directory. Note: this program
doesn’t work if run_control is running (both of this program use
sfeb_control), so, you need to quit from run_control.
Then do ‘cfeb_eprom_loader >> test_09_03.results’ from the same
directory).
 Be sure, that you delete all old data files (*.dat) if you are working on
cms-pc01 or another PC with “small” hard disk (less or about 10Gb).
 Tests: 12, 13. Then lisas_test_manager for 13 -> check diagrams,
copy test_13_13.results to data/anode_thresh/anode_thresh_21_0020
(other tests take threshold from this file).
 Tests: 14,16,17,20,21,11,15; next tests use HV, check that there is
3600 in both HV source channels, tests: 18,19,23,24,25,26. Test #27
use data from test#24. Tests #23,24 are about 3-4 hours each.
 Do read_scalers in both trigger regimes: ALCT, CLCT (see above:
pre-checking).
 Work on data for all tests with lisas_test_manager. Don’t forget to
choose the right type of the chamber (2.1 – 672 channels – type 3 –
one type of the small chambers, 2.2 – 384 channels – type 5 – big
chamber).
 At the end for test#27 copy lisas_test_manager/kumac/*.kumac to
directory with test results, then run PAW, run test_27.kumac. (Note,
that now (01/04/03) there is 64 channels in ALCT per plane is hardcoded, it needs to be changed.)
 Make ~fastdev/data.orig/test_results/DAQ_setup_?? (?? – the number
ot tested setup of three custom boards) directory and copy all results
files from data/test_results/temp/ there.
Note: During data taking you may have error: “READOUT_PAUSED” and
in message window: “readout_control: Incomplete event written: … errno:
28” which corresponds to the absence free space on hard disk.
Note: setups that will be sent to IHEP (China), where we have different
types of chambers need to be checked not only with ALCT-672 (ME2.1),
but also with big chamber setup (ALCT-384, ME2.2) in different trigger
modes with tests #25 (ALCT), #26 (CLCT), #24 (SC), #12 (CCB), #17
(DMB). At least we need to do pre-checking (with no writing to file, but
with event_display).
To be continued…
Short descriptions of test results pictures with comments are also coming…