Boot time very high

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
moebius
Normal user
Posts: 35
Joined: 22 May 2017, 19:36

Boot time very high

#1 Post by moebius » 25 Feb 2018, 18:21

On a Wemos D1, the time from a warm reboot until the device outputs a pwm signal is app. 5 seconds.
The pwm signal is defined with this rule:

on System#Boot do
PWM,14,450,3000
endon

This is way too much to use it for a light.
The normal boot time of an esp8266 is around 300ms - why does it take so long with espeasy?

Micha_he
Normal user
Posts: 143
Joined: 07 Feb 2018, 19:14
Location: Helmstedt, Germany

Re: Boot time very high

#2 Post by Micha_he » 25 Feb 2018, 18:32

Maybe DHCP?

Domosapiens
Normal user
Posts: 307
Joined: 06 Nov 2016, 13:45

Re: Boot time very high

#3 Post by Domosapiens » 25 Feb 2018, 18:35

Talking about an official Wemos D1 or a fake ?
This is the official:
5-Stks-partij-D1-mini-Mini-Voor-NodeMcu-4-M-bytes-Lua-WIFI-Internet-van-Dingen.jpg
5-Stks-partij-D1-mini-Mini-Voor-NodeMcu-4-M-bytes-Lua-WIFI-Internet-van-Dingen.jpg (125.24 KiB) Viewed 2768 times
From here https://nl.aliexpress.com/item/5PCS-lot ... Title=true
See the branding on the chip and board.

I have 2# "fake" Wemos D1 boards, without branding with a lot of problems:
- overly power hungry
- weak WiFi connection
- large start-up time

My other 10+ Wemos D1's (with branding) don't have that problem.
30+ ESP units for production and test. Ranging from control of heating equipment, flow sensing, floor temp sensing, energy calculation, floor thermostat, water usage, to an interactive "fun box" for my grandson. Mainly Wemos D1.

moebius
Normal user
Posts: 35
Joined: 22 May 2017, 19:36

Re: Boot time very high

#4 Post by moebius » 25 Feb 2018, 19:20

Don't know if it's fake, so let's assume it is...but with none of your problems (wifi connection, power consumption (i dont use the onboard regulator)).

I have also some nodemcu boards - i will check, if there is any difference...

My guess would also be, that espeasy does the startup task only after everything else is up (wifi + dhcp, maybe mqtt connection,...)
But for "switched on" devices, this is way too long...i'm wondering that nobody else has this probem, so maybe it's really the board.

moebius
Normal user
Posts: 35
Joined: 22 May 2017, 19:36

Re: Boot time very high

#5 Post by moebius » 25 Feb 2018, 21:44

I've tested now with a nodemcu board and nothing changed...

But the log showed clearly where the time has gone:

Code: Select all

349 : EVENT: System#Boot
380 : ACT : PWM,14,450,3000
3491 : SW : GPIO 14 Set PWM to 450
4463 : WIFI : AP Mode disabled
4464 : WIFI : AP Mode ssid will be laserbeam_55 with address 192.168.4.1
4464 : WIFI : Connecting Portal attempt #1
8282 : WIFI : Connected! IP: 192.168.4.211 (laserbeam_55)
8347 : MQTT : ClientID laserbeam55 connected to broker
8352 : Subscribed to: laserbeam/#
This is the log with a modified espeasy.ino, where i moved the network initialization behind the plugins and rules processing. Otherwise the event and act entries show up after the subscribed entry (8 seconds later in this case).
Now the esp acts like a microcontroller and not win95 :)

I think this should be the default behavior.

User avatar
grovkillen
Core team member
Posts: 3603
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Boot time very high

#6 Post by grovkillen » 25 Feb 2018, 21:53

Please report to Github.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

Post Reply

Who is online

Users browsing this forum: No registered users and 24 guests