Closed Shik-shik closed 4 years ago
Default config files for bladeRF x40 result to RLF. after community request, other configuration was given for test:
still it is not best option (RRC connected after several attempts). But it gives sufficient information for further improvement/debug.
Appreciate for help from community members. Many thanks to justin.tallon@softwareradiosystems.com.
Issue can be closed. After stable RRC from first attempt, config info will be updated.
@Shik-shik thank you for your issue. I set the same properties when i use limesdr as the rf end at ue and enb. it is successful for ue to attach lte network. ue and enb are connected for at most 10minutes. It is much longer than before when i use the default .conf files(dl_earfcn=3400,prb=50). But i dont know why the max online time for ue is no more than 10 minutes. Could you give some comments about how to find the exact properties for the ue and enb to make them always connected? Or Do you have any information for further improvement and debug it? Thank you so much for your help and your posted issue.
Before filing an issue, search for solutions here:
Issue Description
Setup Details
e.g. Network configuration, Operation System, Hardware, RF front-end, library and driver versions
CPU: I7-3630QM; Linux: Ubuntu 18.04; RF: bladerf x40 (both enb and ue) driver/library: $ bladeRF-cli -i --lib-version 2.2.0-2018.12-rc3-2-ppabionic
Expected Behavior
successfull RRC connection setup following with ATTACH procedure
Actual Behaviour
Failed RRC due to timer expire: 14:57:35.735166 [RRC ] [W] Proc "Connection Request" - Timer T300 expired: ConnectionRequest timed out
Steps to reproduce the problem
kindly ask you to test with bladerf x40 on default values. trying different TX/RX gain may change RSRP and SNR value but Radio-Link failure remain.
Additional Information
logs from UE and ENB in attachment to this case.
80_after_calibration.zip