 Thu Jul 2 13:20:51 2015, Felix Bachmair, Creation of Object files
|
HI,
We are using the DRS4 Board in the EUDAQ framework [1]. We wrote a a Producer based on the software of the evaluation board, which is using the
DRS class/header/src files. |
 Fri Jul 3 17:13:27 2015, Stefan Ritt, Creation of Object files
|
Hi Felix,
the distribution does not contain any binaries, since there are too many Linux distributions around, so everybody compiles from the sources under
Linux. Do you want me to just add libDRS.so to the official Makefile? Actually you are the first one asking for this. Would it be beneficial to have this |
|
Mon Jul 6 11:30:56 2015, Felix Bachmair, Creation of Object files
|
Hi Stefan,
That's fine for me. I thought it might be interesting for others as well..
Cheers |
|
Mon Jul 6 19:25:27 2015, Stefan Ritt, Creation of Object files
|
Anyhow it would be nice if you just post your Makefile here, which runs with the standard distribution, so people can use it if needed.
Stefan
Felix |
Tue Jul 7 09:29:21 2015, Felix Bachmair, Creation of Object files 
|
Yes of course no problem.
You can download via github https://github.com/veloxid/DRS4-v5-shared and I
also put it in the attachment. |
|
Wed Feb 11 12:21:07 2009, Stefan Ritt, Corrected datasheet Rev. 0.8
|
Please note the new datasheet Rev. 0.8 available from the DRS web site. It fixes the label of pin #76, which was AGND but is actualy AVDD. The
input IN8+ is located at pin #20 and not at pin #19 as described in the old table 2. |
|
Wed Oct 23 17:56:26 2019, John Jendzurski, Computing corrected time from binary data...what is t_0,0?
|
In the equations for computing the corrected time for channels other than channel 1, does anyone know what the term t0,0 refers
to? This is the last term in the last equation on page 24 of DRS4 Evaluation Board User’s Manual, Board Revision 5 as of January 2014, Last
revised: April 27, 2016. |
|
Fri Oct 25 16:39:07 2019, Stefan Ritt, Computing corrected time from binary data...what is t_0,0?
|
t0,0 refers to the time of cell #0 of channel #0. So basically you keep channel 0 fixed, calculate the difference of each channel's cell #0 in respect
to channel 0, and align all channels except channel 0 so that their cell #0 has the same value. There is an inconsistency between the channel numbering.
The formula uses 0...3 and the manual says "channel 1" but it means actually the first channel, which uses index "0". |
|
Tue Jan 12 17:57:03 2016, Jack Bargemann, Compiling DRS-exam
|
I am trying to compile drs-exam, but am getting an error message I do not understand:
1>musbstd.obj : error LNK2019: unresolved external symbol _usb_open referenced in function _musb_open
1>musbstd.obj : error LNK2019: unresolved external symbol _usb_close referenced in function _musb_close |
|
Tue Jan 12 21:02:31 2016, Stefan Ritt, Compiling DRS-exam
|
I guess you are compiling under MS Windows ??? You probably don't link correctly to the USB lib. Try to compile the examples coming with libusb-1.0
to make you everything is right there.
Jack |
|
Wed Oct 15 10:14:32 2014, Simon Weingarten, Clock settings in daisy chain DAQ
|
Hi,
I'm currently working on a little DAQ system with four DRS evaluation boards. Do i need to apply any specific settings when using the clock in/out
connectors for synchronization? I do not see anything like that in the drs_exam_multi example. |
|
Wed Oct 15 10:52:58 2014, Stefan Ritt, Clock settings in daisy chain DAQ
|
Simon Weingarten wrote:
Hi, |
|
Wed Oct 15 11:34:43 2014, Simon Weingarten, Clock settings in daisy chain DAQ
|
Stefan Ritt wrote:
|
|
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. |
|
Fri Apr 17 10:07:38 2015, Simon Weingarten, Clock settings in daisy chain DAQ
|
Hi Stefan,
do you know how these numbers (400ps and 60ps) scale with the sampling rate? The manual says they are for 5GS/s, do they change with slower sampling?
Thanks and best regards, |
|
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 |
|
Wed Feb 27 13:47:32 2013, Georg Winner, Chip Test - Cell Error
|
When starting Chip Test in DRS Command Line Interface, I receive the following message:
Cell error on channel 1, cell 5: -154.4 mV instead 0 mV
|
|
Wed Mar 6 13:08:03 2013, Stefan Ritt, Chip Test - Cell Error
|
Georg Winner wrote:
When starting Chip Test in DRS Command Line Interface, I receive the following message: |
|
Fri Nov 18 05:52:45 2016, Kurtis Nishimura, Channel offsets in GetTime()
|
Hello,
I have a question about the GetTime() method in DRS.cpp. I understand how the DT values are applied for all channels, and I also understand
from the evaluation board manual that the timing of each channel is synchronized at sample 0, so samples should really be aligned from channel-to-channel |
|
Mon Nov 21 14:13:32 2016, Stefan Ritt, Channel offsets in GetTime()
|
Cell 700 is arbitrary. You can choose any cell to align the channels to each other. The only requirement is that it's always the same cell for each
event. Historically, Daniel chose cell #700 more or less arbitrary, but later we found out that this works with any cell. So for the publication we went
with cell #0 (and that's why we have t_ch,0 in the paper), but cell #700 was left in the code because of lazyness. Feel free to replace 700 with any |