[Discuss-gnuradio] B input on BasicRX not working
Hello everyone, We've run into a problem with the B input on the Basic RX board with a USRP. Specifically, a test tone running into the A input shows up fine in the fft application, as well as in a captured file. However, a test tone running into the B input doesn't have any power in the FFT or in the captured file. Digital sample values on the 'bad' input are all either 0,1, or 2. We've tried tones at 250 MHz and 1 MHz, and we've tried two basicRX boards as well as 2 USRPs. We've also looked at the BasicRX boards to verify that the input signal actually makes it to the high density connector. Any thoughts? To capture I'm using: ./usrp_rx_cfile.py -R A -d 8 -f 0 -s -N 100 filename.dat (Of course, that's the example when the BasicRX is in the A slot.) -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GPS with DBSRX
Based on his Ham callsign, his name is Michael Gram. (However, based on the whois for kd7lmo.net, his name is Michael Gray.) -Roshan Chris Stankevitz wrote: Gregory W Heckler wrote: Has anyone successfully collected any GPS L1 data with the DBSRX Yes, I think this guy(*) used the DBSRX. He includes the collection scripts on his site as well: http://www.kd7lmo.net/ground_gnuradio_ota.html (*) I hate to call him this guy but he keeps his true identity secret! Chris ___ 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] USRP 4 Questions
Hello, If you're talking about F501 (next to the 6V input), the BOM lists it as a 3A 0603 part. Digikey part # P11359-CT-10 (though it doesn't seem to show up in the current digikey catalog). -Roshan Eric A. Cottrell wrote: Hello, I managed to blow the smd fuse on my USRP. It seems to be a 1 Amp 603 fuse. Is there a certain one I need to buy? I would like to order one from Mouser. I got the enclosure recently. Where do I plug the fan in? Should the fan exhaust the air from the enclosure? 73 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
Re: [Discuss-gnuradio] Varying signal with usrp_rx_cfile
What command line options are you using with usrp_rx_cfile.py? Can you send us an example of what you're executing on the command line? Cicale Randy S 2dLt AFRL/VSBXI wrote: I'm trying to save a signal to a file coming from a signal generator. The logical starting point is to use the program usrp_rx_cfile.py. After I put in the center frequency, I would like to vary the signal to view how it changes with time (via Matlab) but no matter how many samples or throttling I do, the signal never changes. The frequency that repeats over the number of samples is the initial one I start with. Is there a way to make this work? It seems very simple, maybe I'm missing something? Thanks, Randy ___ 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] mblock linking error
I've run into the same problem on Ubuntu 6.06 (Dapper Drake) at trunk rev 4662 (current). The trunk tree built fine for me on the same box a month ago. (I already tried make distclean and bootstrap.) -Roshan Josh Blum wrote: I just checked out the trunk rev 4659, did a bootstrap, configure, it fails on the make. I am running ubuntu edgy. Is this an issue with the new linking/integrating mblock? -Josh /bin/bash ../../../libtool --tag=CXX --mode=link g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o test_mblock test_mblock.o libmblock-qa.la http://libmblock-qa.la libmblock.la http://libmblock.la g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o .libs/test_mblock test_mblock.o ./.libs/libmblock-qa.so ./.libs/libmblock.so -Wl,--rpath -Wl,/usr/local/lib ./.libs/libmblock-qa.so: undefined reference to `pmt_list3(boost::shared_ptrpmt_base, boost::shared_ptrpmt_base, boost::shared_ptrpmt_base)' ./.libs/libmblock-qa.so: undefined reference to `pmt_list1(boost::shared_ptrpmt_base)' ./.libs/libmblock-qa.so: undefined reference to `pmt_list2(boost::shared_ptrpmt_base, boost::shared_ptrpmt_base)' collect2: ld returned 1 exit status make[4]: *** [test_mblock] Error 1 make[4]: Leaving directory `/usr/src/gnuradio_trunk/mblock/src/lib' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/src/gnuradio_trunk/mblock/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/gnuradio_trunk/mblock' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/gnuradio_trunk' make: *** [all] Error 2 ___ 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] mblock linking error
Johnathan Corgan wrote: Robert McGwier wrote: This problem is understood. There is a change in libtool in the Debian/Ubuntu community. I believed this was fixed here by finding out some shell changes but it is not. Just FYI, my main development machine is Ubuntu 6.10. I have never had this issue with libtool/rpath that you describe. I have the default build installed which does indeed have the /bin/sh - /bin/dash symlink. So there is something else going on here. I'm running Ubuntu 6.06, and /bin/sh links to /bin/bash, not dash. If you cannot build mblock, you need to install pmt, which alway builds first. Go into the pmt directory and make install or sudo make install depending on your situation. In this particular case, I believe that the specific mblock build failure that was seen was a problem with the Makefile.am that was fixed on the trunk yesterday evening. I'm still waiting confirmation of a fix or not. The updated Makefile didn't fix the problem. I'm now using the 4717 revision. Doing: make distclean ./bootstrap ./configure make fails in the 'boost' section of mblock, while doing the same thing but compiling pmt first results in a failure in the omnithread section of mblock (as Josh Blum saw). -Roshan There are a couple of really aggravating things in Ubuntu 6.1 (maybe earlier) and libtool and link of sh to dash are at the top of my list. I could not understand what in the world was going on with these shells which had Again, there must be something else going on as neither of these are a problem for me. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] mblock linking error
Yup, adding /usr/local/lib to my ld.so.conf file did indeed fix the problem. 4718 now builds cleanly. Thanks for the tip. Roshan Johnathan Corgan wrote: Roshan Baliga wrote: The updated Makefile didn't fix the problem. I'm now using the 4717 revision. Doing: make distclean ./bootstrap ./configure make fails in the 'boost' section of mblock, while doing the same thing but compiling pmt first results in a failure in the omnithread section of mblock (as Josh Blum saw). We established earlier that in at least one case adding: /usr/local/lib ...to the /etc/ld.so.conf file, then re-running ldconfig, would fix the problem. Can you try this? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] regarding fft-ifft processing
Brett L. Trotter wrote: That Cyclone FPGA was awfully full last I checked- I don't know enough about this type of thing to say it wouldn't fit, but it seems at least possible that the amount of real-estate required to do the FFT might be more than the current generation USRP could handle? On that note, does anyone how much of the Cyclone we're currently using? This whole discussion may be moot for the time being... -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] changing the vctcxo
Hans Glitsch wrote: I want to change the clock on the usrp. Anyone know of a mail order place that would have the right kind of vctcxo at 38.4MHz ? I tried Digikey and Mouser. no luck. Based on the common frequency table here: http://www.cardinalxtal.com/common-frequencies.htm it doesn't look like it's going to be easy to find a 38.4 MHz vctcxo. I just spent a decent amount of time looking for more stable clocks to replace the onboard TCXO. I found that unless you're willing to order a custom TCXO/OCXO (which is expensive and takes a long time), your best bet is to choose a frequency which is common, and then use one of those TCXOs. That way, you get the quantity advantage. For example, a 13 MHz GPS TCXO that's 0.5 ppm can cost well under $10. (Also, don't forget you can multiply the clock up, either using a discrete IC, or some transistors.) -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] changing the vctcxo
Hans Glitsch wrote: I just found this one on Digikey: http://www.abracon.com/Oscillators/ASVTX11.pdf I'm not an experienced hardware guy, but it looks like it would work in the usrp. Please tell me if I'm wrong. I believe the USRP needs a 3 Vpp clock in, and this TCXO only outputs 0.8 Vpp. Plus, it's a clipped sine. So you may want to throw it through a squarer that will bump it up to 0 - 3V before putting it into J2001. Is this right Matt? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Re: Re: Re: Re: Tx Path
Anmar wrote: What daughterboards are you using? I have two basic Tx daughterboards, so each one use different AD9862. I have a question the 2 AD9862 they both get there clock in from the usrp motherboard, and that is the same clock? The AD9862s (which are on the motherboard) both get the same clock from AD9513 clock distribution IC. The only difference is that the clock signal goes through separate (but identical) filters on its way to each AD9862. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] For basic daughter board, can you give me some tips?
?? wrote: I'm a newer for the usrp. I want to make the hardware myself. And I have some questions: 1. what is the usage of the connectors except for the 64-pin connector? Which connectors are you referring to? The 64-pin connector on each daughterboard carries all the signals and power from the USRP to the daughterboard. The rest of the .1 inch headers on the top of each daughterboard (for example, on the LFRX, J25, J15, J24, J16, and J17) are just there to bring out other signals for debugging or controlling other boards. 2. In the document RfSections4USRP, it recommended that we should design filter ourself, then how can we design the filter? The design of the external filter depends on what you're trying to accomplish. The USRP performs digital filtering (for example, there's a CIC in the FPGA), but external analog filtering can be helpful. For example, you may want a SAW filter or a bandpass filter to eliminate adjacent channel interference. -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] reading and writing fpga registers
Hello Everyone, I'm trying to read and write the fpga registers using just libusrp (sorry Eric!). (1) My write returns true, but the read returns 0, regardless of which fpga register I read/write to (I've tried a few). For example: snip if (utx-_write_fpga_reg(FR_ADC_OFFSET_0,0x)) snip int readregvalue2 = (utx-_read_fpga_reg(FR_ADC_OFFSET_0)); I must be doing something wrong here. (2) I believe that the user-defined FPGA registers don't exist in the verilog code. Do I need to add them manually? I was going to do that in usrp_std.v. I'm happy to submit a patch if I get things working where you can IFDEF the extra registers out if you need the space. -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] offset at input of LF_RX
You want the full schematics, which I believe are in the subversion repository. You can get them with this command (once you've installed the subversion client, of course): svn co http://gnuradio.org/svn/usrp-hw/trunk usrp-hw -Roshan [EMAIL PROTECTED] wrote: I would like to see this schematic that Don mentions; I look at ettus.com but all I could find is the 1-page basic description of the daughterboard. Is there something more detailed that shows the layout of the 8132 as well as the ADC? thanks, eric p.s.- the USRP performed beautifully for my demo, suitable impressing what might prove to be the next generation of aerospace engineers! On Fri, 22 Jun 2007, Matt Ettus wrote: Don Ward wrote: That's not what I get. With the input open, I measure 108 mV on the SMA connector and a DC component from the ADC (detected using the RSSI register, to avoid the DC offset filter in the FPGA). If I short the input to ground, I get a negative DC component from the ADC. To get zero from the ADC I need to ground the input through a 50 ohm (approximately) resistance; in this case I measure 62 mV at the input to the LFRX board. My conclusion (confirmed by inspection of the schematic) is that the LFRX needs to be driven by a source resistance of 50 ohms *at DC* to be correctly biased. I am sorry. You guys are both right. If you connect a 50 ohm resistor across the SMA, you do indeed get 62mV at the connector, but 0V at the ADC, which is what we really care about. If you leave the SMA open, you do get a small voltage being read at the ADC. So yes, the LFRX does have DC bias on its input, but as long as you drive it with a 50 ohm load, you get the right answer at the ADC. The LFRX wasn't designed for measuring DC voltages, although it can as long as you have a 50 ohm source. And if your source is not 50 ohms, you can do the calculations necessary to scale the gain. Also, please note that the amp is inverting, so if you put 1V through 50 ohms into the SMA, the ADC will tell you that it is -1V. 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] OpenMoko
I noticed the excitement yesterday, then found this tidbit at the bottom of their software page: (*) GPS position calculation and, also for regulatory reasons, firmware contained in peripheral chips are the only exceptions. Those components communicate with the rest of the system through openly specified interfaces, e.g., NMEA, GSM 07.05, etc. Which leads me to believe you won't be able to do much SDR with the phone. Plus, I would be willing to bet they do everything in hardware (I would, if I was building a consumer device). -Roshan John Bratteli wrote: I may be behind the times with this, but have any of you looked at the OpenMoko project? It's an open source cell phone software stack. They're not consumer ready yet, but the Neo1973 was recently put up for sale as developer hardware. There could be real potential for the phone as a GNURadio platform, and we could use some of their code as well. John Bratteli Hardware overview - http://www.openmoko.com/products-neo-base-03-hardware.html Software overview - http://www.openmoko.com/products-neo-base-04-software.html OpenMoko FAQ - http://wiki.openmoko.org/wiki/FAQ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html ___ 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] Reprogram FPGA
S Mande wrote: 1) Do I need a 3rd party tool to transfer my code to the FPGA on USRP ? I remember using a JTAG cable and Active-HDL for this task when i worked with Aldec procesors. I'm sure there are multiple ways to do this, but I just use the existing usrp framework to load the RBF file onto the fpga. That is, when I generate a new RBF file, I throw it into /usr/local/share/usrp/rev4/std_2rxhb_2tx.rbf and load it up with my own C application that links to libusrp.so. It's the quick and dirty way, but hey, it works. 2) I believe that the firmware is loaded everytime I run GNU radio. Is it that I replace the existing fpga Verilog firmware code ( .v file ) from its existing location .i.e. gnuradio folder with my modified Verilog firmware code ? The RBF file that is loaded is picked up from a predetermined location. In my case, with a rev 4 usrp, it's /usr/local/share/usrp/rev4/std_2rxhb_2tx.rbf. In your quartus project, the file you want is in usrp/fpga/toplevel/usrp_std/usrp_std.rbf If you replace the file in /usr/local... with a new rbf file, the gnuradio code will load it next time you power cycle/run the USRP. -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] laptop recommendations
Hi All, I looked through the gnuradio archive, and couldn't find this topic, so I'm posting. Does anyone have a current recommendation for a laptop for use with gnuradio? I've never had a problem with any desktop running Ubuntu 6.0.6, but the first laptop I tried (Dell Latitude D520) had rx overruns. I'm guessing the USB 2.0 chipset it uses sucks. In any case, if anybody uses a laptop with ubuntu and gnuradio, I'd love to know about it, because I need to buy a laptop for some testing. Preferably something on the cheaper side, but not a 8 lbs brick. -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] FPGA sample timestamps
Hi all, For one of our applications we think we need timestamps for some or all samples coming across the USB bus. I know there was some mention of this a while ago on the list, but I didn't find an open ticket on Trac. Obviously we would submit our changes back to gnuradio for inclusion in the project. For this reason, I'd like to know what requirements gnuradio has for FPGA timestamps, and what work, if any, has been done on this so far. Thanks, Roshan Baliga ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Reading registers on the USRP
[EMAIL PROTECTED] wrote: Hi, I'm having a little trouble reading the readback registers that are on the USRP. I know that most registers are write only with their contents mirrored on the computer. The reason I want read those registers back is because of a custom unit I am testing. I currently load a custom implementation on the USRP that consists of 1 TX chain and 2 custom units, one of which feeds back information into the unused readback ports (rssi0 to rssi3). I'm able to read from the capabilities register using '_read_fpga_register(FR_RB_CAPS)' and it returns a value that makes sense. When I try reading from any other register, the value returned is consistently '0'. I'm reading the registers in a loop in case the value changes after a given amount of time. I'm not sure what to try next, can someone give me a new direction? -Kevin This post might help: http://lists.gnu.org/archive/html/discuss-gnuradio/2007-05/msg00356.html -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Which version of Linux is the most convenient, SuSE or Fedora or ...
Zhenghao Zhang wrote: I am new to GNU radio and I was wondering which version of Linux you use. Is it SuSE or Fedora? I just want to know which is the most popular version of Linux for gnu radio such that I would have less problems working on it. I have a PC with CentOS and I cannot install gnu radio on it fully. Thanks very much for your time. This page http://gnuradio.org/trac/wiki/BuildGuide#OperatingSystemSpecificInstructions Includes direction for various flavors of GNU/Linux. My personal experience is that Ubuntu and Fedora are fairly easy to use with gnuradio. -Roshan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
