• State Not Answered
  • Replies 1 reply
  • Subscribers 68 subscribers
  • Views 18 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 338789
Options

delay in downlink and FOTA commands

Timothy

We have a production system running a modified asset_tracker_v2. Things are basically running fine but there is question with downlink and FOTA operations. We publish a JSON packet to AWS basically every 15 minutes. This is working fine. The problem is that we have several parameters such as centigrade/Fahrenheit, temperature limits, duty cycle, etc. that are adjustable from the web by a customer on a customer portal. When a customer tries to send a downlink command to the board to change the parameter it is only seen at the board when we do a publish. This could take 15 minutes or whatever time the duty cycle is set to. A non technical customer sets a command to change a parameter and they do not see it for a very long time. The same with FOTA.

How can I set it up so that downlink and FOTA commands are seen quickly (seconds) not many minutes.

Parents
  • 0

    Hi,

    Thank you for reaching out about your application development.

    While I have limited information about your modified asset_tracker_v2, I can provide some general advice. The balance between power consumption and connection availability is adjustable but depends on your application needs. This decision should ideally be made based on your or your customer’s requirements. In extreme cases, if the device is mains powered, it can remain connected continuously(disable PSM and EDRX). If the device is battery-powered, you’ll need to sacrifice availability time and maximize sleep duration to conserve power.

    At the core level, power management is influenced by the following parameters. However, application settings, such as a 15-minute data transmission interval in you application, also play a significant role. When the device wakes to send data, it establishes a connection with the base station and fetches configuration data from the server.

    # LTE link control
    ## Power saving timers.
    ### 320 hours PSM.
    CONFIG_LTE_PSM_REQ=y
    CONFIG_LTE_PSM_REQ_RPTAU="11000001"
    ### 20 seconds active time.
    CONFIG_LTE_PSM_REQ_RAT="00001010"
     
    You need to find a proper balance for your application. Let me know if you need more help.

    Best regards,

    Charlie

Reply
  • 0

    Hi,

    Thank you for reaching out about your application development.

    While I have limited information about your modified asset_tracker_v2, I can provide some general advice. The balance between power consumption and connection availability is adjustable but depends on your application needs. This decision should ideally be made based on your or your customer’s requirements. In extreme cases, if the device is mains powered, it can remain connected continuously(disable PSM and EDRX). If the device is battery-powered, you’ll need to sacrifice availability time and maximize sleep duration to conserve power.

    At the core level, power management is influenced by the following parameters. However, application settings, such as a 15-minute data transmission interval in you application, also play a significant role. When the device wakes to send data, it establishes a connection with the base station and fetches configuration data from the server.

    # LTE link control
    ## Power saving timers.
    ### 320 hours PSM.
    CONFIG_LTE_PSM_REQ=y
    CONFIG_LTE_PSM_REQ_RPTAU="11000001"
    ### 20 seconds active time.
    CONFIG_LTE_PSM_REQ_RAT="00001010"
     
    You need to find a proper balance for your application. Let me know if you need more help.

    Best regards,

    Charlie

Children
No Data
Related