-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Does nr_cell_search_rf work for band 28? #1404
Comments
I would try running with
|
Looks like this is broken - badly. nr_cell_search_rf gives me the same error as the OPs for every band other than 78. And even for 78, it doesn't seem to scan the actual band but just goes up from 3.3 GHz until I kill it after passing 6 GHz... n78 should go from 3.3 - 3.8 GHz. Perhaps this is operator error - but in the absence of any kind of documentation on this tool other than -h, I really hope the devs chime in here and either fix it or can elaborate what we're doing wrong. |
Issue Description
I would like to scan band 28 using nr_cell_search_rf.
Expected Behavior
Get an output similar to cell_search:
Actual Behaviour
Steps to reproduce the problem
./nr_cell_search_rf --bands 28 --rf.device_name uhd --rf.device_args "type=b200, serial=xxxx" --rf.log_level info --log_level info --rf.rx_gain 50
Additional Information
I don't understand why the central frequency is initialized to 0. I also tried to put it as a parameter and to use the value 780.5MHz as the downlink frequency range for band 28, which goes from 758 MHz to 803 MHz. I have checked that the SSB frequencies calculated for this band are correct following TS38.104 Table 5.4.3.1-1. Could someone help me? I would also be grateful if someone could suggest other ways of scanning this band using software. Thank you all!
The text was updated successfully, but these errors were encountered: