ESP8266 Community Forum

- Sun Apr 24, 2016 4:13 pm #46104 I don't know how you're going to transfer data to somewhere (even in AP mode) without associating with an other station.
And since coming from deep sleep, this is a new associating attempt each time the esp comes up.

- Fri Jun 10, 2016 10:46 am #48939

Barnabybear:
Thanks your experience sharing and suggestion.
Doubling the working clock may be a viable way to accelerate the boot up speed. I prefer to treat it as the last sort to use due to the possible consequence of instability and more power consumption.

torntrousers:
Yes, I am using WiFi with AP mode. So, there would not have something like "time to connect to AP". With AP mode, I
think ES8266 can send a packet ASAP.
I try to use different values of system_deep_sleep_set_option(n). It shows 0,1,2 having a latency 250ms and 4 have 300ms.
Weirdly, disabling wifi takes more time than enabling it. Since this is not my case, I don't dig deep.


As I saw on some Google searches, the alleged "Wake up and transmit packets in < 2ms" is not positive answered by official forum. So, maybe this is the result under extremely optimized configuration.

My tests have the same results, ESP8266 need about 230ms before I can send raw package using wifi_send_pkt_freedom.
To make it worse, I found I need delay 100ms after call: system_deep_sleep(1000*1000*5); otherwise, it won't go into deepsleep.
Do you have similar problem?

Make something useful. 'Eat your own dog food' DevKit for IoT.
http://www.nodeusb.com