DRS4 Forum
  DRS4 Discussion Forum  Not logged in ELOG logo
Entry  Fri Mar 11 17:26:15 2022, Matias Senger, Time calibration and the C++ API 
    Reply  Sat Mar 12 10:13:24 2022, Stefan Ritt, Time calibration and the C++ API 
       Reply  Sat Mar 12 16:52:36 2022, Matias Senger, Time calibration and the C++ API 
          Reply  Mon Mar 14 08:59:51 2022, Stefan Ritt, Time calibration and the C++ API Screenshot_2022-03-14_at_9.04.07_.pngScreenshot_2022-03-14_at_9.03.47_.png
             Reply  Tue Mar 15 13:07:50 2022, Matias Senger, Time calibration and the C++ API 
Message ID: 881     Entry time: Tue Mar 15 13:07:50 2022     In reply to: 880
Author: Matias Senger 
Subject: 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:

Now, when I sample with my code something strange happens, two of the channels are fine and the other two are wrong:

This is a surprise to me because I acquire the 4 channels in the same way within a `for` loop. To get the time data I use `DRSBoard::GetTime` with the `tcalibrated` argument set to `true`. Is there any aditional step to use the calibration?

Best,
Matias.

 

 

 

 

 

 

Stefan Ritt wrote:

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:

 

If your points do not lie on a smooth line, you might habe a problem such as the wrong channel for calibration, an offset of 1 in the index of the time array or some other software bug. Measure the same signal with the DRSOsc application and then your code. If the results differ, you have a software problem on your side.

Stefan

 

 

ELOG V3.1.5-3fb85fa6