search

srsran / srsRAN_4G

Open source SDR 4G software suite from Software Radio Systems (SRS) https://docs.srsran.com/projects/4g
https://www.srsran.com
GNU Affero General Public License v3.0
3.49k stars 1.15k forks source link

srsue can't attach to srsran network using bladeRfx40 frontend #1148

Open Egwel opened 1 year ago

Egwel commented 1 year ago

Issue Description

[Attach failed]

Setup Details

device: Ubuntu18.04 srsepc and srsenb: bladeRFx40 srsue: bladeRFx40

Expected Behavior

I expect the srsue to attach to the network

Actual Behaviour

Attach failed attempt(1/5)

enb log file 2023-04-12T14:23:02.958498 [ENB ] [I] Using binary srsenb with arguments: --rf.device_name bladeRF 2023-04-12T14:23:02.999087 [ENB ] [I] Built in Release mode using commit 5a4eb5d6c on branch master. 2023-04-12T14:23:03.047662 [COMN ] [D] [ 0] Opened SCTP socket=8 2023-04-12T14:23:03.047671 [COMN ] [D] [ 0] Setting RTO_INFO options on SCTP socket. Association 0, Initial RTO 3000, Minimum RTO 1000, Maximum RTO 6000 2023-04-12T14:23:03.047675 [COMN ] [D] [ 0] Successfully bound to address 127.0.1.1:2152 2023-04-12T14:23:03.047677 [COMN ] [D] [ 0] Setting SCTP_INITMSG options on SCTP socket. Max attempts 3, Max init attempts timeout 5000 2023-04-12T14:23:03.047687 [COMN ] [D] [ 0] Successfully bound to address 127.0.1.1:0 2023-04-12T14:23:03.047692 [COMN ] [D] [ 0] RxSockets: socket fd=7 has been registered. 2023-04-12T14:23:03.051288 [COMN ] [D] [ 0] RxSockets: socket fd=8 has been registered. 2023-04-12T14:25:32.945576 [COMN ] [D] [ 0] RxSockets: Closing rx socket handler thread 2023-04-12T14:25:32.947310 [COMN ] [D] [ 0] RxSockets: closed. 2023-04-12T14:25:32.947427 [COMN ] [D] [ 0] Socket=8 was closed. 2023-04-12T14:25:32.953779 [COMN ] [D] [ 0] Socket=-1 could not be closed. 2023-04-12T14:25:32.954935 [COMN ] [D] [ 0] Socket=-1 could not be closed.

The srsue log file 2023-04-12T11:19:33.004544 [UE ] [I] Using binary srsue with arguments: --rf.device_name bladeRF 2023-04-12T11:19:34.292402 [UE ] [I] Built in Release mode using commit 5a4eb5d6c on branch master. 2023-04-12T11:19:34.550017 [STCK ] [E] Unknown PCAP option true 2023-04-12T11:19:35.306403 [PHY ] [W] [ 33] SYNC: radio time seems to be going backwards (rx_time=0.024460, tti_ts=0.140761) 2023-04-12T11:19:35.457575 [MAC ] [W] [ 4514] RA response not received within the response window 2023-04-12T11:19:35.477578 [MAC ] [W] [ 4534] RA response not received within the response window 2023-04-12T11:19:35.497540 [MAC ] [W] [ 4554] RA response not received within the response window 2023-04-12T11:19:35.517542 [MAC ] [W] [ 4574] RA response not received within the response window 2023-04-12T11:19:35.537469 [MAC ] [W] [ 4594] RA response not received within the response window 2023-04-12T11:19:35.557556 [MAC ] [W] [ 4614] RA response not received within the response window 2023-04-12T11:19:35.577600 [MAC ] [W] [ 4634] RA response not received within the response window 2023-04-12T11:19:35.597483 [MAC ] [W] [ 4654] RA response not received within the response window 2023-04-12T11:19:35.617471 [MAC ] [W] [ 4674] RA response not received within the response window 2023-04-12T11:19:35.637500 [MAC ] [W] [ 4694] RA response not received within the response window 2023-04-12T11:19:35.637502 [MAC ] [E] [ 4694] RA: Rx: Maximum number of transmissions reached (10) 2023-04-12T11:19:35.637503 [RRC ] [W] MAC indicated RA problem but either T300, T301, T304 or T311 is running. Ignoring it. 2023-04-12T11:19:37.432537 [RRC ] [W] Proc "Connection Request" - Timer T300 expired: ConnectionRequest timed out 2023-04-12T11:19:37.432615 [RRC ] [W] Could not establish connection. Deallocating dedicatedInfoNAS PDU 2023-04-12T11:19:50.362060 [NAS ] [W] Timer T3410 expired after attach attempt 1/5: starting T3411 2023-04-12T11:20:00.361049 [PHY ] [W] [ 8952] SYNC: TTI jump of 125452 limited to 1000

The log files tell me that RAR cannot transmit in this window

Steps to reproduce the problem

The following are the configuration files for epc, enb ,ue and their log files srsran_conf_log_files.zip

Additional Information

[Any additional information, configuration or data that might be necessary to reproduce the issue]

N2WU commented 1 year ago

How is the UE clocked? A 10MHz PPS or gpsdo? Many of the problems with USRPs that encounter similar errors are fixed by adding an external clock to both the enb and ue.