Most Frugal for a 30s https post

Hi Mike,

Have you seen this page - http://processors.wiki.ti.com/index.php/CC32xx_Power_Management_Framework

Glenn.

In particular check out the following section:-

Recommendations for use of PM framework

Choice of low power mode

Some of the key considerations for the choice of the low power mode can be the following (These are generic suggestions only):

No activity duration

           No activity duration - Order of minutes - Choose HIB

           No activity duration - Order of seconds - Choose LPDS

           No activity duration - Order of milliseconds - Choose Deepsleep/Sleep

--------

Going by the above recommendations, it looks like LPDS would be the right choice for your use case.

And yes, I know this is written for the CC3200 and you are using the CC3100, but according to the data sheet, the CC3100 does include the Power Management Subsystem which supports LPDS (Low Power Deep Sleep). I am not exactly sure how you would go about implementing this, perhaps someone from TI can assist.

From a power saving perspective, your HOST MCU is going to be a significant consideration, and using the CC3200 which combines the MCU and WIFI would likely provide the best results for a frugal design.

Glenn.

Thanks Glenn, 

At the moment I'm more concerned with getting the module to shut down to a sensible current level first, we've isolated all the host MCU stuff so we're just measuring the CC3100 and when connected to an AP but not doing anything (but with SL_LONG_SLEEP_INTERVAL_POLICY and 2s max sleep) its sitting at over 300uA average..

Mike

Have you looked into the nwp_power_policy example that comes with the CC3100 SDK. There is also a pdf in the Documents folder of the SDK which explains some more details on each of the policies and their requirements.

As another suggestion, try the other policies to see if there is any change in power consumption.

Glenn.

Glenn,

Thanks for the response.

Mike,

Can you please share details how you are measuring the current numbers you shared (tool used, configurations on device)?

Regards,
Ankur

Sure, we're using an agilent N6705B analyzer, powering the CC3100BOOST on the VCC jumper of J6...

retVal = sl_WlanPolicySet(SL_POLICY_CONNECTION, SL_CONNECTION_POLICY(0, 1, 0, 0, 0), NULL, 0);
retVal = sl_WlanProfileDel(0xFF);
retVal = sl_NetCfgSet(SL_IPV4_STA_P2P_CL_DHCP_ENABLE, 1, 1, &val);
configOpt = SL_SCAN_POLICY(0);
retVal = sl_WlanPolicySet(SL_POLICY_SCAN, configOpt, NULL, 0);
retVal = sl_WlanSet(SL_WLAN_CFG_GENERAL_PARAM_ID, WLAN_GENERAL_PARAM_OPT_STA_TX_POWER, 5, (unsigned char *) &power);
unsigned short PolicyBuff[4] = { 0, 0, 2000, 0 }; // PolicyBuff[2] is max sleep time in mSec
retVal = sl_WlanPolicySet(SL_POLICY_PM, SL_LONG_SLEEP_INTERVAL_POLICY, (unsigned char *) &PolicyBuff[0], sizeof(PolicyBuff));
retVal = sl_NetAppMDNSUnRegisterService(0, 0);

Hi Michael,

Apologies for the delayed response.

For your use case its better to use SL_LONG_SLEEP_INTERVAL_POLICY with 2 seconds sleep time but please note the internal HTTP server and mDNS will be disable with this policy. Also TCP/UDP server shouldn't be used with this policy.

Regards,
Ankur

Hi Michael,

I hope your query is answered
I am closing this thread, for follow up queries please open a new thread and add a link to this one for reference.

Regards,
Ankur