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.
Posted in IoT
Tagged gps, IoT, LoRaWAN, LPWA, SigFox
Recurrent question where I usually see the wrong option taken by industrials: do I need to implement my own private network for m LPWA network ? In many case the wrong choice has been made due to a lack of understanding of network total cost of ownership. For sure I heard element about MY DATA privacy, but honestly, all the companies are putting added value data into the Cloud, so don’t tell me you unknown machine temperature is a sensitive data ?!? That said, let’s back to the true question : when does it make sense to create your own private network ?
Posted in IoT
Tagged LoRaWAN, LPWA, SigFox
As a backend developer, the Sigfox API is not a really good experience. This for multiple reasons and it is a good example on how a really good product can get a developer push-back just because of the interaction layer.
I can’t change the API itself (and its not y role) but as I was bored to use POSTMAN tool and the Sigfox backend documentation (who already used it will understand) I decided to spend some hours this week to rewrite most of the API endpoint into a clean open-api format into a Spring application to get benefit of the SpringFox swagger front.
This project is not fully terminated but already in place with the most used API endpoint. The next will arrive soon. Read mode to get access.
Following the previous post where we saw how to transmit data on Sigfox with an Arduino MKRFox1200, in the second part we will learn how to consume these data in a backend site. To make this simple we are going to implement a solution using Adafruit.io service. This service allows to create graphics from data received from an API. We will configure Sigfox backend to push device data to this API.
Arduino MkrFox1200 sounds like Arduino for Maker using Sigfox. This board is an official Arduino product, looking like Arduino Nano series (but not pin-compatible, longer and larger)
It is composed of a SAM D21E MCU (Microchip ARM Cortex M0) operating at 48MHz. It includes 256K flash memory and 32K of SRAM. We can consider this as an Arduino under steroid.
The Sigfox radio layer is composed by an ATA8520. This is a Microchip Sigfox module based on AVR MCU. This module is communicating with the SAM D21E module with a SPI bus. The radio module is supporting RCZ1 zone (Europe).
This board can be found in many eShop places for a price around 45€ including an antenna and 2 year of Sigfox network access.
In this Post we will see how to get started with this board and how start programming with it.
Posted in IoT, Sigfox
Tagged arduino, SigFox
There are multiple ways to track something or someone. Cellphone are using different method to be able to give you a precise location in most of the situation. The more global one is GPS, it works anywhere on earth but do not really work indoor. It is also costly (about 8$ or more) and power consuming. Outdoor your usually have a precision of 15 meters. The less precise one is triangulation : a message received by different antennas will be located by the network in an area covered by all these antennas. This solution works anywhere the network is covering and do not need specific power other than for communicating. The precision is usually from 500m to 10km.
The last usual method we use is the one we are going to implement in this post : the WiFi positioning. The tracker is listening for the WiFi access point around and ask one of the existing database knowing most of the WiFi location to get a position. This is working thanks to the crowding effort all of us are doing with our smartphone of capturing WiFi around us and associated locations. The WiFi solution is working where WiFi is, so usually in the cities ; around buildings. It works well indoor, better than outdoor where WiFi is less active. The precision is about 30-50 meters. The power consumption is lower than GPS.
Sigfox is a LPWA (Low Power Wide Area) network covering about 45 countries (as today) dedicated to low power autonomous devices aka IoT. Asset tracking is one of the best use-case.
The use of Sigfox with a WiFi tracker is allowing to create a low-cost tracker device, autonomous on battery from month to years, getting benefit in 45 countries of a WiFi + network localization.
This post will explain how to get started in this technology by using two standard, easy to use and low cost components allowing to get your prototype for about $5 of hardware.
Sigfox is a really nice technology when you want to make a really quick experimentation in IoT. The Time To Hello World will take you less than 5 minutes and it makes it really easy.
That said after the POC comes the production, and the way you manage your Sigfox backend for production is not the way you build your quick & dirty front-end platform for the POC.
This post will introduce how to make your Production platform and what is the difficulty you need to consider. I’ll propose you some architectural solution I’ve put in place but they are one of the ways to implement it. I won’t detail the pre-packages PaaS solution as i’m not a big fan of them : in my point of view, they are firstly responding to the POC situation, but it is only my own opinion.
Posted in Sigfox
Tagged backend, SigFox
This IoT class is an introduction to IoT and LPWAN, it has been made to be a 2x2h teaching session for engineer school students. This class has been given to I.S.I.M.A. school in Clermont-Ferrand in 2017. This class has been completed by 2 more hours on the backend part for IoT by Daniel Petisme. It has been followed by three industrial conferences.
The content of my class had the following slides (in French):
Introduce why IoT is a revolution compared to M2M and why service matter. Introduce the different phases of a connected object design and the involved technologies. Introduce the challenge, from the technical stand point to the business model considerations.
Introduce the LPWAn technologies, presenting Sigfox and LoRaWan solutions.