[Discuss-gnuradio] Re: Jack instead of ALSA
Just in case someone else has the same problem: if you need to force Jack audio: from gnuradio import audio_jack and on the source/sink linles, use audio_jack.source or audio_jack.sink instead of audio.source and audio.sink. Thanks to Oswald Berthold for the help. Best regards, Charles On Tue, Nov 17, 2009 at 9:54 PM, Charles Herdt charles.he...@gmail.com wrote: Hello Hoping anyone had gone through this before. I am trying to make some experiments with jack audio in linux (Ubuntu 9.10), but so far, all I could get is Alsa. I'm using the audio.sink and audio.source blocks, and have not yet figured out a way for it to use Jack. I have jack audio compiled in gnurario 3.2.2. Any suggestions? Thank you in advance, Charles A. Herdt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] usrp2 with atl1e gigabit ethernet device
Hi list, I've connected a USRP2 to my laptop's gigabit ethernet [1] and the USRP2's ethernet indicator LED is not on. Running find_usrp2s returns zero results on my machine, while on another machine, using the same cable, the USRP2 is detected. I've read that some people have actually had it working well with the same gigabit ethernet device [2] and was hoping that someone else could say what the problem is here. My first instinct is to assume that the auto-negotiation process [3] is not working. It used to be the case, that if auto-negotiation was not working, a crossover cable would fix the problem. Does that sound like an accurate diagnosis / prognosis? Rather than buy a new cable, I might be able to add a bit of code to the kernel driver to allow for manual switching through a /sys entry (if the device supports such control operations), but I thought that I would ask the list for suggestions first. Cheers, Chris [1] atl1e driver 03:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) [2] http://old.nabble.com/Netgear-GA311-%28Realtek-8169%29-and-USRP-2-td20908796.html [3] http://en.wikipedia.org/wiki/Ethernet_crossover_cable#Automatic_crossover ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: usrp2 with atl1e gigabit ethernet device
It would seem that the atl1e device does support manual MDI configuration, according to this [1]. [1] http://lwn.net/Articles/289918/ On Wed, Nov 18, 2009 at 12:14 PM, Christopher Friedt chrisfri...@gmail.com wrote: Hi list, I've connected a USRP2 to my laptop's gigabit ethernet [1] and the USRP2's ethernet indicator LED is not on. Running find_usrp2s returns zero results on my machine, while on another machine, using the same cable, the USRP2 is detected. I've read that some people have actually had it working well with the same gigabit ethernet device [2] and was hoping that someone else could say what the problem is here. My first instinct is to assume that the auto-negotiation process [3] is not working. It used to be the case, that if auto-negotiation was not working, a crossover cable would fix the problem. Does that sound like an accurate diagnosis / prognosis? Rather than buy a new cable, I might be able to add a bit of code to the kernel driver to allow for manual switching through a /sys entry (if the device supports such control operations), but I thought that I would ask the list for suggestions first. Cheers, Chris [1] atl1e driver 03:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) [2] http://old.nabble.com/Netgear-GA311-%28Realtek-8169%29-and-USRP-2-td20908796.html [3] http://en.wikipedia.org/wiki/Ethernet_crossover_cable#Automatic_crossover ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Re: Jack instead of ALSA
On Wed, Nov 18, 2009 at 09:07:16AM -0200, Charles Herdt wrote: Just in case someone else has the same problem: if you need to force Jack audio: from gnuradio import audio_jack and on the source/sink linles, use audio_jack.source or audio_jack.sink instead of audio.source and audio.sink. Thanks to Oswald Berthold for the help. Best regards, Charles Much easier to just edit ~/.gnuradio/config.conf Add these three lines to the file: [audio] verbose = True audio_module = audio_jack On Tue, Nov 17, 2009 at 9:54 PM, Charles Herdt charles.he...@gmail.com wrote: Hello Hoping anyone had gone through this before. I am trying to make some experiments with jack audio in linux (Ubuntu 9.10), but so far, all I could get is Alsa. I'm using the audio.sink and audio.source blocks, and have not yet figured out a way for it to use Jack. I have jack audio compiled in gnurario 3.2.2. Any suggestions? Thank you in advance, Charles A. Herdt Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Boost 1.40 won't build on OSX 10.6
Hi Ed - The 3.2.2 release cannot easily be made to be fully working on OSX 10.6, but the complexity depends mostly on whether your computer's CPU is 32- or 64-bit. * If your computer's CPU is 32-bit then I think all components except gr-audio-osx should compile execute without change. You might need to specify --with-md-cpu=i386 to force the use of the correct FIR filter code (I don't have a 32-bit CPU to test this on). * If your computer's CPU is 64-bit, then you have 3 primary choices to get GNU Radio going (at all) on 10.6: 1) If you insist on using GNU Radio 3.2.2, then you'll want to limit compilation to just 32-bit mode by setting the CFLAGS (et.al.) to include -arch i386 (I think) -- and do without native audio support (gr-audio-osx; audio issues are fixed in the GIT master, so you can always diff those files make the mods to the 3.2.2 release hope for the best); or 2) Move to the GIT master, and limit compilation to just 32-bit mode -- and you should get full GNU Radio functionality (assuming you can get all of the background dependencies installed, e.g., via MacPorts). 3) Move to the GIT master, do 64-bit compilation -- and do with a GUI. The GIT master has been updated to allow for 32- or 64-bit compiling on OSX, and should support 10.4, 10.5, and 10.6 -- except the GUI won't work under x86_64 yet (64-bit, any supported OS version; it's a wxpython issue, and the wx folks are working on full 64-bit OSX support for the next [2.9.0] release). The current wxgui should work on i386 (32-bit, any supported OS version). I hope this isn't too confusing! Ask more if this doesn't help enough. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Status of the MIMO Hub?
I have a need to connect three USRP2's together, and am curious as to the status of the proposed MIMO hub. If the MIMO hub is not available, are there any recommendations for a reference clock to use to synchronize these systems. - Wayde ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] GSM Handset Emulation
Now that there is a functional basestation available for GSM, I was wondering if anyone is trying to build software for a GSM handset. This way, I could use my laptop (e.g. in a manner similar to skype) to talk with folks when I don't have a GSM phone handy. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Boost 1.40 won't build on OSX 10.6
On Wed, Nov 18, 2009 at 10:12:35AM -0500, Michael Dickens wrote: Hi Ed - The 3.2.2 release cannot easily be made to be fully working on OSX 10.6, but the complexity depends mostly on whether your computer's CPU is 32- or 64-bit. * If your computer's CPU is 32-bit then I think all components except gr-audio-osx should compile execute without change. You might need to specify --with-md-cpu=i386 to force the use of the correct FIR filter code (I don't have a 32-bit CPU to test this on). * If your computer's CPU is 64-bit, then you have 3 primary choices to get GNU Radio going (at all) on 10.6: 1) If you insist on using GNU Radio 3.2.2, then you'll want to limit compilation to just 32-bit mode by setting the CFLAGS (et.al.) to include -arch i386 (I think) -- and do without native audio support (gr-audio-osx; audio issues are fixed in the GIT master, so you can always diff those files make the mods to the 3.2.2 release hope for the best); or 2) Move to the GIT master, and limit compilation to just 32-bit mode -- and you should get full GNU Radio functionality (assuming you can get all of the background dependencies installed, e.g., via MacPorts). 3) Move to the GIT master, do 64-bit compilation -- and do with a GUI. The GIT master has been updated to allow for 32- or 64-bit compiling on OSX, and should support 10.4, 10.5, and 10.6 -- except the GUI won't work under x86_64 yet (64-bit, any supported OS version; it's a wxpython issue, and the wx folks are working on full 64-bit OSX support for the next [2.9.0] release). The current wxgui should work on i386 (32-bit, any supported OS version). I hope this isn't too confusing! Ask more if this doesn't help enough. - I'm confused! Michael, can you help me understand what the problems are, and what, if anything, we can do on the GNU Radio side to resolve them? It sounds like some of these problems may have more to do with external dependencies than with GNU Radio itself. The guts of GNU Radio definitely run on x86 and x86-64, so I'm not sure what the 64-bit issue is on OS/X. Last I checked, we ran on 64-bit PPC on Fedora too. Thanks! Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GSM Handset Emulation
Isaac Gerg wrote: Now that there is a functional basestation available for GSM, I was wondering if anyone is trying to build software for a GSM handset. This way, I could use my laptop (e.g. in a manner similar to skype) to talk with folks when I don't have a GSM phone handy. No one is working on it AFAIK but if you start I know a few folks that'd be pretty happy :) Sylvain ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Status of the MIMO Hub?
I have a need to connect three USRP2's together, and am curious as to the status of the proposed MIMO hub. If the MIMO hub is not available, are there any recommendations for a reference clock to use to synchronize these systems. - Wayde ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio We used the Meinberg GPS162 as a reference clock. Works quite good. Cheers,Christoph ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Boost 1.40 won't build on OSX 10.6
Michael Dickens wrote: Hi Ed - The 3.2.2 release cannot easily be made to be fully working on OSX 10.6, but the complexity depends mostly on whether your computer's CPU is 32- or 64-bit. It's a brand new MacBook Pro with 2.8 GHz Intel Core2 Duo, so as far as I know it's 64-bit. * If your computer's CPU is 64-bit, then you have 3 primary choices to get GNU Radio going (at all) on 10.6: 1) If you insist on using GNU Radio 3.2.2, This is preferred... then you'll want to limit compilation to just 32-bit mode by setting the CFLAGS (et.al.) to include -arch i386 (I think) -- and do without native audio support Sound's not critical, so this has possibilities. But I can't even get past the ./configure until I get Boost 1.40 to install. 2) Move to the GIT master, and limit compilation to just 32-bit mode -- and you should get full GNU Radio functionality (assuming you can get all of the background dependencies installed, e.g., via MacPorts). Also has possibilities. But MacPorts has been the real problem so far. I can't get the dependencies (specifically Boost =1.35) to install. And I've now broken my previously-working GnuRadio 3.1.3 installation. :( 3) Move to the GIT master, do 64-bit compilation -- and do without a GUI. Not really acceptable for our application. We want the GUI stuff. I hope this isn't too confusing! Ask more if this doesn't help enough. - MLD I really need to figure out the problem with the MacPorts dependencies not installing. Any clues would be appreciated. I'm sure this has to do with the fact that I used Apple's migration assistant to move my account onto the new laptop (including the MacPorts stuff and GR 3.1.3). My old laptop was running 10.4, and now I'm afraid I've got a mix of 32 and 64 bit stuff installed. But 3.1.3 and GRC 0.69 DID run after the migration. @(^.^)@ Ed ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Boost 1.40 won't build on OSX 10.6
On Nov 18, 2009, at 12:06 PM, Eric Blossom wrote: Michael, can you help me understand what the problems are, and what, if anything, we can do on the GNU Radio side to resolve them? It sounds like some of these problems may have more to do with external dependencies than with GNU Radio itself. The guts of GNU Radio definitely run on x86 and x86-64, so I'm not sure what the 64-bit issue is on OS/X. Last I checked, we ran on 64-bit PPC on Fedora too. We made numerous Darwin-specific changes to the GNU Radio GIT master recently to resolve 10.6 and 64-bit compiling issues (mostly debugging printouts, by moving fprintf(stderr,...) to std::cerr ...). Hence the GNU Radio -GIT master- should now be compatible with OSX 10.4, 10.5, or 10.6 as 32-bit or 64-bit. I have successfully tested GNU Radio in 32-bit on each of these (Intel only, but that shouldn't make a difference), and in 64-bit on 10.6, using MacPorts for all installable dependencies (NB for 10.6: see the last real paragraph below). I believe that Ed was asking specifically about the 3.2.2 release. GNU Radio -release 3.2.2- does not have these recent GIT master changes for both 10.6 and 64-bit OSX, but most of 3.2.2 should compile as 32-bit since it was originally (inadvertently) designed to compile as 32-bit -- only gr-audio-osx needs changes to compile under 10.6 because Apple changed the CoreAudio API. To the best of my knowledge, GNU Radio was never compiled as 64-bit under 10.5 (or 10.4,if that's possible) ... hence it's only with the move to 10.6 that these bit- width issues came up -- and were promptly addressed. Thus, to summarize, assuming we're talking about the GNU Radio GIT master: The issues are not with GNU Radio. The issues w/r.t. 10.6 /or 64-bit are instead with the dependencies wxWidgets and wxPython: Up through the 2.8.10 series, the WX* codebase was 32-bit compatible on OSX but would fail when compiled as 64-bit (and, OSX won't allow one to mix match 32- and 64-bit libraries and applications). Starting with WX* 2.9.0, the codebase will be both 32- bit and 64-bit compatible on OSX 10.5 or 10.6 http://wxwidgets.org/ ; wxWidgets 2.9.0 has been released, but wxPython has yet to catch up before we can test them out with GNU Radio (via MacPorts or otherwise) I hope this note clarifies your issues; if not, ask more. - MLD ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Boost 1.40 won't build on OSX 10.6
On Wed, Nov 18, 2009 at 02:22:27PM -0500, Michael Dickens wrote: On Nov 18, 2009, at 12:06 PM, Eric Blossom wrote: Michael, can you help me understand what the problems are, and what, if anything, we can do on the GNU Radio side to resolve them? It sounds like some of these problems may have more to do with external dependencies than with GNU Radio itself. The guts of GNU Radio definitely run on x86 and x86-64, so I'm not sure what the 64-bit issue is on OS/X. Last I checked, we ran on 64-bit PPC on Fedora too. We made numerous Darwin-specific changes to the GNU Radio GIT master recently to resolve 10.6 and 64-bit compiling issues (mostly debugging printouts, by moving fprintf(stderr,...) to std::cerr ...). Hence the GNU Radio -GIT master- should now be compatible with OSX 10.4, 10.5, or 10.6 as 32-bit or 64-bit. I have successfully tested GNU Radio in 32-bit on each of these (Intel only, but that shouldn't make a difference), and in 64-bit on 10.6, using MacPorts for all installable dependencies (NB for 10.6: see the last real paragraph below). I believe that Ed was asking specifically about the 3.2.2 release. GNU Radio -release 3.2.2- does not have these recent GIT master changes for both 10.6 and 64-bit OSX, but most of 3.2.2 should compile as 32-bit since it was originally (inadvertently) designed to compile as 32-bit -- only gr-audio-osx needs changes to compile under 10.6 because Apple changed the CoreAudio API. To the best of my knowledge, GNU Radio was never compiled as 64-bit under 10.5 (or 10.4,if that's possible) ... hence it's only with the move to 10.6 that these bit-width issues came up -- and were promptly addressed. Thus, to summarize, assuming we're talking about the GNU Radio GIT master: The issues are not with GNU Radio. The issues w/r.t. 10.6 /or 64-bit are instead with the dependencies wxWidgets and wxPython: Up through the 2.8.10 series, the WX* codebase was 32-bit compatible on OSX but would fail when compiled as 64-bit (and, OSX won't allow one to mix match 32- and 64-bit libraries and applications). Starting with WX* 2.9.0, the codebase will be both 32- bit and 64-bit compatible on OSX 10.5 or 10.6 http://wxwidgets.org/ ; wxWidgets 2.9.0 has been released, but wxPython has yet to catch up before we can test them out with GNU Radio (via MacPorts or otherwise) I hope this note clarifies your issues; if not, ask more. - MLD Thanks for the detailed answer! Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: usrp2 with atl1e gigabit ethernet device
Someone told me that the USRP2 does not respond when connected to a 100/10 Mbps ethernet device. So, by default, the LEDs apparently do not turn on unless connected to a gigabit device. Even though my ethernet device was a gigabit adapter, thee LEDs still did not turn on. That leads me to believe either a) the MDIX auto-negotiation is not working, or b) my ethernet device is not configured for gigabit speeds, even though it's capable of it. Does anyone else on the list have a device that uses the atl1e ethernet adapter? C On Wed, Nov 18, 2009 at 12:19 PM, Christopher Friedt chrisfri...@gmail.com wrote: It would seem that the atl1e device does support manual MDI configuration, according to this [1]. [1] http://lwn.net/Articles/289918/ On Wed, Nov 18, 2009 at 12:14 PM, Christopher Friedt chrisfri...@gmail.com wrote: Hi list, I've connected a USRP2 to my laptop's gigabit ethernet [1] and the USRP2's ethernet indicator LED is not on. Running find_usrp2s returns zero results on my machine, while on another machine, using the same cable, the USRP2 is detected. I've read that some people have actually had it working well with the same gigabit ethernet device [2] and was hoping that someone else could say what the problem is here. My first instinct is to assume that the auto-negotiation process [3] is not working. It used to be the case, that if auto-negotiation was not working, a crossover cable would fix the problem. Does that sound like an accurate diagnosis / prognosis? Rather than buy a new cable, I might be able to add a bit of code to the kernel driver to allow for manual switching through a /sys entry (if the device supports such control operations), but I thought that I would ask the list for suggestions first. Cheers, Chris [1] atl1e driver 03:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0) [2] http://old.nabble.com/Netgear-GA311-%28Realtek-8169%29-and-USRP-2-td20908796.html [3] http://en.wikipedia.org/wiki/Ethernet_crossover_cable#Automatic_crossover ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
UPDATE: [Discuss-gnuradio] Boost 1.40 won't build on OSX 10.6
Ed Criscuolo wrote: . But MacPorts has been the real problem so far. I can't get the dependencies (specifically Boost =1.35) to install. I found that problem with Boost came from zlib and bzip2. By reinstalling these with the +universal variant specified Boost 1.40 was able to install successfully. Now working on the other missing dependencies. Also got a message that usrp2 was not configured because its only supported on Linux. Is this true? @(^.^)@ Ed ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: UPDATE: [Discuss-gnuradio] Boost 1.40 won't build on OSX 10.6
On Wed, Nov 18, 2009 at 03:37:02PM -0500, Ed Criscuolo wrote: Ed Criscuolo wrote: . But MacPorts has been the real problem so far. I can't get the dependencies (specifically Boost =1.35) to install. I found that problem with Boost came from zlib and bzip2. By reinstalling these with the +universal variant specified Boost 1.40 was able to install successfully. Now working on the other missing dependencies. Also got a message that usrp2 was not configured because its only supported on Linux. Is this true? At this time, yes. It'll be fixed as part of the VRT work (Virtual Radio Transport; AKA VITA-49). Progress is being made on this... ;-) Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Comparison between GNU Radio and FlexRadio
Hi guys, I'm going to be doing some research on digital comms on HF bands, and I'm having trouble deciding between the GNU Radio and the FlexRadio as a platform. The GNU Radio seems more general-purpose, and the FlexRadio more ham-oriented but perhaps more ready-to-go. So I'm just wondering if there's a comparison between the two somewhere? Maybe it'd be a good question for the FAQ: How does GNU Radio compare to other SDRs? Thanks, Ben. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Comparison between GNU Radio and FlexRadio
Considering the hardware, I think that for ham usage, as you said, FlexRadio is more ready-to-use, but usrp, equipped with the correct hardware, allows you to do much more things, and also it can work with a much wider bandwidth. But I don't own a FlexRadio, and don't know about it's intrinsics. I'd also like to hear more about a USRP/FlexRadio comparison too. Rafael Diniz Hi guys, I'm going to be doing some research on digital comms on HF bands, and I'm having trouble deciding between the GNU Radio and the FlexRadio as a platform. The GNU Radio seems more general-purpose, and the FlexRadio more ham-oriented but perhaps more ready-to-go. So I'm just wondering if there's a comparison between the two somewhere? Maybe it'd be a good question for the FAQ: How does GNU Radio compare to other SDRs? Thanks, Ben. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GSM Handset Emulation
Now that there is a functional basestation available for GSM, I was wondering if anyone is trying to build software for a GSM handset. This way, I could use my laptop (e.g. in a manner similar to skype) to talk with folks when I don't have a GSM phone handy. It wouldn't be very convenient, since you'd have to have a USRP, plus antennas, dangling off your laptop. GSM handset software could probably use a lot of the existing low and medium level GSM basestation code. Having free implementations of both sides of the interface would make debugging easier, too. But there'd still be a lot of work involved. You'll need a SIM card and some way to read it, too. Sounds like a fun grad-student project to me. You could skip a lot of hassle with codecs and audio I/O and such by first making something that would offer data service (e.g. SMS text messages, or Internet access) by talking to a GSM basestation. John ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Multihop network using BBN 802.11b
Hi All, I am trying to implement a multihop network on USRP2's using the BBN 802.11b code. I am able to receive and forward (transceiver) with the same USRP running the receive and transmit flow graphs serially. However, after a few runs, the program abruptly gets killed. I have also tried to reinitialize all the flowgraphs and objects, but it doesn't work. Has anybody else encountered the same problem? Any help in this regard will be appreciated. Thanks in advance. Best regards, Arvind Prasanna Research Assistant, Wireless Networks and Embedded Sytems Laboratory, University at Buffalo (SUNY). ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[discuss-gnuradio] Multihop network using BBN 802.11b
-- Forwarded message -- From: Arvind Prasanna arvindprasa...@gmail.com Date: Thu, Nov 19, 2009 at 1:43 AM Subject: Multihop network using BBN 802.11b To: discuss-gnuradio@gnu.org Hi All, I am trying to implement a multihop network on USRP2's using the BBN 802.11b code. I am able to receive and forward (transceiver) with the same USRP running the receive and transmit flow graphs serially. However, after a few runs, the program abruptly gets killed. I have also tried to reinitialize all the flowgraphs and objects, but it doesn't work. Has anybody else encountered the same problem? Any help in this regard will be appreciated. Thanks in advance. Best regards, Arvind Prasanna Research Assistant, Wireless Networks and Embedded Sytems Laboratory, University at Buffalo (SUNY). ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
