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.
The Things Network (TTN) is a global LoRaWan public network kernel based on crowd-source infrastructure. This initiative sounds really interesting in my point of view because it breaks one of the main LoRaWan issues : the country based operators organization.
Related to this good point, the negative point is the current area covered by a such network limited to the contributor localization, generally in the main cities.
That said, I’m convinced : when you want to create a private LoRaWan network you have to manage a network kernel managing gateways, device authorizations… You can do it yourself, you can pay someone to do it for you or, eventually, you can lever TTN for this use. As a counterpart you will extend the network and offer this benefit to any around. That way it makes sense and gives large opportunities to the networks and it’s private users.
Long introduction for a technical topic … How to join this network once you have a Kerlink LoRa Iot station available ? Continue reading →
The RF 868MHz is a public bandwidth European Low Power Networks (LPWAN) as Sigfox and LoRaWan are using for communicating.
This bandwidth is regulated by different norms like ERC-REC-70-3E in Europe and have national norms in relation. In France ARCEP 2014-1263 seems to be the last one validated in the JO on the 30th of January 2015. The following video is a second episode of my VLOG on LPWan technologies. As usual, the video is in French but this post will give you a overview in english.
I’m actually doing some experiment with the French LoraWan network operated by Objenious. To receive the message on your backend application, one of the way is to build a callback function to proceed the data.
Due to LoraWan protocol, you have different type of possible callback like for: joining network, uplink messages and downlink report.
This post gives an exemple on how to implement an uplink message callback handler, with php, for your application backend server.
Today Sigfox is releasing a really good document about antenna design. This pretty document can be found following this link (available on July 7th). This document from TI also contains really well detailed information about the alchemy of antennas and the different kind of product you can find. From Silicon Labs you also have an interesting development kit for 868 antennas with performance published in this application note.
This is to say antenna is one of the most important part of a 868 object, as for Sigfox as for LoRa where the problem is basically the same. I discussed with different sigfox object designed and every-time the antenna was a big project issue. Some has payed about 10-15k€ to get a custom optimized design.
I never experiment a custom design but I made test with various antennas and the purpose of this post will be to give you my feedback on the different solutions.
Making downlink working correctly with RN2483 on LoRaWan is not a simple a quick thing to do if you do not have all the keys to do it. After spending some time to fix my code for this, here are the tips to consider and not forget !
I was looking for a real LoRaWan experimentation on the field, not only a given open field performance where the result do not match the reality.
For this reason, I installed a Kerlink gateway on a friend’s balcony living on a high part of my city. Then I moved a tracker reporting its GPS position on regular basis and day after day I built a map of the area covered by this antenna.
This post details the results of this expermientation
Once you have found the great idea of the year and you want to start implementing your first prototype it is time to choose the right technology. Some would say you should not choose at this step and implement both at end but in my point of view it looks like and economical mistake to do this way. Prototype is to demonstrate and final product. It can request another technology, for sure. But in my point of view the best is to take the right one at the beginning. For most LoRa and Sigfox are both equivalent or for some others one is over the other one, best depends who you ask. In my point of view, if I consider my 2-3 years sigfox experience and my starting experience on LoRa with 1 year background research on it, there is no magic answer. Context of your idea is the keypoint then you have some technical elements to take into account to finalize your decision.
This post will try to illustrate where each of the technology is the best and give you some decision keypoints.
Are you looking for connecting an object ?
Based on BLE, Wifi, Sigfox, GSM, RF433?
IngeniousThings, my company, is able to help you on your IoT design, creativity, business model and provides quick prototypes. We are specialists for helping startups with LoRaWan and SigFox design.
You can also contact me here