SK
Signal K•4mo ago
pa1pdr

Remote debugging in V3.0?

I've just converted my SensESP app to V3.0, which does not have easy serial debugging. Under V2 this was not a problem: pop in -D REMOTE_DEBUG under the build_flags and I could easily telnet into the ESP. According to the upgrade documentation this should work under V3 as well, however when doing so the connection gets refused on port 23.
4 Replies
Matti Airas
Matti Airas•4mo ago
No, sorry, that has been removed in v3. The RemoteDebug library has been abandonded for several years, and also, I wasn't aware anyone was still using that feature. 🙈 One motivation for migrating to native ESP-IDF logging is that logging output can be forwarded to a callback function, meaning that it should be possible to get logging output exposed over e.g. WebSockets to the web UI.
pa1pdr
pa1pdrOP•4mo ago
So any recipe for that? Else I'm pegged to 2.7.2 I'm quite happy with never touching USB: just use OTA for updates and RemoteDebug when in trouble (else debug is off)
Matti Airas
Matti Airas•4mo ago
I have one project in which I create a TCP server for monitoring an NMEA 0183 input stream. I'll clean it up and make it public - it should be quite possible to take the server code and connect ESP-IDF logging to it.
pa1pdr
pa1pdrOP•4mo ago
Perfect, that would be extremely useful. My ESP's disappear embedded and do not expose USB ports that are easily accessible afterwards. Remote is a winner!

Did you find this page helpful?