DRS4 Forum
 DRS4 Discussion Forum, Page 38 of 42 Not logged in
 New entries since: Thu Jan 1 01:00:00 1970
ID Date Author Subject
665   Fri Mar 2 21:05:48 2018 Steven BlockROI

One more question. If no signals were detected in the 1024*200ps time frame in ROI mode, would the DRS4 go dead for 32us (or 30us depending on the supply)  for, or would it dump the earliest events in the buffer for the more recent ones until it detects a signal to readout? Or rather, does filling the buffer force a readout or can it dynamically shift out old data until it detects a signal to readout.

Steven

Stefan Ritt wrote:

N'/N is correct. The 2 us "from the response you got from me" come from the fact that after readout, you have to start the DRS4 again. During this time, the power supply usually becomes slightly unstable, and it takes on the evaluation board about 2us to stabilize it again. Tha't why I add the 2 us. If you don't care about slight offset effect, or if you make a better power supply, you dead time would be 10*30ns = 300ns for 10 samples. Starting the DRS again will take one or two clock cycles from the FPGA, which might add another 30 ns or so, depending on how you program the FPGA. So the best you can achieve for 10 samples is maybe 330 ns, if you have a really good power supply (large capacitors).

You can achieve this functionality with the evaluation board, but you would have to make a special firmware for it.

Stefan

 Steven Block wrote: Hello, I have a question about how ROI works. From what I have read, it will only save data that ocurs some time [ta] dictated by the user after an event is triggered as well as a small time [tb] before the event. The technical manual seems to indicated that the deadtime assciated with operating in ROI mode can be reduced by the following factor:  $\frac{t_a + t_b }{\frac{N}{Sample Speed}}$ . Where N is the number of points in the time window (ex. 2048 or 1024). Is it ok to describe this as: $\frac{N'}{N}$ Where N' is the number of samples in the ROI and N is the same as before. For example, if I were running at 5Gsps (200ps between samples), only recording 1024 samples per event and I had an signal that lasted 2ns, that means the signal would last 10 samples. If I set the ROI to only save 20 samples around this signal, would my Deadtime go to: $\frac{10}{1024} * 30ns*1024 + 2\mu s = 2.3\mu s$? (The second portion of this equation comes from a response I recieved earlier, but I just want to make sure I understand this concept properly) I recognize that the caveat is that this would work only if the signal was detected during acquistion, which leads to my next question. If no signals were detected in the 1024*200ps time frame in ROI mode, would the DRS4 go dead for 32us (using the factor = 1 from above equation), or would it dump the earliest events in the buffer for the more recent ones until it detects a signal?  Finally, I assume this functionality can only be utilized with custom electornics with the DRS4, not the evaulation/demo board, please let me know if this is the case.  Best, Steven

605   Sat Apr 15 03:48:31 2017 Strahinja LukicWave rotation during transfer from the board?

I don't know if this question is already documented elsewhere.

I am developing a DAQ code for the DRS evaluation board, v4 for a test beam experiment. I link parts of the existing DRS code as a library.

To understand the effect of various flags used in calls to the functions DRSBoard::GetTime() and DRSBoard::GetWave(), I performed several tests with the 100 MHz signal connected to the inputs of the chip (DRSBoard::EnableTcal()), and several tests with signals from scintillation counters.

My question is about the flag "adjustToClock" in the call to DRSBoard::GetWave(). From looking at the code, I expected it to cause the waveforms to be "rotated" to start from the trigger cell, in a similar way that the flag "rotated" in the call to DRSBoard::GetTime() does for the time array. However, "adjustToClock" seems to shift the waveforms wrongly. I.e., if I want both the time and the amplitude arrays "rotated"  to start from the trigger cell, I should set rotated=true for time and adjustToClock=false for the amplitude. This is also how these functions are called in e.g., Osci::ReadWaveforms().

Is this correct, and does this mean that the amplitude array is "rotated" already during the transfer from the board?

I am using DRS evaluation board serial #2733, firmware revision 30000.

Many thanks,

Strahinja

607   Thu Apr 20 06:30:13 2017 Strahinja LukicWave rotation during transfer from the board?

Thanks.

Strahinja

Stefan Ritt wrote:

This is correct. Actually the amplitude array is rotated already inside the DRS4 chip. So the readout starts with the stop cell plus one. If you do not do anything, the waveform is already "rotated". If you want the waveform to start with physical cell #0, you have to "unrotate" it.

Stefan

 Strahinja Lukic wrote: Is this correct, and does this mean that the amplitude array is "rotated" already during the transfer from the board?

807   Wed Jan 20 12:14:49 2021 Taegyu Leedrs4 persistence

Dear all,

I have a question about the function that drs4 can perform.

Is there any function in drs4 that is analogous to that of "persistence display" in oscilloscope?? (accumulating pulses)

Thank you

588   Fri Feb 24 17:34:28 2017 Tarik ZenginPassing parameters to drscl

Hi everyone,

I wonder if there is a way to pass parameters to drscl. What I specifically want to do is calling drscl from a shell script and read/save some data. I want to schedule a measurement. Therefore I need to call drscl from the command line using some parameters.

It would look something like this;

#!/bin/bash

for i in {0..100}

do

echo "Reading $i" ./drscl read 0 0 test.xml sleep 1 done This doesn't work of course. drscl won't take arguments from the command line. Can you suggest a way to do this please? Thank you. 811 Fri Feb 26 17:05:26 2021 Tom SchneiderTrouble getting PLL to lock Hello, I am working on a custom PCB design with the DRS4 chip, and I can't get the PLL to lock. I'm feeding CLKIN with a 1MHz CMOS clock (REFCLK- tied to VDD/2), and I'm using the same loop filter as the eval board. I see from the datasheet that the PLL is enabled by default, so I'm not writing anything to the config register on startup. I am just driving DENABLE high approx. 100ms after startup and looking for the PLL lock bit to go high. When I look at DTAP, I see a 3MHz signal. Can anyone tell me what I'm doing wrong? -Tom 813 Fri Feb 26 18:33:52 2021 Tom SchneiderTrouble getting PLL to lock Stefan, Thanks for responding so quickly. Yes I have my clock source going to REFCLK+ (CLKIN is the signal name on my schematic). BIAS is 0.7V exactly, /RESET is high, A0-A3 are 0x0000, and the loop filter has a 4.7nF cap to GND with a 130ohm resistor + 1uF cap in parallel, just like the eval board. Regarding the clock - I am not using an LVDS clock, but rather a 2.5V-level clock signal, with REFCLK- tied to 1.25V. Sheet 9 of the datasheet states: If no LVDS reference clock signal is available, a CMOS signal can be connected to REFCLK+ and the REFCLK input is connected to VDD/2 via a resistor divider. Is that not a true statement? -Tom Stefan Ritt wrote: I guess you mean "1 MHz clock at REFCLK+", and not CLKIN, there is no CLKIN, just a SRCLK, but that is someting else! There could be many reasons why this is not working. It's hard for me to debug your board without actually having it in hands. So just some ideas: - Supply a clean differential REFCLK, I never tried one end tied to VDD/2 - Is /RESET high? - Is BIAS at roughly 0.7V? - Is A0-A3 different from 1111, which puts the chip in standby - Did you double check your loop filter? The easiest usually is to start from a running evaluation board, then compare all pins 1:1 with your board. Stefan  Tom Schneider wrote: Hello, I am working on a custom PCB design with the DRS4 chip, and I can't get the PLL to lock. I'm feeding CLKIN with a 1MHz CMOS clock (REFCLK- tied to VDD/2), and I'm using the same loop filter as the eval board. I see from the datasheet that the PLL is enabled by default, so I'm not writing anything to the config register on startup. I am just driving DENABLE high approx. 100ms after startup and looking for the PLL lock bit to go high. When I look at DTAP, I see a 3MHz signal. Can anyone tell me what I'm doing wrong? -Tom 815 Fri Feb 26 21:24:39 2021 Tom SchneiderTrouble getting PLL to lock Probe capacitance makes that tricky - if I put my probe on DSPEED, I see that it starts at approx. 2.5V then gradually decreases until it hits 0V. DTAP decreases from 3MHz to 0 during this time. I'll try to get something together to show you. Stefan Ritt wrote: Can you post a scope trace of your refclk together with DTAP, DSPEED and DENABLE? Tom Schneider wrote: Stefan, Thanks for responding so quickly. Yes I have my clock source going to REFCLK+ (CLKIN is the signal name on my schematic). BIAS is 0.7V exactly, /RESET is high, A0-A3 are 0x0000, and the loop filter has a 4.7nF cap to GND with a 130ohm resistor + 1uF cap in parallel, just like the eval board. Regarding the clock - I am not using an LVDS clock, but rather a 2.5V-level clock signal, with REFCLK- tied to 1.25V. Sheet 9 of the datasheet states: If no LVDS reference clock signal is available, a CMOS signal can be connected to REFCLK+ and the REFCLK input is connected to VDD/2 via a resistor divider. Is that not a true statement? -Tom Stefan Ritt wrote: I guess you mean "1 MHz clock at REFCLK+", and not CLKIN, there is no CLKIN, just a SRCLK, but that is someting else! There could be many reasons why this is not working. It's hard for me to debug your board without actually having it in hands. So just some ideas: - Supply a clean differential REFCLK, I never tried one end tied to VDD/2 - Is /RESET high? - Is BIAS at roughly 0.7V? - Is A0-A3 different from 1111, which puts the chip in standby - Did you double check your loop filter? The easiest usually is to start from a running evaluation board, then compare all pins 1:1 with your board. Stefan  Tom Schneider wrote: Hello, I am working on a custom PCB design with the DRS4 chip, and I can't get the PLL to lock. I'm feeding CLKIN with a 1MHz CMOS clock (REFCLK- tied to VDD/2), and I'm using the same loop filter as the eval board. I see from the datasheet that the PLL is enabled by default, so I'm not writing anything to the config register on startup. I am just driving DENABLE high approx. 100ms after startup and looking for the PLL lock bit to go high. When I look at DTAP, I see a 3MHz signal. Can anyone tell me what I'm doing wrong? -Tom 817 Fri Feb 26 22:52:13 2021 Tom SchneiderTrouble getting PLL to lock Thats not a simple modification to my PCB, but I'll give it a try. Thanks for your help  Stefan Ritt wrote: Sounds to me like your REFCLK is not getting through or your PLL loop is open. Could be a bad solder connection. Try to measure signals not on the PCB trace, but directly on the DRS4 pins. Drive REFCLK with a proper LVDS signal. Maybe it's wrong what I wrote in the data sheet and the trick with VDD/2 is not really working. Stefan 818 Thu Mar 4 21:36:14 2021 Tom SchneiderTrouble getting PLL to lock I found the problem, and it had nothing to do with the CMOS clock input. As it turns out, even though I was using the default state of the config register, I still had to write to it after powerup. Once I did that, the PLL locked immediately. -Tom Tom Schneider wrote: Thats not a simple modification to my PCB, but I'll give it a try. Thanks for your help  Stefan Ritt wrote: Sounds to me like your REFCLK is not getting through or your PLL loop is open. Could be a bad solder connection. Try to measure signals not on the PCB trace, but directly on the DRS4 pins. Drive REFCLK with a proper LVDS signal. Maybe it's wrong what I wrote in the data sheet and the trick with VDD/2 is not really working. Stefan 350 Thu May 29 04:22:43 2014 Toshihiro NonakaCalibrationWaveform I'm writing the drs_exam.cpp to use multi-boards(v3, firmware:4.0.0), and taking data succeeded. But I have several questions about function written in DRS.cpp. 1. I wrote following code in drs_exam.cpp to set input range -0.4~0.6 b1->SetInputRange(0.1); And the 100mV offset appeared(I attached a picture). I think this is due to the voltage calibration isn't done.(Calibrated to -0.5~0.5mV in DRS Oscilloscope) If so, could you show me a simple usage of "CalibrationWaveform()" function in DRS.cpp? (or other function?) 2. Although this question might be the almost same with above, is there any way to execute voltage and timing calibration in drs_exam.cpp? Now I start DAQ by executing drs_exam.cpp after I execute voltage and timing calibration to each board by DRS Oscilloscope program. 3. Which command is right to use external trigger? b1->SetTriggerSource(4); or b1->SetTriggerSource(1<<4); Best regards, Toshihiro Nonaka 514 Wed Apr 27 08:14:14 2016 Toshihiro Nonakaserial number problem Dear all, I'm using 3 DRS boards simultaneously and their serial numbers are 2169, 2170, 2172 respectively. Recently however, I obtain serial number "0" by DRSBoard::GetBoardSerialNumber() for #2172 board. Data taking can be done without any problems, but I'd like to know what is happening. Any advice？ Thank you. Toshihiro Nonaka 516 Wed Apr 27 09:51:37 2016 Toshihiro Nonakaserial number problem The serial number has been fixed by using drscl. Thank you！ Stefan Ritt wrote: If dis- and reconnecting the board does not help, there is the (small) chance that the serial number got erased in the board. You can re-set it with the "drscl" command line tool:$ drscl
Found DRS4 board 0 on USB, serial #0, firmware revision 21305
B0> serial 2172

 Toshihiro Nonaka wrote: Dear all, I'm using 3 DRS boards simultaneously and their serial numbers are 2169, 2170, 2172 respectively. Recently however,  I obtain serial number "0" by DRSBoard::GetBoardSerialNumber() for #2172 board. Data taking can be done without any problems, but I'd like to know what is happening. Any advice？ Thank you. Toshihiro Nonaka

623   Wed Jul 12 04:24:39 2017 Toshihiro NonakaTime 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.

Is it possible to keep the time resolution between boards below 10ps in daisy-chain mode with v.5 boards?

Best regards,

Toshihiro Nonaka

651   Wed Jan 17 09:51:16 2018 Tran Cong ThienThe 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 are clearly reduced (from 0.3 in oscilloscope to lower than 0.1 in DRS4). Can you show me how to show this problem?

Thank you very much!

Best Regards,

Thien

360   Wed Jul 30 11:38:58 2014 Tsutomu NagayoshiSampling speed of DRS4 Board ver4

Hello!

I have a question concerning the sampling speed of the DRS4 evaluation board.

It is written in the manual that the sampling speed of  DRS4 Evaluation Board is supported above 0.7 GHz.

However I was able to set the sampling speed to be 0.5 GHz with the function DRSBpard::SetFrequency(0.5)  and realized that DRSBoard::GetTime function fills time array in every 2 ns.

I am wondering if the data taken with 0.5 GHz sampling is reliable or not.

Best regards,

Tsutomu Nagayoshi

586   Tue Jan 31 01:37:35 2017 VO HONG HAILLD and ULD discriminations,
Dear Stefan, Is there any way to develop LLD and ULD discrimination in DSR-4 evaluation board? Best regards, V.H.Hai
633   Tue Oct 17 14:58:58 2017 Vadym DenysenkoTime offset

Hello.

I have a simple question, can I set SetTriggerDelayNs() more than 1631 ns?

I need to set this delay to about 5 us... Can I do this?

With best regards,

635   Wed Oct 18 11:48:14 2017 Vadym DenysenkoTime offset

Stefan Ritt wrote:

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

 Vadym Denysenko wrote: Hello.   I have a simple question, can I set SetTriggerDelayNs() more than 1631 ns? I need to set this delay to about 5 us... Can I do this?    Thank you in advance!    With best regards,  Vadym

625   Thu Jul 20 13:00:44 2017 Volodymyr RodinDriver installation on Windows 10

Dear Laura

You need to disable driver signature enforcement.  Then try again with path option.

It helped me.

http://www.drivethelife.com/windows-drivers/how-to-disable-driver-signature-enforcement-on-windows-10-8-7-xp-vista.html

Best regards,

Volodymyr

 Laura Gonella wrote: Hello, I am trying to get a DRS4 board to run on Windows 10. I am having problems with the driver installation. I am getting the follwoing message "There is no driver selected for the device information set or element" I had specified the path to look for the driver as C:\ProgramFilesx86\DRS\driver\. I also tried the option to look online for the driver. None works. Can anyone help? Thanks, Laura

ELOG V3.1.4-80633ba