Hi Josh,
Definitely both daughterboards has different frequency ranges, I just wanted
to test the TX channel of the USRP2 to make sure is working.
That is the way I'm testing the LFTX, I have a spectrum analyzer connected
to the RX ports.
This is the flowgraph:
SignaSource ---> UHD:USRPSink
I
On 06/20/2012 05:08 PM, juancolon wrote:
>
> Hi,
>
> We have a USRP2 with a LFTX Rev 2.2 daughterboard. When I run a GRC program,
> I try to look at the signal with a spectrum analyzer and the signal is not
> there. There is no error at all, everything seems to be up and running. The
> system i
When I first noticed such behavior, I had both the N210 and USRP2 running in
the same computer connected through a switch.
addressing:
PC eth0 ip = 192.168.10.1
USRP2 with addr = 192.168.10.2
N210 with addr = 192.168.10.3
But the LFTX plugged in the USRP2 did not work.
I then decided to just h
Marcus,
This is the output:
linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.002-0-g7f44d838
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
UHD Warning:
Unable to set the thread priority. Performance may be negativ
Hi,
We have a USRP2 with a LFTX Rev 2.2 daughterboard. When I run a GRC program,
I try to look at the signal with a spectrum analyzer and the signal is not
there. There is no error at all, everything seems to be up and running. The
system is recognizing the USRP2, daughterboard and I have also pl
Hi,
We have a USRP2 with a LFTX Rev 2.2 daughterboard. When I run a GRC program,
I try to look at the signal with a spectrum analyzer and the signal is not
there. There is no error at all, everything seems to be up and running. The
system is recognizing the USRP2, daughterboard and I have also pl
