Hey All,
Last month a network provider had some internal issues which rapidly started rejecting our devices with several EMM registration issues, however due to not seeing this issue during development the firmware miss interpreted these rejected requests and caused it to rapidly try to reconnect to other cell towers which had the same errors happening. This caused several of our devices to completely drain their batteries within the down period of the network provider.
In our remote logging server we see these errors:
[00:00:09.578,552] <wrn> lte_lc: Registration rejected, EMM cause: 19, Cell ID: xx, Tracking area: xx, LTE mode: 7 [00:00:15.053,863] <wrn> lte_lc: Registration rejected, EMM cause: 11, Cell ID: xx, Tracking area: xx, LTE mode: 7 [00:00:17.210,876] <wrn> lte_lc: Registration rejected, EMM cause: 14, Cell ID: xx, Tracking area: xx, LTE mode: 7
We would like to modify and test our handling of these errors, does the modem provide any way to simulate a faulty network configuration to test these code paths?
We have tried to remove the sim card but this seems to not do any registration requests at all.
Any pointers to how we can test this behavior would be appreciated!
hardware/sw:
NRF connect 2.9
NRF9160 on a custom board
