Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Late: 35; Underflow: 1; Overflow: 0; message when I am connecting galaxy M33 5G with enb through USRP x310 #971

Open
sruthi81 opened this issue Dec 5, 2024 · 10 comments

Comments

@sruthi81
Copy link

sruthi81 commented Dec 5, 2024

Here I am sharing the problem when I am connecting my ue with gnb. I am running Open5GS and srsRAN in same machine and usrp x310 is used as RU.
Screenshot from 2024-12-05 11-35-54
"Late: 35; Underflow: 1; Overflow: 0;" message.

Please help me to solve this issue.

@pgawlowicz
Copy link
Collaborator

could you share your configs and log?

@sruthi81
Copy link
Author

sruthi81 commented Dec 5, 2024

Yes Sir.

This configuration file example shows how to configure the srsRAN Project gNB to allow srsUE to connect to it.

This specific example uses ZMQ in place of a USRP for the RF-frontend, and creates an FDD cell with 10 MHz bandwidth.

To run the srsRAN Project gNB with this config, use the following command:

sudo ./gnb -c gnb_zmq.yaml

amf:
addr: 127.0.0.5 # The address or hostname of the AMF.
bind_addr: 127.0.0.5 # A local IP that the gNB binds to for traffic from the AMF.

ru_sdr:
device_driver: uhd # The RF driver name.
device_args: addr=192.168.10.2 #tx_port=tcp://127.0.0.1:2000,rx_port=tcp://127.0.0.1:2001,base_srate=23.04e6 # Optionally pass arguments to the selected RF driver.
#sync: gpsdo # Specify the sync source used by the RF.
#device_args: tx_port=tcp://192.168.0.105:2000,rx_port=tcp://192.168.0.114:2001,base_srate=23.04e6 # Optionally pass arguments to the selected RF driver.
clock: internal
srate: 23.04 # RF sample rate might need to be adjusted according to selected bandwidth.
tx_gain: 30 # Transmit gain of the RF might need to adjusted to the given situation.
rx_gain: 30 # Receive gain of the RF might need to adjusted to the given situation.

cell_cfg:
dl_arfcn: 368500 # ARFCN of the downlink carrier (center frequency).
band: 3 # The NR band.
channel_bandwidth_MHz: 20 # Bandwith in MHz. Number of PRBs will be automatically derived.
common_scs: 15 # Subcarrier spacing in kHz used for data.
plmn: "00101" # PLMN broadcasted by the gNB.
tac: 7 # Tracking area code (needs to match the core configuration).
pdcch:
common:
ss0_index: 0 # Set search space zero index to match srsUE capabilities
coreset0_index: 12 # Set search CORESET Zero index to match srsUE capabilities
dedicated:
ss2_type: common # Search Space type, has to be set to common
dci_format_0_1_and_1_1: false # Set correct DCI format (fallback)
prach:
prach_config_index: 1 # Sets PRACH config to match what is expected by srsUE

cu_cp:
inactivity_timer: 7200 # Sets the UE/PDU Session/DRB inactivity timer to 7200 seconds. Supported: [1 - 7200].

log:
filename: /tmp/gnb.log # Path of the log file.
all_level: info # Logging level applied to all layers.
hex_max_size: 0

pcap:
mac_enable: false # Set to true to enable MAC-layer PCAPs.
mac_filename: /tmp/gnb_mac.pcap # Path where the MAC PCAP is stored.
ngap_enable: false # Set to true to enable NGAP PCAPs.
ngap_filename: /tmp/gnb_ngap.pcap # Path where the NGAP PCAP is stored.

I cant open the amf log file, it shows permission denied.

@pgawlowicz
Copy link
Collaborator

you can find logs at /tmp/gnb.log

@sruthi81
Copy link
Author

ok

@sruthi81
Copy link
Author

Screenshot from 2025-01-10 14-43-26
2025-01-10T09:03:01.399720 [PHY ] [W] [ 22.2] Real-time failure in low-phy: Downlink data late for sector 0 and slot 22.2.
2025-01-10T09:03:02.005172 [RF ] [W] Real-time failure in RF: underflow
2025-01-10T09:03:02.382670 [METRICS ] [I] Cell Scheduler Metrics: error_indications=0 mean_latency=6usec latency_hist=[999, 0, 0, 0, 0, 0, 0, 0, 1, 0]
2025-01-10T09:03:03.008283 [RF ] [W] Real-time failure in RF: underflow
2025-01-10T09:03:03.010741 [RF ] [W] Real-time failure in RF: late

@sruthi81
Copy link
Author

Sir,
Please help me to resolve this issue
Thanks

@pgawlowicz
Copy link
Collaborator

please try to run this script:
https://github.com/srsran/srsRAN_Project/blob/main/scripts/srsran_performance

and try again.

@sruthi81
Copy link
Author

Uploading Screenshot from 2025-01-13 10-12-44.png…
Sir, is it correct?

@sruthi81
Copy link
Author

Screenshot from 2025-01-13 10-12-44

@sruthi81
Copy link
Author

same result I got after running the script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants