This was in the MDot logs, how come we are getting such a big number from the getNextTxMs for the join backoff interval? The percentages called out in the Join Backoff features, is that a function of time? FYI we have not been connected to the conduit for about 14-15 hours now, also when we get into a series of join failure we get into a 5 minute sleep cycle, so technically we shouldn’t have reached such as large back off time correct?
4/18/2017 12:55:25 PM: [TRACE] Checking if connected to the LORA Network.....
4/18/2017 12:55:25 PM: [TRACE] Not connected to the network.....
4/18/2017 12:55:25 PM: [TRACE] joining network....
4/18/2017 12:55:25 PM: [TRACE] Initiating join...
4/18/2017 12:55:25 PM: [TRACE] Join Network - Auto OTA
4/18/2017 12:55:25 PM: [TRACE] Join attempt #446
4/18/2017 12:55:25 PM: [DEBUG] Join Backoff: 71122 s
4/18/2017 12:55:25 PM: [ERROR] Join backoff
4/18/2017 12:55:25 PM: [ERROR] failed to join network -4:Join Error
4/18/2017 12:55:25 PM: [DEBUG] getNextTxMs: 71122000
4/18/2017 12:56:31 PM: [TRACE] Initiating join...
4/18/2017 12:56:31 PM: [TRACE] Join Network - Auto OTA
4/18/2017 12:56:31 PM: [TRACE] Join attempt #447
4/18/2017 12:56:31 PM: [DEBUG] Join Backoff: 71057 s
4/18/2017 12:56:31 PM: [ERROR] Join backoff
4/18/2017 12:56:31 PM: [ERROR] failed to join network -4:Join Error
4/18/2017 12:56:31 PM: [DEBUG] getNextTxMs: 71057000
4/18/2017 12:57:36 PM: [TRACE] Initiating join...
4/18/2017 12:57:36 PM: [TRACE] Join Network - Auto OTA
4/18/2017 12:57:36 PM: [TRACE] Join attempt #448
4/18/2017 12:57:36 PM: [DEBUG] Join Backoff: 70991 s
4/18/2017 12:57:36 PM: [ERROR] Join backoff
Thanks,
Ajay