Brief Guide to Setting up Modules for SctRodDaq

1. Connect up cooling pipes. Do pressure test with N2 (Care! in case something bursts), and leave full of N2. Close all disc inlets and the heat-exchanger return valve and monitor pressure drop on outlet manifold preferably over night.
2. Check NTC's
3. Check Diodes ...Use LV-Standby, run the DAQ. Adjust laser DAC settings to give reasonable currents (>= 0.2 mA; but reducing high currents does not seem to work. Min. laser DAC is about 130; 140 to 160 seems to be best).
4. Check HV
5. Check VCSELs: With two people, disconnect test fibres at "PPF1"; have all modules clocked (but power off); briefly turn on one module (< 10 s) at a time and check you see plenty of light on the wavelength shifter card.
   Avoid disconnecting at the BOC: firstly because it can be difficult to replace the infineon connector properly, causing more problems; secondly because it is possible to damage the BOC pluggin boards. There are very few spares of these as they are expensive.
6. Close up and dry out.
7. Cool down and Power on: LV-standby, start a run (clocks on), LV-on. Send module configs. Check modules configure (correct Icc and Idd). Check they configure reliably. Adjust VPIN and laser DAC in BOC if necessary. Store any non-standard VPin's in disc default power supplies settings file.
8. HV on; check V and I. Check to 450 V for Hamamatsu and 400 V for CIS. Look carefully at any tripped modules: could it be failing cables, or are we confidant it is a module that can be trained? In any case, all modules must go straight to 150 V without training.
9. RxThreshold and delay scans:
   1. Any low light output VCSELS, raise VVCSEL. But don't over-saturate the other stream. Any saturated channels, reduce VVCSEL. Re-run RxThreshold scan until you are happy with VVCSEL and thresholds. Store VVCSELs in disk default PS settings file.
   2. Run an Rx Delay scan.
   3. Store the thresholds and delays in the config files using Maaike's script.
   4. Now go through the RxThreshold scan results, looking for slow turn on VCSELs and other problems, for which the software gives bad settings. Adjust the thresholds by hand in the config files.
   5. Similarly, check the delays: where no good delay was found, set it by hand to the average of its neighbours.
   6. Check all modules probe. Best done a few modules at a time, building up to the full disc. The variables available are VPIN, laser DAC, VVCSEL, RxThreshold, RxDelay to get module communications working.
10. (Maybe) Do a TxDAC scan. This can show up PIN/Doric communication problems. Make sure the laser DAC is set to a value far from any non-working regions. Unfortunately, TxDAC scans seem to hang up some Dorics, requiring a power cycle to get the module working. Problematic PIN/Dorics can be improved with higher VPIN and different (higher or lower!) laser DACs.
11. Get pipeline and nmask tests going as a further check of communications. Fine tune VPIN, laser DAC, VVCSEL, RxThreshold, RxDelay. nmask tests seem to give more information on which channels give problems than pipeline tests.
12. Do a strobe delay scan.
13. Do a trim run, to trim any untrimmed modules. Store the trims for modules that previously had no trim data.
14. Do a 3pt Gain test and all other tests you want.
15. Remember to make a DCS report with each significant run.