esib_iot_challenge
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
esib_iot_challenge [2017/05/17 09:17] – samer | esib_iot_challenge [2017/05/17 17:53] – [3. Devices] samer | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== ESIB IoT Challenge ====== | ====== ESIB IoT Challenge ====== | ||
- | Welcome to the ESIB IoT Challenge. In this challenge, you will designing and prototyping the first IoT services based on a LoRaWAN network. | + | Welcome to the ESIB IoT Challenge. In this challenge, you will be designing and prototyping the first IoT services based on a LoRaWAN network. |
- | ===== -. What is a LoRaWAN | + | ===== -. Platform ===== |
- | In this challenge, you will benefit from the first experimental platform implementing an end-to-end LoRaWAN solution in Lebanon. The platform consists of the following elements: | + | During |
* Devices that communicate to one or more gateways via a wireless interface using single hop LoRa and implementing the LoRaWAN protocol. These devices are physically connected to sensors that generate data. | * Devices that communicate to one or more gateways via a wireless interface using single hop LoRa and implementing the LoRaWAN protocol. These devices are physically connected to sensors that generate data. | ||
Line 14: | Line 14: | ||
[{{ : | [{{ : | ||
- | ===== -. Devices | + | <WRAP center round help 100%> |
- | ==== -. Autonomo with LoRaBee ==== | + | * Where is the LoRa modulation implemented on the platform? |
+ | * What are the advantages of the LoRa modulation? | ||
+ | * How LoRa is compatible with LPWAN requirements and constraints? | ||
+ | * What is LoRaWAN? What is the difference between LoRaWAN and LoRa? | ||
+ | * Illustrate the protocol stacks on the LoRaWAN platform. | ||
+ | * What elements are IP enabled in the platform? What do you think about IP support in IoT? | ||
+ | </ | ||
+ | ===== -. Backend | ||
+ | In a LoRaWAN network, the devices communicate with a Network Server through the gateway. The backend installed in the platform is based on an open-source LoRaWAN network-server https:// | ||
- | Starting with the devices in the LoRaWAN platform, we will use an [[http://support.sodaq.com/ | + | [{{ :app-loraserver.png? |
- | In order to configure | + | Start by choosing the application named '' |
+ | * A unique node name: '' | ||
+ | * The node description | ||
+ | * A unique | ||
+ | * The application EUI on 64 bits: '' | ||
+ | * A unique application key on 128 bits also obtained by random generation. | ||
+ | |||
+ | Make sure that the '' | ||
- | - Verify that you have the latest Arduino IDE from [[https:// | + | <WRAP left round help 100%> |
- | - Install | + | * What does the application EUI mean? How is it used in LoRaWAN? |
- | - Add the following library {{ : | + | * What does the application key mean? How is it used in LoRaWAN security? |
+ | * Compare the two device activation methods used in LoRaWAN by giving the advantages and inconvenients. | ||
+ | * What is the difference between the two receive windows | ||
+ | </WRAP> | ||
+ | ===== -. Devices ===== | ||
- | Now you are ready to write a sketch for the device. Here is one example sketch {{ : | + | Devices in the LoRaWAN platform |
- | In this part, you should put the keys for Over-The-Air Activation (OTAA) as explained | + | Start by verifying |
- | <code c++> | + | |
- | // USE YOUR OWN KEYS! | + | |
- | const uint8_t devEUI[8] = | + | |
- | { }; | + | |
- | // USE YOUR OWN KEYS! | + | <WRAP left round help 100%> |
- | const uint8_t appEUI[8] = | + | * Give the characteristics of the Arduino you are using: model, number of pins, type of pins, memory sizes, etc. |
- | { }; | + | * Give the main characteristics of the LoRa shield from Dragino (www.dragino.com). |
+ | * What type of Antenna are you using? Explain the corresponding characteristics. | ||
+ | </ | ||
- | const uint8_t appKey[16] = | + | Now you should configure your device with the same identifiers '' |
- | { }; | + | |
- | </ | + | |
- | + | ||
- | The pins for connecting | + | |
- | <code c++> | + | |
- | int light_pin = A0; | + | |
- | int moisture_pin = A2; | + | |
- | int temperature_pin = 0; | + | |
- | int temperature_vcc_pin = 1; | + | |
- | int moisture_vcc_pin = 8; | + | |
- | int moisture_gnd_pin = 7; | + | |
- | </ | + | |
- | The OTAA method is used for joining the network and Adaptive Data Rate (ADR) is activated: | ||
<code c++> | <code c++> | ||
- | LoRaBee.initOTA(loraSerial, devEUI, appEUI, appKey, true) | + | static const u1_t PROGMEM APPEUI[8]= { }; |
- | </ | + | void os_getArtEui |
- | Eight different sub channels are activated with data rate ranges from 0 to 5: | + | // This should also be in little endian format, see above. |
- | <code c++> | + | static const u1_t PROGMEM DEVEUI[8]= { }; |
- | LoRaBee.configChFreq(0, 868100000L, | + | void os_getDevEui |
- | LoRaBee.configChFreq(1, | + | |
- | LoRaBee.configChFreq(2, | + | static const u1_t PROGMEM APPKEY[16] = { }; |
- | LoRaBee.configChFreq(3, 867100000L, | + | void os_getDevKey |
- | LoRaBee.configChFreq(4, 867300000L,0,5,1); | + | |
- | LoRaBee.configChFreq(5, | + | |
- | LoRaBee.configChFreq(6, 867700000L, | + | |
- | LoRaBee.configChFreq(7, 867900000L, | + | |
</ | </ | ||
- | Finally, | + | <WRAP left round tip 100%> |
- | <code c++> | + | Note that the device and application identifiers should be in little endian format, while the application key is in big endian format. For example, '' |
- | LoRaBee.send(1, (uint8_t*)message.c_str(), message.length()) | + | </WRAP> |
- | </code> | + | |
- | ==== -. Arduino with Dragino Shield ==== | + | |
- | === -. Periodic Message Sending === | + | |
- | Devices in the LoRaWAN platform can also be implemented on Arduino boards with Dragino shields. The combined module as well as the basic configuration steps are presented in [[simple_lora_prototype|Simple Prototype of LoRa Communications]]. Similarly to the Autonomo device, you can download the following sketch {{ : | ||
The pin mapping corresponds to the Dragino electronic schematic: | The pin mapping corresponds to the Dragino electronic schematic: | ||
Line 107: | Line 103: | ||
</ | </ | ||
- | The message containing the sensor values is transmitted on one of the radio channels | + | The message containing the sensor values is transmitted on one of the radio channels: |
<code c++> | <code c++> | ||
LMIC_setTxData2(1, | LMIC_setTxData2(1, | ||
</ | </ | ||
- | |||
- | The adaptive data rate is not supported, and the spreading factor is configured as follows: | ||
- | <code c++> | ||
- | LMIC_setDrTxpow(DR_SF7, | ||
- | </ | ||
- | |||
- | === -. Triggered Message Sending === | ||
- | |||
- | You can also find another example of sketch to download: {{ : | ||
- | ===== -. Gateways ===== | ||
- | ==== -. Single Channel Gateway ==== | ||
- | |||
- | The single channel gateway includes a LoRa transmission module (Dragino Shield) connected to a Raspberry Pi (2 or 3) as shown in Figure 2. Communication between the two modules is done over an SPI interface. | ||
- | |||
- | [{{ : | ||
- | |||
- | In order to assemble the gateway, start by making the wire connections: | ||
- | [{{ : | ||
- | [{{ : | ||
- | |||
- | Connect the Raspberry Pi to the Internet and install the packet forwarding software. The source code of the single channel packet forwarder is available on: [[https:// | ||
- | * Enable SPI on the Raspberry Pi using raspi-config | ||
- | * Download and unzip the source code: | ||
- | |||
- | <code bash> | ||
- | wget https:// | ||
- | unzip master.zip | ||
- | </ | ||
- | |||
- | * Install the wiring library: | ||
- | |||
- | <code bash> | ||
- | apt-get update | ||
- | apt-get install wiring | ||
- | </ | ||
- | |||
- | Compile the packet forwarder: | ||
- | <code bash> | ||
- | make all | ||
- | </ | ||
- | |||
- | For gcc version 4.6.3, a compilation error results in the following warning '' | ||
- | < | ||
- | CFLAGS = -std=c++0x -c -Wall -I include/ | ||
- | </ | ||
- | |||
- | Now, you need to configure the single channel packet forwarder. This is done in the {{ : | ||
- | |||
- | Finally, you can run the packet forwarder as root! | ||
- | |||
- | <code bash> | ||
- | nohup ./ | ||
- | </ | ||
- | ==== -. Kerlink IoT Station ==== | ||
- | |||
- | < | ||
- | # activates eth0 at startup | ||
- | ETHERNET=yes | ||
- | # claims dhcp request on eth0 | ||
- | ETHDHCP=yes | ||
- | |||
- | # Selector operator APN | ||
- | GPRSAPN=gprs.touch.com.lb | ||
- | # Enter pin code if activated | ||
- | GPRSPIN=0000 | ||
- | # Update / | ||
- | GPRSDNS=yes | ||
- | # PAP authentication | ||
- | GPRSUSER= | ||
- | GPRSPASSWORD= | ||
- | |||
- | # Bearers priority order | ||
- | # | ||
- | BEARERS_PRIORITY=" | ||
- | </ | ||
- | |||
- | < | ||
- | ./ | ||
- | </ | ||
- | |||
- | < | ||
- | 3270 root 2548 S /bin/sh ./ | ||
- | 3288 root 34908 S ./ | ||
- | </ | ||
- | |||
- | < | ||
- | / | ||
- | |||
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | ||
- | pppd (pid 5273) is running... | ||
- | Session: Rx=58, Tx=163 | ||
- | Globals: Rx=1130457, Tx=1195592 | ||
- | Sum: | ||
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | ||
- | </ | ||
- | |||
- | ===== -. Backend ===== | ||
- | ==== -. Loraserver ==== | ||
- | |||
- | The Loraserver has a web interface for configuring the applications and devices on the platform. Full details for installing the software are provided on [[https:// | ||
- | |||
- | [{{ : | ||
- | |||
- | Start by creating and application as in Figure 5. Then create a node in this application and provide the following information: | ||
- | * A unique node name | ||
- | * The node description | ||
- | * A unique device EUI on 64 bits: Random identifiers can be generated on [[https:// | ||
- | * The application EUI on 64 bits: this can be a common identifier for all nodes using the same application. | ||
- | * A unique application key on 128 bits | ||
- | |||
- | In order to enable OTAA join method, you have to make sure that the '' | ||
- | |||
- | |||
- | ==== -. The Things Network ==== | ||
- | |||
===== -. Applications ===== | ===== -. Applications ===== | ||
- | ==== -. mqtt-spy ==== | ||
- | |||
mqtt-spy is an open source utility intended to help you with monitoring activity on MQTT topics. It has been designed to deal with high volumes of messages, as well as occasional publications. mqtt-spy is a JavaFX application, | mqtt-spy is an open source utility intended to help you with monitoring activity on MQTT topics. It has been designed to deal with high volumes of messages, as well as occasional publications. mqtt-spy is a JavaFX application, | ||
You can use mqtt-spy to debug the messages received from the LoRaWAN devices. For this, you should download the software tool from [[https:// | You can use mqtt-spy to debug the messages received from the LoRaWAN devices. For this, you should download the software tool from [[https:// | ||
- | ==== -. Emoncms ==== |
esib_iot_challenge.txt · Last modified: 2021/08/28 09:53 by samer