Nrf9160 not setting requested active time

Good day I am wondering if you can help me.

For background information.

Network - NB-iot

Firmware -  1.3.1

Software - Serial LTE Modem

Hardware - nrf9160dk

I am trying to set the requested active time down so that when I go into idle to save power and keep my IP connection that the modem doesn't stay active for 60 seconds there after.

The device is going into low power mode but only after 60 seconds. 

I will attach a screen shot of the AT-commands that I take to get to the point where I'd like to go into low power but the Requested Active Time does not change.

I came across this following link while attempting to get my power consumption down.

(+) turn off active time and go directly to power save mode - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

I tried the command AT+CPSMS=1,"","","10101010","00000000" to set the periodic TAU to 10 minutes and the requested active time to 0 and to 2 (00000001) seconds.

But they had no influence on the 60 seconds of high power consumption after issuing the AT#XSLEEP=2 to put the system into idle.

If anyone has any input as to where I am going wrong I will greatly appreciate it.

Parents
  • Hello Pieter,

    first of all, my apologies for the delayed reply. I have been out of office for the last couple of days.

    PieterK said:

    If not please let me know then I will do it again.

    I am very new to the nr9160 family but I am slowly getting the hang of it.

    No worries, we will do this step by step :-)

    PieterK said:
    I hope they have been done correctly, This is the first time that I use the trace tool.

    Unfortunately, something went wrong during the record, as I mostly see errors in the modem trace.



    But we actually do not have to start with that, an application log should be enough for the moment. Below you can find an example from the AT Client, which I control using a serial terminal.

    *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
    The AT host sample started
    AT+CEREG=5
    OK
    AT%CESQ=1
    OK
    AT%XMODEMSLEEP=1,1000,60000
    %XMODEMSLEEP: 4
    OK
    AT+CFUN=1
    %XMODEMSLEEP: 4,0
    OK
    %CESQ: 56,2,23,3
    +CEREG: 2,"7AA9","01444000",7
    +CEREG: 1,"7AA9","01444000",7,,,"00001010","11000001"
    %CESQ: 255,0,255,0
    %XMODEMSLEEP: 1,1151979975

    Regards,

    Markus

Reply
  • Hello Pieter,

    first of all, my apologies for the delayed reply. I have been out of office for the last couple of days.

    PieterK said:

    If not please let me know then I will do it again.

    I am very new to the nr9160 family but I am slowly getting the hang of it.

    No worries, we will do this step by step :-)

    PieterK said:
    I hope they have been done correctly, This is the first time that I use the trace tool.

    Unfortunately, something went wrong during the record, as I mostly see errors in the modem trace.



    But we actually do not have to start with that, an application log should be enough for the moment. Below you can find an example from the AT Client, which I control using a serial terminal.

    *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
    The AT host sample started
    AT+CEREG=5
    OK
    AT%CESQ=1
    OK
    AT%XMODEMSLEEP=1,1000,60000
    %XMODEMSLEEP: 4
    OK
    AT+CFUN=1
    %XMODEMSLEEP: 4,0
    OK
    %CESQ: 56,2,23,3
    +CEREG: 2,"7AA9","01444000",7
    +CEREG: 1,"7AA9","01444000",7,,,"00001010","11000001"
    %CESQ: 255,0,255,0
    %XMODEMSLEEP: 1,1151979975

    Regards,

    Markus

Children
Related