-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Endless loop when DS18B20 is activated with esp8266 #25
Comments
I expect it may be a library issue. I haven't retested the code with a
newer core version recently. If you monitor the output on serial it may
give an indication as to where it is failing.
…On Wed, Jun 10, 2020 at 11:42 AM frederic-kleinert ***@***.***> wrote:
Hello!
I am trying to activate the internal temperature sensor in the code
myClock.ino. To do this, I remove the comment sign in front of the line
//#define DS18 // enable DS18B20 temperature sensor. Compilation runs
without errors. But the display gets into a loop during execution: Welcome
screen, instruction to start the web server, then briefly the current time
and before the next seconds, again everything from the beginning. With DS18
deactivated, everything runs normally. Is the cause known?
With kind regards
Translated with www.DeepL.com/Translator (free version)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#25>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM5GPVV2UP6JPJ6BF7KTXLRV7AXPANCNFSM4N2THQ5A>
.
--
david denney
dragondaud AT gmail DOT com
719-821-8900
|
Thanks for the quick answer:
Here is the output of the serial port:
Correct (without DS18)
18:47:47.830 -> readSPIFFS: mounted
18:47:47.864 -> *WM: [1] <form action='/wifi' method='get'><button>Configure WiFi</button></form><br/>
18:47:47.864 -> <form action='/info' method='get'><button>Info</button></form><br/>
18:47:47.864 -> <form action='/exit' method='get'><button>Exit</button></form><br/>
18:47:47.864 ->
18:47:48.035 -> WiFi: myClock-E9FF32 192.168.192.226
18:47:48.069 -> setup: 66119, DE, Europe/Berlin, true
18:47:48.477 -> getOffset: 7200
18:47:48.477 -> setNTP: configure NTP ... OK
18:47:48.477 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:47:49.505 -> 18:47
19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:47:49.845 -> 18:47 31336 600 18:48 30728 889 18:49 30728 902 18:50 31136 902
wrong (with DS18)
8:56:00.698 -> readSPIFFS: mounted
18:56:00.731 -> *WM: [1] <form action='/wifi' method='get'><button>Configure WiFi</button></form><br/>
18:56:00.731 -> <form action='/info' method='get'><button>Info</button></form><br/>
18:56:00.731 -> <form action='/exit' method='get'><button>Exit</button></form><br/>
18:56:00.731 ->
18:56:00.938 -> WiFi: myClock-E9FF32 192.168.192.226
18:56:00.938 -> setup: 66119, DE, Europe/Berlin, true
18:56:01.413 -> getOffset: 7200
18:56:01.413 -> setNTP: configure NTP ... OK
18:56:01.413 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:56:02.404 -> 18:56 19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:56:02.713 -> 18:56 31184 599
18:56:03.256 -> Exception (28):
18:56:03.256 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
18:56:03.256 ->
18:56:03.256 -> >>>stack>>>
18:56:03.256 ->
18:56:03.256 -> ctx: cont
18:56:03.256 -> sp: 3ffffd50 end: 3fffffc0 offset: 01a0
18:56:03.256 -> 3ffffef0: 3fffff40 00000000 3fff05d4 4021b33f
18:56:03.256 -> 3fffff00: 00000000 31f126f6 40100400 00000a30
18:56:03.256 -> 3fffff10: 401004fc 00000001 c0039035 3fff05c2
18:56:03.256 -> 3fffff20: 3fff05d4 00000000 3fffff40 4021b5d4
18:56:03.256 -> 3fffff30: 3fff073c 3fff05d4 00000000 4021b6fd
18:56:03.256 -> 3fffff40: 00000850 000002ee 3fff05d4 4021b464
18:56:03.256 -> 3fffff50: 3fff073c 00000001 3fff05d4 4021b725
18:56:03.256 -> 3fffff60: 3fff22e4 00000038 3fff05d4 40209e4c
18:56:03.289 -> 3fffff70: feefeffe feefeffe 00000000 5ee27e42
18:56:03.289 -> 3fffff80: 00000002 00000030 3fff2084 3ffe8579
18:56:03.289 -> 3fffff90: feefeffe feefeffe feefeffe 3fff2430
18:56:03.289 -> 3fffffa0: 3fffdad0 00000000 3fff23f0 4021ea1c
18:56:03.289 -> 3fffffb0: feefeffe feefeffe 3ffe8598 40100f29
18:56:03.289 -> <<<stack<<<
18:56:03.289 ->
18:56:03.289 -> ets Jan 8 2013,rst cause:2, boot mode:(3,6)
18:56:03.289 ->
18:56:03.324 -> load 0x4010f000, len 1392, room 16
18:56:03.324 -> tail 0
18:56:03.324 -> chksum 0xd0
18:56:03.324 -> csum 0xd0
18:56:03.324 -> v3d128e5c
18:56:03.324 -> ~ld
18:56:03.392 ->
18:56:03.392 -> readSPIFFS: mounted
18:56:03.458 -> *WM: [1] <form action='/wifi' method='get'><button>Configure WiFi</button></form><br/>
18:56:03.458 -> <form action='/info' method='get'><button>Info</button></form><br/>
18:56:03.458 -> <form action='/exit' method='get'><button>Exit</button></form><br/>
18:56:03.458 ->
18:56:03.631 -> WiFi: myClock-E9FF32 192.168.192.226
18:56:03.631 -> setup: 66119, DE, Europe/Berlin, true
18:56:04.035 -> getOffset: 7200
18:56:04.035 -> setNTP: configure NTP ... OK
18:56:04.035 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:56:05.050 -> 18:56
19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:56:05.319 -> 18:56 31288 599
18:56:05.865 -> Exception (28):
18:56:05.865 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
18:56:05.865 ->
18:56:05.865 -> >>>stack>>>
Gesendet: Mittwoch, 10. Juni 2020 um 19:51 Uhr
Von: "daud" <[email protected]>
An: "dragondaud/myClock" <[email protected]>
Cc: "frederic-kleinert" <[email protected]>, "Author" <[email protected]>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated with esp8266 (#25)
I expect it may be a library issue. I haven't retested the code with a
newer core version recently. If you monitor the output on serial it may
give an indication as to where it is failing.
…On Wed, Jun 10, 2020 at 11:42 AM frederic-kleinert ***@***.***> wrote:
Hello!
I am trying to activate the internal temperature sensor in the code
myClock.ino. To do this, I remove the comment sign in front of the line
//#define DS18 // enable DS18B20 temperature sensor. Compilation runs
without errors. But the display gets into a loop during execution: Welcome
screen, instruction to start the web server, then briefly the current time
and before the next seconds, again everything from the beginning. With DS18
deactivated, everything runs normally. Is the cause known?
With kind regards
Translated with www.DeepL.com/Translator (free version)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#25>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM5GPVV2UP6JPJ6BF7KTXLRV7AXPANCNFSM4N2THQ5A>
.
--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
If you install https://github.com/me-no-dev/EspExceptionDecoder (for
ESP8266) into your Arduino environment, you can paste the stack output into
it to see where it failed(If you are using ESP32, there is a similar
package for it, too).
I cannot do that on my end, because it requires your local object files.
Send the output from there and I'll help track down the culprit. It is
probably related to the OneWire or the DallasTemperature library. Make sure
you're using the latest versions.
On Thu, Jun 11, 2020 at 11:20 AM frederic-kleinert <[email protected]>
wrote:
…
Thanks for the quick answer:
Here is the output of the serial port:
Correct (without DS18)
18:47:47.830 -> readSPIFFS: mounted
18:47:47.864 -> *WM: [1] <form action='/wifi'
method='get'><button>Configure WiFi</button></form><br/>
18:47:47.864 -> <form action='/info'
method='get'><button>Info</button></form><br/>
18:47:47.864 -> <form action='/exit'
method='get'><button>Exit</button></form><br/>
18:47:47.864 ->
18:47:48.035 -> WiFi: myClock-E9FF32 192.168.192.226
18:47:48.069 -> setup: 66119, DE, Europe/Berlin, true
18:47:48.477 -> getOffset: 7200
18:47:48.477 -> setNTP: configure NTP ... OK
18:47:48.477 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:47:49.505 -> 18:47
19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:47:49.845 -> 18:47 31336 600 18:48 30728 889 18:49 30728 902 18:50
31136 902
wrong (with DS18)
8:56:00.698 -> readSPIFFS: mounted
18:56:00.731 -> *WM: [1] <form action='/wifi'
method='get'><button>Configure WiFi</button></form><br/>
18:56:00.731 -> <form action='/info'
method='get'><button>Info</button></form><br/>
18:56:00.731 -> <form action='/exit'
method='get'><button>Exit</button></form><br/>
18:56:00.731 ->
18:56:00.938 -> WiFi: myClock-E9FF32 192.168.192.226
18:56:00.938 -> setup: 66119, DE, Europe/Berlin, true
18:56:01.413 -> getOffset: 7200
18:56:01.413 -> setNTP: configure NTP ... OK
18:56:01.413 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:56:02.404 -> 18:56 19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:56:02.713 -> 18:56 31184 599
18:56:03.256 -> Exception (28):
18:56:03.256 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
excvaddr=0x00000000 depc=0x00000000
18:56:03.256 ->
18:56:03.256 -> >>>stack>>>
18:56:03.256 ->
18:56:03.256 -> ctx: cont
18:56:03.256 -> sp: 3ffffd50 end: 3fffffc0 offset: 01a0
18:56:03.256 -> 3ffffef0: 3fffff40 00000000 3fff05d4 4021b33f
18:56:03.256 -> 3fffff00: 00000000 31f126f6 40100400 00000a30
18:56:03.256 -> 3fffff10: 401004fc 00000001 c0039035 3fff05c2
18:56:03.256 -> 3fffff20: 3fff05d4 00000000 3fffff40 4021b5d4
18:56:03.256 -> 3fffff30: 3fff073c 3fff05d4 00000000 4021b6fd
18:56:03.256 -> 3fffff40: 00000850 000002ee 3fff05d4 4021b464
18:56:03.256 -> 3fffff50: 3fff073c 00000001 3fff05d4 4021b725
18:56:03.256 -> 3fffff60: 3fff22e4 00000038 3fff05d4 40209e4c
18:56:03.289 -> 3fffff70: feefeffe feefeffe 00000000 5ee27e42
18:56:03.289 -> 3fffff80: 00000002 00000030 3fff2084 3ffe8579
18:56:03.289 -> 3fffff90: feefeffe feefeffe feefeffe 3fff2430
18:56:03.289 -> 3fffffa0: 3fffdad0 00000000 3fff23f0 4021ea1c
18:56:03.289 -> 3fffffb0: feefeffe feefeffe 3ffe8598 40100f29
18:56:03.289 -> <<<stack<<<
18:56:03.289 ->
18:56:03.289 -> ets Jan 8 2013,rst cause:2, boot mode:(3,6)
18:56:03.289 ->
18:56:03.324 -> load 0x4010f000, len 1392, room 16
18:56:03.324 -> tail 0
18:56:03.324 -> chksum 0xd0
18:56:03.324 -> csum 0xd0
18:56:03.324 -> v3d128e5c
18:56:03.324 -> ~ld
18:56:03.392 ->
18:56:03.392 -> readSPIFFS: mounted
18:56:03.458 -> *WM: [1] <form action='/wifi'
method='get'><button>Configure WiFi</button></form><br/>
18:56:03.458 -> <form action='/info'
method='get'><button>Info</button></form><br/>
18:56:03.458 -> <form action='/exit'
method='get'><button>Exit</button></form><br/>
18:56:03.458 ->
18:56:03.631 -> WiFi: myClock-E9FF32 192.168.192.226
18:56:03.631 -> setup: 66119, DE, Europe/Berlin, true
18:56:04.035 -> getOffset: 7200
18:56:04.035 -> setNTP: configure NTP ... OK
18:56:04.035 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:56:05.050 -> 18:56
19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:56:05.319 -> 18:56 31288 599
18:56:05.865 -> Exception (28):
18:56:05.865 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
excvaddr=0x00000000 depc=0x00000000
18:56:05.865 ->
18:56:05.865 -> >>>stack>>>
Gesendet: Mittwoch, 10. Juni 2020 um 19:51 Uhr
Von: "daud" ***@***.***>
An: "dragondaud/myClock" ***@***.***>
Cc: "frederic-kleinert" ***@***.***>, "Author" <
***@***.***>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated
with esp8266 (#25)
I expect it may be a library issue. I haven't retested the code with a
newer core version recently. If you monitor the output on serial it may
give an indication as to where it is failing.
On Wed, Jun 10, 2020 at 11:42 AM frederic-kleinert <
***@***.***>
wrote:
> Hello!
> I am trying to activate the internal temperature sensor in the code
> myClock.ino. To do this, I remove the comment sign in front of the line
> //#define DS18 // enable DS18B20 temperature sensor. Compilation runs
> without errors. But the display gets into a loop during execution:
Welcome
> screen, instruction to start the web server, then briefly the current
time
> and before the next seconds, again everything from the beginning. With
DS18
> deactivated, everything runs normally. Is the cause known?
> With kind regards
>
> Translated with www.DeepL.com/Translator (free version)
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#25>, or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AGM5GPVV2UP6JPJ6BF7KTXLRV7AXPANCNFSM4N2THQ5A
>
> .
>
--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM5GPSHGTWCJ3XRHK2WKGDRWEG5LANCNFSM4N2THQ5A>
.
--
david denney
dragondaud AT gmail DOT com
719-821-8900
|
Hallo
Here is the result:
Decoding stack results
0x4021b33f: DallasTemperature::readScratchPad(unsigned char const*, unsigned char*) at C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp line 184
0x40100400: __wrap_spi_flash_read(uint32_t, uint32_t*, size_t) at C:\Users\jzimmer\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.6.3\cores\esp8266\core_esp8266_phy.cpp line 313
0x401004fc: delayMicroseconds(unsigned int) at C:\Users\jzimmer\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.6.3\cores\esp8266\core_esp8266_wiring.cpp line 210
0x4021b5d4: DallasTemperature::isConnected(unsigned char const*, unsigned char*) at C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp line 172
0x4021b6fd: DallasTemperature::getTemp(unsigned char const*) at C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp line 555
0x4021b464: DallasTemperature::blockTillConversionComplete(unsigned char) at C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp line 435
0x4021b725: DallasTemperature::getTempC(unsigned char const*) at C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp line 567
Gesendet: Donnerstag, 11. Juni 2020 um 20:30 Uhr
Von: "daud" <[email protected]>
An: "dragondaud/myClock" <[email protected]>
Cc: "frederic-kleinert" <[email protected]>, "Author" <[email protected]>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated with esp8266 (#25)
If you install https://github.com/me-no-dev/EspExceptionDecoder (for
ESP8266) into your Arduino environment, you can paste the stack output into
it to see where it failed(If you are using ESP32, there is a similar
package for it, too).
I cannot do that on my end, because it requires your local object files.
Send the output from there and I'll help track down the culprit. It is
probably related to the OneWire or the DallasTemperature library. Make sure
you're using the latest versions.
On Thu, Jun 11, 2020 at 11:20 AM frederic-kleinert <[email protected]>
wrote:
…
Thanks for the quick answer:
Here is the output of the serial port:
Correct (without DS18)
18:47:47.830 -> readSPIFFS: mounted
18:47:47.864 -> *WM: [1] <form action='/wifi'
method='get'><button>Configure WiFi</button></form><br/>
18:47:47.864 -> <form action='/info'
method='get'><button>Info</button></form><br/>
18:47:47.864 -> <form action='/exit'
method='get'><button>Exit</button></form><br/>
18:47:47.864 ->
18:47:48.035 -> WiFi: myClock-E9FF32 192.168.192.226
18:47:48.069 -> setup: 66119, DE, Europe/Berlin, true
18:47:48.477 -> getOffset: 7200
18:47:48.477 -> setNTP: configure NTP ... OK
18:47:48.477 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:47:49.505 -> 18:47
19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:47:49.845 -> 18:47 31336 600 18:48 30728 889 18:49 30728 902 18:50
31136 902
wrong (with DS18)
8:56:00.698 -> readSPIFFS: mounted
18:56:00.731 -> *WM: [1] <form action='/wifi'
method='get'><button>Configure WiFi</button></form><br/>
18:56:00.731 -> <form action='/info'
method='get'><button>Info</button></form><br/>
18:56:00.731 -> <form action='/exit'
method='get'><button>Exit</button></form><br/>
18:56:00.731 ->
18:56:00.938 -> WiFi: myClock-E9FF32 192.168.192.226
18:56:00.938 -> setup: 66119, DE, Europe/Berlin, true
18:56:01.413 -> getOffset: 7200
18:56:01.413 -> setNTP: configure NTP ... OK
18:56:01.413 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:56:02.404 -> 18:56 19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:56:02.713 -> 18:56 31184 599
18:56:03.256 -> Exception (28):
18:56:03.256 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
excvaddr=0x00000000 depc=0x00000000
18:56:03.256 ->
18:56:03.256 -> >>>stack>>>
18:56:03.256 ->
18:56:03.256 -> ctx: cont
18:56:03.256 -> sp: 3ffffd50 end: 3fffffc0 offset: 01a0
18:56:03.256 -> 3ffffef0: 3fffff40 00000000 3fff05d4 4021b33f
18:56:03.256 -> 3fffff00: 00000000 31f126f6 40100400 00000a30
18:56:03.256 -> 3fffff10: 401004fc 00000001 c0039035 3fff05c2
18:56:03.256 -> 3fffff20: 3fff05d4 00000000 3fffff40 4021b5d4
18:56:03.256 -> 3fffff30: 3fff073c 3fff05d4 00000000 4021b6fd
18:56:03.256 -> 3fffff40: 00000850 000002ee 3fff05d4 4021b464
18:56:03.256 -> 3fffff50: 3fff073c 00000001 3fff05d4 4021b725
18:56:03.256 -> 3fffff60: 3fff22e4 00000038 3fff05d4 40209e4c
18:56:03.289 -> 3fffff70: feefeffe feefeffe 00000000 5ee27e42
18:56:03.289 -> 3fffff80: 00000002 00000030 3fff2084 3ffe8579
18:56:03.289 -> 3fffff90: feefeffe feefeffe feefeffe 3fff2430
18:56:03.289 -> 3fffffa0: 3fffdad0 00000000 3fff23f0 4021ea1c
18:56:03.289 -> 3fffffb0: feefeffe feefeffe 3ffe8598 40100f29
18:56:03.289 -> <<<stack<<<
18:56:03.289 ->
18:56:03.289 -> ets Jan 8 2013,rst cause:2, boot mode:(3,6)
18:56:03.289 ->
18:56:03.324 -> load 0x4010f000, len 1392, room 16
18:56:03.324 -> tail 0
18:56:03.324 -> chksum 0xd0
18:56:03.324 -> csum 0xd0
18:56:03.324 -> v3d128e5c
18:56:03.324 -> ~ld
18:56:03.392 ->
18:56:03.392 -> readSPIFFS: mounted
18:56:03.458 -> *WM: [1] <form action='/wifi'
method='get'><button>Configure WiFi</button></form><br/>
18:56:03.458 -> <form action='/info'
method='get'><button>Info</button></form><br/>
18:56:03.458 -> <form action='/exit'
method='get'><button>Exit</button></form><br/>
18:56:03.458 ->
18:56:03.631 -> WiFi: myClock-E9FF32 192.168.192.226
18:56:03.631 -> setup: 66119, DE, Europe/Berlin, true
18:56:04.035 -> getOffset: 7200
18:56:04.035 -> setNTP: configure NTP ... OK
18:56:04.035 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
18:56:05.050 -> 18:56
19F, 59%, 4 NE (50), Ein paar Wolken (801)
18:56:05.319 -> 18:56 31288 599
18:56:05.865 -> Exception (28):
18:56:05.865 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
excvaddr=0x00000000 depc=0x00000000
18:56:05.865 ->
18:56:05.865 -> >>>stack>>>
Gesendet: Mittwoch, 10. Juni 2020 um 19:51 Uhr
Von: "daud" ***@***.***>
An: "dragondaud/myClock" ***@***.***>
Cc: "frederic-kleinert" ***@***.***>, "Author" <
***@***.***>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated
with esp8266 (#25)
I expect it may be a library issue. I haven't retested the code with a
newer core version recently. If you monitor the output on serial it may
give an indication as to where it is failing.
On Wed, Jun 10, 2020 at 11:42 AM frederic-kleinert <
***@***.***>
wrote:
> Hello!
> I am trying to activate the internal temperature sensor in the code
> myClock.ino. To do this, I remove the comment sign in front of the line
> //#define DS18 // enable DS18B20 temperature sensor. Compilation runs
> without errors. But the display gets into a loop during execution:
Welcome
> screen, instruction to start the web server, then briefly the current
time
> and before the next seconds, again everything from the beginning. With
DS18
> deactivated, everything runs normally. Is the cause known?
> With kind regards
>
> Translated with www.DeepL.com/Translator (free version)
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#25>, or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AGM5GPVV2UP6JPJ6BF7KTXLRV7AXPANCNFSM4N2THQ5A
>
> .
>
--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM5GPSHGTWCJ3XRHK2WKGDRWEG5LANCNFSM4N2THQ5A>
.
--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I'm looking into what is causing this. I will try to test this later today.
Exception 28 is defined as:
28 LoadProhibitedCause A load referenced a page mapped with an attribute
that does not permit loads Region Protection or MMU YesWhich leads me to
believe something changed in the way the library is called.
Using an older version of the ESP core would likely fix the problem, but
I'm sure I can track this down and fix it with current, given a little time.
On Thu, Jun 11, 2020 at 2:17 PM frederic-kleinert <[email protected]>
wrote:
… Hallo
Here is the result:
Decoding stack results
0x4021b33f: DallasTemperature::readScratchPad(unsigned char const*,
unsigned char*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 184
0x40100400: __wrap_spi_flash_read(uint32_t, uint32_t*, size_t) at
C:\Users\jzimmer\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.6.3\cores\esp8266\core_esp8266_phy.cpp
line 313
0x401004fc: delayMicroseconds(unsigned int) at
C:\Users\jzimmer\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.6.3\cores\esp8266\core_esp8266_wiring.cpp
line 210
0x4021b5d4: DallasTemperature::isConnected(unsigned char const*, unsigned
char*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 172
0x4021b6fd: DallasTemperature::getTemp(unsigned char const*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 555
0x4021b464: DallasTemperature::blockTillConversionComplete(unsigned char)
at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 435
0x4021b725: DallasTemperature::getTempC(unsigned char const*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 567
Gesendet: Donnerstag, 11. Juni 2020 um 20:30 Uhr
Von: "daud" ***@***.***>
An: "dragondaud/myClock" ***@***.***>
Cc: "frederic-kleinert" ***@***.***>, "Author" <
***@***.***>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated
with esp8266 (#25)
If you install https://github.com/me-no-dev/EspExceptionDecoder (for
ESP8266) into your Arduino environment, you can paste the stack output into
it to see where it failed(If you are using ESP32, there is a similar
package for it, too).
I cannot do that on my end, because it requires your local object files.
Send the output from there and I'll help track down the culprit. It is
probably related to the OneWire or the DallasTemperature library. Make sure
you're using the latest versions.
On Thu, Jun 11, 2020 at 11:20 AM frederic-kleinert <
***@***.***>
wrote:
>
>
>
> Thanks for the quick answer:
> Here is the output of the serial port:
>
>
>
>
> Correct (without DS18)
>
>
>
> 18:47:47.830 -> readSPIFFS: mounted
> 18:47:47.864 -> *WM: [1] <form action='/wifi'
> method='get'><button>Configure WiFi</button></form><br/>
> 18:47:47.864 -> <form action='/info'
> method='get'><button>Info</button></form><br/>
> 18:47:47.864 -> <form action='/exit'
> method='get'><button>Exit</button></form><br/>
> 18:47:47.864 ->
> 18:47:48.035 -> WiFi: myClock-E9FF32 192.168.192.226
> 18:47:48.069 -> setup: 66119, DE, Europe/Berlin, true
> 18:47:48.477 -> getOffset: 7200
> 18:47:48.477 -> setNTP: configure NTP ... OK
> 18:47:48.477 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
> 18:47:49.505 -> 18:47
> 19F, 59%, 4 NE (50), Ein paar Wolken (801)
> 18:47:49.845 -> 18:47 31336 600 18:48 30728 889 18:49 30728 902 18:50
> 31136 902
>
>
> wrong (with DS18)
>
>
> 8:56:00.698 -> readSPIFFS: mounted
> 18:56:00.731 -> *WM: [1] <form action='/wifi'
> method='get'><button>Configure WiFi</button></form><br/>
> 18:56:00.731 -> <form action='/info'
> method='get'><button>Info</button></form><br/>
> 18:56:00.731 -> <form action='/exit'
> method='get'><button>Exit</button></form><br/>
> 18:56:00.731 ->
> 18:56:00.938 -> WiFi: myClock-E9FF32 192.168.192.226
> 18:56:00.938 -> setup: 66119, DE, Europe/Berlin, true
> 18:56:01.413 -> getOffset: 7200
> 18:56:01.413 -> setNTP: configure NTP ... OK
> 18:56:01.413 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
> 18:56:02.404 -> 18:56 19F, 59%, 4 NE (50), Ein paar Wolken (801)
> 18:56:02.713 -> 18:56 31184 599
> 18:56:03.256 -> Exception (28):
> 18:56:03.256 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
> excvaddr=0x00000000 depc=0x00000000
> 18:56:03.256 ->
> 18:56:03.256 -> >>>stack>>>
> 18:56:03.256 ->
> 18:56:03.256 -> ctx: cont
> 18:56:03.256 -> sp: 3ffffd50 end: 3fffffc0 offset: 01a0
> 18:56:03.256 -> 3ffffef0: 3fffff40 00000000 3fff05d4 4021b33f
> 18:56:03.256 -> 3fffff00: 00000000 31f126f6 40100400 00000a30
> 18:56:03.256 -> 3fffff10: 401004fc 00000001 c0039035 3fff05c2
> 18:56:03.256 -> 3fffff20: 3fff05d4 00000000 3fffff40 4021b5d4
> 18:56:03.256 -> 3fffff30: 3fff073c 3fff05d4 00000000 4021b6fd
> 18:56:03.256 -> 3fffff40: 00000850 000002ee 3fff05d4 4021b464
> 18:56:03.256 -> 3fffff50: 3fff073c 00000001 3fff05d4 4021b725
> 18:56:03.256 -> 3fffff60: 3fff22e4 00000038 3fff05d4 40209e4c
> 18:56:03.289 -> 3fffff70: feefeffe feefeffe 00000000 5ee27e42
> 18:56:03.289 -> 3fffff80: 00000002 00000030 3fff2084 3ffe8579
> 18:56:03.289 -> 3fffff90: feefeffe feefeffe feefeffe 3fff2430
> 18:56:03.289 -> 3fffffa0: 3fffdad0 00000000 3fff23f0 4021ea1c
> 18:56:03.289 -> 3fffffb0: feefeffe feefeffe 3ffe8598 40100f29
> 18:56:03.289 -> <<<stack<<<
> 18:56:03.289 ->
> 18:56:03.289 -> ets Jan 8 2013,rst cause:2, boot mode:(3,6)
> 18:56:03.289 ->
> 18:56:03.324 -> load 0x4010f000, len 1392, room 16
> 18:56:03.324 -> tail 0
> 18:56:03.324 -> chksum 0xd0
> 18:56:03.324 -> csum 0xd0
> 18:56:03.324 -> v3d128e5c
> 18:56:03.324 -> ~ld
> 18:56:03.392 ->
> 18:56:03.392 -> readSPIFFS: mounted
> 18:56:03.458 -> *WM: [1] <form action='/wifi'
> method='get'><button>Configure WiFi</button></form><br/>
> 18:56:03.458 -> <form action='/info'
> method='get'><button>Info</button></form><br/>
> 18:56:03.458 -> <form action='/exit'
> method='get'><button>Exit</button></form><br/>
> 18:56:03.458 ->
> 18:56:03.631 -> WiFi: myClock-E9FF32 192.168.192.226
> 18:56:03.631 -> setup: 66119, DE, Europe/Berlin, true
> 18:56:04.035 -> getOffset: 7200
> 18:56:04.035 -> setNTP: configure NTP ... OK
> 18:56:04.035 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
> 18:56:05.050 -> 18:56
> 19F, 59%, 4 NE (50), Ein paar Wolken (801)
> 18:56:05.319 -> 18:56 31288 599
> 18:56:05.865 -> Exception (28):
> 18:56:05.865 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
> excvaddr=0x00000000 depc=0x00000000
> 18:56:05.865 ->
> 18:56:05.865 -> >>>stack>>>
>
>
>
>
> Gesendet: Mittwoch, 10. Juni 2020 um 19:51 Uhr
> Von: "daud" ***@***.***>
> An: "dragondaud/myClock" ***@***.***>
> Cc: "frederic-kleinert" ***@***.***>, "Author" <
> ***@***.***>
> Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated
> with esp8266 (#25)
>
>
>
> I expect it may be a library issue. I haven't retested the code with a
> newer core version recently. If you monitor the output on serial it may
> give an indication as to where it is failing.
>
> On Wed, Jun 10, 2020 at 11:42 AM frederic-kleinert <
> ***@***.***>
> wrote:
>
> > Hello!
> > I am trying to activate the internal temperature sensor in the code
> > myClock.ino. To do this, I remove the comment sign in front of the line
> > //#define DS18 // enable DS18B20 temperature sensor. Compilation runs
> > without errors. But the display gets into a loop during execution:
> Welcome
> > screen, instruction to start the web server, then briefly the current
> time
> > and before the next seconds, again everything from the beginning. With
> DS18
> > deactivated, everything runs normally. Is the cause known?
> > With kind regards
> >
> > Translated with www.DeepL.com/Translator (free version)
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#25>, or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AGM5GPVV2UP6JPJ6BF7KTXLRV7AXPANCNFSM4N2THQ5A
> >
> > .
> >
>
>
> --
> david denney
> dragondaud AT gmail DOT com
> 719-821-8900
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#25 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AGM5GPSHGTWCJ3XRHK2WKGDRWEG5LANCNFSM4N2THQ5A
>
> .
>
--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM5GPR35NDJ2DVHS3RPE73RWE3UVANCNFSM4N2THQ5A>
.
--
david denney
dragondaud AT gmail DOT com
719-821-8900
|
Hello!
That gives me hope. Thank you very much for your efforts.
Yours sincerely
Gesendet: Freitag, 12. Juni 2020 um 17:30 Uhr
Von: "daud" <[email protected]>
An: "dragondaud/myClock" <[email protected]>
Cc: "frederic-kleinert" <[email protected]>, "Author" <[email protected]>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated with esp8266 (#25)
I'm looking into what is causing this. I will try to test this later today.
Exception 28 is defined as:
28 LoadProhibitedCause A load referenced a page mapped with an attribute
that does not permit loads Region Protection or MMU YesWhich leads me to
believe something changed in the way the library is called.
Using an older version of the ESP core would likely fix the problem, but
I'm sure I can track this down and fix it with current, given a little time.
On Thu, Jun 11, 2020 at 2:17 PM frederic-kleinert <[email protected]>
wrote:
… Hallo
Here is the result:
Decoding stack results
0x4021b33f: DallasTemperature::readScratchPad(unsigned char const*,
unsigned char*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 184
0x40100400: __wrap_spi_flash_read(uint32_t, uint32_t*, size_t) at
C:\Users\jzimmer\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.6.3\cores\esp8266\core_esp8266_phy.cpp
line 313
0x401004fc: delayMicroseconds(unsigned int) at
C:\Users\jzimmer\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\2.6.3\cores\esp8266\core_esp8266_wiring.cpp
line 210
0x4021b5d4: DallasTemperature::isConnected(unsigned char const*, unsigned
char*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 172
0x4021b6fd: DallasTemperature::getTemp(unsigned char const*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 555
0x4021b464: DallasTemperature::blockTillConversionComplete(unsigned char)
at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 435
0x4021b725: DallasTemperature::getTempC(unsigned char const*) at
C:\Users\jzimmer\Documents\Arduino\libraries\DallasTemperature\DallasTemperature.cpp
line 567
Gesendet: Donnerstag, 11. Juni 2020 um 20:30 Uhr
Von: "daud" ***@***.***>
An: "dragondaud/myClock" ***@***.***>
Cc: "frederic-kleinert" ***@***.***>, "Author" <
***@***.***>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated
with esp8266 (#25)
If you install https://github.com/me-no-dev/EspExceptionDecoder (for
ESP8266) into your Arduino environment, you can paste the stack output into
it to see where it failed(If you are using ESP32, there is a similar
package for it, too).
I cannot do that on my end, because it requires your local object files.
Send the output from there and I'll help track down the culprit. It is
probably related to the OneWire or the DallasTemperature library. Make sure
you're using the latest versions.
On Thu, Jun 11, 2020 at 11:20 AM frederic-kleinert <
***@***.***>
wrote:
>
>
>
> Thanks for the quick answer:
> Here is the output of the serial port:
>
>
>
>
> Correct (without DS18)
>
>
>
> 18:47:47.830 -> readSPIFFS: mounted
> 18:47:47.864 -> *WM: [1] <form action='/wifi'
> method='get'><button>Configure WiFi</button></form><br/>
> 18:47:47.864 -> <form action='/info'
> method='get'><button>Info</button></form><br/>
> 18:47:47.864 -> <form action='/exit'
> method='get'><button>Exit</button></form><br/>
> 18:47:47.864 ->
> 18:47:48.035 -> WiFi: myClock-E9FF32 192.168.192.226
> 18:47:48.069 -> setup: 66119, DE, Europe/Berlin, true
> 18:47:48.477 -> getOffset: 7200
> 18:47:48.477 -> setNTP: configure NTP ... OK
> 18:47:48.477 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
> 18:47:49.505 -> 18:47
> 19F, 59%, 4 NE (50), Ein paar Wolken (801)
> 18:47:49.845 -> 18:47 31336 600 18:48 30728 889 18:49 30728 902 18:50
> 31136 902
>
>
> wrong (with DS18)
>
>
> 8:56:00.698 -> readSPIFFS: mounted
> 18:56:00.731 -> *WM: [1] <form action='/wifi'
> method='get'><button>Configure WiFi</button></form><br/>
> 18:56:00.731 -> <form action='/info'
> method='get'><button>Info</button></form><br/>
> 18:56:00.731 -> <form action='/exit'
> method='get'><button>Exit</button></form><br/>
> 18:56:00.731 ->
> 18:56:00.938 -> WiFi: myClock-E9FF32 192.168.192.226
> 18:56:00.938 -> setup: 66119, DE, Europe/Berlin, true
> 18:56:01.413 -> getOffset: 7200
> 18:56:01.413 -> setNTP: configure NTP ... OK
> 18:56:01.413 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
> 18:56:02.404 -> 18:56 19F, 59%, 4 NE (50), Ein paar Wolken (801)
> 18:56:02.713 -> 18:56 31184 599
> 18:56:03.256 -> Exception (28):
> 18:56:03.256 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
> excvaddr=0x00000000 depc=0x00000000
> 18:56:03.256 ->
> 18:56:03.256 -> >>>stack>>>
> 18:56:03.256 ->
> 18:56:03.256 -> ctx: cont
> 18:56:03.256 -> sp: 3ffffd50 end: 3fffffc0 offset: 01a0
> 18:56:03.256 -> 3ffffef0: 3fffff40 00000000 3fff05d4 4021b33f
> 18:56:03.256 -> 3fffff00: 00000000 31f126f6 40100400 00000a30
> 18:56:03.256 -> 3fffff10: 401004fc 00000001 c0039035 3fff05c2
> 18:56:03.256 -> 3fffff20: 3fff05d4 00000000 3fffff40 4021b5d4
> 18:56:03.256 -> 3fffff30: 3fff073c 3fff05d4 00000000 4021b6fd
> 18:56:03.256 -> 3fffff40: 00000850 000002ee 3fff05d4 4021b464
> 18:56:03.256 -> 3fffff50: 3fff073c 00000001 3fff05d4 4021b725
> 18:56:03.256 -> 3fffff60: 3fff22e4 00000038 3fff05d4 40209e4c
> 18:56:03.289 -> 3fffff70: feefeffe feefeffe 00000000 5ee27e42
> 18:56:03.289 -> 3fffff80: 00000002 00000030 3fff2084 3ffe8579
> 18:56:03.289 -> 3fffff90: feefeffe feefeffe feefeffe 3fff2430
> 18:56:03.289 -> 3fffffa0: 3fffdad0 00000000 3fff23f0 4021ea1c
> 18:56:03.289 -> 3fffffb0: feefeffe feefeffe 3ffe8598 40100f29
> 18:56:03.289 -> <<<stack<<<
> 18:56:03.289 ->
> 18:56:03.289 -> ets Jan 8 2013,rst cause:2, boot mode:(3,6)
> 18:56:03.289 ->
> 18:56:03.324 -> load 0x4010f000, len 1392, room 16
> 18:56:03.324 -> tail 0
> 18:56:03.324 -> chksum 0xd0
> 18:56:03.324 -> csum 0xd0
> 18:56:03.324 -> v3d128e5c
> 18:56:03.324 -> ~ld
> 18:56:03.392 ->
> 18:56:03.392 -> readSPIFFS: mounted
> 18:56:03.458 -> *WM: [1] <form action='/wifi'
> method='get'><button>Configure WiFi</button></form><br/>
> 18:56:03.458 -> <form action='/info'
> method='get'><button>Info</button></form><br/>
> 18:56:03.458 -> <form action='/exit'
> method='get'><button>Exit</button></form><br/>
> 18:56:03.458 ->
> 18:56:03.631 -> WiFi: myClock-E9FF32 192.168.192.226
> 18:56:03.631 -> setup: 66119, DE, Europe/Berlin, true
> 18:56:04.035 -> getOffset: 7200
> 18:56:04.035 -> setNTP: configure NTP ... OK
> 18:56:04.035 -> setNTP: next timezone check @ Sat Jun 13 02:00:00 2020
> 18:56:05.050 -> 18:56
> 19F, 59%, 4 NE (50), Ein paar Wolken (801)
> 18:56:05.319 -> 18:56 31288 599
> 18:56:05.865 -> Exception (28):
> 18:56:05.865 -> epc1=0x4021b0ab epc2=0x00000000 epc3=0x00000000
> excvaddr=0x00000000 depc=0x00000000
> 18:56:05.865 ->
> 18:56:05.865 -> >>>stack>>>
>
>
>
>
> Gesendet: Mittwoch, 10. Juni 2020 um 19:51 Uhr
> Von: "daud" ***@***.***>
> An: "dragondaud/myClock" ***@***.***>
> Cc: "frederic-kleinert" ***@***.***>, "Author" <
> ***@***.***>
> Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated
> with esp8266 (#25)
>
>
>
> I expect it may be a library issue. I haven't retested the code with a
> newer core version recently. If you monitor the output on serial it may
> give an indication as to where it is failing.
>
> On Wed, Jun 10, 2020 at 11:42 AM frederic-kleinert <
> ***@***.***>
> wrote:
>
> > Hello!
> > I am trying to activate the internal temperature sensor in the code
> > myClock.ino. To do this, I remove the comment sign in front of the line
> > //#define DS18 // enable DS18B20 temperature sensor. Compilation runs
> > without errors. But the display gets into a loop during execution:
> Welcome
> > screen, instruction to start the web server, then briefly the current
> time
> > and before the next seconds, again everything from the beginning. With
> DS18
> > deactivated, everything runs normally. Is the cause known?
> > With kind regards
> >
> > Translated with www.DeepL.com/Translator (free version)
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#25>, or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AGM5GPVV2UP6JPJ6BF7KTXLRV7AXPANCNFSM4N2THQ5A
> >
> > .
> >
>
>
> --
> david denney
> dragondaud AT gmail DOT com
> 719-821-8900
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#25 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AGM5GPSHGTWCJ3XRHK2WKGDRWEG5LANCNFSM4N2THQ5A
>
> .
>
--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGM5GPR35NDJ2DVHS3RPE73RWE3UVANCNFSM4N2THQ5A>
.
--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Just tested it using ESP8266 2.6.3 core, and 3.8.0 Dallas Temp and do not
see your issue. Make sure you are using this version:
https://github.com/milesburton/Arduino-Temperature-Control-Library/releases/tag/3.8.0
…--
david denney
dragondaud AT gmail DOT com
719-821-8900
|
Hello!
Sorry, it's not working. When I install the Dallas temp library (3.8.0) via the library management and look in DallasTemperature.h, it says 3.7.9. If I now install the Arduino Temperature Control Library master, it says 3.8.1 in DallasTemperature.h. I can't find 3.8.0 anywhere. Do you remember it being related to different OneWire libraries?
Gesendet: Samstag, 13. Juni 2020 um 22:02 Uhr
Von: "daud" <[email protected]>
An: "dragondaud/myClock" <[email protected]>
Cc: "frederic-kleinert" <[email protected]>, "Author" <[email protected]>
Betreff: Re: [dragondaud/myClock] Endless loop when DS18B20 is activated with esp8266 (#25)
Just tested it using ESP8266 2.6.3 core, and 3.8.0 Dallas Temp and do not
see your issue. Make sure you are using this version:
https://github.com/milesburton/Arduino-Temperature-Control-Library/releases/tag/3.8.0
…--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hello!
When the display is in loop mode, you can briefly see the time display. I took a picture of it. I noticed that the top line does not move to the right to make room for the inside temperature display. Is that correct?
Just tested it using ESP8266 2.6.3 core, and 3.8.0 Dallas Temp and do not
see your issue. Make sure you are using this version:
https://github.com/milesburton/Arduino-Temperature-Control-Library/releases/tag/3.8.0
…--
david denney
dragondaud AT gmail DOT com
719-821-8900
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
I am trying to activate the internal temperature sensor in the code myClock.ino. To do this, I remove the comment sign in front of the line
//#define DS18 // enable DS18B20 temperature sensor. Compilation runs without errors. But the display gets into a loop during execution: Welcome screen, instruction to start the web server, then briefly the current time and before the next seconds, again everything from the beginning. With DS18 deactivated, everything runs normally. Is the cause known?
With kind regards
Translated with www.DeepL.com/Translator (free version)
The text was updated successfully, but these errors were encountered: