discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] about tune the daughterboard


From: WaveMaker
Subject: Re: [Discuss-gnuradio] about tune the daughterboard
Date: Fri, 21 Jul 2006 13:31:57 -0700 (PDT)

What "code of GMSK2" are you talking about?

I read this in CVS at
http://cvs.savannah.gnu.org/viewcvs/gnuradio/gnuradio-examples/python/gmsk2/benchmark_gmsk_tx.py?rev=1.19&view=markup
and it does not contain any mention of tune.

This code is only 3 weeks old, so I'm ASSsuming it's good :)


2 1 wrote:
> 
> Hi, all:)
> I've read through the code of GMSK2 and I found the difference of tune in
> transmit_path and receive_path.
> In the transmit_path:
>     self.u.tune(self.subdev._which, self.subdev, target_freq)
> In the receive_path:
>     self.u.tune(0, self.subdev, target_freq)
> 
> The self.subdev._which indicate the channel of TX/RX, 0 for A, 1 for B.
> (Am
> I right?)
> 
> So I am confused about why the first parameter of tune depends on channel
> selection in transmit_path while it's set to 0 in receive_path?
> 
> I am using 2 USRP with a FLEX2400 on B channel of both, so subdev._which
> is
> actually 1. I change the 0 in recieve_path to subdev._which, and I cannot
> recieve the signal anymore. So 0 must be set when using usrp as source.
> 
> BUT, why? Can you explain in detail about the first parameter of tune() to
> me?
> 
> Thanks!
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 
-- 
View this message in context: 
http://www.nabble.com/about-tune-the-daughterboard-tf1958954.html#a5439865
Sent from the GnuRadio forum at Nabble.com.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]