[SOLVED] 7 segment display (4 digit)

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

[SOLVED] 7 segment display (4 digit)

#1 Post by mackowiakp » 12 Jul 2019, 18:42

7 segment, 4 digit display TM1637 based, does not working after SW ver 20190107 test. After installing the newest version of SW, display is shown in device list as disabled. It is possible to enable one manually but it still display nothing and after reboot is again shown as disabled. I wite content of display manually and after reboot should be displayed four minus signs according to rule:

Code: Select all

On System#Boot do
  delay,2000
  7dn,----
  delay,500
 endon
But nothing is display. Is it bug? Any workaround?
Last edited by mackowiakp on 01 Aug 2019, 06:36, edited 1 time in total.

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

Re: 7 segment display (4 digit)

#2 Post by grovkillen » 12 Jul 2019, 21:24

If you type the command in the tools window, does it work then?
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:

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#3 Post by mackowiakp » 13 Jul 2019, 04:54

No, because after boot device is marked in device list as "X" and "Enable" option is not checked. So probably it was not properly initiated during boot time.

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

Re: 7 segment display (4 digit)

#4 Post by grovkillen » 13 Jul 2019, 08:27

Have you re-saved the settings for the plugin after you updated the unit?
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:

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#5 Post by mackowiakp » 13 Jul 2019, 11:09

Yes, of course. It was necessary because - as I wrote - display was disabled aftre reboot. So I click "Edit" on appropriate line in device list, check setup parameters like GPIO`s assignment, mode as manual etc, etc. All setup parameter were ok except that device was disabled. So I mark "Enabled" checkbox and click on "Submit". Pup-up window shows "Submitted" and device was enabled in device list. But nothing was possible to display. So I rebooted device and display was disabled again.

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

Re: 7 segment display (4 digit)

#6 Post by grovkillen » 13 Jul 2019, 13:10

Then it must be something causing the OS to disable the plugin. Can you monitor the serial log?
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:

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#7 Post by mackowiakp » 13 Jul 2019, 13:52

I think yes. Will send You both working SW boot logs and not-working. But can You pass me link how to do it? I have 3,3V UART to USB converter.

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

Re: 7 segment display (4 digit)

#8 Post by grovkillen » 13 Jul 2019, 14:39

You simply plug it in the computer and use a serial monitor. Of you're on Windows you can use the one provided with the Flasher.
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:

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#9 Post by mackowiakp » 14 Jul 2019, 10:14

OK. So You have logs from working and not-working versions of SW. Debug level was set to "dev". Notice that after installing 20190630 the unit reboots itself 12 times and after that it seams to not work. For example no rules run.

Working ver 20190107

Code: Select all

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
vbb28d4a3
~ld
   �U99 : 

INIT : Booting version: mega-20190107 (ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support)
100 : INIT : Warm boot #4 - Restart Reason: Software/System restart
102 : FS   : Mounting...
127 : FS   : Mount successful, used 78312 bytes of 957314
528 : CRC  : program checksum       ...OK
rules1.txt 1
rules2.txt 1
rules3.txt 1
rules4.txt 1
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
state: 3 -> 5 (10)
                  add 0
                       aid 4
                            cnt 

                                connected with maciek24, channel 1
                                                                  ip:192.168.0.29,mask:255.255.255.0,gw:192.168.0.1
                                                                                                                   ip:192.161
                                                                                                                            t
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
pm open,type:2 0
                RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output:
RuleDebug Processing:rules1.txt
     flags CMI  parse output:
RuleDebug Processing:rules2.txt
     flags CMI  parse output:
RuleDebug Processing:rules3.txt
     flags CMI  parse output:
RuleDebug Processing:rules4.txt
     flags CMI  parse output: 
Not working ver 20190630

Code: Select all

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v8b899c12
~ld
   �U66 : 

INIT : Booting version: mega-20190630 (ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support)
67 : INIT : Free RAM:30584
68 : INIT : Warm boot #12 - Restart Reason: Exception
70 : FS   : Mounting...
95 : FS   : Mount successful, used 78312 bytes of 957314
559 : CRC  : program checksum       ...OK

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

Re: 7 segment display (4 digit)

#10 Post by grovkillen » 14 Jul 2019, 10:29

Looks like the log level is set to "none" for the latest version. And the fact that the unit is rebooting 12 times suggest that it's not liking one or more plugins. Could you make sure that the latest version is set to show serial log?
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:

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#11 Post by mackowiakp » 14 Jul 2019, 11:07

After several power reboots, it does not reboot itself 12 times.

Code: Select all

INIT : Booting version: mega-20190630 (ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support)
65 : INIT : Free RAM:30584
66 : INIT : Warm boot #1 - Restart Reason: Software/System restart
69 : FS   : Mounting...
93 : FS   : Mount successful, used 78312 bytes of 957314
558 : CRC  : program checksum       ...OK
And my debug setup.
Screenshot_20190714_105834.png
Screenshot_20190714_105834.png (80.52 KiB) Viewed 4791 times
Last edited by mackowiakp on 14 Jul 2019, 12:22, edited 1 time in total.

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

Re: 7 segment display (4 digit)

#12 Post by grovkillen » 14 Jul 2019, 11:27

Does it stop adding serial output after those 500+ ms?

Could you please set the log level to normal/info and try?
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:

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#13 Post by mackowiakp » 14 Jul 2019, 11:47

Log leve set to "Info"

Code: Select all

 ets Jan  8 2013,rst cause:1, boot mode:(3,6)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v8b899c12
~ld
   �U65 : 

INIT : Booting version: mega-20190630 (ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support)
66 : INIT : Free RAM:30584
67 : INIT : Warm boot #1 - Restart Reason: Software/System restart
69 : FS   : Mounting...
94 : FS   : Mount successful, used 78312 bytes of 957314
559 : CRC  : program checksum       ...OK
Does it stop adding serial output after those 500+ ms?
I really dont know. Simply it stops output.

Additional infos.

It seams to rules starting with "On System#Boot do" does not run with 7 segment display connected.
When unit boot, it is possible to run rule from Domoticz (blinking LED) and it is possible to turn on/off connected relays both using GPIO,13,1 (example) command from "Tools" menu and remotely from Domoticz. Connected temperature sensor sends properly values to Domoticz.
7 segment display is disabled after reboot. But when I enable one manually and enter command "7dn,----" from "Tools" menu, nodeMCU reboots.
Last edited by mackowiakp on 14 Jul 2019, 11:55, edited 1 time in total.

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#14 Post by mackowiakp » 14 Jul 2019, 11:54

UPDATE

Running rule remotely (like blinking LED) and GPIO command from "Tools" menu, is not logged both in "Info" and "Dev" mode.

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

Re: 7 segment display (4 digit)

#15 Post by grovkillen » 14 Jul 2019, 19:51

You haven't got the serial port/communication enabled.
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:

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#16 Post by mackowiakp » 15 Jul 2019, 08:02

OK. You are right. My fault.

Below boot log in "dev" mode. Do not look at the lines:

Code: Select all

6365 : Domoticz Controller: Not yet implemented sensor type: 0 idx: 100
6366 :  Domoticz: Sensortype: 0 idx: 100 values: 
It is generic sensor sending uptime to Domoticz. I simply re-setup this sensor and it start work properly.

Code: Select all

ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v8b899c12
~ld
   �U65 : 

INIT : Booting version: mega-20190630 (ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support)
66 : INIT : Free RAM:30584
67 : INIT : Warm boot #1 - Restart Reason: Software/System restart
69 : FS   : Mounting...
94 : FS   : Mount successful, used 78312 bytes of 957314
559 : CRC  : program checksum       ...OK
596 : CRC  : SecuritySettings CRC   ...OK 
692 : INIT : Free RAM:27472
694 : INIT : SPI not enabled
1562 : INFO : Plugins: 80 [Normal] [Testing] (ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support)
1564 : EVENT: System#Wake
1760 : mode : sta(84:f3:eb:b7:45:42)
                                    add if0
                                           WIFI : Set WiFi to STA
1796 : WIFI : Connecting maciek24 attempt #0
1798 : ip:192.168.0.29,mask:255.255.255.0,gw:192.168.0.1
                                                        IP   : Static IP : 192.168.0.29 GW: 192.168.0.1 SN: 255.255.255.0 DN1
1801 : WIFI : Not configured in Station Mode!!: maciek24
1816 : EVENT: System#Boot
1838 : ACT  : GPIO,0,0
1841 : SW   : GPIO 0 Set to 0
1844 : ACT  : GPIO,12,0
1847 : SW   : GPIO 12 Set to 0
1851 : ACT  : GPIO,13,0
1854 : SW   : GPIO 13 Set to 0
1859 : ACT  : delay,2000
1872 : Command: delay
3875 : ACT  : 7dn,----
3888 : Command: 7dn
3889 : Command unknown: "7dn"
3892 : ACT  : delay,500
3901 : Command: delay
4404 : ACT  : GPIO,14,0
4407 : SW   : GPIO 14 Set to 0
4410 : ACT  : timerSet,1,3000
4420 : Command: timerset
4424 : ACT  : timerSet,2,3
4433 : Command: timerset
4437 : ACT  : timerSet,4,420
4446 : Command: timerset
4561 : ACT  : TimerSet,5,5
4571 : Command: timerset
4575 : ACT  : Let,1,0
4584 : Command: let
4680 : scandone
               state: 0 -> 2 (b0)
                                 DS   : Temperature: 19.62 (28-ff-f6-ba-33-18-1-6)
5570 : state: 2 -> 3 (0)
                        EVENT: Temp-in#Temperatura-Salon=19.62
state: 3 -> 5 (10)
                  add 0
                       aid 4
                            cnt 

                                connected with maciek24, channel 1
                                                                  ip:192.168.0.29,mask:255.255.255.0,gw:192.168.0.1
                                                                                                                   5790 :  D2
5897 : WIFI : Connected! AP: maciek24 (74:DA:38:72:B0:D9) Ch: 1 Duration: 3804 ms
5899 : EVENT: WiFi#ChangedAccesspoint
6110 : IP   : Static IP : 192.168.0.29 GW: 192.168.0.1 SN: 255.255.255.0 DNS: 192.168.0.201
6112 : WIFI : Static IP: 192.168.0.29 (Salon-1) GW: 192.168.0.1 SN: 255.255.255.0   duration: 507 ms
6127 : EVENT: WiFi#Connected
6338 : Webserver: start
6360 : SYS  : 
6365 : Domoticz Controller: Not yet implemented sensor type: 0 idx: 100
6366 :  Domoticz: Sensortype: 0 idx: 100 values: 
6379 : SW  : GPIO=14 State=0 Output value=0
6389 : EVENT: Switch-1#Zwarcie_DIO_wy�ietlaczy=0.00
7574 : EVENT: Rules#Timer=2
7728 : WD   : Uptime 0 ConnectFailures 0 FreeMem 17992 WiFiStatus 3
10429 : EVENT: Rules#Timer=5
10544 : ACT  : Let,1,1
10556 : Command: let
10560 : ACT  : Event,UpdateDisplay
10573 : Command: event
10575 : EVENT: UpdateDisplay
fpm close 3 
            pm open,type:2 0
                            26440 : NTP  : NTP replied: delay 10 mSec Accuracy increased by 0.953 seconds
26442 : Time adjusted by -1563166022525.78 msec. Wander: -434212784.03 msec/second
26444 : Current Time Zone:  DST time start: 2019-03-31 02:00:00 offset: 120 minSTD time start: 2019-10-27 03:00:00 offset: 6n
26447 : EVENT: Time#Initialized
26600 : EVENT: Clock#Time=Mon,06:47
26720 : ACT  : Event,UpdateDisplay
26732 : Command: event
26733 : EVENT: UpdateDisplay
26850 : ACT  : Let,1,0
26861 : Command: let
26867 : ACT  : 7dst,6,47
26879 : Command: 7dst
26880 : Command unknown: "7dst"
26883 : ACT  : Let,1,1
26893 : Command: let
35982 : WD   : Uptime 1 ConnectFailures 0 FreeMem 17616 WiFiStatus 3
58430 : EVENT: Clock#Time=Mon,06:48
58548 : ACT  : Event,UpdateDisplay
58560 : Command: event
58561 : EVENT: UpdateDisplay
58679 : ACT  : Let,1,0
58690 : Command: let
58697 : ACT  : 7dst,6,48
58708 : Command: 7dst
58709 : Command unknown: "7dst"
58712 : ACT  : Let,1,1
58722 : Command: let
64917 : DS: SP: 3a,1,4b,46,7f,ff,c,10,a5,OK,7
64927 : DS   : Temperature: 19.62 (28-ff-f6-ba-33-18-1-6)
64933 : EVENT: Temp-in#Temperatura-Salon=19.62
65098 :  Domoticz: Sensortype: 1 idx: 106 values: 19.62
65982 : WD   : Uptime 1 ConnectFailures 0 FreeMem 17616 WiFiStatus 3
74697 : HTTP: event,set_temp=11.6
74719 : EVENT: set_temp=11.6
74779 : ACT  : GPIO,0,1
74782 : SW   : GPIO 0 Set to 1
74786 : ACT  : 7dt,11.6
74797 : Command: 7dt
74798 : Command unknown: "7dt"
74802 : ACT  : GPIO,0,0
74805 : SW   : GPIO 0 Set to 0
74810 : ACT  : timerSet,4,420
74821 : Command: timerset
Because 7 segment display device was disabled after reboot, I enabled one manually. It reboots and during next boot the error is display and nodeMCU stops oututs logs. See below:

Code: Select all

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v8b899c12
~ld
   �U64 : 

INIT : Booting version: mega-20190630 (ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support)
65 : INIT : Free RAM:30584
66 : INIT : Warm boot #6 - Restart Reason: Exception
68 : FS   : Mounting...
93 : FS   : Mount successful, used 78312 bytes of 957314
558 : CRC  : program checksum       ...OK
595 : CRC  : SecuritySettings CRC   ...OK 
691 : INIT : Free RAM:27488
693 : INIT : SPI not enabled
1570 : INFO : Plugins: 80 [Normal] [Testing] (ESP82xx Core 2_5_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.1.2 PUYA support)
1572 : EVENT: System#Wake
1767 : mode : sta(84:f3:eb:b7:45:42)
                                    add if0
                                           WIFI : Set WiFi to STA
1803 : WIFI : Connecting maciek24 attempt #0
1804 : ip:192.168.0.29,mask:255.255.255.0,gw:192.168.0.1
                                                        IP   : Static IP : 192.168.0.29 GW: 192.168.0.1 SN: 255.255.255.0 DN1
1808 : WIFI : Not configured in Station Mode!!: maciek24
1823 : EVENT: System#Boot
1844 : ACT  : GPIO,0,0
1847 : SW   : GPIO 0 Set to 0
1850 : ACT  : GPIO,12,0
1854 : SW   : GPIO 12 Set to 0
1859 : ACT  : GPIO,13,0
1862 : SW   : GPIO 13 Set to 0
1867 : ACT  : delay,2000
1881 : Command: delay
3887 : ACT  : 7dn,----
3890 : Fatal exception 3(LoadStoreErrorCause):
                                              epc1=0x4022d6c5, epc2=0x00000000, epc3=0x00000000, excvaddr=0x402e482e, depc=00

                                                                                                                            :
                                                                                                                            0
So maybe You have more infos I hope.

TD-er
Core team member
Posts: 1817
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: 7 segment display (4 digit)

#17 Post by TD-er » 16 Jul 2019, 10:50

Jimmy was spamming me a lot via Slack about this issue.

See also this issue here: https://github.com/letscontrolit/ESPEasy/issues/2380
My trigger was the "LoadStoreError".
So it should work in the builds with "SDK3.0"

The error given by Domoticz suggests the settings were not saved again for the system info plugin (is a known bug I need to fix)


Edit:
I made a test build, where the 7dgt plugin should be included in the "normal" list.
https://www.dropbox.com/s/jwl75yx14c9jp ... 9.bin?dl=0
It is based on core 2.5.2 (which should not work according to other reports)
The things I changed is that I removed the F() macro from short strings used to compare commands and the PROGMEM declaration for the "font"

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#18 Post by mackowiakp » 16 Jul 2019, 12:12

Yep. Your test build works properly! Will rapport after several hours too.

TD-er
Core team member
Posts: 1817
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: 7 segment display (4 digit)

#19 Post by TD-er » 16 Jul 2019, 12:15

OK, I will also make one built in Linux.
The last nightly build seems to have issues (again) since the normal build is causing crashes.

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#20 Post by mackowiakp » 16 Jul 2019, 12:22

Today build (test) couse that after reboot only Wi-Fi led blinking once per 4-5 sec and there is no connection to my home AP. It was necessary download old SW via USB.

TD-er
Core team member
Posts: 1817
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: 7 segment display (4 digit)

#21 Post by TD-er » 16 Jul 2019, 14:24

mackowiakp wrote:
16 Jul 2019, 12:22
Today build (test) couse that after reboot only Wi-Fi led blinking once per 4-5 sec and there is no connection to my home AP. It was necessary download old SW via USB.
That's true.
I already removed today's build from the releases after testing myself.
There's something wrong with the builds, since they work fine if I build them myself in Windows.

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#22 Post by mackowiakp » 16 Jul 2019, 14:54

OK, so good luck !

TD-er
Core team member
Posts: 1817
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: 7 segment display (4 digit)

#23 Post by TD-er » 17 Jul 2019, 01:55

mackowiakp wrote:
16 Jul 2019, 12:22
Today build (test) couse that after reboot only Wi-Fi led blinking once per 4-5 sec and there is no connection to my home AP. It was necessary download old SW via USB.
Just to make sure...
Was the test build (download via Dropbox link) failing after a reboot, or did you mean the nightly build ?

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#24 Post by mackowiakp » 17 Jul 2019, 06:52

Dropbox build works properly in the meaning of 7 segment display. Bootloop accrues using the nightly build (You remove one of course).
But with Dropbox taken build is another problem. That is watchdog reboots. Look to the chart of uptime of nodeMCU taken from Domoticz.
Uptime.png
Uptime.png (477.05 KiB) Viewed 4459 times
Using 20190630 (test, 2.4.2), watchdog also causes reboots, but very rarely (about once a day). Maybe it will take place, because I do reconnect WiFi every 50 minutes from the rule.

TD-er
Core team member
Posts: 1817
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: 7 segment display (4 digit)

#25 Post by TD-er » 17 Jul 2019, 14:34

Watchdog reboots are a known issue and I'm working on it.
And indeed the watchdog reboot has a very close relation to WiFi reconnects.

But at least the plugin now does seem to work with another core, other than 2.6.0 SDK3.
So at least that does seem to be tackled now.

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#26 Post by mackowiakp » 17 Jul 2019, 14:43

Yes I know about watchdog issue. I revert my unit to ver ESP_Easy_mega-20190107_test_ESP8266_4096.bin which is the best working for me with this specific configuration of HW.

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: 7 segment display (4 digit)

#27 Post by mackowiakp » 01 Aug 2019, 06:33

Fixed in release mega-20190731

TD-er
Core team member
Posts: 1817
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: [SOLVED] 7 segment display (4 digit)

#28 Post by TD-er » 03 Aug 2019, 01:35

And how about the WDT reboots?
Are they occurring less often now?

mackowiakp
Normal user
Posts: 183
Joined: 07 Jun 2018, 06:47
Location: Gdynia/Poland

Re: [SOLVED] 7 segment display (4 digit)

#29 Post by mackowiakp » 03 Aug 2019, 06:16

Yes. Much less often. But still occurs.

TD-er
Core team member
Posts: 1817
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: [SOLVED] 7 segment display (4 digit)

#30 Post by TD-er » 03 Aug 2019, 13:03

mackowiakp wrote:
03 Aug 2019, 06:16
Yes. Much less often. But still occurs.
That's also what I'm seeing here.
Still a WDT reboot on some nodes, but the main cause of them was when the WiFi reconnects.
That bug is now fixed.

Post Reply

Who is online

Users browsing this forum: No registered users and 33 guests