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.
After making some post on Arduino MKRFOX1200, here I come with the first steps to use MKRWAN1300 board to send your first frame on TTN and also how to use them for discovering the TTN coverage around.
MKRWAN1300 board is a LoRaWan Arduino board based on the Murata CMWX1ZZABZ module. This module is capable for LoRaWan in Europe (868Mhz), NA (915MHz) Asia (923MHz) …. It is also capable for Sigfox in both zone (but actually not with this board as much as I know). Producing 14dB emission and capable for 20dB emission for FCC zone. The price of the Arduino board is about 40€ and it is largely available on Internet.
In this post we are going to see how to make the first steps with this board and create a device to map the TTN network coverage with and without a GPS.
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.
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 ?
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.
LPWA networks needs antennas and gateway to receive the device communication and transfer them to a network kernel. You can take a look to my post on the LPWA network architecture for more details.
In the LoRaWan ecosystem we call the first part of this network architecture a gateway. There are different kind of gateway : The network operator gateway with a big and efficient antenna, capable to support external weather like the Kerlink IoT Station and some low costs solution you can deploy at home or within a building (indoor) to cover a local device fleet.
The Kerlink Wirenet iFemtoCell device is a such type of gateway. this post will review how to get start with it and what we can expect in term of coverage.
New episode of my LPWAn post series, this time, about the network architecture and the role of the network kernel.
The network architecture is different than a classical IP communication from client to server: the LPWAn architecture is based on a kernel network allowing the protocol transformation from the Sigfox / LoRaWan world to the IP-Internet world.
In the LPWAn protocol the addressing is limited to one device address only to reduce the frame size and as a consequence all the frame have to be captured by a central system: the network kernel. It will route the message correctly to the end user application based on device association made on registration.
This post is related to a french video (as usual) and detailed in the following part of this post.