RobMeades
commented
4 months ago Hi there, and sorry to hear you're having so many problems. Splitting them out:
upon re-establishing the connection, the system enters an error loop where it fails to connect, consistently throwing UMQTTER error code 13,0.
From the trace you have pasted in above this looks as though it would be a module problem: at least, I can't see how the ubxlib code would cause this, unless you can see something? If it is a module problem we can try to help but it is kind of a "best effort" thing from a ubxlib standpoint and you might be better off raising it through the proper module support routes.
Occasionally I noticed a discrepancy between the actual connection status and the one identified by the internal callbacks (network is up but it is detected as down). This behavior is reproducible consistently.
This may, of course, be a ubxlib issue - it would imply that we have missed a registration URC, which would be interesting. if you are able to a log of the ubxlib debug output at the time that would be very interesting.
Furthermore, I've observed that the module fails to shut down properly. After every shutdown attempt (with AT commands), the UART pins on the ESP32 side remain active, causing a current leak into the u-blox module. As a consequence the ublox module outputs 0.7v-1.1v not allowing a proper shutdown procedure. I patched this issue by resetting the gpios.
When we close a UART we expect the platform code to put any pins into an "off" state but it might well be that not all platforms do this. We could "grab" any pins that were once UART pins, making them GPIOs and then put them into some form of "off" state (let them float high?). This would be quite difficult to test of course, not something our automated system is built to do. Or we could add a note somewhere that this is something to look out for at application level? I'm always a little wary making a behavioural change to code that has been out there for several years.
tommas0serafin
Hi Rob, Upon losing internet connection on my device, regardless of whether it's due to antenna disconnection or forced disconnection, the device starts throwing UMQTTER error code 13,0, which then transitions to 13,50 or 13,34, indicating a normal behavior. However, upon re-establishing the connection, the system enters an error loop where it fails to connect, consistently throwing UMQTTER error code 13,0. Occasionally I noticed a discrepancy between the actual connection status and the one identified by the internal callbacks (network is up but it is detected as down). This behavior is reproducible consistently.
Furthermore, I've observed that the module fails to shut down properly. After every shutdown attempt (with AT commands), the UART pins on the ESP32 side remain active, causing a current leak into the u-blox module. As a consequence the ublox module outputs 0.7v-1.1v not allowing a proper shutdown procedure. I patched this issue by resetting the gpios on the microcontroller's side but I need to understand if there's an hardware issue causing it or if it's a library bug.
Serial output upon reconnection: