| ID |
Date |
Author |
Subject |
Text |
 |
|
888
|
Fri Jul 29 17:23:43 2022 |
Stefan Ritt | Spikes/noise sensitive to clock settings? | Look at the DRS4 data sheet, Figure 12.
You see there the rising SRCLK pulse which
outputs the next analog value. You also see |
|
|
887
|
Fri Jul 29 14:09:35 2022 |
Stefan Ritt | Increase event rate, use ROI mode, and install sw from source in Mac | The firmware from the website always reads
1024 bins. You have to modify it to stop
before that, like reading only 128 samples |
|
|
886
|
Tue Jul 19 02:35:04 2022 |
Jingyu Zhang | Increase event rate, use ROI mode, and install sw from source in Mac | Dear
experts,
|
|
|
885
|
Fri Jun 24 09:57:36 2022 |
LynseyShun | Spikes/noise sensitive to clock settings? | Hello, I now have periodic spikes in CH0
and CH1 output. How can I eliminate
these spikes? I'm sorry I didn't |
|
|
884
|
Thu Jun 16 05:31:25 2022 |
LynseyShun | | Thank you very much for your help!
|
|
|
883
|
Tue Apr 12 10:49:27 2022 |
Stefan Ritt | | A3-A0 = 1001 should be all you need to
activate OUT0-OUT7. It works in our designs.
Maybe double check the address lines with |
|
|
882
|
Tue Apr 12 10:40:36 2022 |
LynseyShun | | Hello, I am Lynsey. now I set A3-A0 to
1001 in ROI mode, but only OUT0 has output,
and the other seven channels(OUT1-OUT7) do |
|
|
881
|
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: |
|
|
880
|
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, |
|
|
879
|
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 |
|
|
878
|
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 |
|
|
877
|
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 |
|
|
876
|
Tue Mar 8 12:20:00 2022 |
Matias Senger | Why does not trigger at higher sampling frequencies? | Sorry for the spam. Just want to let you
know that I was able to solve the problem,
it was all due to a `float` being casted |
|
|
875
|
Tue Mar 8 00:25:56 2022 |
Matias Senger | Why does not trigger at higher sampling frequencies? | I have seen in the app that the trigger
source buttons do something different than
the "or" and "transparent |
|
|
874
|
Mon Mar 7 16:37:54 2022 |
Stefan Ritt | Scaler issue to evaluate live time | I tried your measurement with the DRSOscilloscope
app (see below), and I measure a constant
difference of 10 Hz among the whole range |
|
|
873
|
Mon Mar 7 13:38:03 2022 |
Radoslaw Marcinkowski | Problems with DRS4 Evaluation Board after Windows 10 upgrade - share of experiences | Dear DRS4 Users,
I would like to share my expireinces
with using of DRS4 Evaluation Board software |
|
|
872
|
Mon Mar 7 08:45:32 2022 |
Stefan Ritt | Why does not trigger at higher sampling frequencies? | Unfortunately I have not idea what the
problem could be. In principle the trigger
should be independent of the sampling speed, |
|
|
871
|
Sun Mar 6 17:54:47 2022 |
Matias Senger | Why does not trigger at higher sampling frequencies? | I have connected 3 signals to the DRS4
Evaluation Board V5 which look like this
in the drsosc app: |
|
|
870
|
Fri Mar 4 03:55:33 2022 |
Keita Mizukoshi | Scaler issue to evaluate live time | Thank you very much for your explanation.
I would like to show you a pulse |
|
|
869
|
Thu Mar 3 16:14:16 2022 |
Stefan Ritt | Scaler issue to evaluate live time | The scalers are read out 10x per seconds,
so they have an accuracy of 10 Hz. I tried
a 50 Hz pulser, and measured 40 Hz, I tried |
|