On 2022-07-28 10:17, Giuseppe Santaromita wrote:
Yes, but the link still doesn't work, and I think it's a USRP problem.
To check whether the USRP is working, I thought I would do this:
N310: ./tx_waveforms --freq 915e6 --rate 15.36e6 --gain 40 --wave-type
RAMP --wave-freq 5e6
B210: sudo ./rx_ascii_art_dft --freq 98e6 --rate 15.36e6 --gain 20
--bw 5e6 --ref-lvl -60 --args "serial=31722CF"
Your RX-side gain is quite low, also use a wave-type like COS or SIN
Also, you're specifying a tuned frequency on the RX side of 98MHz,
rather than 915MHz.
I don't see anything in the spectrum.
Il 27/7/22 14:39, Marcus D. Leech ha scritto:
On 2022-07-26 19:35, Giuseppe Santaromita wrote:
Dear community,
I am trying to use OpenAirInterface with an N310 as gNB. I am
writing on this mail list because I think my problem is caused by
the configuration of the N310.
When I run the N310 I get variable errors. When I run it for the
first time after a long time I get no errors.
But when I run it after a short time I get these warnings and errors
(not always all of them):
[WARNING] [MPM.RPCServer] Someone tried to claim this device again
(From: 192.168.20.1)
[WARNING] [MPM.RPCServer] A timeout event occured!
[WARNING] [RFNOC::GRAPH] One or more blocks timed out during flush!
terminate called after throwing an instance of 'uhd::runtime_error'
what(): RuntimeError: rx xport timed out getting a response from
mgmt_portal
Aborted
And these are just a few examples.
I could think of ignoring them, using the N310 only a few minutes
after the previous use. The problem is that the device does not seem
to transmit anything over the air, even on the first try. I say this
because using the same configuration file that I use with a B210 the
gNB does not work, while with the B210 it works and I can connect
the smathphone.
I attach the log file of OperAirInterface.
Also, I frequently get the classic "L" indicating overflow after
about ten seconds.
I have solved a similar problem before (I report a previous mail):
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I installed the UHD 4.1 version and followed this tutorial:
https://kb.ettus.com/USRP_N300/N310/N320/N321_Getting_Started_Guide
for updating the Linux File System and updating the FPGA Image.
When I try a simple example file:
./rx_ascii_art_dft --freq 98e6 --rate 5e6 --gain 20 --bw 5e6
--ref-lvl -30
I get the following error:
[WARNING] [0/Radio#0] set_rx_bandwidth take no effect on AD9371.
Default analog bandwidth is 100MHz
I cannot find any useful information online, apart from this
discussion:
https://www.mail-archive.com/usrp-users@lists.ettus.com/msg05735.html
which did not help me.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Although in the forum it was told to me that this was just a
warning, I fixed it by upgrading the version of UHD to 4.3.
All this suggests to me that there is something messed up in the
initial setup.
Does anyone have any ideas and can help me?
When an application terminates abnormally, the N310 doesn't "know"
that the application has "gone away", and takes it a while to notice,
and reset its internal state.
Many network-based applications that use connectionless protocols
like UDP have the same issue, even outside of the SDR universe.
The bandwidth warning is just a warning. It will have little to no
effect on your application. This has been explained in previous posts.
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
