• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 258 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1352R: Sometimes high power consumption in orphan mode

Marijn Achterkamp
Expert 1460 points
Part Number: CC1352R

We have an issue where devices do not seem to do behave well in orphan mode.

When I shut down the gateway, normally the device goes into orphan mode waking up every 5 minutes and do an orphan scan.

But sometimes the device just doe not go into low power mode and stays active all the time. I measured this with a power analyzer and it keeps drawing 5mA forever, quickly draining the battery this way.

We use beacon mode for our network. Also I see that the orphan scan is trying to scan all channels although only one channel is needed (the configured channel).

  • 0
    Expert 1460 points

    From looking in the code I got another question.

    Why do I need to do an orphan scan at all? Can't I just do a sync request every 5 minutes to reestablish a connection?

  • 0
    TI__Genius 14845 points

    Hi Marijn, 

    In order to help you resolve this issue, I need some more information on what SW and HW you are using. Please share as much information as you can including:

    Are you using a Launchpad or a custom board?

    Which version of the SDK are you using? 

    Which application are you basing your SW on and what changes have you made?

    Please also share any log files you have, including the power analyzer measurements that you discussed in your post.

    Thanks, 
    Elin

  • 0 in reply to Elin W
    Expert 1460 points

    Hi,

    We run on a custom board with firmware based on dmm_sensor_remote_display_oad from SDK3.40.

    Can I DM you with more details?

    thanks,

    Marijn

  • 0 in reply to Marijn Achterkamp
    Expert 1460 points

    Also, can you comment about the need for orphan scan?

    in the docs there is no mention of orphan scan for beacon mode, only for non-beacon mode.

    What is the best way to reconnect to the network once the gateway is 'temporarily' shut down?

  • 0 in reply to Marijn Achterkamp
    TI__Guru* 82271 points

    Hi Marijn,

    You can do a sync request ever 5 minutes instead of going into orphan mode if it suits your use-case better. You are correct that orphan mode does consume a lot of power.

    I think you will probably know best what works for you. The reason why we implemented orphan mode was to make sure the node rejoins the collector as soon as possible.

  • 0 in reply to Marie H
    Expert 1460 points

    Hi Marie,

    I implemented the sync request every 5 min and in works as far that it does a succesful syncrequest and receives a beacon again when I have restarted the collector.

    However in the beaconNotifyIndCb there is a check done on the APIMAC_SFS_ASSOCIATION_PERMIT which is normally off on a formed network. Due to this check the 

    ApiMac_mlmeSetReqBool(ApiMac_attribute_autoRequest, true); is not set so although it has succesfully resync on the beacons and can transmit messages again. It does not respond to received messages this way. I'm wondering if this implementation from TI is correct according to spec and how I best solve this issue.

    I can of course ignore this check but probably it has side effects and might not be according to spec.

    The docs don't mention how this should be implemented.

    How should a resync be properly implemented?

  • 0 in reply to Marijn Achterkamp
    Expert 1460 points

    any update on this question?