Closed eulenleber closed 10 months ago
Hi @eulenleber ,
You are getting a lot of lates
and underflows
on the UE machine. I would first try to get rid of these, as they may be the cause of the UE not being able to connect. You can try running the following command to set your CPU governor to performance:
echo "performance" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
You can also reduce the log level being reported, as this can take up compute power that the UE may need. Try setting your logs to info
for the UE - it is currently set to debug
.
If the issue persists after trying the above, please attach the logs and pcaps for the test. You should leave the logs in info
mode for this.
Thank you very much, I'll have to check whether I have the access to more powerful hardware. Since that's a reoccurring phenomenon I suggest a kind of explicit warning message like "too many L's or U's consider upgrading the hardware"
Also a specific minimal hardware requirement would help (at least in the https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html there's just an Ubuntu :v: PC :v: mentioned)
I will come back to this.
Any update on this issue? We're seeing largely the same behavior. We have even tried using different b210s and different host machines but the underflow messages still remain. What's also confusing is that even though the UE never connects, the behavior varies in a seemingly random way. Sometimes the UE output prints information about the Random Access transmission, and sometimes it doesn't. Sometimes the UE log file has "SYNC" issues, sometimes it has "SFN does not match" issues (like in the attached log)
Our setup looks like the following ue host -> usrp b210 -> 30 dB attenuation -> usrp b210 -> gnb/open5gs core host.
We're using UHD 3.15 and commit 1afd7240f2b5e2061ab4158e8fcdacb15961813a for srsRAN_Project and fa56836b14dc6ad7ce0c3484a1944ebe2cdbe63b for srsRAN_4G for the UE.
Hi @ncmatson , it seems your issue is different. I don't see Lates/Underflows in your logs. Your issue is CFO:
2023-09-05T15:52:00.598835 [RRC-NR ] [I] Proc "Cell Selection" - Cell search found ARFCN=0 PCI=1 epre=-36.4 snr=+22.8 cfo=-3951.8 delay=+0.0 sfn=957 ssb_idx=0 hrf=n scs=15 ssb_offset=6
Please use an external clock as described in the tutorial.
Issue Description
gnb is connected to open5g core and "visible" to the client sdr (via spectrum analyzer) but the client sdr can not connect using
srsue
Setup Details
Expected Behavior
srsue connects
Actual Behaviour
srsue does not connect
Steps to reproduce the problem