5G SA End-to-End with USRP B210's #870
Comments
|
Hey, can you share the logs files in info mode please until this happens? It's likely a hickup in the last messages that cause the UE do be in state without recovery. Note that the recovery and retransmission of NAS signaling, etc. isn't implemented yet |
|
Hi, I am working on 5G SA End-to-End with USRP B205-mini's. Using the same enb.conf, rr.conf and ue.conf. However, there is no response on both sides. Here is the display by srsenb: Built in Release mode using commit f2dff0b on branch master. Opening 1 channels in RF device=uhd with args=type=b200,serial=3180ECB,clock=internal,sampling_rate=23.04e6,lo_freq_offset_hz=23.04e6,None ==== eNodeB started === Here is the display by srsue: Opening 1 channels in RF device=uhd with args=type=b200,serial=1710009,clock=internal,sampling_rate=23.04e6,lo_freq_offset_hz=23.04e6,None cat /tmp/srsue.log produces: What am I missing? |
|
I since have this working; I use a 30 dB attenuation on the cable connection, and I had to use a tx_gain of 75 and rx_gain of 35 for the enb.conf: The same for the ue.conf. Your mileage may vary, it probably depends on your connections. You will also have to create a record for your SIM in the 5G Core Network (I used open5gs for this). Please not I used UHD 3.15 instead of 4.0.0, not sure if that makes a difference. |
|
Using the latest agpl_next branch makes things a lot more resilient. I get 30 Mbps DL and 17 Mbps UL with 5G SA. Using the a similar setup with 4G 2x2 MIMO (RF1 -> RF1 and RF2 -> RF2 with a 30 dB attenuation) with PRB=100 I get 147 Mbps DL and 48.5 Mbps UL. |
|
@loktiing Could you check that your CPU is running at full performance? I have to run |
|
Thanks @TallGuy74, I tried follow your suggestions, both sides still do not get any response. If I run srsenb and then srsue, /tmp/srsue.log produces: If I do not run srsenb, I run srsue, /tmp/srsue.log produces: UE cannot seem to read ENB TX signal properly. Is it some synchronization issue? |
|
The setup works if I used ZMQ Virtual Radios on both node. But not for USRP B205-mini's |
|
I'm not sure if the B205 mini's use a different radio component (mostly the RF parts, with perhaps differing output power?). |
Hi @TallGuy74, have you managed to find the right gains for a USRP X300 setup, yet? |
|
@mariatsampazi 30 dB attenuation on the line with a tx_gain of 6 and an rx_gain of 0 worked with Amarisoft, and I think will work for srsue to srsenb as well. I currently use 2 x 30 dB attenuation and tx_gain of 20 and rx_gain of 13. |
|
Also, it looks like the clocks need to be really stable to make things work correctly. In my setup, if X300-1 is connected to the eNB, and X300-2 connected to the UE, things don't work correctly (connection is slow and unstable). If I switch X300-1 to UE, things work (30.5 Mbps DL and 18.9 Mbps UL for 5G SA SISO vs 9 Mbps DL and 18.9 Mbps UL with the non-working setup). Using a GPSDO or an octaclock should help with that though. |
|
Hi @TallGuy74 , thanks for your answer. In the configuration files, as soon as you made it work with usrps b210, the only change to the ones you shared was the tx and rx gains, right? |
|
Hi @mariatsampazi , @TallGuy74 I am also trying to connect two B210s through a 5G link. I can ping between gNB and UE, but the link only lasts for a few seconds/minutes. Does the same happen to you? I am using tx_gain=80, rx_gain=40 and a fixed attenuator of 30 dB connected to the TX port of the B210s. I am running Ubuntu 20.04 LTS and UHD 3.15-LTS on both. |
|
Yes, it has happened to me as well To combat if I followed the steps mentioned here: If the steps mentioned in the previous step don't help you can also try this: |
|
Thanks for your response, @mariatsampazi I used the command you suggested and followed the steps mentioned on the video, including using an external clock reference, and the link is way more stable, especially with the lower MCS they use (with MCS=10, the connection lasts over one hour). Are you also using a lower MCS? With the maximum MCS, I'm getting only ~26 Mbps in DL and 12 Mbps in UL. How stable is the link in your case? |
|
Hi @nadiayoza After following the steps mentioned above the link becomes more stable (I also use an MCS of 10). I have noticed that when the connection hangs the error is: |
|
Hi @mariatsampazi |
|
Yes, the RRC inactivity timer should be increased in the enb side. |
|
Good to know! We currently don't have X310, but only N310. I will see if we can use it. |
|
I used MCS value 0 for UL and DL and now it works really well with USRP X300. I would recommend to use lowest MCS value if you only want to test the connection procedure. |
|
Thanks, @whitecloudy Using B210 SDRs and a fixed MCS of 10, the connection lasts for almost 3 hours. That is significantly more stable than with the maximum MCS of 28. It's good to know that this works well with USRP X300, but unfortunately we don't have one. If you know of any other way to improve the stability and throughput using the B210, let me know. |
|
Hi, |
|
@Bhuvaneshnetcon If you are seeing high number of Lates either your PC is not strong enough or the CPU governor is not put in performance mode. |
|
Hi @herlesupreeth |
|
On Intel based machines I usually do the following steps to get maximum performance (resulting in less Lates and underflows) |
|
Hi @herlesupreeth |
|
Notice in your logs above (screenshot) that USRP B210 is using USB2 rather than USB3. Please check the port to which you have connected the USB cable of B210. |
|
Hi @herlesupreeth |
|
Hi @herlesupreeth |
|
Hi |
|
Please post here the gNB logs at info log level in order to debug the issue |
|
I have attached the gnb logs. 2024-01-08T10:29:38.478536 [FAPI ] [W] [ 281.8] Real-time failure in FAPI: Received late UL_TTI.request from slot 281.7 |
|
I would suggest benchmark your system connected to USRP B210 for the BW you are testing - https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio#Benchmarking_your_system There should no dropped/overflows. If there are then I would suggest using more powerful machine to run gNB |
Hey, I trying to setup 5G SA End to End with ZMQ in Oracle VM and Free5GC as core. I tested srs4g setup with ZMQ and its worked as expected. but when I add nr_cell_list info in rr.config file as part of 5G SA and run the enb. I am getting this error: |
|
Still not sloving the problem? I also got USRP B210 srsUE overflow problem.. |
Hi @loktiing , did u solved the tx & rx gain configuration for the over-the-air setup? I'm also using b205-mini and have the same problem (stuck on RF overflows). Thanks in advance |
Issue Description
I am unable to get a connection if I use two B210's instead of the ZeroMQ setup.
I get a connection on RRC level, but after that things just stop.
Setup Details
I use two Dell Inc. XPS 8950, with 32 GB of RAM and a 12900K CPU. Both of them are connected over USB3 to a USRP B210 with a cable connecting the RX and TX (with a 30 dB attenuation).
One of the Dell machines is running Open5GS, with the subscriber added.
Expected Behavior
A valid 5G connection, where I can ping the gNB machine from the UE machine.
Actual Behaviour
After the RRC is connected, I get a lot of this in my log file; the PHY configuration is done, SR procedure is starting, and it keeps trying to retransmit (and failing because it doesn't have anything to transmit? not sure)
Steps to reproduce the problem
I have installed Open5GS on one PC, in combination with srsRAN 22.04. This machine also has a B210 connected with USB3.
I used srsran_install_configs.sh user to install the default configuration files in /root/.config/srsran, and replaced enb.conf and
rr.conf.
The second PC has srsRAN 22.04 installed, and is also connected to a USRP B210 with USB3. Again, used srsran_install_configs.sh user to install the default configuration files in /root/.config/srsran, and replaced
ue.conf.
When starting, I first start the gNB using the command
sudo UHD_IMAGES_DIR=/usr/share/uhd/images srsenbon the first PC. This gets a connection to the 5G Core network, and can communicate with the B210.After that, I start the UE using the command
sudo UHD_IMAGES_DIR=/usr/share/uhd/images srsueon the second PC. This can communicate with the B210, and looks like it can communicate with the gNB as well, up to a point. The UE is attaching, and it gets a connection on the RRC level (see the output in the previous section).Additional Information
I have the log files available if needed (they're rather big).
The text was updated successfully, but these errors were encountered: