Mike G

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

8 years, 7 months ago.

Dynamics of a Multitech mDot connection

https://developer.mbed.org/teams/MultiTech/code/libmDot/file/0b4eb17d07ae/mDot.h

I'm trying to understand some details of an mDot's connected status.

If I call joinNetwork() from the libmDot library and my unit connects, ( using AUTO_OTA ) does my code have to handle the "join" any further?

For example, if after joining successfully, the mDot perceives difficulty communicating with the Conduit gateway (say, receiving no ACKs), or if the gateway does not hear from some particular mDot for some extended period of time, will the "join" still exist, or somehow heal itself, etc.?

In other words, does my mDot code need to test the mDot network status with something like getJoinMode() and take steps or does the mDot take care of this automatically? If I need to roll my own code to handle this "stay connected" issue, is there a preferred methodology?

Be the first to answer this question.