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.

CC1312R: Power Consumption

Part Number: CC1312R
Other Parts Discussed in Thread: SIMPLELINK-CC13X2-26X2-SDK

Hi,

Two questions:

1) I have an application based on the TI15.4 Sensor example. Current consumption after POR is about 3.72mA. After I attempt to join a network, this drops to around 2uA. I have determined that if the mac is asked to scan then the processor will transition to low power mode as required. However, I need this low power state straight out of POR. If I place:

Power_releaseConstraint(PowerCC26XX_SB_DISALLOW);
Power_releaseConstraint(PowerCC26XX_DISALLOW_STANDBY);

At the very top of main() then it will go to low power after POR as required. However, if I wake the processor without calling a mac function then the power returns to 3.7mA, again, till I call a mac scan.

Do you know what can be done to solve this?

*I think that the RF is in SynthAct state on POR, but I am having many difficulties with Energy Trace so this may not be true. It would explain the extra current though.

2) Once the processor is in low power mode I see a pulse every 1s around 200uA. I'd like to know what this is and if this can be disabled.

  • Hi Andrew,

    I have replicated this behavior as well and am investigating whether it is intentional or not.  The pulse you see is for the BOD and cannot be disabled.

    Regards,
    Ryan

  • Hi Ryan,

    Thanks for your reply. The datasheet states an average standby current of 850nA (internal RC LPOSC) which is what I see so the BOD duty cycle is not a problem for me.

    I have thrown in a Jdllc_join(); in my initialisation code which lets the processor sleep after a scan on POR. Obviously this is not ideal, so any findings you have here will be gratefully received.

    Thanks,

    Andy

  • Hi Andy,

    I was mistaken before, the high power consumption I observed earlier was due to the sensor attempting to associate with nearby beacon sources and therefore not allowing the radio to turn off when idle for the CONFIG_SCAN_BACKOFF_INTERVAL duration.

    Does your application not define CONFIG_AUTO_START?  This would automatically set the SENSOR_START_EVT which would call Jdllc_join.  Have you tried simply setting ApiMac_mlmeSetReqBool(ApiMac_attribute_RxOnWhenIdle, false);?  Also, what version of SDK are you evaluating?

    Regards,
    Ryan

  • Hi Ryan,

    I had temporarily left this issue awaiting your response. I will look into again. However, I can confirm that ApiMac_attribute_RxOnWhenIdle is set to false on power up. It only becomes set to true when in scan mode. I have modified my sensor code considerably as I have created a router network running on custom hardware. However, I thought I saw the same issue running the original sensor code on a CC1312R Launchpad, but I will re-check and give you an update.

    Thanks,

    Andy

  • Hey Andy,

    You may want to reduce your channel options in CONFIG_CHANNEL_MASK to avoid the same issue I was experiencing.  Are you using the SIMPLELINK-CC13X2-26X2-SDK?

    Regards,
    Ryan

  • Hi,

    I have only one channel enabled so I can sniff.

    Yes, I am using the second to latest simplelink SDK.

    I plan to investigate this again on Monday starting with the sensor example on a Launchpad.

    Regards

    Andy

  • Hi Andy,

    While re-investigating please consider the SIMPLELINK-CC13X2-26X2-SDK v3.20 as well and let me know what you find.

    Regards,
    Ryan