CCS/CC1350: Power consumption in orphan state too high

The thread is pretty old and use obsolete SimpleLink SDK ver. 2.10.00.36. Do you try this with latest SDK simplelink_cc13x0_sdk_3_20_00_23?

Hi, Yes it is with the current 3.20 SDK

Any update on this? Are there settings I can try?

Apologies for the late response, have you tried removing BOARD_DISPLAY_USE_UART and adding POWER_MEAS inside sensor.opts?

Regards,
Ryan

Hi,

Thanks for the response.

BOARD_DISPLAY_USE_UART is disable already.

POWER_MEAS, I'm not sure what it is supposed to do.

I have not enabled it but I can try. The only part in code where it is used is in sensor.h

#ifdef POWER_MEAS
/*! Power Measurement Statistics */
 extern Smsgs_powerMeastatsField_t Sensor_pwrMeasStats;
#endif

and sensor.c

        if((reportingInterval < MIN_REPORTING_INTERVAL)
           || (reportingInterval > MAX_REPORTING_INTERVAL))
        {
            stat = Smsgs_statusValues_partialSuccess;
        }
        else
        {
#ifndef POWER_MEAS
            configSettings.reportingInterval = reportingInterval;
#endif
            {
                uint32_t randomNum;
                randomNum = ((ApiMac_randomByte() << 16) +
                             (ApiMac_randomByte() << 8) + ApiMac_randomByte());
                randomNum = (randomNum % reportingInterval) +
                        SENSOR_MIN_POLL_TIME;
                Ssf_setReadingClock(randomNum);
            }

        }

I do not see directly how it helps the high power consumption in sync loss state...

Will give it a try nevertheless

Thank you for the details Marjin, I have replicated this behavior and am having the Software Development Team further investigate.

Regards,
Ryan

Good to hear that it is indeed a bug. Hope to hear for a solution soon.

Thanks!

Hi Ryan,

Can you give me an update on the status of this issue?

best regards,

Marijn

Hi Marjin,

The Software Development Team is still working to identify and resolve the issue.  It is not expected that a solution will not be found in time for the SIMPLELINK-CC13X0-SDK v3.30 release but a workaround will be provided as soon as possible.

Regards,
Ryan

Thanks Ryan!

A workaround for the time being would work fine for us.

Best,

Marijn

I see in the 3.30 release changelog that the bug is indeed not fixed yet and put on the known issues list. 

Is there a workaround available already that we can test/use?

Resolution has been delayed due to preparing for release of the v3.30 SDK.  Now that this has passed the R&D Teams are focusing on addressing this issue and will provide a workaround as soon as possible.  Thank you for your patience during our continued efforts to improve the stack quality.

Regards,
Ryan