I know this is an old thread, but... I just had the same issue and found one alternative.
If you are using two cables to connect a set of BasicTX and BasicRX daughterboards, there is a simple workaround. Just replace the definition of carrier_sensed(self) to "False" instead of "self.rxpath.carrier_sensed()." Since your TX and RX paths are non-interfering, being contained in the cables, you have the equivalent of full duplex communications and will never sense a carrier to block your transmit opportunity. I suppose it's a bit like falling back to a null mac. I just did this on a recent svn pull and two Fedora Core 6 boxes, so I know it works in at least one case. :-) This will allow you to show IP data moving over two USRPs without having to have the RFX-* cards. Best, Mike > -----Original Message----- > From: > [EMAIL PROTECTED] > [mailto:discuss-gnuradio-bounces+michael.weber=baesystems.com@ > gnu.org] On Behalf Of Eric Blossom > Sent: Thursday, June 22, 2006 7:37 PM > To: Brett L Trotter > Cc: [email protected] > Subject: Re: [Discuss-gnuradio] gmsk2 (new tunnel.py) > > On Thu, Jun 22, 2006 at 03:59:26PM -0500, Brett L Trotter wrote: > > Eric Blossom wrote: > > > On Thu, Jun 22, 2006 at 03:32:10PM -0500, Brett L Trotter wrote: > > > > > > First off, this example will only work with RFX-* > daugherboards, not > > > the basic tx and rx board. Why: we currently can't > enable/disable > > > the transmitter on the basic tx board. > > > Thanks for your wonderful help and patience so far. > > > > I've gotten rid of the B's with sufficently high -c > options, but ping > > still isnt happening.. > > As I said above, this example will *NOT* work with the Basic > Tx and Basic Rx daughterboards. > > Eric > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
