Hi,
I do not get any neighboring cells reported using this command. Is one particular state required to receive information regarding neighboring cells?
-Marius
Hi,
I do not get any neighboring cells reported using this command. Is one particular state required to receive information regarding neighboring cells?
-Marius
Hi, and thanks for all the traces.
We see that the documentation for the command is a bit thin, and are working on improving it.
wgeraedts: In your trace, the first NCELLMEAS is issued while in RRC connected and there are no measured neighbors available thus only own cell is reported.
Second NCELLMEAS is issued while in RRC idle but again no neighbors available.
mschweig: In your trace, there are no mobility SI broadcasted in cell where NCELLMEAS is issued, only SIB1 and SIB2. In this case neighbor measurements are not possible.
And for completeness, in my test the first NCELLMEAS is issued while UE is in RRC connected mode and connected mode measurements are not configured. Results are available only from own cell.
Second NCELLMEAS is issued while UE is in RRC idle but mobility is not configured on cell by network (only SIB2 scheduled). Neighbor measurements are not possible, thus results are available only from own cell.
Ok, thanks for the information.
I have another question regarding the neighboring cell IDs. For the Location APIs there is the E-UTRAN cell ID, MCC, MNC required. However, NCELLMEAS only returns physical cellID of neighboring cells. How can this be used for Location APIs?
Thanks.
Kind regards,
Manuel
In the webinar Nordic used the API's from the following thread: devzone.nordicsemi.com/.../webinar-on-nrf9160-modem-fw1-3-0
In the webinar Nordic used the API's from the following thread: devzone.nordicsemi.com/.../webinar-on-nrf9160-modem-fw1-3-0