 Mon Sep 15 16:24:41 2014, Hannes Wachter, Timing Calibration Fail
|
Hi,
has anyone experienced a shutdown of the DRSosc.exe or DRScl.exe when executing a Timing Calibration? Also, when we add the command b->CalibrateTiming(NULL);
to the drs_exam.cpp and run the exe, our program shuts down immediately and windows shows an error message (identical to DRSosc and DRScl). |
 Mon Sep 22 15:04:37 2014, Stefan Ritt, Timing Calibration Fail
|
Hannes Wachter wrote:
Hi, |
|
Wed Oct 5 22:43:29 2016, Will Flanagan, Timestamp for each DRS4 waveform
|
Hi DRS4 Experts,
I have been analyzing DRS4 binary data with scripts based on Stefan's (very helpful!) macro:
https://midas.psi.ch/elogs/DRS4+Forum/361 |
|
Thu Oct 6 11:18:05 2016, Stefan Ritt, Timestamp for each DRS4 waveform
|
In the mentioned read_binary.cpp file you have the line where you read the event header
i = fread(&eh, sizeof(eh), 1, f);
The C structure eh now contains the full timestamp, and you can access it with |
|
Wed Jul 12 04:24:39 2017, Toshihiro Nonaka, Time resolution between boards
|
Hello,
I 'm using four evaluation boards v.3 to construct the multi-board DAQ system. One channel for each board is used as reference clock, then
calibrate timing offline, which allow below 10ps resolution between boards. |
|
Wed Jul 12 20:16:05 2017, Stefan Ritt, Time resolution between boards
|
Yes this should be possible.
Stefan
Toshihiro |
|
Fri Jul 21 09:16:02 2017, Volodymyr Rodin, Time output
|
Hello Stefan
I tried to convert binary to a simple txt file and found next problem - strange time output.
Here is output from little modification for read_binary.cpp (Its last output line also is strange: dT = -1.#IOns +- -1.$ps) |
|
Tue Jul 25 14:47:05 2017, Volodymyr Rodin, Time output
|
Hi again.
Okay, it works with 5.05 version very good and it is enough for me.
Besides, |
|
Tue Oct 17 14:58:58 2017, Vadym Denysenko, Time offset
|
Hello.
I have a simple question, can I set SetTriggerDelayNs() more than 1631 ns? |
|
Wed Oct 18 09:12:26 2017, Stefan Ritt, Time offset
|
No this is not possible. But you can delay your signal externally (like with a delay cable or electronically) and then send the dealyed signal to the
evaluation board for triggering.
Stefan |
|
Wed Oct 18 11:48:14 2017, Vadym Denysenko, Time offset
|
Thank you for your reply!
Stefan
Ritt wrote:
No this is not possible. But you can delay your signal externally (like |
|
Fri Mar 11 17:26:15 2022, Matias Senger, Time calibration and the C++ API
|
I am using the V5 board at a fixed sampling frequency. With the `drsosc` app I have executed the time calibration at 5 GS/s (actually 5.12 GS/s). This
is how my setup looks like in the app:
|
|
Sat Mar 12 10:13:24 2022, Stefan Ritt, Time calibration and the C++ API
|
DRSBoard::GetTime is declared in DRS.h line 720.
If you want to measure timing down to ps, you need some basic knowledge, especially about signal-to-noise and risetime. This cannot be taught
in a few sentenses, needs a full lecture. As a starting point please read that papat: |
|
Sat Mar 12 16:52:36 2022, Matias Senger, Time calibration and the C++ API
|
Dear Stefan,
For the time of each bin I am using the values returend by `GetTime` without any assumption by my side. I did not notice before that the sampling
time is not uniform, but I see that this is already happening. This is an example plot from one of the signals I processed: |
Mon Mar 14 08:59:51 2022, Stefan Ritt, Time calibration and the C++ API 
|
Looks like you have the some time calibration, not sure if it's the correct one. Sample the sine wave from the calibration clock, once with and once
without the timing calibration, then you will see if all points lie on a smooth line. Left: without timing calibration, right: with proper timing calibration:
|
|
Tue Mar 15 13:07:50 2022, Matias Senger, Time calibration and the C++ API
|
Thanks for your help. If I look into the app the behavior for the 4 channels is exactly as you show:
|
|
Wed Jan 17 09:51:16 2018, Tran Cong Thien, The input signals recorded are different with the signal showed in oscilloscope
|
Dear Stefan,
I am using an DRS4 board to record the signals from an plastic scintillator detector. It was working really good, yet a few day ago the signals
became "not right". When I checked the signal using an oscilloscope it show the normal signals previously recorded. The signal amplitude |
|
Wed Jan 17 10:09:09 2018, Stefan Ritt, The input signals recorded are different with the signal showed in oscilloscope
|
First thing is to do another voltage calibration. Disconnect input, "Config", "Execute Voltage Calibration". If this does not fix
the problem, the board is probably broken. This can happen if you send very high input singals to the board (like >10V) and exceed the maximul allowed
limit from the datasheet. In that case the board needs to be repaired. Please contact me directly (via email) so that we can make you a quote. |
|
Thu Apr 17 12:02:28 2014, Wang , The first channel is wrong.
|
Hi,
I want to describe this phenomenon again. The diagram |
|
Tue Jun 19 06:42:23 2018, Phan Van Chuan, The data acquisition speed
|
Dear Stefan,
We are using an DRS4 board V5.1 for building a metering system for the scintillator detector by a Labview program. The program was built based
on the functions in DRS.cpp and it reads data from channel 0 very well (Fig 1). Now, I am having a problem with the data acquisition from DRS4 board. The |