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

Original question:

CC1354R10: Simple Peripheral example & DMM Example

CC1354R10: Idle Mode Current Consumption

RSSATHEESH KUMAR
Prodigy 30 points

Part Number: CC1354R10

We created an EasyLink project on the CC1354R10 and measured the idle-mode current consumption before and after the EasyLink tone transmission (CW Tx). The device draws about 2 mA in idle mode before CW Tx, and about 1.6 mA after CW Tx.

  • 0
    TI__Mastermind 27477 points

    Hi RSSATHEESH,

    Do you have more details about the API calls that you are making? What API calls are you using, and what SDK version? Is the debug probe connected and active while making the measurements ?

    Regards,

    Arthur

  • 0 in reply to Arthur R☑️
    Prodigy 30 points

    Hi  

     I am using simplelink_cc13xx_cc26xx_sdk_8_30_01_01 SDK. refer the below code snippet image. Debug probe is not connected in the device

    My Test. Steps

    Step1: Set the device in Idel mode 

    Step2: Measure the Current Consumptions

    Step3: CW Transmission 

    Step4:  Abort CW Tx after 10 ms

    Step5: UHF Packet Tx using Easy link driver

    Step6: Set the device in Idel mode 

    Step7: Measure the Current Consumptions

    I get around 2 mA consumption in STEP2 & 1.65 mA Current consumption in STEP7

  • 0 in reply to RSSATHEESH KUMAR
    TI__Mastermind 27477 points

    Hi,

    I would advise against trying to control the power state directly, as this is already handled by the RF driver. 

    What happens if instead of Power_releasexXXXX, you use sleep() for the period that you need?

    Regards,

    Arthur

  • 0 in reply to Arthur R☑️
    Prodigy 30 points

      

    Hi i provide the full detail of my test.

    We are testing three main functionalities:
    1) LF reception during Idle mode with a sleep timeout of 40 ms
    2) Battery measurement using a 10 ms CW stress test
    3) UHF packet transmission that includes the LF value and battery measurement, with an option to view this information over BLE

    Step 1: LF Reception in Idle Mode
    1) Disable Standby mode
    2) Enable GLDO (because enabling DCDC introduces LF noise)
    3) Add a 40 ms delay using a semaphore
    4) Disable GLDO
    5) Re-enable Standby mode

    Step 2: Battery Measurement during UHF CW Stress
    1) Enable EasyLink CW Tx
    2) Start the battery measurement task in Sensor Controller Studio
    3) Introduce a 9.5 ms delay inside Sensor Controller Studio
    4) Perform ADC battery measurement
    5) Exit from Sensor Controller Studio
    6) Abort CW Tx

    Step 3: UHF Packet Transmission
    1) Configure EasyLink UHF Packet Tx
    2) Transmit UHF packet and BLE data containing the LBI (battery) value and received LF ID
    3) Close the RF handle

    Current consumption Test Results
    1) LF processing current: ~1.6 mA
    2) Battery measurement under UHF CW stress
    3) UHF Packet transmission
    4) LF processing current ~2 mA

    Why my device takes 2 different consumptions in Idle mode?

  • 0 in reply to RSSATHEESH KUMAR
    TI__Mastermind 27477 points

    Hi RSSA,

    The problem most likely lies at Step 2. Are you actually using Sensor Controller Studio in Task Testing mode for that? This will turn on the JTAG power domain, and increase power consumption subsequently: https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/8.31.00.11/exports/docs/drivers/doxygen/html/_power_c_c26_x_x_8h.html#acaed4f189f650d485596cd173016ca1b

    Regards,

    Arthur