 Tue Dec 12 00:25:50 2017, Diego Yankelevich, External trigger using Raspberry Pi
|
Dear Steffan:
We have been able to use the DRS4 using a Raspberry Pi but we have not been able to use the external trigger. What we are doing is basically
comment out the code shown below (downloaded from PSI) to use the hardware trigger and uncomment the code to use the external trigger. We have not been |
 Tue Dec 12 13:58:06 2017, Stefan Ritt, External trigger using Raspberry Pi
|
Indeed the code does not work for the current evaluation board, it has been written for a previous version and never been updated. Please use following
code to enable the external trigger
/* use following lines to enable the external trigger */ |
|
Tue Sep 22 17:45:26 2020, Elmer Grundeman, External triggering
|
Dear all,
I had a question about timing jitter and external triggering.
I trigger the board externally with a 3V pulse from a DG645 delay generator and as a test I use the gated charge function to integrate another |
|
Wed Oct 7 10:56:03 2020, Stefan Ritt, External triggering
|
The trigger is there only to trigger the chip, but cannot be used as a precise time reference. If you want to measure precise timing, do this always
BETWEEN two inputs, never between an input and the trigger. You might want to split and delay your trigger signal and feed one copy to another input of
the evaluation board as your reference. |
|
Wed Oct 7 11:17:52 2020, Elmer Grundeman, External triggering
|
I will try that, thanks!
Stefan
Ritt wrote:
The trigger is there only to trigger the chip, but cannot be used as |
|
Sun Jan 31 23:52:15 2010, Hao Huan, Failure In Flashing Xilinx PROM
|
Hi Stefan,
I have an old-version DRS4 evaluation board which doesn't have the latest firmware. I tried to flash the drs_eval1.ipf boundary
scan chain into the XCF02S PROM with Xilinx IMPACT, and the firmware seemed to go through into the PROM. However, when I started the DRS command line interface |
Mon Feb 1 08:30:42 2010, Stefan Ritt, Failure In Flashing Xilinx PROM 
|
Hao Huan wrote:
Hi Stefan, |
|
Mon Jul 19 12:07:04 2010, Jinhong Wang, Fixed Patter Timing Jitter
|
| Hi Stefan, can you give some suggestions on determination of fixed pattern timing jitter of DRS4? Thanks~ |
|
Mon Jul 19 12:47:17 2010, Stefan Ritt, Fixed Patter Timing Jitter
|
Jinhong Wang wrote:
Hi Stefan, can you give some suggestions on determination of fixed pattern timing jitter of DRS4? |
|
Mon Jul 4 05:06:00 2011, Jinhong Wang, Fixed Patter Timing Jitter
|
Stefan Ritt wrote:
|
|
Tue Jul 5 10:09:43 2011, Stefan Ritt, Fixed Patter Timing Jitter
|
Jinhong Wang wrote:
|
|
Tue Jul 12 09:49:08 2011, Jinhong Wang, Fixed Patter Timing Jitter
|
Stefan Ritt wrote:
|
|
Wed Jul 13 04:26:52 2011, Stefan Ritt, Fixed Patter Timing Jitter
|
Jinhong Wang wrote:
|
|
Thu Apr 14 18:23:53 2011, Bob Hirosky, Fixes to DOScreen.cpp for recent built on linux
|
Hello,
I was just building version 3.1.0 and ran into some problems in DOScreen.cpp. Basically the conversions from
|
|
Fri Apr 15 08:28:54 2011, Stefan Ritt, Fixes to DOScreen.cpp for recent built on linux
|
> Hello,
>
> I was just building version 3.1.0 and ran into some problems in DOScreen.cpp. Basically the conversions from
|
|
Fri Dec 9 17:45:48 2011, Michael Büker, Fixes to DOScreen.cpp for recent built on linux
|
> I was just building version 3.1.0 and ran into some problems in DOScreen.cpp. Basically the conversions from
> char* to wxString were generating "ambiguous overload" errors (in gcc 4.4.3, wx-2.8)
>
|
|
Mon Oct 29 18:30:28 2012, Martin Petriska, GetWave
|
I have some question according to GetWave function. In drs_exam.cpp simple GetWave(0,0,wave_array[]) etc...is used. Is there primary (cell) calibration,
secondary calibration (Readout) and remove Spikes used, as in DRS Oscilloscope application? |
|
Tue Nov 13 11:26:32 2012, Stefan Ritt, GetWave
|
Martin Petriska wrote:
I have some question according to GetWave function. In drs_exam.cpp simple GetWave(0,0,wave_array[]) |
|
Wed May 13 00:52:51 2015, Cosmin Deaconu, Getting Trigger Source
|
I'd like to be able to know which channel (0,1,2,3 or external) was responsible for the trigger. DRSBoard::GetTriggerSource() seems to always
return 1. Is there a way to get this information? Using the DRS4 evaluation board and software version 5.0.3.
Thanks, |
|
Wed May 13 08:19:53 2015, Stefan Ritt, Getting Trigger Source
|
DRSBoard::GetTriggerSource() simply returns what has been enabled via DRSBoard::SetTriggerSource(). The actual source which causes the trigger is not
stored in the hardware of the board, because I can be reconstructed easily from the waveforms. So just look which of the channels is above your trigger
threshold. If none of the channels has a waveform obove the threshold, then the trigger must have been come from the external trigger. |