 Thu Mar 11 11:45:52 2010, Stefan Ritt, Readout of DRS Data
|
Hao Huan wrote:
Hi Stefan, |
 Thu Mar 22 14:36:01 2018, Phan Van Chuan, Read the CalibrateWaveform
|
Helo
I'm building an application for reading waveforms from the DRS4 board to PC. However, I am having problems reading calibration data from EEPROM
on DRS4 board. The calibration data is read through the function reference: |
|
Fri Mar 23 09:39:55 2018, Stefan Ritt, Read the CalibrateWaveform
|
You don't have to read and calibrate the waveforms in your user code, but can rely on the DRS.cpp library to do that. Just look at the drs_exam.cpp
program coming with the distribution. It uses the function b->GetWave() to retrieve the calibrated waveform. If you like, you can look into that function
to learn how to apply the calibration, but I can tell you that it's a bit complicated. Since each event starts at an arbitrary stop cell in the DRS4, |
|
Mon Nov 17 16:36:18 2014, Mickey Chiu, Raspberry Pi drsosc does not exit properly
|
When running drsosc on a raspberry pi, it seems the exit doesn't seem to work at all. This is true for the "exit" button on the window,
or the file menu exit, or the "x" on the window. I end up having to kill drsosc manually from the command line. This wouldn't be
such a bad thing except that it doesn't seem to store any settings when killed in this way. I'm wondering if anyone else sees the same thing, or |
|
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 Oct 13 03:39:01 2017, Jonathan Wapman, Raspberry Pi Connection Failure
|
I am currently attempting to use a raspberry pi to connect to the DRS 4 board. I whenever I try to use the DRS Command Line TOol, Revision 21435 to connect
to the drs board, I get the error
"musb_open: libusb_open() error -3" |
|
Mon Oct 16 15:35:22 2017, Stefan Ritt, Raspberry Pi Connection Failure
|
Have you tried as root? Maybe you miss some permissions.
Stefan
Jonathan |
|
Wed May 5 22:30:50 2010, Ignacio Diéguez Estremera, Random noise spec in datasheet
|
Hi,
According to DRS4's datasheet, the random noise is 0.35mVrms. Is this the input equivalent noise voltage? It is computed over the 0-950MHz frequency
band? |
|
Thu May 6 08:15:39 2010, Stefan Ritt, Random noise spec in datasheet
|
Ignacio Diéguez Estremera wrote:
Hi, |
Tue Jun 18 14:19:39 2013, Stefan Ritt, ROOT program to decode binary data from DRSOsc 
|
Please find attached a simple ROOT based program (http://root.cern.ch) to decode binary data from the DRSOsc program. It assumes that all four channels
were recorded. If this is not the case, the program can be adjusted accordingly.
To use it, simply type (assuming that you have written a data file "test.dat" with DRSOsc): |
|
Wed Jul 30 17:05:06 2014, Stefan Ritt, ROOT program to decode binary data from DRSOsc
|
Stefan Ritt wrote:
Please find attached a simple ROOT based program (http://root.cern.ch) to decode binary data from the |
|
Fri Mar 8 19:35:11 2019, Abaz Kryemadhi, ROOT Macro for newest software
|
The older root macro did not work for me for data acquired with the newest software.
so for the newest software and multiple boards, I modified the read_binary.cpp into read_binary.C for those who like to use the root macro, see
the attachment. |
|
Tue Jan 29 14:43:44 2019, Abaz Kryemadhi, ROOT Macro for data acquired with the newest software
|
Hello,
Is there a root macro for decoding binary data acquired with the newest software for single board or multi-boards daisy chained?
Cheers, |
|
Wed Jan 30 17:08:58 2019, Stefan Ritt, ROOT Macro for data acquired with the newest software
|
This one elog:361 should still work.
Stefan
Abaz |
|
Fri Mar 2 18:08:55 2018, Steven Block, ROI
|
Hello,
I have a question about how ROI works. From what I have read, it will only save data that ocurs some time |
|
Fri Mar 2 20:17:17 2018, Stefan Ritt, ROI
|
N'/N is correct. The 2 us "from the response you got from me" come from the fact that after readout, you have to start the DRS4 again.
During this time, the power supply usually becomes slightly unstable, and it takes on the evaluation board about 2us to stabilize it again. Tha't why
I add the 2 us. If you don't care about slight offset effect, or if you make a better power supply, you dead time would be 10*30ns = 300ns for 10 samples. |
|
Fri Mar 2 21:05:48 2018, Steven Block, ROI
|
Great! That is very helpful.
One more question. If no signals were detected in the 1024*200ps time frame in ROI mode, would the DRS4 go dead for 32us (or 30us depending on
the supply) for, or would it dump the earliest events in the buffer for the more recent ones until it detects a signal to readout? Or rather, does |
|
Mon Mar 19 16:22:42 2018, Stefan Ritt, ROI
|
The DRS4 has an internal storage of 1024 capacitors. They work as a ring buffer, so at 5GSPS you can store 200ns wide signals. After 200ns, the first
samples are overwritten by new samples, so you always have the last 200ns of samples stored. Once you trigger the DRS4, this buffer is frozen, and the
readout of this buffer causes the dead time. No trigger, no dead time. Hope this answers your question. |
|
Tue Mar 30 22:57:34 2010, Hao Huan, ROFS Configuration
|
Hi Stefan,
according to the DRS4 datasheet, if we want an input range centered around U0, the ROFS should be 1.55V-U0. However when I read
the codes of the evaluation board application, ROFS seems to be 1.6V-1.25*U0 where the coefficient 1.25 is said to come from sampling cell charge injection |
|
Thu Apr 15 13:48:40 2010, Stefan Ritt, ROFS Configuration
|
Hao Huan wrote:
Hi Stefan, |