PSM active time not Correct

[Hkhan7861]

Good Day

I have enabled power saving on my nrf9160dk and am using NBIOT.  In doing so I found that there was a 60 sec offset to what I selected and what I wanted the active time to be.  IN doing some research I came across this question :  https://devzone.nordicsemi.com/f/nordic-q-a/87330/nrf9160-not-setting-requested-active-time 

The device is probably stuck in RRC idle for 60s before entering power saving mode.  This answer was never really solved and wanted to know if anybody found a way around this or if I will have to contact my provider?  If so, what would i need them to changed?

Kind regards,

Hassan

[Achim Kraus]

> In doing so I found that there was a 60 sec offset

How did you found that? Using %XMONITOR ? And which active time did you test?

If not already done, please test with a active time of 0s "00000000" and use %XMONITOR after registered to the network. If that reports the "00000000" at the active time position, almost everything is right.

The next question then is more, why your device doesn't enter the sleep mode.

One idea would be nRF9160-DK - sometimes busy for 1 minute before entering PSM .

So, is your device in "roaming"? Do you have the 60 sec offset always or just sometime (always => other issue, sometimes, then it may be related to the HPPLMN search.

[Hkhan7861]

HI Achim

I tested a 0s active time and the %XMONITOR command shows a 0s active time.  The offset happens consistently.  I haven't had any occasions where the offset is any less.  I suspect it is similar situation to the link I added.  My device is not in roaming as well.

Kind regard,

Hassan

[Hkhan7861]

Also,  I see that I could try using the command  "AT+COPS" in manual selection. However, I would like to do this inside my code.  I know this may a be longshot but if you have done it before could you tell me what could possibly be wrong.

nrf_modem_at_cmd(response2, sizeof(response2), "AT+COPS=1",2,"REDACTED");

        

[Achim Kraus]

> My device is not in roaming as well.

If that's the case, then a HPPLMN search should not be the issue.