 Fri Sep 12 13:41:43 2014, Stefan Ritt, synchronizing two DRS4 evaluation boards readout with one computer
|
Dmitry Hits wrote:
|
|
Fri Sep 12 16:08:49 2014, Stefan Ritt, compilation error for v5.0.2
|
Dmitry Hits wrote:
Hi, |
|
Mon Sep 22 14:52:21 2014, Stefan Ritt, compilation error for v5.0.2
|
Dmitry Hits wrote:
|
|
Mon Sep 22 15:04:37 2014, Stefan Ritt, Timing Calibration Fail
|
Hannes Wachter wrote:
Hi, |
|
Mon Oct 13 16:46:56 2014, Stefan Ritt, USB Microcontroller firmware
|
Stephane Debieux wrote:
Hi, |
|
Mon Oct 13 17:14:58 2014, Stefan Ritt, USB Microcontroller firmware
|
Stephane Debieux wrote:
|
|
Tue Oct 14 16:29:12 2014, Stefan Ritt, USB Microcontroller firmware
|
Stephane Debieux wrote:
|
|
Tue Oct 14 16:38:14 2014, Stefan Ritt, USB Microcontroller firmware
|
Stephane Debieux wrote:
|
|
Wed Oct 15 10:52:58 2014, Stefan Ritt, Clock settings in daisy chain DAQ
|
Simon Weingarten wrote:
Hi, |
Wed Oct 15 12:15:58 2014, Stefan Ritt, Clock settings in daisy chain DAQ 
|
Here is the full version of the program with clock daisy-chaining. Before switching to the external clock, it checks if the clock really
is there (by reading an internal scaler), and only then enables it. Note that the code also works without clock daisy-chaining. But without clock daisy-chaining
your have some 400 ps time resolution between boards, and with clock daisy-chaining you get some 60 ps. |
|
Thu Oct 16 16:15:16 2014, Stefan Ritt, binary files with more than 4 drs board ver. 5.0.2
|
> Dear Stefan
>
> after having some problems with writing binary files with more than 4 drs boards (in multiboard-mode) I might
|
|
Thu Oct 16 16:16:12 2014, Stefan Ritt, binary files time calibration header in drs-5.0.2
|
> Dear Stefan
>
> I have a problem considering binary data files.
|
|
Tue Nov 25 14:06:34 2014, Stefan Ritt, Raspberry Pi drsosc does not exit properly
|
Mickey Chiu wrote:
When running drsosc on a raspberry pi, it seems the exit doesn't seem to work at all. This is |
|
Fri Jan 16 14:12:19 2015, Stefan Ritt, Mac OSX Yosemite 10.10
|
> Hello,
>
> I can compile version 5.0.3 of DRS4sc on Mac OSX 10.0 without errors but when I want to execute the program I get the following error:
|
|
Tue Mar 17 02:53:26 2015, Stefan Ritt, Running 2 instances of a DRS DAQ program
|
I never had in mind running two systems in parallel, that's why the code claims all interfaces when started. You have to dig into the usb code which
is located in musbstd.c at function musb_open(). There you will find a line libusb_claim_interface() which requests exclusive access to the usb subsystem.
The code is there because I copied it from some standard example for the libusb library. You have to read the documentation for libusb (http://libusb.sourceforge.net/api-1.0/) and |
|
Mon Apr 20 13:08:24 2015, Stefan Ritt, Clock settings in daisy chain DAQ
|
The resolution coming from the sampling rate goes into these numbers, but just marginally. At 5 GSPS, you get a few ps reolution, while at 1 GSPS, you
get like 15 ps. If you convolve 15 ps with 400 ps, you get 400.3 ps, which is not significantly worse than 400 ps.
Simon |
|
Tue Apr 21 12:01:45 2015, Stefan Ritt, DRSBoard::SetTriggerSource
|
Your first assumption is correct, e.g.
source = 00000000'00000001 = 0x0001 ==> CH1
source = 00010001'00000000 = 0x1100 ==> CH1 and EXT |
|
Tue Apr 21 12:52:18 2015, Stefan Ritt, DRS4 Evaluation Board Baseline/Voltage Calibration
|
1) I tried to cablirate a V5 board with drsosc 5.0.3 and it just worked fine for me. No idea what went wrong in your case.
2) The "found 4096 stuck pixels on this board" can be safely ignored. It comes from the fact that the standard evaluation board has
four cannels unconnected (the DRS4 chip has 8 channels, four are connected to in the evaluation board and four are unconnected). So the software sees |
|
Tue Apr 21 13:06:39 2015, Stefan Ritt, DRS4 Evaluation Board Baseline/Voltage Calibration
|
Sure, for a V3 board you need a pre-V5 software, but I assumed Julien had a V5 board.
Daniel
Stricker-Shaver wrote:
I also use Ubuntu 14.04 LTS and for my V3 borad I have to |
|
Wed May 13 08:19:53 2015, Stefan Ritt, Getting Trigger Source
|
DRSBoard::GetTriggerSource() simply returns what has been enabled via DRSBoard::SetTriggerSource(). The actual source which causes the trigger is not
stored in the hardware of the board, because I can be reconstructed easily from the waveforms. So just look which of the channels is above your trigger
threshold. If none of the channels has a waveform obove the threshold, then the trigger must have been come from the external trigger. |