We are using bc66 and capturing cell Id of the serving cell to locate the approx location of the device.
I am considering ways to improve accuracy including whether the bc66 can identify all cell towers.
I am using quecooen.
Methods,
So I know I could limit the band, and see whether I can connect and transmit a message. Will qeng etc be updated for cells that aren’t on my sim? I.e. If I use at&t will bc66 on report at&t cells? Or will I get a connection error but hopefully qeng will update?
It seems at commands qeng I think it is has neighbouring PCI…
Is there a way to make the network registration process continue looking for more cells?
I think perhaps I am asking too much of NB iot nb1 and this perhaps an lte-m use case.
@Abner-Q, AT+QENG=0 does report neighbor cells PCI, at least that’s how they are called in +QENG: 1 message description. But, in normal usage, I don’t get any reported. Only when I disable PSM and keep the module in RRC idle state for some time (at least a few minutes) I get some cells reported.
@rastik thanks so much for testing. I think that is expected behaviour, that NB iot only does cell measurements in idle state (and perhaps on "first connection before PSM)… based on a rather brief read of the 3gpp spec.
What I am finding is my devices seem to switch between two base stations after every exit from psm. There isn’t much delay, so I don’t think PSM wake-up is failing (debug also confirms this) and in my head I thought the device would always use the last know cell tower?!
@James_Hillman I always thought so as well, but my experience shows that sometimes the module selects different cell. I don’t know the reason for that.