However, when I look to see what that cordic_freq is, I see that the
default
is 29.32e6 (Line 19). I thought that the 2400 was supposed to
communicate
from 2.3-2.9 GHz. The comment for set_tx_freq() in usrp_standard.h says
that
the frequency argument for set_tx_freq() has to be set from [-44M, 44M].
Even more confusing is that when I tune the receiving USRP board to
2.4GHz,
I get a high reading. How can I determine what center frequency the
transmitting board is actually communicating at?
On Wed, Aug 09, 2006 at 04:30:50PM -0500, Michael F. wrote:
is 29.32e6 (Line 19). I thought that the 2400 was supposed to
communicate
from 2.3-2.9 GHz. The comment for set_tx_freq() in usrp_standard.h
says that
the frequency argument for set_tx_freq() has to be set from [-44M,
44M].
Even more confusing is that when I tune the receiving USRP board to
2.4GHz,
I get a high reading. How can I determine what center frequency the
transmitting board is actually communicating at?
Michael, please try using the current code. There’s a reason that
fsk_tx.py is not in the current code base, and hasn’t been for the
past year.
If you want an example of transmit code that works with any
daughterboard, please take a look (in the current svn code – http://gnuradio.utah.edu/trac – for directions)
usrp-examples/python/usrp/fm_tx4.py
My apologies - I didn’t know it wasn’t available anymore, but the file
was
there when I checked out the code from the CVS server earlier this
summer.
The site I posted was just for easy reference.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.