Giter VIP home page Giter VIP logo

Comments (5)

ismagom avatar ismagom commented on August 27, 2024

Thanks for reporting.

This is a known issue (#93) and will be fixed in the following days

from srsran_project.

brendan-mcauliffe avatar brendan-mcauliffe commented on August 27, 2024

Hi @polhenarejos the latest version of srsUE is now available, it contains a fix for this issue.

I suggest you update both srsRAN 4G and srsRAN Project now. There is also now a sample configuration file that ships with srsRAN Project that will work with srsUE.

from srsran_project.

polhenarejos avatar polhenarejos commented on August 27, 2024

Hi @brendan-mcauliffe

I updated both srsRAN 4G and srsRAN Project with commit id 64be27895 (ue) and 133e71a (gnb) but the problem still persists. However, this time the log is different:

2023-06-19T14:51:09.575241 [GNB     ] [W] Could not check DRM KMS polling. filename=/sys/module/drm_kms_helper/parameters/poll error="No such file or directory"
2023-06-19T14:51:13.472175 [FAPI    ] [W] [     0.0] Real-time failure in FAPI: Received late DL_TTI.request. Current slot is 217.2 while message corresponds to 217.1
2023-06-19T14:51:13.472181 [FAPI    ] [W] [     0.0] Real-time failure in FAPI: Received UL_TTI.request message out of time. Current slot is 217.2 while message corresponds to 217.1
2023-06-19T14:51:20.057267 [UL-PHY0 ] [D] [   865.4] PRACH:  rssi=+32.8dB detected_preambles=[{idx=0 ta=-10.94us power=+120.1dB snr=0.0dB}] t=361.9us
  rsi=1
  preambles=[0, 64)
  format=0
  set=unrestricted
  zcz=0
  rssi=+32.8dB
  res=0.5us
  max_ta=103.12us
  detected_preambles=[{idx=0 ta=-10.94us power=+120.1dB snr=0.0dB}]

2023-06-19T14:51:20.057270 [FAPI    ] [W] [     0.0] All detected PRACH preambles have a negative TA value in slot=865.4, no PRACH.ind message will be generated
2023-06-19T14:51:20.217352 [UL-PHY0 ] [D] [   881.4] PRACH:  rssi=+22.9dB detected_preambles=[{idx=0 ta=-10.94us power=+110.2dB snr=0.0dB}] t=337.1us
  rsi=1
  preambles=[0, 64)
  format=0
  set=unrestricted
  zcz=0
  rssi=+22.9dB
  res=0.5us
  max_ta=103.12us
  detected_preambles=[{idx=0 ta=-10.94us power=+110.2dB snr=0.0dB}]

2023-06-19T14:51:20.217352 [FAPI    ] [W] [     0.0] All detected PRACH preambles have a negative TA value in slot=881.4, no PRACH.ind message will be generated
2023-06-19T14:51:20.377279 [UL-PHY0 ] [D] [   897.4] PRACH:  rssi=+22.9dB detected_preambles=[{idx=0 ta=-10.94us power=+110.2dB snr=0.0dB}] t=338.1us
  rsi=1
  preambles=[0, 64)
  format=0
  set=unrestricted
  zcz=0
  rssi=+22.9dB
  res=0.5us
  max_ta=103.12us
  detected_preambles=[{idx=0 ta=-10.94us power=+110.2dB snr=0.0dB}]
...

It seems that something is 1 subframe time-misaligned. In the failing setup there is the warning message Real-time failure in FAPI: Received late DL_TTI.request., which is not present in the working setup. Is it related?

from srsran_project.

ismagom avatar ismagom commented on August 27, 2024

Hi @polhenarejos ,

I think I was wrong and your issue is different than #93.

I think your original issue is an incorrect TX/RX calibration in the USRP.

Looking at your gnb_ok.log:

2023-06-14T10:51:15.106681 [UL-PHY0 ] [D] [   689.4] PRACH:  rssi=+38.0dB detected_preambles=[{idx=0 ta=-10.94us power=+124.8dB snr=0.0dB}] t=359.6us

it seems the PRACH came too early. The gnb returned TA=0, but that makes the following PUCCH/PUSCH signal arrive early too. You could establish a connection, but the UL SNR was very low. With the later version, we added a check to avoid that, see in your gnb_ko.log you have the same PRACH reception but now with a warning message:

2023-06-14T10:58:59.678394 [UL-PHY0 ] [D] [   849.4] PRACH:  rssi=+38.0dB detected_preambles=[{idx=0 ta=-10.94us power=+125.5dB snr=0.0dB}] t=359.0us
 rsi=1
 preambles=[0, 64)
 format=0
 set=unrestricted
 zcz=0
 rssi=+38.0dB
 res=0.5us
 max_ta=103.12us
 detected_preambles=[{idx=0 ta=-10.94us power=+125.5dB snr=0.0dB}]

2023-06-14T10:58:59.678395 [FAPI    ] [W] [     0.0] All detected PRACH preambles have a negative TA value in slot=849.4, no PRACH.ind message will be generated

The solution to this problem is to calibrate the time_alignment_calibration as indicated here.

Hope that helps.

from srsran_project.

polhenarejos avatar polhenarejos commented on August 27, 2024

Hi @ismagom
It did the trick. I am using a delay of -127 samples and it works as before.

BTW, I still get the warning message about FAPI. Do you think it might introduce additional errors on higher layers?

Many thanks.

from srsran_project.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.