Hello
Is it possible to run benchmark_tx and benchmark_rx on same computer
with
one USRP with RFX-1800 Transciever daughter board.
Is it possible to run benchmark_tx and benchmark_rx on same computer with
one USRP with RFX-1800 Transciever daughter board.
I believe if you have two daughter cards it is possible to run the
benchmark_x scripts on the same USRP but different daughtercards, but
I think you need to combine them into a single flow graph. If I
remember correctly when you open a new instance of usrp_source_ (as
you would when you run the second script), the settings for the old
one get wiped out.
One thing to note here is that with the leakage from the cards
themselves (caveat, I have not used the RFX1800) it is very likely
that you will get an excellent BER even without antennas. For
example, even with both the transmitter and receiver ports terminated,
I still receive a very high SNR waveform when listening from one card
and transmitting from the other in a single USRP. Based on my
experience with the RFX2400, if you are planning to use this to
attempt to model some sort of communication system, your antenna
choice/interference will likely have little impact on your results.
If you simply want to ‘see it work’ then the single USRP set up should
be fine, however for any real testing you will probably need two
USRPs.
Jason
On Wed, Jul 01, 2009 at 07:51:31AM -0500, Jason U. wrote:
Is it possible to run benchmark_tx and benchmark_rx on same computer with
one USRP with RFX-1800 Transciever daughter board.I believe if you have two daughter cards it is possible to run the
benchmark_x scripts on the same USRP but different daughtercards, but
I think you need to combine them into a single flow graph. If I
remember correctly when you open a new instance of usrp_source_ (as
you would when you run the second script), the settings for the old
one get wiped out.
You can’t run benchmark_tx and _rx using one USRP and two
daughtercards. The two sides of the USRP aren’t fully independent.
Eric
On Wed, Jul 01, 2009 at 11:38:53AM -0500, Jason U. wrote:
Even if you combine the code into a single flowgraph?
Sorry, you’re right. The tunnel code does something very much like
what you have below.
The problem I was thinking of was the case where you’re trying to run
two daughterboards, each of which is trying to run half-duplex, and
the Tx/Rx timing on the two sides is independent. In that case the
Auto-TR stuff gets in the way.
Eric
I believe if you have two daughter cards it is possible to run the
benchmark_*x scripts on the same USRP but different daughtercards, but
I think you need to combine them into a single flow graph. If I
You can’t run benchmark_tx and _rx using one USRP and two
daughtercards. The two sides of the USRP aren’t fully independent.Eric
Even if you combine the code into a single flowgraph? It’s been a
very long time since I tried it, so maybe there are new firmware
changes I’m not aware of; but I know that I’ve gotten something like
the following working with the *_path files modified to use different
daughterboards and the passed usrp object:
class my_top_block(gr.top_block):
def init(self, demodulator, rx_callback, options):
gr.top_block.init(self)
(SNIP: Set up the usrp here)
self.rxpath = receive_path(self.usrp, demodulator,
rx_callback, options)
self.connect(self.rxpath)
self.txpath = transmit_path(self.usrp, demodulator, options)
self.connect(self.txpath)