S468 preparation ----- 23/03/2020 - try to run the full system again (S4 crate, prolong crate, 4 FRS and S2 crate) does not work, error on s2 tpc crate, MT does not reach -S2 tpc crate was changed to one without JAUX connectors from RISING.... the week before -several test done conclusion was no clue -we changed the crate, the system worked again -try to add the adc on the active stopper crate, did not work same error no MT -check signal is there properly ----- 24/03/2020 - play with CVT, removing several adc and the mdpp from main.cfg, still error CVT is 60 us! - two options, either crate/mdpp issue with ADC or the signal sent is not the proper one!!! - check the cable in detail, all seems fine and the ADC does send back the gate it claims not to receive - try removing the mdpp16 physically from the crate, does not changes anything - put back the mdpp16 and remove the one we do not use still same issue - no clue what it could be... - check the signals again it is correct -800 mV NIM signal being sent. - put back second mdpp16 in - no clue tire ma langue au Hans - finally use a crate with PAUX connector and it works means the MR tof was disconnedted -MR tof crate is 140.181.91.42 -S4 crate is 140.181.80.29 -S2 crate is 140.181.79.249 - try to run with an actvise stopper trigger, does not work ----- 26/03/2020 - try to update vulom.trlo does not succed, so decide to create new function s468 in vulom.trlo - rename all trloii to vulom for peace of mind - update the startup.scom in eb_all but no in others... do delete[] - issues with firmware in r4l-64 vulom? reboot and issue seem solved - testing new function, all vetar go number (WR general issue?) so put direct=false for vetar in r4l-13 and r4l-64 - sis runs again this means WR shall be running so I enable again the Vetar in R4L-13 and R4L-64 - now the very short S468 function for r4l-64 trloii works ----- 30/03/2020 - comment out the vetar cause WR is unstable facility wide - issue with the daq, try to reboot everything again - accepted pulse for trigger 12 and 13 and mt for others, so accept pulse for vetar at MH and no vetar at S2 needed, deactivate. - to do send the accept pulse to S2 to make sure we can run 12 and 13 - vetar is fine as long as we do not access it... - NIM -> TTL conv in MH is horrible, chose a "somewhat" passable channel, Vetar latching more stable now. ---- 31/03/2020 - test with mdpp16 for LaBr3, changed the polarity - issue mdpp16 triggers like crazy - after playing inside with the jumpers and putting as it was (better connection) the trigger stopper to 3 kHz with source present - start checking how the configuration should be, we kept the 3V range for the mdpp for the LaBr3 - polarity negative, terminated 50 Ohm - First test: th 100, pole 10 us, diff 30ns gain 1000, shaptime 100ns risetime 0ns --> 710 000 triggers, decide gain 1 - Second test: th 100, pole 10 us, diff 30ns gain 100, shaptime 100ns risetime 0ns --> 704 000 triggers..., 1200 (2% of range 60 mV), 600 000 if power off - Thrid test: th 1200, pole 10 us, diff 30ns gain 100, shaptime 100ns risetime 0ns - This is better, no trigger is no voltage, 10 Hz if all detectors at 600V. - Decide to divide by two the threshold - Fourth test: th 600, pole 10 us, diff 30ns gain 100, shaptime 100ns risetime 0ns - spectra goes to 200, we increase gain 1000 and threshold to 1200 - now spectra goes to 2000!!! We put a factor 4... this works fine - resolution on the 569 of 207Bi roughly 5% in FWHM, decide to move shaping time from 100ns to 400ns... no change but reduced spectra ---- 02/04/2020 - suggestion from Julien to test: Music diff 60ns, shap 100 ns. LaBr3 PZ 1us shap 40 to 60 ns would need reducing gain/HV ---- 05/04/2020 - current situation with an Eu source: files LaBr3_set1_Eu_0250.lmd - - now setting 2: 30 ns diff, 40 ns shap pz 1us: files LaBr3_set2_Eu_251.lmd and [...]252.lmd - does not change much, I would propose to keep this. No way to reduce gain - it seems LaBr3 have different PMTs, two of them come out of the trend V/I LaBr3_3 and LaBr3_7 - no clear where the threshold is and what is the low energy peak. Conclusion, runs one by one - first run LaBr3_1: 50% trigger in the noise, move thrshold to, 1500 see the begining of the smallest peak, rate 2400 Hz, so 350 kB source Eu, 2 gamma per decay... - test with lower threshold, 1200 now 2600 Hz, file LaBr3_1_th1200_0253 and 254 --LaBr3_2 run--: -test with threshold 1500, rate 2400, file LaBr3_2_th1500_0255 - 257 --LaBr3_3 run--: -test with threshold 1200, rate 2300, file LaBr3_3_th1200_0258 --LaBr3_4 run--: - test with threshold 1200,rate 2300, file LaBr3_4_th1200_0259 and 260 --LaBr3_5 run--: - test with threshold 1200,rate 2250, file LaBr3_5_th1200_0261 and 262 --LaBr3_6 run--: - test with threshold 1200,rate 2400, file LaBr3_6_th1200_0263 and 264 --LaBr3_7 run--: - test with threshold 1200,rate 2400, file LaBr3_7_th1200_0265 and 266 --LaBr3_8 run--: - test with threshold 1200,rate 2500, file LaBr3_8_th1200_0267 and 268i - now set all valuesL 1000 1200 1000 1100 900 1150 1050 1150 - efficiency run source somehow center, no box: labr3_eff_20usg_pulse_0271 -349... oups too long;) ---- 07/04/2020 - tried to play with CVT for the issue on the readout message of ADC 6, could not find a value to solve, but the value currently lowers the occurence - LaBr3 are triggering quite high - 807/871/1220/1400/1473/1100/900/800 Hz for each detector no source present ----08/04/2020 - les piedestaux sont mit dans les adc de l active stopper --- 09/04/2020 - r4l-42 went on sigbus, r4l-13 2 times two. All the time people were around the crates ---20/04/2020 - after several sigbus of r4l-42 we move to r4l-40 for all TPC electronic (see elog entry 268 s468 elog) - here are the logs for crashes 202704:03-Apr-20 11:13:17#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 230202:05-Apr-20 11:54:54#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 330576:10-Apr-20 10:28:19#R4L-13 :read_meb :exiting.. SIGBUS (hardware fault) signal (fideling with cables around) 331779:10-Apr-20 11:28:57#R4L-13 :read_meb :exiting.. SIGBUS (hardware fault) signal (fideling with cables around) 332261:10-Apr-20 12:49:43#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 336821:12-Apr-20 18:42:53#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 341315:15-Apr-20 09:07:18#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 345345:17-Apr-20 07:40:30#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 346890:19-Apr-20 17:37:47#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 347433:19-Apr-20 18:09:17#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 347922:19-Apr-20 18:27:25#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 348359:19-Apr-20 19:00:36#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 349322:19-Apr-20 19:19:54#R4L-42 :read_meb :exiting.. SIGBUS (hardware fault) signal 350201:19-Apr-20 20:23:35#R4L-40 :read_meb :exiting.. SIGBUS (hardware fault) signal (modules of r4l-42 moved to r4l-40) 350852:19-Apr-20 21:58:47#R4L-40 :read_meb :exiting.. SIGBUS (hardware fault) signal 351308:20-Apr-20 01:05:26#R4L-40 :read_meb :exiting.. SIGBUS (hardware fault) signal ------- --- 24/04/2020 Switch to FRS DAQ for FRS, tpat 1 and 10, no r4l-34 anymore, worked firt time, new directory x86l-93despec --- 26/04/2020 Switch to daq for s469, just remove tpat 10, only one tpat: tpat=1 --- 28/04/2020 Around 18:00 I realize the r4l-64 had lost connection, did not notice no more trigger Around 20:30 no more trigger Try resa and reboot, but all crate see trigger 14, @s ends with acquisition running but no trigger passing 20:44 => try reboot procedure again ==>issue is r4l-13 with an exist failure, I reboot physically the crate as well as x86l-93 who has 2 hours too early 20:57: I switch to a new eb after not having the mbs environement on x86l-93 after reboot now eb is x86l-92, directory is eb_all alias but points to x86l-92despec with same configuration as x86l-93despec ==> runs again TODO, investigate issue of x86l-93[]