Is there a way to find you the reason for RRC Connect?
I'm using a simple software developed based on NCS AWS IoT sample. I've implemented the SW to test power consumption in different modem idle modes. The SW updates data to AWS periodically and is idle between update periods. For some reason the SW operates differently using different networks and I don't know why.
I had trouble with PSM earlier as I mentioned in this ticket: https://devzone.nordicsemi.com/f/nordic-q-a/80120/asset-tracker-v2-power-consumption-with-thingy-91
Now I know better and I know how to set appropriate PSM parameters that are accepted by network. The thing that I don't understand is why my device constantly transitions between RRC idle and RRC connected randomly when the device is in DNA network. The same RRC mode toggling is not present in Elisa or Telia networks, in those networks the idle modes work as expected.
In DNA network the device very seldom stays in RRC idle for 60 seconds which is the shortest possible active timer value granted by the network. As a result the modem usually won't go to PSM during the 20 minutes that is the keepalive time for AWS IoT MQTT.
If the modem goes to PSM in DNA network, it stays in PSM until the next periodic data update. Thus I'm guessing the RRC toggling is network (not AWS) originated, but I would like to know if there is something that I can do to prevent the toggling.
I've attached a log file with 2min data update interval. In the beginning of the log there are only application writes. After a reboot there are library debug logs with the following flags:
