Watchdog timers on the nRF9160

We programmers never write bugs. And when we do, these bugs sometimes bring the program screeching to a halt. While this is typically better than accidentally leaking user data or launching nuclear missiles, it is still decidedly inconvenient1 for the user to have to contact customer service, wait on hold for half an hour, and then be asked “Have you tried turning it off an on again?”. The solution, as always… »

Using CoAP on SARA N2 NB-IoT modules

UDP packets are generally nice but there’s one thing they are: Datagrams. You can’t tell for sure that they have been delivered or when. Usually this is solved by saying “use TCP if you want flow control” but when you are working on NB-IoT modules that might not be an option. The problem If you are sending UDP packets with the SARA N2 module you generally don’t know what will happen with the data once it is sent. »

Log in with GitHub

Up until now we’ve been using the CONNECT ID login for the NB-IoT console. It’s worked fine for some of us but there have been a few drawbacks, particularly that you’ll need a phone to sign up and usually we use the same phone for work and home which again means you have to use the same account for both work and personal projects. For some of us they are pretty much the same but for others – not so much. »

Making sense out of nonsense

One of the first thing we found necessary after we created our NB-IoT platform, was fancy graphs. Because you know, people like graphs. It also helps as a sanity check to see that your data makes sense graphically. There was only one problem, Tm9zeSBsaXR0bGUgYmFzdGFyZCBhcmVuJ3QgeW91Pw== doesn't really translate well into a graph. »