 31 Jan 2019 15:18, Pierre, Configuration, Trigger, Trigger rate
|
Somehow the trigger rate was not matching the trigger source.
Find out that Link 3 was not collecting and possibly holding the fragment assembly in the main thread.
Swap Link3 <-> Link0 on the V1725, restarted.
|
|
06 Mar 2019 15:10, Thomas, Pierre, Routine, Trigger, Setup of chronobox
|
Summary of setup of chronobox on network (mostly done by Pierre):
1) Hook up USB connection from chronobox to ds-proto-daq. Start serial-USB connection by doing
|
 06 Mar 2019 18:19, Bryerton Shaw, Routine, Trigger, Setup of chronobox
|
The SDcard is currently required for operation of the device, the ext3/4 filesystem will immediately fail upon removal.
|
|
11 Mar 2019 12:30, Thomas, Routine, Trigger, New chronobox firmware; run start/stop implemented
|
a) Bryerton implemented new version of the firmware. New features:
1) run start/stop state
|
|
11 Mar 2019 15:27, Thomas, Routine, Trigger, New chronobox firmware; run start/stop implemented
|
> f) However, I found that the frontend program still consistently failed with this error when the trigger rate
> was above the maximum sustainable:
|
|
27 Mar 2019 14:04, Pierre, Configuration, Trigger, Time stamp sync
|
The ChronoBox latest FW is loaded. Let tme know if this is what the chronobox should look like in term of registers.
Are we monitoring the PLL Lock Loss (odb: /DEAP Alarm ?)
|
|
28 Mar 2019 02:18, Pierre, Configuration, Trigger, Test
|
| |
|
11 Apr 2019 08:20, Thomas, Routine, Trigger, Missing ZMQ banks
|
I have done a couple longer tests of the DAQ setup. The runs were done with a high trigger rate of ~60Hz, with
the V1725 asserting their busy to throttle the trigger.
|
|
11 Jul 2019 15:52, Thomas, Routine, Trigger, invert first chronobox busy signal
|
The DAQ seems to be ready for tests with proto-0 tomorrow.
I had to invert the first busy input in order to get chronobox to produce triggers. I modified the setup script
|
|
12 Jul 2019 02:05, Marco Rescigno, Problem, Trigger, MB1 test in proto-0 setup/1
|
Tried to get laser sync signal into chronobox (clkin1 input), apparently all triggers dropped by chronobox
Problem is that the same now happen also with the regular setup where the clkin1 signal is taken by the dual timer.
|
|
16 Jul 2019 02:41, Marco Rescigno, Problem, Trigger, Busy handling
|
This morning tried to get some data with Vbias=65 V, which seems better for the SiPM in MB1.
Busy handling still erratic.
At the beginning it seemed to work fine with busy_invert off and busy_enable on. |
|
11 Nov 2019 23:57, Yi Wang, Problem Fixed, Trigger, ID 117 problem is fixed
|
| The problem reported in ID 117 is somehow fixed this morning. |
|
11 Dec 2018 15:17, Thomas, Configuration, Software, Setup elog for ds-proto-daq
|
1) Install and tweak elog:
|
|
11 Dec 2018 15:20, Thomas, Configuration, Software, Setup elog for ds-proto-daq
|
1) Install and tweak elog:
|
|
28 Jan 2019 01:44, Thoms, Routine, Software, Added web display of V1725 waveforms
|
I added javascript webdisplay of the V1725 waveforms to the Darkside setup. You can see the waveform display here:
https://ds-proto-daq.triumf.ca/CS/webdisplay
|
|
07 Feb 2019 17:30, Thomas, Routine, Software, Testing the maximum data throughput
|
First check the maximum trigger rate and maximum data rate for different sample lengths (for each channels):
sample length Maximum rate MB/s CPU % (per thread)
|
|
03 Apr 2019 15:11, Thomas, Routine, Software, CERN SSO proxy for ds-proto-daq
|
Pierre and I got the CERN proxy setup for the Darkside prototype.
Using your CERN single-sign-on identity, you should be able to login to this page
|
|
03 Apr 2019 15:31, Thomas, Routine, Software, test of elog
|
| The last elog didn't go out cleanly. Modified the elogd.cfg to point to the proxy. Try again. |
|
02 Jul 2019 18:01, Thomas, Routine, Software, MIDAS running again
|
Darkside people seem to be doing some tests at CERN next week. It looks like they aren't going to use our DAQ (they will I think just use CAEN tools).
But we took
opportunity to make TRIUMF DAQ work again. There was a couple issues
|
26 Oct 2019 07:33, Sam Hill, Problem, Software, Test of IV Script 
|
People: Simone, Sam, Tom, Edgar
Tested IV curve python script that runs using MIDAS. Measured resistance consistant with resistor specification. elog:46/1
The resistance is attached to ch11, and we called the script (channels go from 0 to 24): |