RE: [Discuss-gnuradio] Unable to tune Tx or Rx with XCVR2450 on USRP2
Hi Matt Apologies is you got a similar reply about 10 minutes ago, but the webmail logged me out whilst I was trying to send it and it didn't appear in my sent items when I logged back in. You should know that we only spec the boards from 2.4 to 2.5 GHz and 4.9 to 5.9 GHz. When we test XCVRs before shipping, we make sure that they will lock from 2.35 to 2.55 and 4.85 to 5.95 so that there is 50 MHz of margin in case of variation due to temperature or other factors. But there is no reason to think that they would lock all the way to the edges of the ranges you list since those are well outside of what we (and the chip manufacturer) specify. Thanks. I had thought the low and high limits in the source code were the spec'd ones. Based on your above comment, combinations A, C, and D would seem to be within spec, though I didn't try all the stepped frequencies for case C or D, but just a few (e.g. 2.4G, 2.462G, 5G). Combination ID | USRP2 Serial | XCVR2450 Serial | Working A | 933 | 990 | YES B | 933 | 988 | NO C | 1159 | 990 | YES D | 1159 | 988 | YES In my testing today, an additional problem was also noticed, as below. To simplify testing, you only need to run either RX or TX since they both share the same synthesizer on the XCVR2450. Thanks. I will do this in future. Normally I would tell you to send the parts back for me to check them, but since you are in AU, it would be expensive and take a long time. Instead, we may be able to debug this if you have an oscilloscope. If so, can you look at the signal on R45 and R56 on the XCVR? Note the frequency, and high and low voltages for each of the 4 combinations you mention above. They should look like a square wave in all cases. We have a borrowed oscilloscope spec'd to 1.5 GHz with no probe. I will try to borrow or buy a suitable probe. Can you confirm R45 and R56 are just digital logic signals, as would seem to be the case from what you state above? Assuming the signal you were transmitting was a sine wave with a baseband frequency of 0, then what you are seeing here is completely expected and normal. When the clocks are not locked to the same reference, there is some frequency error, and the signal received is at some frequency other than exactly on the LO of the receiver, and it will get through just fine. However, when the 2 clocks are locked to the same reference, the transmitted tone will be received exactly on the LO frequency of the receiver. When this is downconverted to baseband, it will appear at DC, and it will be nulled out by the DC offset correction, which occurs in both the analog and digital domains. You can turn off the digital one, but not the analog one on the XCVR. To demonstrate this, you can run the following commands: - To show a good tone being received: usrp_siggen.py -f 5.65G -A 0.1 -x 100k --sine usrp2_fft.py -f 5.65G - To show the tone being nulled out: usrp_siggen.py -f 5.65G -A 0.1 -x 0 --sine usrp2_fft.py -f 5.65G Whoops. Didn't think about the DC offset correction. It was a sine wave at the carrier frequency that I tried. I will hence try your suggestion tomorrow, as it is evening here and I am at home without access to the radios. Thanks Ian. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] output of rfx900 and 2400 daughter board in receive mode
how will the frequency,Amplitude,phase of I and Q output signals from quadrature demodulator of rfx900/rfx2400 receivers be? I feel 1. frequency of I and Q will be a constant for all RF signal inputs.if it is true what is the frequency? 2. Amplitude of I and Q varies according to RF*cos(phi) and RF*sin(phi) In-phase and Quadrature phase components of RF signals respectively.is it so?can explain in detail. 3. what is prominence of phase of I and Q. -- chandu bckav...@tatapowersed.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] input of DDC?
What is the default input signal frequency of DDC of USRP(1). 1. how I and Q are given to DDC?I Q to same DDC?I Q to two different DDC's among 4 DDC's?two ADC outputs to single DDC? 2. how to give IF or only real signal to DDC through ADC? what IF frequency can we select? 3. If two receivers 900/2400 are used simultaneously how will be the ADC-MUX-DDC configuration? -- chandu bckav...@tatapowersed.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] gnuradio-3.2.2 build on mac os 10.6.2
Hi all, I have been trying to build gnuradio-3.2.2 on an iMac with a 2GHz Intel Core 2 Duo and Mac OS 10.6.2 with no success. I am using the tar file gnuradio-3.2.2.tar.gz. The 'configure' process works fine but 'make' ends up with this error: float_dotprod_sse.S:63:suffix or operands invalid for `push' float_dotprod_sse.S:163:suffix or operands invalid for `pop' make[6]: *** [float_dotprod_sse.lo] Error 1 make[5]: *** [all] Error 2 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 I have seen in the mailing list archive that someone else had the same problem and that it was related to the build for 64bit architectures. Is there any update on this issue? Is there any workaround available? Thanks in advance, Carlos Avilés. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gnuradio-3.2.2 build on mac os 10.6.2
Is there any update on this issue? Is there any workaround available? A quick search of the discuss GNU Radio list archive at http://lists.gnu.org/archive/html/discuss-gnuradio/ reveals the following in the first page: http://lists.gnu.org/archive/html/discuss-gnuradio/2009-10/msg00185.html http://lists.gnu.org/archive/html/discuss-gnuradio/2010-01/msg00442.html ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gnuradio-3.2.2 build on mac os 10.6.2
Oh, thanks Michael, you're right. I didn't find those messages on my search... It works now fine. Carlos. On Thu, Feb 4, 2010 at 2:05 PM, Michael Dickens m...@alum.mit.edu wrote: Is there any update on this issue? Is there any workaround available? A quick search of the discuss GNU Radio list archive at http://lists.gnu.org/archive/html/discuss-gnuradio/ reveals the following in the first page: http://lists.gnu.org/archive/html/discuss-gnuradio/2009-10/msg00185.html http://lists.gnu.org/archive/html/discuss-gnuradio/2010-01/msg00442.html -- Carlos Avilés Leibnizstr. 47, 10629 Berlin carlos.avil...@googlemail.com +49 15117321801 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to implement 64QAM?
On Wed, Feb 3, 2010 at 6:43 PM, alanluo mortimer1...@gmail.com wrote: Thanks Isaac for your kindly suggestion. I think i have to dive into python now... idg101 wrote: Hi, I haven't looked at any of the QAM-related code in the GNU Radio baseline, but it should be possible to design a generic MQAM demodulator. In fact, you should be able to build a generic MQAM demodulator for a given constellation set. This, I've done before in Matlab. You start with an AGC, feed through an equalizer which is optimized for minimizing the phase error between recovered and truth symbols. Another way to look at it that for each symbol, find the symbol that matches closest to the constellation vector (thats your decode symbol) and then feed the error into the equalizer. I believe there is a way to form a generic carrier recovery and symbol recovery loops that can deal with generic MPSK style constellation of which MQAM is a part of. In fact, you could write a routine that can do anything from BPSK to 64QAM. my 2 cents, Isaac You can look at gnuradio-core/src/python/gnuradio/blks2impl/qam*.py for a place to start. It doesn't really do proper synchronization, just the symbol mapping, but it should give you a way forward. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] running OFDM on USRP2
On Wed, Feb 3, 2010 at 1:55 PM, bin zan zanbin2...@gmail.com wrote: Hi Tom, In our case, even with script from Veljko, the OFDM receiver doesn't show any thing. And we always see usrp2: failed to enable realtime scheduling. Do you think that will cause problem? Thanks, Bin No, that message is just telling you that you don't have permissions to run it at the highest priority. It means you won't be able to run as fast, but that shouldn't be the cause of your problems. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] A strange question involving costas loop
Hi, What is expected if I input a costas loop block with a complex sine wave signal? Will the Costas track the sine and give me a baseband output containing nothing? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Questions about synchronization and modulation in benchmark
I am not very good at this either but I will try the same thing first on my computer and see if I can help. On Tue, Feb 2, 2010 at 5:50 AM, Timothy Lawrence Sitorus timothy.l.sito...@gmail.com wrote: Hi Mir thank for the reply. Sorry for my lack of information. Actually my problem is not in the modulator. But in the Frequency offset or timing error. I have removed the differential encoder in the path. The path worked when i executed it in one computer without usrp2(like benchmark_loopback.py). But when i executed it between two usrp2, I couldn't receive it in properly. the signal can't be locked. I plot the result from gr.mpsk_receiver (see attached file). Any suggest? On Tue, Feb 2, 2010 at 5:21 PM, Mir M. Ali mirmurt...@gmail.com wrote: Check the source code of costas loop and Mueller Mueller clock recovery blocks. They have the link to the reference papers used for the implementation. Regarding your bpsk/dbpsk question. There is a differential encoder block in the transmit_path of this modulator. Remove this from the connect path and you will get bpsk. Thanks, Mir On Sun, Jan 31, 2010 at 2:54 AM, Timothy Lawrence Sitorus timothy.l.sito...@gmail.com wrote: Hi Adib Thanks for the reply. I check it in the net and download it. I don't know about costas loop and clock recovery in detail. may I know how they they estimate frequency offset, and recover it? as far as I know, they are using gr.quadrature_demod_cf(1) and subtract it using gr.single_pole_iif_filter_ff(alpha) for frequency offset?is it right? Tim On Sun, Jan 31, 2010 at 4:03 PM, adib_sairi adib_sa...@yahoo.comwrote: there is some work from Thomas Schmid which modulate and demodulate O-QPSK which mean for IEEE802.15.4 standard.. you can search and download the code online. good luck.. Adib Timothy Lawrence Sitorus wrote: HI all, Please anyone help me. Is there anyone succeeded to modulate qpsk, even frequency offset occurs? Best Regards, Tim ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- View this message in context: http://old.nabble.com/Questions-about-synchronization-and-modulation-in-benchmark-tp27371719p27390702.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ 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 mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] input of DDC?
On Thu, Feb 04, 2010 at 03:42:10PM +0530, chandu wrote: What is the default input signal frequency of DDC of USRP(1). 1. how I and Q are given to DDC?I Q to same DDC?I Q to two different DDC's among 4 DDC's?two ADC outputs to single DDC? 2. how to give IF or only real signal to DDC through ADC? what IF frequency can we select? 3. If two receivers 900/2400 are used simultaneously how will be the ADC-MUX-DDC configuration? Chandu, Please read through the USRP FAQ and take a look at the pages below. If you've still got a question after reading this stuff ask again. In particular look at usrp_standard_rx::set_mux http://gnuradio.org/redmine/wiki/gnuradio/UsrpRfxDiagrams http://gnuradio.org/redmine/attachments/129/USRP_Documentation.pdf http://gnuradio.org/doc/doxygen/classusrp__basic__rx.html http://gnuradio.org/doc/doxygen/classusrp__standard__rx.html Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Current state of timestamping in USRP 1
What is the status of this? Isaac -- View this message in context: http://old.nabble.com/Current-state-of-timestamping-in-USRP-1-tp27457715p27457715.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] running OFDM on USRP2
On Thu, Feb 04, 2010 at 07:25:47AM -0600, Tom Rondeau wrote: On Wed, Feb 3, 2010 at 1:55 PM, bin zan zanbin2...@gmail.com wrote: Hi Tom, In our case, even with script from Veljko, the OFDM receiver doesn't show any thing. And we always see usrp2: failed to enable realtime scheduling. Do you think that will cause problem? Thanks, Bin No, that message is just telling you that you don't have permissions to run it at the highest priority. It means you won't be able to run as fast, but that shouldn't be the cause of your problems. Tom To enable real-time scheduling (highly recommended), do this: Ensure that you are in the usrp group, and then add this line to the end of /etc/security/limits.conf: @usrp- rtprio 50 Log out, then back in, and the message should go away. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] PLL loop bandwidth
On 02/03/2010 11:57 AM, Per Zetterberg wrote: Hi All, But I guess only Matt can answer this :-) What is the bandwidth of the PLL loop of the RFX1800 and the XCVR2450 ? The XCVR2450 has a roughly 50 kHz loop bandwidth. The RFX1800 has about a 20 kHz loop bandwidth, but that will vary with settings. I suggest downloading ADISimPLL from Analog devices, and entering the values from our schematics if it is critical that you have control of the loop bandwidth on any RFX-series board. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] A strange question involving costas loop
On Thu, Feb 4, 2010 at 09:23, Mir M. Ali mirmurt...@gmail.com wrote: What is expected if I input a costas loop block with a complex sine wave signal? Will the Costas track the sine and give me a baseband output containing nothing? You will get a complex DC value. I will be the magnitude of the input signal and Q will be 0, plus a small amount of noise due to round off error. Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] weird real-time scheduling problem
Hi All, I have Ubuntu 9.10 and gnuradio 3.2.2 installed on two identical PC configurations, with two USRP2s (one per PC, obviously). on both computers I have /etc/security/limits.conf file with the following line: @usrp - rtprio 50 and on both of them I set the permissions for usrp2_socket_opener so I can use USRP2 as a non-root user. On both PCs I run gnuradio sa user moment with following ID: uid=1000(moment) gid=1000(moment) groups=4(adm),20(dialout),24(cdrom),46(plugdev),104(lpadmin),115(admin),120(sambashare),1000(moment),1001(usrp) However, on one of the PCs I can't get real time scheduling working. I get Warning: failed to enable realtime scheduling for every example I tried, although the examples do continue to run. Any ideas about what could this be? Is there some other thing that has to be changed to enable real-time scheduling? Could it be that some of the group/user manipulation files are corrupted? Thanks, Veljko ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] MacPorts and GNU Radio 32-bit
I've updated MacPorts to use GNU Radio 3.2.2 ; if you're using OSX 10.5 or 10.6 as 32-bit, please give these ports a try see if they work for you. And, let me know if you run into any difficulties. Your shell environment's PYTHONPATH and such just need to work with MacPorts -- nothing special added for GNU Radio since it's installed by MacPorts. These ports will compile on as 32-bit only right now. I'll be adding in patches for 64-bit compilation real soon now. Turns out it's easier to just commit the changes than create a tarball have folks beta test ... really wish they used GIT, since it would make beta testing doable and quite simple. More soon. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] A strange question involving costas loop
In GRC I have a complex sine source with amplitude 10 and frequency 2000Hz sampled at 4000Hz as a input to the costas loop through a throttle block. The max and min frequency used is +/- 0.157rad/sample which is 100Hz /sample. When I see the output on scope and FFT scope i see peak at 0Hz in the FFt scope but on the oscilloscope I see a sine wave with amplitude 10 on the Inphase component and 0 in the Q component. Why? The output is shown in the figure. http://img690.imageshack.us/img690/7879/snapshot1u.jpg Thanks On Thu, Feb 4, 2010 at 2:52 PM, Johnathan Corgan jcor...@corganenterprises.com wrote: On Thu, Feb 4, 2010 at 09:23, Mir M. Ali mirmurt...@gmail.com wrote: What is expected if I input a costas loop block with a complex sine wave signal? Will the Costas track the sine and give me a baseband output containing nothing? You will get a complex DC value. I will be the magnitude of the input signal and Q will be 0, plus a small amount of noise due to round off error. Johnathan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] Straight from USRP to Wave File
Thanks for the response Eric. Each input is a separate antenna. I believe we have the basic daughter board. So far I've attempted to do this via GRC but I'm not sure how to go from the complex output of the USRP sources to the floats needed for the wave file sink. Date: Wed, 3 Feb 2010 19:44:48 -0800 From: e...@comsec.com To: anti_p...@hotmail.com CC: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Straight from USRP to Wave File On Wed, Feb 03, 2010 at 03:39:34PM -0700, Jon Paul Lundquist wrote: Hello, I wish to have a USRP source receiving at 54.1Mhz sent straight to a stereo wave file sink with no demodulation or any other manipulation. Side A of the USRP would record to the left channel and side B to right. I'd like to record at 192khz 24bit if possible (and no this isn't for a listening application that would just be silly). Let's just say I'm not a crack programmer and the documentation for this things are scattered in the wind across the internet. This is probably one of the simplest programs you can write for gnuradio but I need some help. Thanks! To get that signal in, it will need to be downconverted in the FPGA. Is your input a quadrature signal (i.e., two inputs: I Q), or is it two (unrelated) real signals? Which daughterboard are you planning on using? Take a look at usrp_rx_cfile.py for the basic framework for a single channel (or quadrature signal). If the two inputs are independent, gnuradio-examples/python/multi-antenna/multi_file.py may provide a better starting point. You'll want to use a gr.wavefile_sink to write the wavefile. http://gnuradio.org/doc/doxygen/classgr__wavfile__sink.html Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] issue 406
Dimitrios, Just by an accident I found the same bug and submitted a patch to gnuradio-patch mailing list a while ago. Eric Blossom pushed it to master as 6b1bcb301ff4cb just few hours ago (surprisingly, _before_ I read your mail). So I think you can close the ticket. On Tue, Feb 2, 2010 at 19:00, Dimitrios Symeonidis azim...@gmail.com wrote: Back in August I found a small issue with the usrp_fft.py and usrp_oscope.py utlis always selecting subdevice(0,0). I created ticket 406 and attached my 2-line patch. http://gnuradio.org/redmine/issues/show/406 Since then nothing happened. Johnathan (or anyone else), can you please merge that? Thanks Dimitris Symeonidis If you think you're too small to make a difference, try sleeping with a mosquito! - Amnesty International ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- Regards, Alexander Chemeris. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] A strange question involving costas loop
On Thu, Feb 4, 2010 at 4:37 PM, Mir M. Ali mirmurt...@gmail.com wrote: In GRC I have a complex sine source with amplitude 10 and frequency 2000Hz sampled at 4000Hz as a input to the costas loop through a throttle block. The max and min frequency used is +/- 0.157rad/sample which is 100Hz /sample. When I see the output on scope and FFT scope i see peak at 0Hz in the FFt scope but on the oscilloscope I see a sine wave with amplitude 10 on the Inphase component and 0 in the Q component. Why? The output is shown in the figure. http://img690.imageshack.us/img690/7879/snapshot1u.jpg Thanks I assume you are using a bpsk costas loop (m=2). In bpsk all of the data is in the real portion of the signal, therefore any amplitude in the Q is considered error. In order to recover the data, the loop rotates the data so the Q component to 0, and the I component is presumably +/-1. If you were to do the same with a qpsk loop (m=4), you should see both components looking like a saw wave. Additionally, a standard costas loop assumes that the data has already been sampled. Your samples per 'symbol' is higher than 1 in this case, and the loop output would not be predicable if you were sending data. Jason ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] A strange question involving costas loop
Thank you very much. :) On Thu, Feb 4, 2010 at 8:26 PM, Jason Uher jasonu...@gmail.com wrote: On Thu, Feb 4, 2010 at 4:37 PM, Mir M. Ali mirmurt...@gmail.com wrote: In GRC I have a complex sine source with amplitude 10 and frequency 2000Hz sampled at 4000Hz as a input to the costas loop through a throttle block. The max and min frequency used is +/- 0.157rad/sample which is 100Hz /sample. When I see the output on scope and FFT scope i see peak at 0Hz in the FFt scope but on the oscilloscope I see a sine wave with amplitude 10 on the Inphase component and 0 in the Q component. Why? The output is shown in the figure. http://img690.imageshack.us/img690/7879/snapshot1u.jpg Thanks I assume you are using a bpsk costas loop (m=2). In bpsk all of the data is in the real portion of the signal, therefore any amplitude in the Q is considered error. In order to recover the data, the loop rotates the data so the Q component to 0, and the I component is presumably +/-1. If you were to do the same with a qpsk loop (m=4), you should see both components looking like a saw wave. Additionally, a standard costas loop assumes that the data has already been sampled. Your samples per 'symbol' is higher than 1 in this case, and the loop output would not be predicable if you were sending data. Jason ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] A strange question involving costas loop
The output is shown in the figure. http://img690.imageshack.us/img690/7879/snapshot1u.jpg In unrelated help... you can install the icons and menu items with: sudo grc_setup_freedesktop install -Josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] Unable to tune Tx or Rx with XCVR2450 on USRP2
Hi Matt I have completed the probing as you suggested. The results are in the following table. Please note that the voltages did not seem to be stable when I tried reprobing in some cases. An example of this is for R45, where I give two sets of results for Combo D. Also, please note the following expanded definitions for comments in the table. Triangle = The wave looked more like a triangular wave, never really settling on a fixed high or low level. Square50 = The wave looked approximately square, with equal time in low/high states. Square33 = The wave looked approximately square, with approx. 1/3 time in the high state, and 2/3 time in the low state. Results for probing R45: Combo | U2# | XCVR# | Set freq? | Vh (mV) | Vlow (mV) | f (MHz) | Comment --- A | 933 | 990 | YES | 16 | -12.8 | 100 | Triangle B | 933 | 988 | NO| 19.6| -16 | 100.184 | Triangle C | 1159 | 990 | YES | 20.8| -19.2 | 100 | Triangle D(1st)| 1159 | 988 | YES | 21.2| -20 | 100.125 | Triangle D(2nd)| 1159 | 988 | YES | 12 | -15.6 | 99.83(?)| Triangle Results for probing R56: Combo | U2# | XCVR# | Set freq? | Vh (mV) | Vlow (mV) | f (MHz) | Comment --- A | 933 | 990 | YES | 16 | -7.6 | 33.3| Square33 B | 933 | 988 | NO| 15.2| -6| 33.3| Square33 C | 1159 | 990 | YES | 15.2| -6.8 | 33.3| Square33 D | 1159 | 988 | YES | 12 | -11.6 | 49.969 | Square50 I guess, the difference in the R56 for case D (the only case for which XCVR 988 was able to set the frequency) may shed some light??? Anyway, hopefully from these results you will be able to determine which card is suspected to have the problem. Thanks Ian. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Testing USRP with WBX
Hi List, I have a USRP1 with a WBX in the B side and a DBSRX in the A side. I have just done a fresh install of the stable tarball (3.2.2) and I ran the usrper load_standard_bits. The USRP1 serial number is in the 3700-3800 range so I believe it is compatible with the WBX. When I run usrp_benchmark I get the following error:- Testing 32MB/sec... Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Tx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Rx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. uUusb_throughput = 32M ntotal= 1600 nright= 15988058 runlength = 15988058 delta = 11942 OK Max USB/USRP throughput = 32MB/sec Is there something more I need to do to make this work? Cheers, Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Testing USRP with WBX
I believe you need to use the current source from the git tree, not the 3.2.2 tarball. Tim Matthew Robert wrote: Hi List, I have a USRP1 with a WBX in the B side and a DBSRX in the A side. I have just done a fresh install of the stable tarball (3.2.2) and I ran the usrper load_standard_bits. The USRP1 serial number is in the 3700-3800 range so I believe it is compatible with the WBX. When I run usrp_benchmark I get the following error:- Testing 32MB/sec... Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Tx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Rx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. uUusb_throughput = 32M ntotal= 1600 nright= 15988058 runlength = 15988058 delta = 11942 OK Max USB/USRP throughput = 32MB/sec Is there something more I need to do to make this work? Cheers, Matt ___ 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
Re: [Discuss-gnuradio] Testing USRP with WBX
Yes, the releases don't support the WBX, you need git. Matt On 02/04/2010 09:04 PM, Timothy Newman wrote: I believe you need to use the current source from the git tree, not the 3.2.2 tarball. Tim Matthew Robert wrote: Hi List, I have a USRP1 with a WBX in the B side and a DBSRX in the A side. I have just done a fresh install of the stable tarball (3.2.2) and I ran the usrper load_standard_bits. The USRP1 serial number is in the 3700-3800 range so I believe it is compatible with the WBX. When I run usrp_benchmark I get the following error:- Testing 32MB/sec... Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Tx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Rx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. uUusb_throughput = 32M ntotal = 1600 nright = 15988058 runlength = 15988058 delta = 11942 OK Max USB/USRP throughput = 32MB/sec Is there something more I need to do to make this work? Cheers, Matt ___ 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 mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] Unable to tune Tx or Rx with XCVR2450 on USRP2
Hi Matt Additional to below: I tried to resume normal testing with A as Rx and D as Tx. Now, it seems I have an offset of about 2 MHz using internal clocks and running usrp2_fft.py on A, when I transmit a BPSK signal from D. Moreover, I am unable to tune D for the low (2.4 GHz) band anymore. In fact, when I just tried again I don't even seem to be able to detect any received signal even in the high band, and even though it appears to lock on D. Regards Ian. Hi Matt I have completed the probing as you suggested. The results are in the following table. Please note that the voltages did not seem to be stable when I tried reprobing in some cases. An example of this is for R45, where I give two sets of results for Combo D. Also, please note the following expanded definitions for comments in the table. Triangle = The wave looked more like a triangular wave, never really settling on a fixed high or low level. Square50 = The wave looked approximately square, with equal time in low/high states. Square33 = The wave looked approximately square, with approx. 1/3 time in the high state, and 2/3 time in the low state. Results for probing R45: Combo | U2# | XCVR# | Set freq? | Vh (mV) | Vlow (mV) | f (MHz) | Comment --- A | 933 | 990 | YES | 16 | -12.8 | 100 | Triangle B | 933 | 988 | NO| 19.6| -16 | 100.184 | Triangle C | 1159 | 990 | YES | 20.8| -19.2 | 100 | Triangle D(1st)| 1159 | 988 | YES | 21.2| -20 | 100.125 | Triangle D(2nd)| 1159 | 988 | YES | 12 | -15.6 | 99.83(?)| Triangle Results for probing R56: Combo | U2# | XCVR# | Set freq? | Vh (mV) | Vlow (mV) | f (MHz) | Comment --- A | 933 | 990 | YES | 16 | -7.6 | 33.3| Square33 B | 933 | 988 | NO| 15.2| -6| 33.3| Square33 C | 1159 | 990 | YES | 15.2| -6.8 | 33.3| Square33 D | 1159 | 988 | YES | 12 | -11.6 | 49.969 | Square50 I guess, the difference in the R56 for case D (the only case for which XCVR 988 was able to set the frequency) may shed some light??? Anyway, hopefully from these results you will be able to determine which card is suspected to have the problem. Thanks Ian. ___ 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
RE: [Discuss-gnuradio] Unable to tune Tx or Rx with XCVR2450 on USRP2
Hi Matt Additional to below: I tried to resume normal testing with A as Rx and D as Tx. Now, it seems I have an offset of about 2 MHz using internal clocks and running usrp2_fft.py on A, when I transmit a BPSK signal from D. Moreover, I am unable to tune D for the low (2.4 GHz) band anymore. In fact, when I just tried again I don't even seem to be able to detect any received signal even in the high band, and even though it appears to lock on D. Regards Ian. Hi Matt I have completed the probing as you suggested. The results are in the following table. Please note that the voltages did not seem to be stable when I tried reprobing in some cases. An example of this is for R45, where I give two sets of results for Combo D. Also, please note the following expanded definitions for comments in the table. Triangle = The wave looked more like a triangular wave, never really settling on a fixed high or low level. Square50 = The wave looked approximately square, with equal time in low/high states. Square33 = The wave looked approximately square, with approx. 1/3 time in the high state, and 2/3 time in the low state. Results for probing R45: Combo | U2# | XCVR# | Set freq? | Vh (mV) | Vlow (mV) | f (MHz) | Comment --- A | 933 | 990 | YES | 16 | -12.8 | 100 | Triangle B | 933 | 988 | NO| 19.6| -16 | 100.184 | Triangle C | 1159 | 990 | YES | 20.8| -19.2 | 100 | Triangle D(1st)| 1159 | 988 | YES | 21.2| -20 | 100.125 | Triangle D(2nd)| 1159 | 988 | YES | 12 | -15.6 | 99.83(?)| Triangle Results for probing R56: Combo | U2# | XCVR# | Set freq? | Vh (mV) | Vlow (mV) | f (MHz) | Comment --- A | 933 | 990 | YES | 16 | -7.6 | 33.3| Square33 B | 933 | 988 | NO| 15.2| -6| 33.3| Square33 C | 1159 | 990 | YES | 15.2| -6.8 | 33.3| Square33 D | 1159 | 988 | YES | 12 | -11.6 | 49.969 | Square50 I guess, the difference in the R56 for case D (the only case for which XCVR 988 was able to set the frequency) may shed some light??? Anyway, hopefully from these results you will be able to determine which card is suspected to have the problem. Thanks Ian. ___ 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
Re: [Discuss-gnuradio] Testing USRP with WBX
Awesome, thanks guys, I built the current git version and it works perfectly. Regards, Matt On Fri, Feb 5, 2010 at 4:19 PM, Matt Ettus m...@ettus.com wrote: Yes, the releases don't support the WBX, you need git. Matt On 02/04/2010 09:04 PM, Timothy Newman wrote: I believe you need to use the current source from the git tree, not the 3.2.2 tarball. Tim Matthew Robert wrote: Hi List, I have a USRP1 with a WBX in the B side and a DBSRX in the A side. I have just done a fresh install of the stable tarball (3.2.2) and I ran the usrper load_standard_bits. The USRP1 serial number is in the 3700-3800 range so I believe it is compatible with the WBX. When I run usrp_benchmark I get the following error:- Testing 32MB/sec... Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Tx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. Warning: Treating daughterboard with invalid EEPROM contents as if it were a Basic Rx. Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom utility. uUusb_throughput = 32M ntotal = 1600 nright = 15988058 runlength = 15988058 delta = 11942 OK Max USB/USRP throughput = 32MB/sec Is there something more I need to do to make this work? Cheers, Matt ___ 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 mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
