Thu Feb 22 10:37:03 2024, Stefan Ritt, Simulation of FPGA
|
The Cypress has its own firmware, contained in the distribution under firmware/CY7C68013A/drs_eval.c. There you can see how the data is fetched. I kind
of forgot how exactly it worked, since I wrote that code back in 2011. But most if the Cypress code is just the configuration of the USB, the communication
with the FPGA is kind of straight forward in the Cypress implementation. But you have to read the manual of that chip to understand it. |
Tue Apr 28 11:44:07 2009, Stefan Ritt, Simple example application to read a DRS evaluation board
|
Several people asked for s simple application to guide them in writing their own application to read out a DRS board. Such an application has been added
in software revions 2.1.1 and is attached to this message. This example program drs_exam.cpp written
in C++ does the following necessary steps to access a DRS board: |
Wed Apr 29 07:57:33 2009, Stefan Ritt, Simple example application to read a DRS evaluation board 
|
Stefan Ritt wrote:
|
Mon Apr 5 17:57:41 2010, Heejong Kim, Simple example application to read a DRS evaluation board
|
Stefan Ritt wrote:
Several people asked for s simple application to guide them in writing their own application to read out |
Tue Apr 13 14:15:16 2010, Stefan Ritt, Simple example application to read a DRS evaluation board
|
Heejong Kim wrote:
|
Tue May 30 20:45:30 2017, Esperienza Giove, Setting input range
|
Hello,
is it possible to set a completely negative input range like -1 to 0 or -0.95 to 0.05 ? |
Tue May 30 21:00:26 2017, Stefan Ritt, Setting input range
|
See elog:531
Esperienza
Giove wrote:
Hello, |
Tue May 30 21:22:10 2017, Esperienza Giove, Setting input range
|
Thank you
Stefan
Ritt wrote:
See elog:531 |
Tue Mar 9 23:28:45 2010, Hao Huan, Serial Interface Frequency of the DRS Chip
|
Hi Stefan,
in the DRS4 datasheet I read that the optimal frequency for SRCLK is 33MHz. However in the evaluation board firmware SRCLK is
toggled at rising edges of the internal 33MHz clock, i.e. the frequency of SRCLK itself is 16.5MHz instead. Is that frequency better than 33MHz? |
Wed Mar 10 10:07:28 2010, Stefan Ritt, Serial Interface Frequency of the DRS Chip
|
Hao Huan wrote:
in the DRS4 datasheet I read that the optimal frequency for SRCLK is 33MHz. However in the evaluation |
Thu Mar 18 21:38:10 2010, Hao Huan, Serial Interface Frequency of the DRS Chip
|
Stefan Ritt wrote:
|
Thu Mar 18 22:10:41 2010, Stefan Ritt, Serial Interface Frequency of the DRS Chip
|
Hao Huan wrote:
|
Tue Mar 1 19:03:37 2022, Keita Mizukoshi, Scaler issue to evaluate live time
|
Hi. I'm trying to evaluate livetime of the evaluation board with the hardware scaler. I'm facing a strange issue.
I took the rate with the function, DRS->GetScaler(int channel).
I guess that channels 0--3 mean the rate for the channel, and channel 4 means the counter of the trigger. |
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 52 Hz and measured 50
Hz. This is about what you can expect.
The scaler rate is measured after the discriminator of the trigger, so the trigger level also affects the scaler reading. If you have a 100 mV |
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 example ('black line is the threshold). |
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 of 100 Hz to 3
kHz.
So I don't know what's wrong on your side. Did you try with the oscilloscope app as well? Have you checked your pulse generator? The |
Fri Sep 13 15:27:41 2019, Arseny Rybnikov, Scaler / How to modify the firmware to change the scaler integration time
|
Hello,
We want to use the inner DRS4 counter(scaler) within more than the 100ms integration time. We guess that we need to modify the original
firmware around this point: |
Thu Nov 26 18:59:27 2015, Robert Adams, Saving histogram data
|
I would really love to be able to save histogram data, though I have not been able to do this. I could take a screenshot and extract the data from an
image, but would prefer to avoid this if there is a simpler way... possibly I have overlooked something obvious? Thanks very much for any advice or tips. |
Tue Feb 16 11:21:43 2016, Stefan Ritt, Saving histogram data
|
There is no histogram save functoinality in ther DRSOscilloscope program - on purpose. The board and the software are meant to evaluate the board, not
to replace a full DAQ system. If we want to save histograms, you maybe also want to set the range, make cuts, do fits etc. So it would take lots of resources
to add all that. Therefore we recommend to use the stand-alone C program drs_exam.cpp to read the board, the you can either do whatever you want in the |
Tue Feb 16 11:55:54 2016, Martin Petriska, Saving histogram data
|
Robert
Adams wrote:
I would really love to be able to save histogram data, though I have |