• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 362 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.

LAUNCHXL-CC1352R1: Sleepy mode in practice with Sensor example

andres_dalmati
Expert 1110 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: ENERGYTRACE

Hi,

I am working on Launchpad CC1352R1. I imported the sensor example code and I have some doubts.

My configuration is:

-Frequency Hopping
-Sleepy Mode
-Policy Power on
-disabled CUI
-removed all jumpers (including LED jumpers)
-lastest Simplelink  version
-sensor example without any addons

1- I know that the purpose of a Power Policy is to make a decision regarding power savings when the CPU is idle.  When the sensor is Orphan (without connection with collector), shouldn’t it go to sleep since it is “in” an idle task? I'm measuring the current using EnergyTrace and the current isn't "zero".
I made another simple TI-RTOS project and I do have "zero" current when is idle.

2- I read in a e2e post "Also note that FH devices are never sleepy until they've joined a network." Shouldn’t it go to sleep between network scans?
I'm confused between the policy power and the node's sleepy mode.

3- I have already done the power test with both "DATA & ACK" and "POLL & DATA" profiles with zero current as was predicted but the power test exclude readSensors function. Should I simply chance the macro define "POWER_MEAS". How can I send real data anyhow? I can't find a clear explanation about the Power test and its profiles.

Thanks in advance

Andrés

  • 0
    TI__Guru 58425 points

    Hi Andres,

    Could you tell us which SDK version you are currently using?

  • 0
    TI__Guru* 82341 points

    1. In orphan mode the sensor spends most of its time searching for the collector, so it's not idle. 

    2. Yes - sorry this is the distinction between the device going to "sleep" aka standby vs. a sleepy node.

    3. I'm not sure what you asking. If you want to measure the power in a more real context you can simply run your application and measure the power?

  • 0 in reply to Marie H
    Expert 1110 points

    Hi MW

    My version is:




    Hi Marie

    1- 2-

    Watching the RTOS analyzer, I noticed that it spends most of its time idle, is this correct?



     Shouldn’t it go to sleep between network scans (5s)?

    3- I can't find a clear explanation about the Power test and its profiles:
     *POLLING ONLY
     *DATA & ACK
     *POLL & DATA
     *SLEEP

    Thanks in advance

    Andrés

  • 0 in reply to andres_dalmati
    TI__Guru* 82341 points

    Hi Andrés,

    What you are seeing is the scan being scheduled (app task running), then the scan being conducted (mac task running). When scan has finished the results are sent to and processed in the app task.

    Regarding the power test I will try to find some more information and get back to you.

  • 0 in reply to andres_dalmati
    TI__Guru* 82341 points

    Hi Andrés,

    I'm sorry, we don't really have any more documentation.

    You can try looking in the power calculator documentation: 

  • 0 in reply to Marie H
    Genius 5680 points

    Hey andres_dalmati,

    i didnt read the whole thread completely, but if you want the device to be low power inbetween scans in FH mode, set ApiMac_attribute_RxOnWhenIdle to false if you have finished scanning and listening for response. If I remember correctly, the sensor node RX is always on in FH mode until the node has connected to a network.

    best wishes

    Slev1n