| ID |
Date |
Author |
Subject |
Text |
 |
|
680
|
Tue Apr 17 13:28:23 2018 |
Stefan Ritt | DRS4 read_binary.cpp | On the software download page at https://www.psi.ch/drs/software-download
you find a link to all versions of the DRS
software, which is located at: https://www.dropbox.com/sh/clqo7ekr0ysbrip/AACoWJzrQAbf3WiBJHG89bGGa?dl=0 |
|
|
679
|
Mon Apr 16 21:21:29 2018 |
Sobimpe Eniola | DRS4 read_binary.cpp | Hello everyone,
The new read_binary.cpp code
I will be very glad if anyone can |
|
|
678
|
Fri Apr 13 18:14:07 2018 |
Alessio Berti | Voltage and Timing Calibration in drs_exam.cpp | Hi,
we were trying to implement an
automatic way to calibrate our DRS4 both |
|
|
677
|
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 |
|
|
676
|
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 |
|
|
675
|
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. |
|
|
674
|
Mon Mar 19 15:12:02 2018 |
Stefan Ritt | Running drs_example.cpp | The time channel is already calibrated
in ns. So for 5 GSPS, the time scale goes
from zero to 200. Concerning your other issues |
|
|
673
|
Fri Mar 16 14:00:06 2018 |
Stefan Ritt | confusion about the description in drs.cpp | The FPGA is very small, so it only has
an address space of 256 bytes. Look at the
definition in DRS.cpp |
|
|
672
|
Thu Mar 15 08:44:26 2018 |
Stefan Ritt | sub-ms precision timestamps? | Putting sub-ms precision into the header
does not make sense, since the USB transfer
only happens in time-slots of about 2 ms. |
|
|
671
|
Wed Mar 14 09:13:39 2018 |
chen wenjun | confusion about the description in drs.cpp | Hi,Stefan:
recently,whtn I study the
drs.cpp code ,I found that the buffer[1] |
|
|
668
|
Wed Mar 14 00:38:15 2018 |
Will Flanagan | sub-ms precision timestamps? | Dear DRS4 community,
Is there a way to extract timestamps
with sub-ms precision? The milliseconds of |
|
|
667
|
Thu Mar 8 22:54:20 2018 |
Rodrigo Trindade de Menezes | Running drs_example.cpp | We found a way to solve the previous problem,
but right now when we try to set the input
range only -0.5 to 0.5 is working. When we |
|
|
666
|
Wed Mar 7 22:49:38 2018 |
Rodrigo Trindade de Menezes | Running drs_example.cpp | Hello,
We have been using the DRS4 evaluation
board (S/N 2636) that works with the scope |
|
|
665
|
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 |
|
|
664
|
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 |
|
|
663
|
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 |
|
|
662
|
Tue Feb 27 18:12:32 2018 |
Stefan Ritt | DRS4 Dead times | For applications which are critical on
the dead time, one typically uses one ADC
per DRS4 channel, and thus the dead time |
|
|
661
|
Tue Feb 27 18:04:18 2018 |
Steven Block | DRS4 Dead times | That is extremely helpful! Many thanks.
One more question; If I were to take inputs
from 2 channels at once, would that scale |
|
|
660
|
Tue Feb 27 17:04:12 2018 |
Stefan Ritt | DRS4 Dead times | XML is very slow to write, and you are
probably limited by that. Switch to binary
mode, which is much faster. You will see |
|
|
659
|
Tue Feb 27 16:34:26 2018 |
Steven Block | DRS4 Dead times | Hello All,
I am currently trying to figure
out how to properly characterize the dead |
6x |