You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a project I need to get the MKNBR connected to a Azure cloud server and yes, I did it! But then I started making it bulletproof. To simulate a loss of communication I just disconnect the antenna and check the signal strength via the nbScanner class. That seems to work and the unit stays operational and on the debug serial issues the problem with signal loss. But then just now and then the signal is up again for no apparent reason, the antenna is still disconnected. All the time the antenna is disconnect I keep on calling the ready() function and status() keeps returning value 3 -> READY. How is that possible? The signal is totally lost. What am I missing?
Then the MQTT client wants to send data and the unit freezes and a WDT occurs.
So, how do I tell the MQTT the connection has dropped and how to get the nbAccess to 'reset' when signal strength is lost.
The text was updated successfully, but these errors were encountered:
Hi all,
For a project I need to get the MKNBR connected to a Azure cloud server and yes, I did it! But then I started making it bulletproof. To simulate a loss of communication I just disconnect the antenna and check the signal strength via the nbScanner class. That seems to work and the unit stays operational and on the debug serial issues the problem with signal loss. But then just now and then the signal is up again for no apparent reason, the antenna is still disconnected. All the time the antenna is disconnect I keep on calling the ready() function and status() keeps returning value 3 -> READY. How is that possible? The signal is totally lost. What am I missing?
Then the MQTT client wants to send data and the unit freezes and a WDT occurs.
So, how do I tell the MQTT the connection has dropped and how to get the nbAccess to 'reset' when signal strength is lost.
The text was updated successfully, but these errors were encountered: