I'm testing the powersave and deep sleep function on the QuickSilver evaluation board and I'm getting deceiving result.
I'm wondering if I'm doing thing wrong.
For now i've tested the powersave and deepsleep snippet that is included in the WICED SDK. And I'm measuring the current draw with a multimeter inline with the USB port. So every measurement is done at 5V level.
With the "snip.ping_deepsleep-Quicksilver_EVL download run" :
I'm getting 220 mA down to 180 mA in deepsleep.
With the "snip.ping_powersave-Quicksilver_EVL download run"
I'm getting 190 mA in powersave and 210 mA in ping .
and for comparaison with "snip.uart-Quicksilver_EVL download run" I get 190 mA.
In WICED Studio under the Project Explorer tab, go to the doc directory. Right click on the API.html file and choose open with System Editor. This will open the WICED™ 6.2.1 - API Reference Guide. In the guide under the WICED Documentation section, click to open the WICED Power Save Application Note. This App Note provides some good information on the low power modes of the WICED devices.
You can use the wiced_deinit() function as described in Section 2.1 of the App Note to cut power to the WiFi chip to see the current draw of the module vs current draw of the entire board.
In the ping_powersave.c file, on line; 76 #define WIFI_SLEEP_TIME (1000 * MILLISECONDS), change the value from 1000 to 10,000 or greater to ensure your power measurements are accurate. 1 second may not be enough time for your multi meter to settle in and give an accurate measurement whereas 10+ seconds will eliminate this possibility.
Keep in mind your current measurements include all of the parts on the board including some things you may not want to use in a product if you are concerned about current consumption, such as the FTDI, RGB LED, and Ethernet sections.