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] – [2.1. Autonomo with LoRaBee] samer | esib_iot_challenge [2017/05/17 19:50] – [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%> |
+ | * 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:// | ||
- | ==== -. Arduino with Dragino Shield ==== | + | [{{ :app-loraserver.png? |
- | === -. Periodic Message Sending === | + | |
- | Devices in the LoRaWAN platform | + | Start by choosing |
+ | * A unique node name: '' | ||
+ | * The node description | ||
+ | * A unique device EUI on 64 bits: Random identifiers | ||
+ | * The application EUI on 64 bits: '' | ||
+ | * A unique application key on 128 bits also obtained by random generation. | ||
+ | |||
+ | Make sure that the '' | ||
- | The pin mapping corresponds to the Dragino electronic schematic: | + | <WRAP left round help 100%> |
- | <code c++> | + | * What does the application EUI mean? How is it used in LoRaWAN? |
- | const lmic_pinmap lmic_pins = { | + | * What does the application key mean? How is it used in LoRaWAN security? |
- | .nss = 10, | + | * Compare the two device activation methods used in LoRaWAN by giving the advantages and inconvenients. |
- | .rxtx = LMIC_UNUSED_PIN, | + | * What is the difference between the two receive windows in LoRaWAN? What are they used for? |
- | .rst = 9, | + | </WRAP> |
- | .dio = {2, 6, 7}, | + | ===== -. Devices ===== |
- | }; | + | |
- | </code> | + | |
- | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | + | Devices in the LoRaWAN platform are implemented on Arduino boards with Dragino shields. |
- | <code c++> | + | |
- | case EV_TXCOMPLETE: | + | |
- | Serial.println(F(" | + | |
- | if(LMIC.dataLen) { | + | |
- | // data received | + | |
- | Serial.print(F(" | + | |
- | Serial.write(LMIC.frame+LMIC.dataBeg, | + | |
- | Serial.println(); | + | |
- | } | + | |
- | // Schedule next transmission | + | |
- | os_setTimedCallback(& | + | |
- | break; | + | |
- | </ | + | |
- | The send function is initially scheduled here: | + | Start by verifying the installation on your PC of the latest Arduino IDE. Drop the Arduino LMIC library in the corresponding folder. These tools are provided at the beginning of the challenge. Open the example sketch '' |
- | <code c++> | + | |
- | do_send(& | + | |
- | </ | + | |
- | The message containing | + | <WRAP left round help 100%> |
- | <code c++> | + | * Give the characteristics |
- | LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0); | + | * Give the main characteristics of the LoRa shield from Dragino |
- | </code> | + | * What type of Antenna are you using? Explain the corresponding characteristics. |
+ | </WRAP> | ||
+ | |||
+ | Now you should configure your device with the same identifiers '' | ||
- | The adaptive data rate is not supported, and the spreading factor is configured as follows: | ||
<code c++> | <code c++> | ||
- | LMIC_setDrTxpow(DR_SF7,14); | + | static const u1_t PROGMEM APPEUI[8]= { }; |
- | </ | + | void os_getArtEui |
- | === -. Triggered Message Sending === | + | // This should also be in little endian format, see above. |
+ | static const u1_t PROGMEM DEVEUI[8]= { }; | ||
+ | void os_getDevEui (u1_t* buf) { memcpy_P(buf, | ||
- | You can also find another example of sketch to download: | + | static const u1_t PROGMEM APPKEY[16] = { }; |
- | ===== -. Gateways ===== | + | void os_getDevKey |
- | ==== -. 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 | + | <WRAP left round tip 100%> |
+ | Note that the device and application identifiers should be in little endian format, while the application key is in big endian format. For example, '' | ||
+ | </ | ||
- | <code bash> | + | Let us analyze to radio parameters in the sketch by answering the following questions. |
- | apt-get update | + | |
- | apt-get install wiring | + | |
- | </ | + | |
- | Compile the packet forwarder: | + | <WRAP left round help 100%> |
- | <code bash> | + | * In the setup function, which channels are activated on the device? |
- | make all | + | * What are the different spreading factors on each channel? |
- | </code> | + | * What is the regulation on the radio channels in LoRa? |
+ | </WRAP> | ||
- | For gcc version 4.6.3, a compilation error results | + | The LMIC library defines a set of events corresponding to the protocol machine state. These events appear |
- | < | + | |
- | CFLAGS = -std=c++0x -c -Wall -I include/ | + | |
- | </ | + | |
- | Now, you need to configure the single channel packet forwarder. This is done in the {{ : | + | <WRAP left round help 100%> |
+ | * What is the difference between | ||
+ | * When is the EV_TXCOMPLETE event called? | ||
+ | </ | ||
- | Finally, you can run the packet forwarder as root! | + | Finally |
- | <code bash> | + | <WRAP left round help 100%> |
- | nohup ./ | + | * What is the function for sending messages on the device? How it is called? |
- | </code> | + | * What is the period of message sending? Explain the implementation choice. |
- | ==== -. Kerlink IoT Station ==== | + | * Is this period guaranteed according to the LoRaWAN specification? |
+ | </WRAP> | ||
- | < | + | Now you are ready to compile the sketch and upload it to the LoRaWAN device. Connect the device a USB port on your PC, choose the board type as '' |
- | # activates eth0 at startup | + | |
- | ETHERNET=yes | + | |
- | # claims dhcp request | + | |
- | ETHDHCP=yes | + | |
- | # Selector operator APN | + | Open the serial monitor in the Arduino IDE at 115200 baud and analyse |
- | 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 | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | Start by creating | + | |
- | * 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 ==== | + | |
+ | <WRAP left round help 100%> | ||
+ | * What is the radio transmit parameters of the captured debug messages? | ||
+ | * What is the radio receive parameters of the captured debug messages for the two receive windows? | ||
+ | </ | ||
===== -. 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