[Discuss-gnuradio] problem with simple test of USRP2+WBX
Hello: I'm stuck, and I need some help. I'm running GNU Radio 3.3.0 on openSUSE 11.2. I have two USRP2 boards, each with a WBX daughterboard, connected to two Intel PRO/1000 GT NICs, on eth1 and eth2. I'm using the txrx_wbx_raw_eth_20100608.bin firmware, not the from-the-factory firmware. I made a simple flowgraph which connects an FFT window to a USRP2 Source, tuned to 900 MHz at a sample rate of 3.125 MHz (decimation factor 32). I input a 901 MHz sine from an HP signal generator into the TX/RX connector on the WBX daughterboard. When I run the flowgraph with the USRP2 Source set to eth1 (for the first USRP2), it runs fine, and I see a nice clear tall spike in the FFT at 1 MHz. However, when I set the USRP2 Source to eth2 (for the second USRP2) and re-run the flowgraph, I get a spike at 901 MHz that is barely noticeable and greatly attenuated. What's going wrong here? I used that second USRP2 a few weeks ago with a different daughterboard and it ran fine, so I don't think that USRP2 is bad. Is there something wrong with the WBX daughterboard? Am I doing something wrong in GRC? Any ideas? Any help would be GREATLY appreciated. Thanks a lot!! Steve McMahon ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Carrier frequency mismatching?
I use USRP sink and source and set frequency with 2.6 GHz When I run a flow graph, I see like below: == A: Flex 2400 Tx MIMO B r.baseband_frequency = 260400.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False A: Flex 2400 Rx MIMO B r.baseband_frequency = 259600.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False === Both of baseband frequency are near 2.6 G, but they do not match up Can it be problmeatic for communicating each other? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Carrier frequency mismatching?
On Fri, Nov 19, 2010 at 05:17:53PM +0900, Songsong Gee wrote: I use USRP sink and source and set frequency with 2.6 GHz When I run a flow graph, I see like below: == A: Flex 2400 Tx MIMO B r.baseband_frequency = 260400.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False A: Flex 2400 Rx MIMO B r.baseband_frequency = 259600.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False === Both of baseband frequency are near 2.6 G, but they do not match up Can it be problmeatic for communicating each other? The actual frequencies on the air will be 2.6 G +/- oscillator tolerance. In the Tx case, the LO is set 4MHz higher than the target, and the DUC is used to adjust the baseband -4MHz. In the Rx case the LO is set 4MHz lower than the target, and the DDC is used to move the digitized IF signal 4MHz lower prior to decimating. This is easy to confirm with a siggen and a spectrum analyzer. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Carrier frequency mismatching?
I understan what you told me... Then... however, why they have same sign? One is for up conversion, and the other is for down conversion they might have opposite signs. one is MINUS 4 MHz, and the other is PLUS 4 MHz and one another... They meet in frequency by DXC, but, in my opinion, they are basically different in baseband frequency... I really really cannot understand this magic :( 2010/11/19 Eric Blossom e...@comsec.com On Fri, Nov 19, 2010 at 05:17:53PM +0900, Songsong Gee wrote: I use USRP sink and source and set frequency with 2.6 GHz When I run a flow graph, I see like below: == A: Flex 2400 Tx MIMO B r.baseband_frequency = 260400.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False A: Flex 2400 Rx MIMO B r.baseband_frequency = 259600.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False === Both of baseband frequency are near 2.6 G, but they do not match up Can it be problmeatic for communicating each other? The actual frequencies on the air will be 2.6 G +/- oscillator tolerance. In the Tx case, the LO is set 4MHz higher than the target, and the DUC is used to adjust the baseband -4MHz. In the Rx case the LO is set 4MHz lower than the target, and the DDC is used to move the digitized IF signal 4MHz lower prior to decimating. This is easy to confirm with a siggen and a spectrum analyzer. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] problem with simple test of USRP2+WBX
On 11/19/2010 03:13 AM, Steve Mcmahon wrote: Hello: I'm stuck, and I need some help. I'm running GNU Radio 3.3.0 on openSUSE 11.2. I have two USRP2 boards, each with a WBX daughterboard, connected to two Intel PRO/1000 GT NICs, on eth1 and eth2. I'm using the txrx_wbx_raw_eth_20100608.bin firmware, not the from-the-factory firmware. I made a simple flowgraph which connects an FFT window to a USRP2 Source, tuned to 900 MHz at a sample rate of 3.125 MHz (decimation factor 32). I input a 901 MHz sine from an HP signal generator into the TX/RX connector on the WBX daughterboard. When I run the flowgraph with the USRP2 Source set to eth1 (for the first USRP2), it runs fine, and I see a nice clear tall spike in the FFT at 1 MHz. However, when I set the USRP2 Source to eth2 (for the second USRP2) and re-run the flowgraph, I get a spike at 901 MHz that is barely noticeable and greatly attenuated. What's going wrong here? I used that second USRP2 a few weeks ago with a different daughterboard and it ran fine, so I don't think that USRP2 is bad. Is there something wrong with the WBX daughterboard? Am I doing something wrong in GRC? Any ideas? Any help would be GREATLY appreciated. Thanks a lot!! Steve McMahon What power level did you use for the signal generator? The GaAs MMIC LNAs on these boards don't like high power input, and the gate insulator will often go phhhttt! if you input more than -15dBm for any length of time. -- Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] adjustable clock oscillator?
Hello, I want to clarify one thing that is, if i replace the VCTCXO osc 64Mhz 3.3 V +/- 50ppm with 64Mhz 3.3 V +/- 2ppm, in USRP1, will it affect basic operations of usrp1 , or will improve on account of frequency stability, ass 10Khz frequency offset is inherent feature of USRP1, also wants to confirm that if main osc frequency been change ass Matt told to less like 52 Mhz with OpenBTS did, do we need to do some changes with USSRP1 firmware or need to do changes only with our custom application /signal processing blocks ? Thanks Kind Regards, marten ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Carrier frequency mismatching?
On Fri, Nov 19, 2010 at 09:19:04PM +0900, Songsong Gee wrote: I understan what you told me... Then... however, why they have same sign? One is for up conversion, and the other is for down conversion they might have opposite signs. one is MINUS 4 MHz, and the other is PLUS 4 MHz and one another... They meet in frequency by DXC, but, in my opinion, they are basically different in baseband frequency... I really really cannot understand this magic :( Try drawing a picture... Eric 2010/11/19 Eric Blossom e...@comsec.com On Fri, Nov 19, 2010 at 05:17:53PM +0900, Songsong Gee wrote: I use USRP sink and source and set frequency with 2.6 GHz When I run a flow graph, I see like below: == A: Flex 2400 Tx MIMO B r.baseband_frequency = 260400.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False A: Flex 2400 Rx MIMO B r.baseband_frequency = 259600.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False === Both of baseband frequency are near 2.6 G, but they do not match up Can it be problmeatic for communicating each other? The actual frequencies on the air will be 2.6 G +/- oscillator tolerance. In the Tx case, the LO is set 4MHz higher than the target, and the DUC is used to adjust the baseband -4MHz. In the Rx case the LO is set 4MHz lower than the target, and the DDC is used to move the digitized IF signal 4MHz lower prior to decimating. This is easy to confirm with a siggen and a spectrum analyzer. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] gnuradio-examples/python/digital/tunnel.py issue
I seem to be having trouble with gnuradio-examples/python/digital/tunnel.py on a fedora 13 box complaining with an eng_notation error about any value I put in (eg 10M, 10e6, 1000) for --rx-freq or --tx-freq where the same exact script (md5 matches) on an ubuntu box works fine. This is the latest gnuradio git on track origin/next. Any thoughts how I might fix this? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP1 question
Hi , If any one can tell me in USRP1 ver4.5, how many layer PCB used , i examined it and it looks like it is double sided PCB, or it has multiple layers,like 6 layers? Thanks in advance for confirmation. Kind Regards, On Fri, Nov 19, 2010 at 2:31 PM, Eric Blossom e...@comsec.com wrote: On Fri, Nov 19, 2010 at 05:17:53PM +0900, Songsong Gee wrote: I use USRP sink and source and set frequency with 2.6 GHz When I run a flow graph, I see like below: == A: Flex 2400 Tx MIMO B r.baseband_frequency = 260400.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False A: Flex 2400 Rx MIMO B r.baseband_frequency = 259600.0 r.dxc_frequency = -400.0 r.residual_frequency = 0.0 r.inverted = False === Both of baseband frequency are near 2.6 G, but they do not match up Can it be problmeatic for communicating each other? The actual frequencies on the air will be 2.6 G +/- oscillator tolerance. In the Tx case, the LO is set 4MHz higher than the target, and the DUC is used to adjust the baseband -4MHz. In the Rx case the LO is set 4MHz lower than the target, and the DDC is used to move the digitized IF signal 4MHz lower prior to decimating. This is easy to confirm with a siggen and a spectrum analyzer. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Debug the UHD
p { margin-bottom: 0.08in; }
Hi all,
I need to change some parts of the code
in the UHD driver. I am wondering is it possible for me to debug the
UHD driver code to find out what is wrong in my code. The problem
for me is that I don't know how to change the Makefile of the UHD to
enable the debug option. Currently, I can only debug into the hpp
file and can not get into the source code.
Thanks!
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Packet handling blocks
Hi all, I'm playing with gnuradio and am trying to create a simple example where I take some data, do a virtual transmission, and then check I have the same data at the receiving end. I've got it successfully working with the following string of blocks: vector_source_b, dbpsk_mod, channel_model, dpsk_demod, vector_sink_b It works but I have to do some messing round in python beforehand and afterwards adding on access codes and headers and putting some buffers before and after the packet. I expect that blocks already exist to do most of this stuff but I haven't managed to find them. I don't have any background in this kind of stuff so I might be going about this in completely the wrong way. I also don't have a good idea of what exactly gnuradio's scope is and what I should expect it to be able to do. The following is the list of the steps I would like my simple example to do, and what I have or have not been able to find in gnuradio. 1) Start of with some raw data. There are lots of source blocks to choose from, no problem here. 2) Parcel it into packets. gr_message_sink? (puts it into a message queue, all in one message) 3) Add access codes and headers to packets. I couldn't find anything to do this. Seems surprising. 4) Combine packets into a stream to be transmitted. Can't find anything. 5) Modulation. Plenty of options. 6) Transmit stream. gr_channel_model (because I don't have anything real) 7) Demodulation. Plenty of options. 8) Receive stream, split out packets and remove access codes and headers. gr_correlate_access_code_bb/gr_framer_sink_1 (to queue) OR gr_packet_sink (to queue) 9) Combine packets to get original raw data. Can't find anything. If anyone could tell me of any blocks I've overlooked, or how I should be going about it differently I'd appreciate it. Cheers, Ben ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
