MHI-AC-Ctrl: Update from 2.02 to 2.8 doesn't work

Hi, have been using your project since 2020 without any problems with currently SW version 2.02. Now I wanted to upgrade the software version to the latest version 2.8. So I flashed a new Wemos D1 Mini and put it on the PCB. Unfortunately it doesn’t work and I don’t know why. Is the SW V2.8 compatible with the “old” PCB?

According to the log, it looks to me like the ESP keeps rebooting, doesn’t it? I have flashed the Wemos with 80MHz and also with 160MHz, but nothing has changed. Maybe you can help me, otherwise I’ll just stick with the “old” version, it works without any problems 😃

Name of my AC: SRK50-ZM-S Used MHI-AC-Ctrl HW: PCB from Dec 2019 (no HW Version Number on PCB) Used MHI-AC-Ctrl SW: 2.02

Log:

17:31:57.024 -> Starting MHI-AC-Ctrl v2.8
17:31:57.024 -> CPU frequency[Hz]=160000000
17:31:57.024 -> ESP.getCoreVersion()=3.1.2
17:31:57.024 -> ESP.getSdkVersion()=2.2.2-dev(38a443e)
17:31:57.316 -> ESP.checkFlashCRC()=1
17:31:57.625 -> Measure frequency for SCK, MOSI and MISO pin
17:31:58.630 -> SCK frequency=4299Hz (expected: >3000Hz) o.k.
17:31:58.630 -> MOSI frequency=590Hz (expected: <SCK frequency) o.k.
17:31:58.630 -> MISO frequency=0Hz (expected: ~0Hz) o.k.
17:31:58.630 -> OTA Ready
17:31:58.630 -> setupWiFi: Start async scanNetworks
17:31:58.630 -> WIFI_CONNECT_SCANNING
17:31:58.697 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.768 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.844 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.915 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.992 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.062 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.134 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.207 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.277 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.380 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.454 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.525 -> mhi_ac_ctrl_core.loop error: -4
17:31:59.600 -> mhi_ac_ctrl_core.loop error: -4
17:31:59.671 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.744 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.819 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.930 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.967 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.075 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.148 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.194 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.304 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.373 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.449 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.517 -> mhi_ac_ctrl_core.loop error: -4
17:32:00.593 -> mhi_ac_ctrl_core.loop error: -4
17:32:00.668 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.741 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.816 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.883 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.988 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.062 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.138 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.209 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.281 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.349 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.422 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.496 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.567 -> mhi_ac_ctrl_core.loop error: -4
17:32:01.675 -> mhi_ac_ctrl_core.loop error: -4
17:32:01.744 -> mhandleWiFiScanResult(): 10 access points available
17:32:01.744 ->  1              TP-Link_84FE  1 -93dBm 98:DA:C4:68:3E:31 secured 08
17:32:01.744 ->  2                CoyoteGast  1 -81dBm 1E:E8:29:A7:77:0D secured 04
17:32:01.744 ->  3                 CoyoteIoT  1 -82dBm 22:E8:29:A7:77:0D secured 04
17:32:01.744 ->  4                CoyoteGast  1 -95dBm 7E:8A:20:2D:D9:4C secured 04
17:32:01.782 ->  5                 CoyoteIoT  1 -90dBm 82:8A:20:2D:D9:4C secured 04
17:32:01.782 ->  6                 CoyoteIoT  6 -83dBm 86:8A:20:27:54:75 secured 04
17:32:01.782 ->  7                CoyoteGast  6 -93dBm 4A:D9:E7:FA:DB:16 secured 04
17:32:01.782 ->  8                 CoyoteIoT  6 -91dBm 4E:D9:E7:FA:DB:16 secured 04
17:32:01.782 ->  9             Vodafone-87A0 11 -91dBm 2C:3A:FD:6B:84:01 secured 04
17:32:01.782 -> 10                    Coyote  1 -80dBm 18:E8:29:A7:77:0D secured 04
17:32:01.782 -> current BSSID: FF:FF:FF:FF:FF:FF, strongest BSSID: 22:E8:29:A7:77:0D
17:32:01.819 -> Connecting from bssid:FF:FF:FF:FF:FF:FF to bssid:22:E8:29:A7:77:0D, channel:1
17:32:01.819 -> WIFI_CONNECT_ONGOING
17:32:01.819 -> hi_ac_ctrl_core.loop error: -2
17:32:01.890 -> mhi_ac_ctrl_core.loop error: -2
17:32:02.870 -> mhi_ac_ctrl_core.loop error: -2
17:32:02.923 -> mhi_ac_ctrl_core.loop error: -2
17:32:02.993 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.061 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.140 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.207 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.277 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.352 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.424 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.495 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.574 -> mhi_ac_ctrl_core.loop error: -4
17:32:03.677 -> mhi_ac_ctrl_core.loop error: -4
17:32:03.750 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.826 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.907 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.976 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.044 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.122 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.192 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.272 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.340 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.412 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.488 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.564 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.640 -> mhi_ac_ctrl_core.loop error: -4
17:32:04.750 -> mhi_ac_ctrl_core.loop error: -4
17:32:04.817 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.893 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.962 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.031 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.104 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.142 ->  connected to CoyoteIoT, IP address: 192.168.59.110 (-83dBm)
17:32:05.142 -> WIFI_CONNECT_OK
17:32:05.214 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.214 -> MQTTreconnect(): Attempting MQTT connection (MQTTclient.state=-1), WiFi.status()=3 ...
17:32:05.214 ->  connected
17:32:05.214 -> MQTTclient.connected=1
17:32:05.214 -> status=64 topic=connected payload=1
17:32:05.214 -> 
17:32:05.214 -> --------------- CUT HERE FOR EXCEPTION DECODER ---------------
17:32:05.249 -> 
17:32:05.249 -> Exception (3):
17:32:05.249 -> epc1=0x40219716 epc2=0x00000000 epc3=0x00000000 excvaddr=0x4024a3ec depc=0x00000000
17:32:05.249 -> 
17:32:05.249 -> >>>stack>>>
17:32:05.249 -> 
17:32:05.249 -> ctx: cont
17:32:05.249 -> sp: 3ffffd30 end: 3fffffd0 offset: 0150
17:32:05.249 -> 3ffffe80:  4024a3ec 65696c63 632e746e 00000000  
17:32:05.249 -> 3ffffe90:  4024a3f0 4024a3ec 00000040 40203050  
17:32:05.249 -> 3ffffea0:  5f49484d 746e6957 61677265 6e657472  
17:32:05.249 -> 3ffffeb0:  6f632f32 63656e6e 00646574 00000000  
17:32:05.249 -> 3ffffec0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3ffffed0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3ffffee0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3ffffef0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3fffff00:  00000000 3ffeea70 3ffeec34 00000000  
17:32:05.284 -> 3fffff10:  3ffeeadc 3ffeea70 3ffeec34 402031c9  
17:32:05.284 -> 3fffff20:  00000001 3ffe893c 5f6c7274 65726f63  
17:32:05.284 -> 3fffff30:  6f6f6c2e 72652070 3a726f72 0a322d20  
17:32:05.284 -> 3fffff40:  00000000 0000208e a4dd2f1a 0025a4ee  
17:32:05.284 -> 3fffff50:  3ffeec34 00000000 0000000c 40100664  
17:32:05.327 -> 3fffff60:  3fffffa0 3fffff70 00000008 402012b1  
17:32:05.327 -> 3fffff70:  402456c6 3ffeea00 3ffeea08 00000001  
17:32:05.327 -> 3fffff80:  ffffffff 0000208f e4dd2f1a 0025a660  
17:32:05.327 -> 3fffff90:  3ffef81c 402039b4 3fffffa0 3ffeee10 <
17:32:05.327 -> 3fffffa0:  3ffe85f0 3ffeea08 3ffeea18 40202850  
17:32:05.327 -> 3fffffb0:  3fffdad0 00000000 3ffeede4 4020e398  
17:32:05.327 -> 3fffffc0:  feefeffe feefeffe 3fffdab0 40101261  
17:32:05.327 -> <<<stack<<<
17:32:05.327 -> 
17:32:05.327 -> --------------- CUT HERE FOR EXCEPTION DECODER ---------------
17:32:05.360 -> 
17:32:05.360 ->  ets Jan  8 2013,rst cause:2, boot mode:(3,6)
17:32:05.360 -> 
17:32:05.360 -> load 0x4010f000, len 3424, room 16 
17:32:05.360 -> tail 0
17:32:05.360 -> chksum 0x2e
17:32:05.360 -> load 0x3fff20b8, len 40, room 8 
17:32:05.360 -> tail 0
17:32:05.360 -> chksum 0x2b
17:32:05.360 -> csum 0x2b
17:32:05.360 -> v00052b50
17:32:05.360 -> ~ld
17:32:05.428 -> ⸮⸮n⸮r⸮⸮n|⸮l⸮l`bbrl⸮nb⸮nl`⸮rl⸮l⸮⸮
17:32:05.537 -> Starting MHI-AC-Ctrl v2.8
17:32:05.537 -> CPU frequency[Hz]=160000000
17:32:05.537 -> ESP.getCoreVersion()=3.1.2
17:32:05.537 -> ESP.getSdkVersion()=2.2.2-dev(38a443e)
17:32:05.824 -> ESP.checkFlashCRC()=1
17:32:06.147 -> Measure frequency for SCK, MOSI and MISO pin
17:32:07.127 -> SCK frequency=4280Hz (expected: >3000Hz) o.k.
17:32:07.127 -> MOSI frequency=587Hz (expected: <SCK frequency) o.k.
17:32:07.127 -> MISO frequency=0Hz (expected: ~0Hz) o.k.
17:32:07.127 -> OTA Ready
17:32:07.127 -> setupWiFi: Start async scanNetworks
17:32:07.160 -> WIFI_CONNECT_SCANNING
17:32:07.194 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.268 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.340 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.416 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.487 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.561 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.633 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.743 -> mhi_ac_ctrl_core.loop error: -4
17:32:07.817 -> mhi_ac_ctrl_core.loop error: -4
17:32:07.889 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.964 -> mhi_ac_ctrl_core.loop error: -2

About this issue

Original URL
State: closed
Created 6 months ago
Comments: 17

Most upvoted comments

I see in your log it is near wifi connection, in my case, after months of stable working, without network changes, connected goes nearly all the time to 0. Didn’t connect to serial to debug. But you can give it a try to change parameter: #define WiFI_SEARCHStrongestAP false For me, this solved the problem.

Henk50V on Jan 10, 2024