ID |
Date |
Author |
Subject |
187
|
Thu Nov 1 20:17:42 2012 |
Stefan Ritt | DRS4 firmware |
hongwei yang wrote: |
Hi,
We are using drs4 board, but oscilloscope app will somehow stop to work if we config trigger into "or and", When I look into the drs4 firmware file drs4_eval3_app.vhd, I couldn't find the trigger_config value assignment which is mentioned at(#7 offset 0x1E from 31 downto 16) in manual_version 4.
could you help me find this trigger_config access point?
thanks
Hongwei
|
The "and" in the trigger section means now "coincidence". So the V4 board can trigger on a coincidence between two or more channels. If there is no pulse at the same time on the coincidence channels, the board will of course not trigger. The according firmware was introduced in V4, so please look at drs4_eval4_app.vhd (not eval3).
I just realized that the V4 firmware might be missing in the distribution, so I have attached it here. Look for drs_ctl_trigger_config.
Best regards,
Stefan |
Attachment 1: drs4_eval4_app.vhd
|
--*************************************************************
-- Author : Boris Keil, Stefan Ritt
-- Contents : Main file for DRS4 control and readout
-- $Id: drs4_eval4_app.vhd 15159 2010-04-29 10:12:25Z ritt $
-- $Revision: 15159 $
--*************************************************************
library ieee;
use ieee.std_logic_1164.all;
-- use ieee.std_logic_arith.all;
use ieee.std_logic_unsigned.all;
use ieee.numeric_std.all;
-- synopsys translate_off
library UNISIM;
use UNISIM.Vcomponents.ALL;
-- synopsys translate_on
use work.drs4_pack.all;
entity drs4_eval4_app is
port (
-- clocks
I_CLK33 : in std_logic;
I_CLK66 : in std_logic;
I_CLK132 : in std_logic;
I_CLK264 : in std_logic;
O_CLK_PS_VALUE : out std_logic_vector(7 downto 0);
I_CLK_PS : in std_logic;
I_RESET : in std_logic; -- active high power-up reset
-- analog triggers
I_ANA_TRG : in std_logic_vector(3 downto 0);
-- external trigger
IO_ETRG_IN : inout std_logic;
O_ETRG_IND : out std_logic;
IO_ETRG_OUT : inout std_logic;
O_ETRG_OUTD : out std_logic;
-- external (MMCX clock) clock
IO_ECLK_OUT : inout std_logic;
IO_ECLK_IN : inout std_logic;
-- PMC
P_IO_PMC_USR : inout std_logic_vector(63 downto 0);
-- Simple bus interface to DPRAM
O_DPRAM_CLK : out std_logic;
O_DPRAM_ADDR : out std_logic_vector(31 downto 0);
O_DPRAM_D_WR : out std_logic_vector(31 downto 0);
O_DPRAM_WE : out std_logic;
I_DPRAM_D_RD : in std_logic_vector(31 downto 0);
-- Control & status registers from system FPGA interface
I_CONTROL_REG_ARR : in type_control_reg_arr;
O_STATUS_REG_ARR : out type_status_reg_arr;
I_CONTROL_TRIG_ARR : in type_control_trig_arr;
I_CONTROL0_BIT_TRIG_ARR : in std_logic_vector(31 downto 0);
-- LEDs signals
O_LED_RED : out std_logic;
O_LED_YELLOW : out std_logic;
-- Debug signals
O_DEBUG1 : out std_logic;
O_DEBUG2 : out std_logic
);
end drs4_eval4_app;
--*************************************************************
architecture arch of drs4_eval4_app is
attribute BOX_TYPE : string;
component USR_LIB_VEC_FDC
generic (
width : integer := 1
);
port (
I_CLK : in std_logic_vector (width-1 downto 0);
I_CLR : in std_logic_vector (width-1 downto 0);
I : in std_logic_vector (width-1 downto 0);
O : out std_logic_vector (width-1 downto 0)
);
end component;
component USR_LIB_VEC_IOFD_CPE_NALL
generic (
width : integer := 1;
init_val_to_pad : string := "0";
init_val_from_pad : string := "0"
);
port (
O_C : in std_logic_vector (width-1 downto 0);
O_CE : in std_logic_vector (width-1 downto 0);
O_CLR : in std_logic_vector (width-1 downto 0);
O_PRE : in std_logic_vector (width-1 downto 0);
O : out std_logic_vector (width-1 downto 0);
I_C : in std_logic_vector (width-1 downto 0);
I_CE : in std_logic_vector (width-1 downto 0);
I_CLR : in std_logic_vector (width-1 downto 0);
I_PRE : in std_logic_vector (width-1 downto 0);
I : in std_logic_vector (width-1 downto 0);
IO : inout std_logic_vector (width-1 downto 0);
T : in std_logic_vector (width-1 downto 0)
);
end component;
component OFDDRTCPE
port (
O : out STD_ULOGIC;
C0 : in STD_ULOGIC;
C1 : in STD_ULOGIC;
CE : in STD_ULOGIC;
CLR : in STD_ULOGIC;
D0 : in STD_ULOGIC;
D1 : in STD_ULOGIC;
PRE : in STD_ULOGIC;
T : in STD_ULOGIC
);
end component;
attribute BOX_TYPE of OFDDRTCPE : component is "PRIMITIVE";
component IOBUFDS
port (
O : out STD_ULOGIC;
IO : inout STD_ULOGIC;
IOB : inout STD_ULOGIC;
I : in STD_ULOGIC;
T : in STD_ULOGIC
);
end component;
component LUT1
generic (
INIT : bit_vector
);
port(
O : out STD_ULOGIC;
I0 : in STD_ULOGIC
);
end component;
signal GND : std_logic;
signal VCC : std_logic;
-- ADC
signal i_drs_adc : std_logic_vector(13 downto 0);
signal o_drs_adc_clk : std_logic;
signal adc_clk_sr : std_logic_vector(15 downto 0);
-- Serial interface for DAC, EEPROM and Temp. Sensor
signal o_drs_serial_data : std_logic;
signal o_drs_serial_clk : std_logic;
signal i_drs_serial_data : std_logic;
signal i_drs_eeprom_data : std_logic;
signal o_drs_dac_cs_n : std_logic;
signal o_drs_eeprom_cs_n : std_logic;
signal o_drs_tempsens_cs_n : std_logic;
-- Status LED
signal drs_led_yellow : std_logic;
signal drs_led_trigger : std_logic;
signal drs_led_counter : std_logic_vector(20 downto 0);
type type_drs_led_state is (led_idle, led_on, led_off);
signal drs_led_state : type_drs_led_state;
-- DRS Start/enable
signal o_drs_enable : std_logic;
signal o_drs_write : std_logic;
-- Internal DRS shift registers
signal o_drs_srin : std_logic;
signal o_drs_srclk : std_logic;
signal o_drs_rsrload : std_logic;
signal i_drs_srout : std_logic;
signal i_drs_wsrout : std_logic;
subtype type_sr_count is integer range 0 to 1024;
signal drs_sr_count : type_sr_count;
signal drs_sr_reg : std_logic_vector(7 downto 0);
-- DRS address
signal o_drs_addr : std_logic_vector(3 downto 0);
-- PLL refence clock signal
signal drs_refclk : std_logic;
signal o_drs_refclk : std_logic;
signal drs_refclk_counter : std_logic_vector(16 downto 0);
signal i_drs_plllck : std_logic;
signal i_drs_dtap : std_logic;
-- 132/264 MHz calibration signal output
signal o_drs_tcalib_sig : std_logic;
-- internal amplitude calibration via input multiplexers
signal o_drs_aswitches : std_logic;
-- power signal for chip test board
signal o_drs_on : std_logic;
-- Control registers
signal drs_ctl_start_trig : std_logic;
signal drs_ctl_reinit_trig : std_logic; -- 1 sets drs_reinit_reqest to '1'
signal drs_ctl_soft_trig : std_logic;
signal drs_ctl_eeprom_write_trig: std_logic;
signal drs_ctl_eeprom_read_trig: std_logic;
signal drs_ctl_autostart : std_logic;
signal drs_ctl_dmode : std_logic;
signal drs_ctl_dactive : std_logic;
signal drs_ctl_adc_active : std_logic;
signal drs_ctl_acalib : std_logic;
signal drs_ctl_led_red : std_logic;
signal drs_ctl_tcal_en : std_logic;
signal drs_ctl_tcal_source : std_logic;
signal drs_ctl_refclk_source : std_logic;
type type_drs_dac_val_arr is array (7 downto 0) of std_logic_vector(15 downto 0);
signal drs_ctl_dac_arr : type_drs_dac_val_arr;
signal drs_ctl_first_chn : std_logic_vector(3 downto 0);
signal drs_ctl_last_chn : std_logic_vector(3 downto 0);
signal drs_ctl_config : std_logic_vector(7 downto 0);
signal drs_ctl_chn_config : std_logic_vector(7 downto 0);
signal drs_ctl_sampling_freq : std_logic_vector(15 downto 0);
signal drs_ctl_transp_mode : std_logic;
signal drs_ctl_standby_mode : std_logic;
signal drs_ctl_enable_trigger : std_logic;
signal drs_ctl_trigger_config : std_logic_vector(15 downto 0);
signal drs_ctl_neg_trigger : std_logic;
signal drs_ctl_readout_mode : std_logic;
signal drs_ctl_delay_sel : std_logic_vector(7 downto 0);
-- Status registers
signal drs_stat_busy : std_logic;
signal drs_eeprom_busy : std_logic;
signal drs_stat_stop_cell : std_logic_vector(9 downto 0);
signal drs_stat_stop_wsr : std_logic_vector(7 downto 0);
signal drs_temperature : std_logic_vector(15 downto 0);
signal drs_trigger_bus : std_logic_vector(15 downto 0);
signal drs_serial_number : std_logic_vector(15 downto 0);
signal svn_revision : std_logic_vector(15 downto 0);
-- Misc. internal signals
signal drs_reinit_request : std_logic;
signal drs_old_readout_mode : std_logic;
-- Trigger signals
signal drs_trigger : std_logic;
signal drs_soft_trig : std_logic;
signal drs_trigger_syn : std_logic;
signal drs_write_set : std_logic;
signal drs_trig_ff : std_logic;
signal drs_write_ff : std_logic;
signal drs_hard_inp : std_logic_vector(4 downto 0);
signal drs_hard_or : std_logic;
signal drs_hard_and : std_logic;
signal drs_hard_trig : std_logic;
signal drs_arm_trig : std_logic;
signal drs_trg_delay : std_logic_vector(2047 downto 0);
-- Tell P&R to not optimize away the drs_trg_delay array
attribute keep : string;
attribute keep of drs_trg_delay : signal is "true";
-- Serial bus internal signals
type type_serial_bus_state is (idle, wait_serdes, eeprom_read, eeprom_write, done);
signal serial_bus_state : type_serial_bus_state;
subtype type_serial_count is integer range 0 to 200;
signal serial_count : type_serial_count;
signal serial_ret_addr : type_serial_count;
signal serial_start_flag1 : std_logic;
signal serial_start_flag2 : std_logic;
type type_serdes_state is (idle, busy, busy_temp);
signal serdes_state : type_serdes_state;
subtype type_serdes_clk is integer range 0 to 10;
signal serdes_clk : type_serdes_clk;
signal serdes_speed : type_serdes_clk;
subtype type_serdes_count is integer range 0 to 100;
signal serdes_count : type_serdes_count;
subtype type_serdes_bit_count_m1 is integer range 0 to 32;
signal serdes_bit_count_m1 : type_serdes_bit_count_m1;
signal serdes_bit_no : type_serdes_bit_count_m1;
signal serdes_trig : std_logic;
signal serdes_trig_temp : std_logic;
signal serdes_wdata : std_logic_vector(31 downto 0);
signal serdes_rdata : std_logic_vector(31 downto 0);
type type_drs_dac_reg is array (7 downto 0) of std_logic_vector(15 downto 0);
signal drs_dac_reg : type_drs_dac_reg;
signal drs_dac_newval_flag : std_logic_vector(7 downto 0);
subtype type_dac_bit_count is integer range 0 to 31;
signal temp : std_logic_vector(15 downto 0);
signal temp_timer : std_logic_vector(25 downto 0); -- once per second
signal temp_cmd : std_logic_vector(7 downto 0);
subtype type_eeprom_count is integer range 0 to 100;
signal drs_eeprom_write_trig : std_logic;
signal drs_eeprom_read_trig : std_logic;
signal drs_eeprom_sector : std_logic_vector(15 downto 0);
signal drs_eeprom_page : std_logic_vector(7 downto 0);
signal drs_eeprom_byte : std_logic_vector(7 downto 0);
signal drs_eeprom_cmd : std_logic_vector(59 downto 0);
-- PMC IO pin control signals
signal pmc_clk_i : std_logic_vector(P_IO_PMC_USR'range); -- input FF clock
signal pmc_ce_i : std_logic_vector(P_IO_PMC_USR'range); -- input FF clock enable
signal pmc_clr_i : std_logic_vector(P_IO_PMC_USR'range); -- input FF async clear
... 1459 more lines ...
|
186
|
Thu Nov 1 20:08:33 2012 |
hongwei yang | DRS4 firmware | Hi,
We are using drs4 board, but oscilloscope app will somehow stop to work if we config trigger into "or and", When I look into the drs4 firmware file drs4_eval3_app.vhd, I couldn't find the trigger_config value assignment which is mentioned at(#7 offset 0x1E from 31 downto 16) in manual_version 4.
could you help me find this trigger_config access point? Or is there any drs4_eval4_app.vhd missing in the source files?
thanks
Hongwei |
185
|
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? |
184
|
Fri Oct 12 14:09:37 2012 |
Stefan Ritt | DRS abbreviation |
Moritz von Witzleben wrote: |
Hello,
what is the abbreviation of DRS?
Thanks and kind Regards,
Moritz
|
Domino Ring Sampler. |
183
|
Fri Oct 12 14:06:04 2012 |
Moritz von Witzleben | DRS abbreviation | Hello,
what is the abbreviation of DRS?
Thanks and kind Regards,
Moritz |
182
|
Thu Oct 4 21:07:27 2012 |
Zach Miller | DRS5 |
Stefan Ritt wrote: |
Zach Miller wrote: |
Hi,
Our group had previously heard that a "DRS-5.0" might be on the horizon and that it may have ethernet capabilities as well as 16-input channels (we heard this when ordering the DRS-4). Is this still in the works and accurate information? If so, is there a rough estimate to the "release date?"
Thanks for your time,
Zach Miller
|
You mix up two things: The DRS5 chip is a new device with improved samling speed (10 GSPS) and lower dead time. This chip might come in 2-3 years. The 16-input board you mentioned is a DAQ board based on the DRS4 chip. This board well be operational beginning of 2013 as a prototype. It is not clear however at this point in which way this board will be made available for public. Maybe we will license this to industry. The design is however pretty much defined: 16 channels with gain 0.1-100, 1 GHz Bandwidth, Gigabit Ethernet output, and multi-board capabilities. Trigger on each channel with logical combinations. 80 MSPS continuous sampling (in addition to the DRS4 sampling). Each channel can be biased 0-210 V for SiPMT or APD power. A 19" 3 HE crate will host 16 boards with 256 channels.
/Stefan
|
Thanks, Stefan. That was the information we were looking for.
Cheers.
-Zach |
181
|
Thu Oct 4 20:59:18 2012 |
Stefan Ritt | DRS5 |
Zach Miller wrote: |
Hi,
Our group had previously heard that a "DRS-5.0" might be on the horizon and that it may have ethernet capabilities as well as 16-input channels (we heard this when ordering the DRS-4). Is this still in the works and accurate information? If so, is there a rough estimate to the "release date?"
Thanks for your time,
Zach Miller
|
You mix up two things: The DRS5 chip is a new device with improved samling speed (10 GSPS) and lower dead time. This chip might come in 2-3 years. The 16-input board you mentioned is a DAQ board based on the DRS4 chip. This board well be operational beginning of 2013 as a prototype. It is not clear however at this point in which way this board will be made available for public. Maybe we will license this to industry. The design is however pretty much defined: 16 channels with gain 0.1-100, 1 GHz Bandwidth, Gigabit Ethernet output, and multi-board capabilities. Trigger on each channel with logical combinations. 80 MSPS continuous sampling (in addition to the DRS4 sampling). Each channel can be biased 0-210 V for SiPMT or APD power. A 19" 3 HE crate will host 16 boards with 256 channels.
/Stefan |
180
|
Thu Oct 4 20:50:36 2012 |
Zach Miller | DRS5 | Hi,
Our group had previously heard that a "DRS-5.0" might be on the horizon and that it may have ethernet capabilities as well as 16-input channels (we heard this when ordering the DRS-4). Is this still in the works and accurate information? If so, is there a rough estimate to the "release date?"
Thanks for your time,
Zach Miller |
179
|
Wed Aug 29 16:57:49 2012 |
Zach Miller | DRS-4.0.0 DOScreen.cpp |
Stefan Ritt wrote: |
Zach Miller wrote: |
Stefan Ritt wrote: |
Zach Miller wrote: |
Hi,
I found an old thread regarding a fix for DOScreen.cpp for DRS-3.1.0, that fixes an "ambiguous overload problem." Currently when I attempt to build the drs-4.0.0, I get this similar error:
src/DOScreen.cpp:332:39: error: call of overloaded ‘Append(int)’ is ambiguous
This section of code is different than what the previous thread was correcting, and though I attempted to apply the logic of the old thread, I haven't fixed this yet.
The following is the code for that section:
-----
329 for (int i=0 ; i<5 ; i++)
330 if (tc & (1<<(i+8))) {
331 if (i < 4)
332 wxst1.Append(wxT('1'+i));
333 else
334 wxst1.Append(wxT('E'));
335 wxst1.Append(wxT('&'));
336 }
337 if (wxst1.Length() > 0)
338 wxst1 = wxst1.Left(wxst1.Length()-1);
339 wxst1.Append(wxT(')'));
------
I've attempted a few fixes, but unfortunately, my understanding of the code is not great, and I haven't managed to fix this yet. Any help would be appreciated.
Thanks,
Zach Miller
|
Just put (char) in front of wxT(...), like
if (tc > 0) {
wxString wxst1, wxst2;
wxst1.Append((char)wxT('('));
for (int i=0 ; i<5 ; i++)
if (tc & (1<<i)) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('|'));
}
for (int i=0 ; i<5 ; i++)
if (tc & (1<<(i+8))) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('&'));
}
if (wxst1.Length() > 0)
wxst1 = wxst1.Left(wxst1.Length()-1);
wxst1.Append((char) wxT(')'));
|
Hi Stefan,
Thanks for the response. I have tried that and it fixes all the lines except the ones that have:
wxst1.Append((char) (wxT('1'+i)));
Those lines still don't compile for me. I've also tried: wxst1.Append((char) (wxT('1'+(char)i))); and wxst1.Append((char) (wxT((char)'1'+i))); as well as a few other combinations of (char) and Append.
I get the same error of: "Call of overloaded "Append(int)" is ambiguous."
Any other help would be greatly appreciated. Thanks!
-Zach
|
wxst1.Append((char) (wxT((char)('1'+i)))); maybe ???
|
Aha!
wxst1.Append((char) (wxT('1'+i)));
That one actually works as you initially thought, but you my editor was being picky of (char)wxt... instead of (char) (wxt....). For some reason, it has to have the extra set of parentheses around wxt(). Thank You! |
178
|
Wed Aug 29 16:45:36 2012 |
Stefan Ritt | DRS-4.0.0 DOScreen.cpp |
Zach Miller wrote: |
Stefan Ritt wrote: |
Zach Miller wrote: |
Hi,
I found an old thread regarding a fix for DOScreen.cpp for DRS-3.1.0, that fixes an "ambiguous overload problem." Currently when I attempt to build the drs-4.0.0, I get this similar error:
src/DOScreen.cpp:332:39: error: call of overloaded ‘Append(int)’ is ambiguous
This section of code is different than what the previous thread was correcting, and though I attempted to apply the logic of the old thread, I haven't fixed this yet.
The following is the code for that section:
-----
329 for (int i=0 ; i<5 ; i++)
330 if (tc & (1<<(i+8))) {
331 if (i < 4)
332 wxst1.Append(wxT('1'+i));
333 else
334 wxst1.Append(wxT('E'));
335 wxst1.Append(wxT('&'));
336 }
337 if (wxst1.Length() > 0)
338 wxst1 = wxst1.Left(wxst1.Length()-1);
339 wxst1.Append(wxT(')'));
------
I've attempted a few fixes, but unfortunately, my understanding of the code is not great, and I haven't managed to fix this yet. Any help would be appreciated.
Thanks,
Zach Miller
|
Just put (char) in front of wxT(...), like
if (tc > 0) {
wxString wxst1, wxst2;
wxst1.Append((char)wxT('('));
for (int i=0 ; i<5 ; i++)
if (tc & (1<<i)) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('|'));
}
for (int i=0 ; i<5 ; i++)
if (tc & (1<<(i+8))) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('&'));
}
if (wxst1.Length() > 0)
wxst1 = wxst1.Left(wxst1.Length()-1);
wxst1.Append((char) wxT(')'));
|
Hi Stefan,
Thanks for the response. I have tried that and it fixes all the lines except the ones that have:
wxst1.Append((char) (wxT('1'+i)));
Those lines still don't compile for me. I've also tried: wxst1.Append((char) (wxT('1'+(char)i))); and wxst1.Append((char) (wxT((char)'1'+i))); as well as a few other combinations of (char) and Append.
I get the same error of: "Call of overloaded "Append(int)" is ambiguous."
Any other help would be greatly appreciated. Thanks!
-Zach
|
wxst1.Append((char) (wxT((char)('1'+i)))); maybe ??? |
177
|
Wed Aug 29 16:42:42 2012 |
Zach Miller | DRS-4.0.0 DOScreen.cpp |
Stefan Ritt wrote: |
Zach Miller wrote: |
Hi,
I found an old thread regarding a fix for DOScreen.cpp for DRS-3.1.0, that fixes an "ambiguous overload problem." Currently when I attempt to build the drs-4.0.0, I get this similar error:
src/DOScreen.cpp:332:39: error: call of overloaded ‘Append(int)’ is ambiguous
This section of code is different than what the previous thread was correcting, and though I attempted to apply the logic of the old thread, I haven't fixed this yet.
The following is the code for that section:
-----
329 for (int i=0 ; i<5 ; i++)
330 if (tc & (1<<(i+8))) {
331 if (i < 4)
332 wxst1.Append(wxT('1'+i));
333 else
334 wxst1.Append(wxT('E'));
335 wxst1.Append(wxT('&'));
336 }
337 if (wxst1.Length() > 0)
338 wxst1 = wxst1.Left(wxst1.Length()-1);
339 wxst1.Append(wxT(')'));
------
I've attempted a few fixes, but unfortunately, my understanding of the code is not great, and I haven't managed to fix this yet. Any help would be appreciated.
Thanks,
Zach Miller
|
Just put (char) in front of wxT(...), like
if (tc > 0) {
wxString wxst1, wxst2;
wxst1.Append((char)wxT('('));
for (int i=0 ; i<5 ; i++)
if (tc & (1<<i)) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('|'));
}
for (int i=0 ; i<5 ; i++)
if (tc & (1<<(i+8))) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('&'));
}
if (wxst1.Length() > 0)
wxst1 = wxst1.Left(wxst1.Length()-1);
wxst1.Append((char) wxT(')'));
|
Hi Stefan,
Thanks for the response. I have tried that and it fixes all the lines except the ones that have:
wxst1.Append((char) (wxT('1'+i)));
Those lines still don't compile for me. I've also tried: wxst1.Append((char) (wxT('1'+(char)i))); and wxst1.Append((char) (wxT((char)'1'+i))); as well as a few other combinations of (char) and Append.
I get the same error of: "Call of overloaded "Append(int)" is ambiguous."
Any other help would be greatly appreciated. Thanks!
-Zach |
176
|
Wed Aug 29 10:52:44 2012 |
Stefan Ritt | DRS-4.0.0 DOScreen.cpp |
Zach Miller wrote: |
Hi,
I found an old thread regarding a fix for DOScreen.cpp for DRS-3.1.0, that fixes an "ambiguous overload problem." Currently when I attempt to build the drs-4.0.0, I get this similar error:
src/DOScreen.cpp:332:39: error: call of overloaded ‘Append(int)’ is ambiguous
This section of code is different than what the previous thread was correcting, and though I attempted to apply the logic of the old thread, I haven't fixed this yet.
The following is the code for that section:
-----
329 for (int i=0 ; i<5 ; i++)
330 if (tc & (1<<(i+8))) {
331 if (i < 4)
332 wxst1.Append(wxT('1'+i));
333 else
334 wxst1.Append(wxT('E'));
335 wxst1.Append(wxT('&'));
336 }
337 if (wxst1.Length() > 0)
338 wxst1 = wxst1.Left(wxst1.Length()-1);
339 wxst1.Append(wxT(')'));
------
I've attempted a few fixes, but unfortunately, my understanding of the code is not great, and I haven't managed to fix this yet. Any help would be appreciated.
Thanks,
Zach Miller
|
Just put (char) in front of wxT(...), like
if (tc > 0) {
wxString wxst1, wxst2;
wxst1.Append((char)wxT('('));
for (int i=0 ; i<5 ; i++)
if (tc & (1<<i)) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('|'));
}
for (int i=0 ; i<5 ; i++)
if (tc & (1<<(i+8))) {
if (i < 4)
wxst1.Append((char) (wxT('1'+i)));
else
wxst1.Append((char) wxT('E'));
wxst1.Append((char) wxT('&'));
}
if (wxst1.Length() > 0)
wxst1 = wxst1.Left(wxst1.Length()-1);
wxst1.Append((char) wxT(')'));
|
175
|
Tue Aug 28 17:52:45 2012 |
Zach Miller | DRS-4.0.0 DOScreen.cpp | Hi,
I found an old thread regarding a fix for DOScreen.cpp for DRS-3.1.0, that fixes an "ambiguous overload problem." Currently when I attempt to build the drs-4.0.0, I get this similar error:
src/DOScreen.cpp:332:39: error: call of overloaded ‘Append(int)’ is ambiguous
This section of code is different than what the previous thread was correcting, and though I attempted to apply the logic of the old thread, I haven't fixed this yet.
The following is the code for that section:
-----
329 for (int i=0 ; i<5 ; i++)
330 if (tc & (1<<(i+8))) {
331 if (i < 4)
332 wxst1.Append(wxT('1'+i));
333 else
334 wxst1.Append(wxT('E'));
335 wxst1.Append(wxT('&'));
336 }
337 if (wxst1.Length() > 0)
338 wxst1 = wxst1.Left(wxst1.Length()-1);
339 wxst1.Append(wxT(')'));
------
I've attempted a few fixes, but unfortunately, my understanding of the code is not great, and I haven't managed to fix this yet. Any help would be appreciated.
Thanks,
Zach Miller |
174
|
Mon Aug 6 02:44:00 2012 |
Stefan Ritt | Calculation of loop filter parameters (R,C1and C1) for 1 GHz |
Mayank S. Rajguru wrote: |
Hi,
we are planning to use the DRS4 in our board for 1 GHz sampling and digitization.
I have seen in the data sheet that "For the PLL to work, an external loop filter is required. This filter ensures quick locking and stable operation at the desired sampling frequency".
What formula do you use to calculate the values of R, C1 and C2?
Can we use the same given value for different frequencies?
Thanks,
Mayak
|
I never worked out an exact formula for the parameters. It also depends if you want a fast locking time, or a low phase jitter of the PLL. A good starting point are the values from the evaluation board:
R = 130 Ohm
C1 = 4.7 nF
C2 = 1 uF
They should work from 800 MHz to 5 GHz.
- Stefan |
173
|
Wed Aug 1 17:42:32 2012 |
Mayank S. Rajguru | Calculation of loop filter parameters (R,C1and C1) for 1 GHz | Hi,
we are planning to use the DRS4 in our board for 1 GHz sampling and digitization.
I have seen in the data sheet that "For the PLL to work, an external loop filter is required. This filter ensures quick locking and stable operation at the desired sampling frequency".
What formula do you use to calculate the values of R, C1 and C2?
Can we use the same given value for different frequencies?
Thanks,
Mayak |
172
|
Wed Jul 11 10:04:51 2012 |
Ivan Petrov | Problem compiling drs_exam.cpp on windows |
Stefan Ritt wrote: |
Ivan Petrov wrote: |
Hello again. I have not got evaluation board yet, but already faced some difficulties:) I'm trying to compile drs_exam.cpp on Windows 7 using dev-c++ with imagelib-2 and WxWindows 2.4.2 DevPaks installed, but nothing works. Compile log is attached. Honestly, I'm not very familiar with c++, so any suggestions will be helpful. Thank you.
|
I have no experience with dev-c++, so I cannot be of help here. The supported systems are Linux and Windows with MS Visual C++. But it looks like the problems are related to compiling wxWidgets, which actually you do NOT need for drs_exam.cpp. The wxWidgets library is only needed for the DRSOsc application. If you want to compile it anyhow, first learn how to compile standard WxWidgets applications from
http://www.wxwidgets.org/docs/tutorials/devcpp.htm
Best regards,
Stefan
|
Ok, this was my bad, I added some unnecessary files to project. Drs_exam compiles well with ms vc++. Thanks! |
171
|
Tue Jul 10 13:15:00 2012 |
Stefan Ritt | Problem compiling drs_exam.cpp on windows |
Ivan Petrov wrote: |
Hello again. I have not got evaluation board yet, but already faced some difficulties:) I'm trying to compile drs_exam.cpp on Windows 7 using dev-c++ with imagelib-2 and WxWindows 2.4.2 DevPaks installed, but nothing works. Compile log is attached. Honestly, I'm not very familiar with c++, so any suggestions will be helpful. Thank you.
|
I have no experience with dev-c++, so I cannot be of help here. The supported systems are Linux and Windows with MS Visual C++. But it looks like the problems are related to compiling wxWidgets, which actually you do NOT need for drs_exam.cpp. The wxWidgets library is only needed for the DRSOsc application. If you want to compile it anyhow, first learn how to compile standard WxWidgets applications from
http://www.wxwidgets.org/docs/tutorials/devcpp.htm
Best regards,
Stefan |
170
|
Mon Jul 9 14:14:48 2012 |
Ivan Petrov | Problem compiling drs_exam.cpp on windows | Hello again. I have not got evaluation board yet, but already faced some difficulties:) I'm trying to compile drs_exam.cpp on Windows 7 using dev-c++ with imagelib-2 and WxWindows 2.4.2 DevPaks installed, but nothing works. Compile log is attached. Honestly, I'm not very familiar with c++, so any suggestions will be helpful. Thank you. |
Attachment 1: compile_log.txt
|
Compiler: Default compiler
Building Makefile: "G:\devcpp\Makefile.win"
Executing make...
make.exe -f "G:\devcpp\Makefile.win" all
g++.exe -c AboutDialog.cpp -o AboutDialog.o -I"C:/Dev-Cpp/lib/gcc/mingw32/3.4.2/include" -I"C:/Dev-Cpp/include/c++/3.4.2/backward" -I"C:/Dev-Cpp/include/c++/3.4.2/mingw32" -I"C:/Dev-Cpp/include/c++/3.4.2" -I"C:/Dev-Cpp/include"
In file included from C:/Dev-Cpp/include/wx/wx.h:15,
from DRSOscInc.h:7,
from AboutDialog.cpp:7:
C:/Dev-Cpp/include/wx/defs.h:179: error: redeclaration of C++ built-in type `int'
In file included from C:/Dev-Cpp/include/wx/memory.h:20,
from C:/Dev-Cpp/include/wx/object.h:25,
from C:/Dev-Cpp/include/wx/wx.h:16,
from DRSOscInc.h:7,
from AboutDialog.cpp:7:
C:/Dev-Cpp/include/wx/string.h:160:4: #error "Please define string case-insensitive compare for your OS/compiler"
In file included from DRSOscInc.h:12,
from AboutDialog.cpp:7:
DRSOsc.h:38:26: wx/hyperlink.h: No such file or directory
In file included from DRSOscInc.h:12,
from AboutDialog.cpp:7:
DRSOsc.h:532: error: ISO C++ forbids declaration of `wxHyperlinkCtrl' with no type
DRSOsc.h:532: error: expected `;' before '*' token
make.exe: *** [AboutDialog.o] Error 1
Execution terminated
|
169
|
Mon Jun 25 14:21:13 2012 |
Stefan Ritt | triger for measuring time between pulses in channels |
Andrey Kuznetsov wrote: |
Stefan Ritt wrote: |
On the evaluation board, yes. This board is not optimized for high readout rate. If you do your own electronics, like GBit Ethernet, you could be much faster.
|
What is the readout rate via GBit Ethernet that you have achieved?
Where is the bottleneck in ethernet?
What is the proposed scheme by which the GBit Ethernet will be implemented, will the DRS4 Eval Board have to wait for the computer to respond before sending the data (wouldn't this make the readout much slower?), or will the DRS4 Eval Board keep sending the data to the computer?
|
With GBit Ethernet you get close to 100 MB/sec, which is the maximal line speed. The protocol to be implemented will achieve that rate. What one usually does is to send events in large blocks upon request from the PC. The trick is to do the request in a clever way, like using a high water mark on the receiving event buffer. So as long as the PC can digest the data quickly enough, the board just keeps sending, which means no overhead.
|
168
|
Sat Jun 23 00:29:52 2012 |
Andrey Kuznetsov | triger for measuring time between pulses in channels |
Stefan Ritt wrote: |
On the evaluation board, yes. This board is not optimized for high readout rate. If you do your own electronics, like GBit Ethernet, you could be much faster.
|
What is the readout rate via GBit Ethernet that you have achieved?
Where is the bottleneck in ethernet?
What is the proposed scheme by which the GBit Ethernet will be implemented, will the DRS4 Eval Board have to wait for the computer to respond before sending the data (wouldn't this make the readout much slower?), or will the DRS4 Eval Board keep sending the data to the computer? |
|