This post explains how to use ST LoRaWAN development kit to transmit data over French Orange LoRaWAN network. We will use a sample source code from ST, which we will compile and link using System Workbench for STM32, based on Eclipse. Continue reading “Connecting ST LoRaWAN development kit to Orange LoRaWAN network”
In this article, I maintain a list of various (private or public) organizations that are active in the field of standards that can be used by the Internet of Things. For each organization, a what and a who sections are provided. The source of information is the organization’s website.
This is the fourth year I give my classes about the Internet of Things, to postgraduate students of a Telecom and Electronics Master of the University of Nice (France). From six hours for previous years, my course slot increased to nine hours. Consequently, I was able to spend more time on some important topics, like communications and embedded software. And I introduced two new sections: big data and security.
The new edition of the presentation I use as a support is available on SlideShare.
Here is a list of various low cost programmable boards, with some (wireless) connectivity.
- Thunderboard Sense 2 Sensor-to-Cloud Advanced IoT Development Kit, from Silicon Labs – ARM Cortex M4 core with 256 kB RAM and 1024 kB Flash, multi-protocol radio, sensors, source code of applications for Android, iOS and web – US$36 (Dec-2019)
- Icarus IoT Board, from Actinius – based on the nRF9160 – LTE-M / NB-IoT, GPS – 99.50 € (Nov-2019)
- Thingy:91, from Nordic – based on the nRF9160 – LTE-M / NB-IoT, GPS, 16 sensors, Bluetooth / Thread / Zigbee / ANT, plastic and rubber case – around US$ 119 (Aug-2019)
The Munic.Box is highly configurable. It can monitor many vehicle parameters (location, speed, acceleration, etc.) in real time, including some OBD data. Data is sent to CloudConnect, a communication server that can forward received data to your own application, thanks to a webhook. Continue reading “Munic.Box data”
In the beginning of the 2000s, while the small company I had cofounded in 1990 was still active, we decided to answer a Request for Proposal submitted by a waste removal company, for a system allowing to check whether all planned daily garbage collections had been performed. At this time, we didn’t know a lot about the waste removal market. But we knew we were experienced enough in technologies we would have to assemble in order to answer the RFP: onboard equipment and embedded software, GNSS positioning, wireless communications, Geographical Information Systems, etc. Continue reading “IoT tips and tricks #2”
As I wrote in another post, one of the distinctive features of IoT projects is that they require integration of technical blocks originating from three different domains: electronics, communications and software. And inside these three domains, various different sub-domains are usually involved: analog and digital electronics, wireless communication modules, protocol stacks, embedded software, user interfaces, database management, analytics, geospatial data, etc. Continue reading “IoT tips and tricks #1”
Keeping in mind the global view is very important when designing an IoT system. Why?
A first distinctive feature of IoT projects is that they require integration of technical blocks originating from three different domains: electronics, communications and software. And in every of these three domains, various different subdomains are usually involved: analog and digital electronics, wireless communication modules, protocol stacks, embedded software, user interfaces, database management, analytics, geospatial data, etc. Continue reading “Uploading sensor data using a cellular network”