ESP8266 Community Forum

- Mon Apr 18, 2016 8:50 am #45710 So like have a new 'autorun' comand that is inserted at the beginning of a script when wanted?

"autorun" to be selected only when the program has been debugged.

... but thinking about it, perhaps might be better to have a 'no_autorun' instruction instead, to offer the new option while still maintaining backwards compatability?

It would avoid people having to modify all their existing scripts in order to make them autorun as before.

Where to get modules?

https://www.banggood.com/custlink/KvGGhGF4wG

- Mon Apr 18, 2016 9:28 am #45715 If autorun would make the program execute immediately upon power up, this would be great for battery operated units. Having to wait the 30 seconds before the default program starts makes battery operation (using sleep) somewhat limited.

Hopefully I assumed correctly what the autorun function is....

- Mon Apr 18, 2016 9:45 am #45718 I was thinking about a new option in the option menu, and not in the script itself.
This could permit also to run immediately the script after startup.
The GPIO0 pin will be the "emergency exit" in case of problem.

- Mon Apr 18, 2016 9:55 am #45720 Yes, that sounds a good idea.

I'm not sure if it would make much difference with your startup delay though viscomjim, cos I suspect most of that may be due to the time it takes the ESP to wake up and get out of bed , even before it starts thinking of what clothes to wear... so I think the biggest delay is re-negotiating the connection before it can do much else.

Where to get modules?

https://www.banggood.com/custlink/KvGGhGF4wG