You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an application that, as part of it's process, raises an ESP8266 module output pin high; the length of time the pin stays high is process dependent. After the process is completed the module goes essentially into hibernation until awakened by an external signal.
I've noticed that after the initial boot-up on power-up the length of time the pin stays high is about twice as long as when a subsequent external signal becomes active. Given that there are a number of "Imports", is the reason the initial power-up lasts longer is that code is initially being imported, but once imported the code runs quicker for subsequent boot-ups?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have an application that, as part of it's process, raises an ESP8266 module output pin high; the length of time the pin stays high is process dependent. After the process is completed the module goes essentially into hibernation until awakened by an external signal.
I've noticed that after the initial boot-up on power-up the length of time the pin stays high is about twice as long as when a subsequent external signal becomes active. Given that there are a number of "Imports", is the reason the initial power-up lasts longer is that code is initially being imported, but once imported the code runs quicker for subsequent boot-ups?
Thanks,
MM
Beta Was this translation helpful? Give feedback.
All reactions