ESP8266 Community Forum

- Wed Oct 04, 2017 9:33 am #70591 I would just utilize delay (0) which is functionally equivalent to yield ()
Unless the 10mS delay is actually required,

For example, the 1mS is necessary in the code below:

/* Initializations */
// ------------------begin ESP8266'centric----------------------------------
WiFi.forceSleepBegin(); // turn off ESP8266 RF
delay(1); // give RF section time to shutdown
system_update_cpu_freq(FREQUENCY);
// ------------------end ESP8266'centric------------------------------------


I have a few other ESP8266 projects over on my page:
https://www.hackster.io/rayburne/projects


Ray

- Thu Oct 05, 2017 10:44 am #70613 Whenever possible, use delays based on interrup timer rather than closed loop "delay(value)" implementations.

"part of the world that you live in, you are the part that you're giving" - Renaissance

- Thu Oct 05, 2017 12:40 pm #70615

Whenever possible, use delays based on interrup timer rather than closed loop "delay(value)" implementations.

No.
The entire purpose of yield () or delay (0) is to provide a release of the Arduino thread so that non-OS can have some cpu time. There is no benefit in this case of interrupt-timed pauses.

Ray

- Thu Oct 05, 2017 5:33 pm #70621

No.
The entire purpose of yield () or delay (0) is to provide a release of the Arduino thread so that non-OS can have some cpu time. There is no benefit in this case of interrupt-timed pauses.

I wonder how one could implement a longest delay by using the suggested structure with argument 0.
Interrupt-based delay is allways the better choice, since this way can use a time slot to split the tasks into specific time alocation.

"part of the world that you live in, you are the part that you're giving" - Renaissance