Sigfox is not publishing its detailed specifications. For this reason different people (like me) are doing reverse engineering. Thank to this activity we are now getting more and more information on how the IoT network communication works. I’ve been the first one to publish the uplink frame in details more than a year ago.
Today, during the 35th edition of CCC Congress, Florian Euchner has published, on Github, the first Open-Source Sigfox stack : LibRenard.
This library allows to transform a Sigfox radio signal into a decoded frame (uplink demodulation). It allows to create a Sigfox radio signal from a decoded frame (downlink modulation).
The LibRenard implementation follows the Open Sigfox Protocol specification also host on Github from Florian. It details the uplink as the downlink communication frames. Making this open specification as the real first Sigfox global protocol specification published.
I really want to congratulate Florian for this excellent work. I hope the stack will be soon enriched with the native Sigfox encryption I’ve just finished to detail, with the associated OOB frames.
When you write an IoT firmware, there are different things you may never forget to think about… The coming 10 things you can’t ignore are coming from my experience of smart object creation and the associated field experience.
The field experience is unfortunately the real step where you will improve your firmware and discover all you have forgotten when you have written the firmware and tested it in your laboratory. In laboratory everything is perfect.
The following 10 things you can’t ignore when writing a Firmware is a non exhaustive checklist of points to verify before pushing your code to the field. It is also a list of test conditions you can execute to validate a Firmware / device made by a third party.
STM32 solution for using Sigfox is actually one of the best offer on the market has the solution is powerful, low consumption and allows global coverage with the use of the last Sigfox library versions including Monarq, Bubble… Different module providers are actually designing solutions based on this platform.
In this post we are going to see how to configure the STM32 platform, starting from a STM32L053 devkit plus a S2LP extension. Using a eclipse/gcc environment. The environment installation is described in this post about installing Eclipse for STM32.
For the second year I had the chance to introduce the IoT and LPWAN networks to a group of 150 students in computer engineering school. This year we add a longer time to detail a bit the Sigfox and LoRaWan solution and I’ve added a part on the IoT security.
I’ve tried to propose a different point of view on security aspect, not based on fear but practical things to do and a larger contextual aspect. I’ll try to make video on this specific topic on my Youtube (where you can find in french most of the content of these slides).
So … here are the slides, for my students who joined or not the conferences, and for those who would like to join this course.
After having tested different LoRaWan gateway like Kerlink iFemToCell, TheThingsGateway and Kerlink Wirnet, in the past two years, I was looking for a new low cost indoor gateway for deploying TheThingsNetwork (the global crowd-sourced LoRaWan network) in my city.
Gateway are not all easy to shop, Kerlink at first. As one of my iFemToCell has burned into the hell this summer with no reason after only 3 months powered-on I was not looking for the same. TheThingsGateway has different semiconductor provider reseller but myne suffer of certain instabilities actually and I need to reboot on regular basis. So that’s the reason of this new try.
In the real life you need to create a specific setup once your prototype is transformed into a custom board. This setup redefines the pin mapping, the target MCU and needs to refine the firmware transfer method as you will use and external STLINK programmer.
In this post we are going to see the different step for doing this.
I want to start a new category of posts about IoT, not focus on the technology itself but on the use-cases. That said, for sure my words will be on the technological aspects of this use-case. The objective is to let you understand what are the solution but also what are the challenges behind that use-case. To start I’ve selected the Tracking use-case, reviewing all the GPS, WiFi and operator technics.
Regarding my experience in IoT from the past 5 years, one of the biggest market for LPWAn is actually assets tracking. In number I assume alarm backup is a little bit behind but thanks to one uniq actor. Tracking is far away first regarding the number of actors already having implemented a solution in production. This is also where we find the largest number of objects on the market for a single use-case.
That’s why I decided to start with this use case. I also know it really well for being the founder of one of these solution : Foxtrackr and I’ve already implemented all the technics described below.