• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 710 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.

CC2630: TI-MAC 1.5.2 Simplelink SDK Low-Power mode

user4322441
Prodigy 30 points
Part Number: CC2630


Hello!

I use the CC2630 as the end device and the CC2630 as a coordinator.
I use TI-MAC 1.5.2 Simplelink SDK.

The measuring tool is the ammeter.
the end device is configured as standby mode ,See the following figure:

1-step
when the end device first power on, Before networking,the current moves between 60uA and 1.5mA.

2-step
Then, the coordinator power on，Associated，Power consumption of the end device is shown below:

if not send RF data，the current is 54uA（200uA measuring range for the ammeter ）.

3-step
the coordinator power off， the end device always power on ，Power consumption of the end device is shown below:

the current is above 700uA by little probability（20mA measuring range for the ammeter ）.


4-step
the coordinator power up again， Associated again，the current is above 700uA，Why is the current not 60uA?


5-step
the end device power off and power up again,Power consumption is shown below:

if not send RF data，the current is always 270uA（20mA measuring range for the ammeter ），Why is the current not 60uA?


6-step
If I want to reduce the terminal current to 60uA, I must reburn the program.

Data_LowPower.psd
"P.nbr.RX < 64 " belong to 1-step and 2-step.
"P.nbr.RX > 65 " and "P.nbr.RX <89 " belong to 3-step.
"P.nbr.RX > 90 " belong to 4-step and 5-step.

How do I deal with this problem? It is unavoidable that the power failure of the coordinator and the current rise of the terminal equipment will affect the battery life of the product.

Looking forward to your reply.
Thank you.

  • 0
    TI__Genius 12415 points
    Hi,

    I am looking into this I will let you know as soon as I have found something
  • 0 in reply to Hector_r
    TI__Genius 12415 points

    Hi sorry for the delayed response, this looks like the receiver in the device is not being turned off. Can you try adding the following line of code to turn off the receiver 

     uint_least16_t MSA_ProcessEvent(TimacMSG_MacCbackEvent_t *pMsg)
{
  TimacMSG_MacCbackEvent_t* pData;

...


  case MAC_MLME_ASSOCIATE_CNF:
    /* Retrieve the message */
    pData = (TimacMSG_MacCbackEvent_t *) pMsg;
    
    MAC_MlmeSetReq(MAC_RX_ON_WHEN_IDLE, &msa_MACFalse); //ADD THIS LINE TO TURN OFF THE RECEIVER

...


}