-
-
Notifications
You must be signed in to change notification settings - Fork 98
TelnetSpy interferes with EMS bus communication on the ESP8266 #63
Comments
that's correct. the hardware Serial uses the same UART0. This is why I built in the 'set serial' command which disables the EMS when Serial is enabled and had to use Telnet instead. Serial is only really used for debugging as you don't plug one end of the circuit into the EMS line and the other end into a PC. I also describe this in the documentation. |
Serial is set to |
Check if you're using the latest version. This shouldn't happen. Line 146 of MyEsp.cpp should say:
If it still happens, create a case so I can reproduce it. Or try and fix it in the code. |
Immediately above that code is the call to |
you're using an old build. do a git pull. That problem was solved a while
back.
…On Thu, Feb 28, 2019 at 10:19 AM Simon Arlott ***@***.***> wrote:
Immediately above that code is the call to _wifi_callback which calls
emsuart_init(). It's still using the serial output after it has been
reconfigured.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#63 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABLHeFldasmCqwFXhzre9bOCTCH4-7p2ks5vR58TgaJpZM4bVal9>
.
|
After much debugging the UART interrupt handler, I've discovered I need to initialise
usedSer
toNULL
inlib/TelnetSpy/TelnetSpy.cpp
otherwise the hardwareSerial
functions will overwrite the RX interrupt handler (as well as output messages over serial) and no messages will ever be received.The text was updated successfully, but these errors were encountered: