LTE, analysis of connectivity
-
This information might be of some value to some members of the community. I have tested my setup through the night.
My code is pretty straight forward and based on @micksta 's example for an LTE Cat M1 setup in Melbourne (which is also where I am).
I use Telstra's network, band 28.
lte.attach() seems to hang sometimes, so I have introduced the WDT to take care of a connection that is taking longer than expected (or that will never be made...).
I use the deep sleep mode for 30 seconds after doing all the required operations (mostly setting up the LTE connection). From the data below, we can safely assume that these take about 35 seconds (65s - 30s deep sleep). I could probably reduce some delays between AT commands in the code, but would decrease the reliability of the system.
The behaviour is generally predictable, when the connection is made, then all is good (it will take pretty much the same amount of time to do all the data exchange). But sometimes the connection is not established and the WDT takes over. Several failures have happened in a row, multiple times.
Overall, 19 operations out of the 365 took longer than expected for this test. So we are looking at a reliability of 94.79 % .
Here is the data:
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login