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:36] – [2.1. Arduino with Dragino Shield] samer | esib_iot_challenge [2017/05/17 22:45] – [7. The Radio Challenge] 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:// | ||
- | ==== -. PC Configuration ==== | + | [{{ :app-loraserver.png? |
- | In orde to program the LoRaWAN devices, you should verify the installation one your PC of the following software: | + | |
- | | + | Start by choosing the application named '' |
- | * LMIC Library | + | |
+ | * The node description | ||
+ | * A unique device EUI on 64 bits: Random identifiers can be generated on [[https:// | ||
+ | * The application EUI on 64 bits: '' | ||
+ | * A unique application key on 128 bits also obtained by random generation. | ||
+ | |||
+ | Make sure that the '' | ||
- | ==== -. Arduino with Dragino Shield | + | <WRAP left round help 100%> |
- | === -. Periodic Message Sending | + | * What does the application EUI mean? How is it used in LoRaWAN? |
+ | * 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 in LoRaWAN? What are they used for? | ||
+ | </ | ||
+ | ===== -. Devices ===== | ||
- | Devices in the LoRaWAN platform are 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]]. You can download the following sketch {{ : | + | Devices in the LoRaWAN platform are 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]]. |
- | The pin mapping corresponds to the Dragino electronic schematic: | + | Start by verifying |
- | <code c++> | + | |
- | const lmic_pinmap lmic_pins = { | + | |
- | | + | |
- | | + | |
- | | + | |
- | .dio = {2, 6, 7}, | + | |
- | }; | + | |
- | </code> | + | |
- | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | + | <WRAP left round help 100%> |
- | <code c++> | + | * Give the characteristics of the Arduino you are using: model, number of pins, type of pins, memory sizes, etc. |
- | case EV_TXCOMPLETE: | + | * Give the main characteristics of the LoRa shield from Dragino |
- | Serial.println(F(" | + | * What type of Antenna are you using? Explain the corresponding characteristics. |
- | if(LMIC.dataLen) { | + | </WRAP> |
- | // data received in rx slot after tx | + | |
- | Serial.print(F(" | + | |
- | Serial.write(LMIC.frame+LMIC.dataBeg, | + | |
- | | + | |
- | } | + | |
- | // Schedule next transmission | + | |
- | os_setTimedCallback(& | + | |
- | break; | + | |
- | </code> | + | |
- | The send function is initially scheduled here: | + | Now you should configure your device with the same identifiers '' |
- | <code c++> | + | |
- | do_send(& | + | |
- | </ | + | |
- | The message containing the sensor values is transmitted on one of the radio channels (as in the Autonomo case): | ||
<code c++> | <code c++> | ||
- | LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0); | + | static const u1_t PROGMEM APPEUI[8]= { }; |
- | </ | + | void os_getArtEui |
- | The adaptive data rate is not supported, and the spreading factor is configured as follows: | + | // This should |
- | <code c++> | + | static const u1_t PROGMEM DEVEUI[8]= { }; |
- | LMIC_setDrTxpow(DR_SF7, | + | void os_getDevEui |
- | </code> | + | |
- | + | ||
- | === -. 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 | + | |
- | + | ||
- | [{{ : | + | |
- | + | ||
- | 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> | + | static const u1_t PROGMEM APPKEY[16] = { }; |
- | wget https:// | + | void os_getDevKey (u1_t* buf) { memcpy_P(buf, |
- | 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 the debug messages. |
- | GPRSAPN=gprs.touch.com.lb | + | |
- | # Enter pin code if activated | + | |
- | GPRSPIN=0000 | + | |
- | # Update / | + | |
- | GPRSDNS=yes | + | |
- | # PAP authentication | + | |
- | GPRSUSER= | + | |
- | GPRSPASSWORD= | + | |
- | # Bearers priority order | + | <WRAP left round help 100%> |
- | # | + | * What is the radio transmit parameters of the captured debug messages? |
- | BEARERS_PRIORITY=" | + | * What is the radio receive parameters of the captured debug messages for the two receive windows? |
- | </code> | + | </WRAP> |
- | < | + | Getting back to the backend, you can monitor some important information related to your device. Click on the corresponding node session. |
- | ./ | + | |
- | </ | + | |
- | <code> | + | <WRAP left round help 100%> |
- | 3270 root 2548 S | + | * What are the different fields that appear in the node session corresponding to you device? |
- | 3288 root 34908 S | + | * Explain how each field is created according to the LoRaWAN specification. |
- | </code> | + | * What are the different counters visible at the backend? Explain how they get incremented and how they are used. |
+ | </WRAP> | ||
+ | ===== -. Applications ===== | ||
+ | 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. The tool is provided at the beginning of the challenge. After starting the application, | ||
- | <code> | + | <WRAP left round help 100%> |
- | /etc/init.d/gprs start | + | * Summarize the concepts and functionalities of the MQTT protocol. |
+ | * What are the possible strengths and weaknesses in terms of security of MQTT? | ||
+ | * What are the different types of topics used by the backend? Explain. | ||
+ | * Explain the different fields in a captured MQTT message received from you device. | ||
+ | </WRAP> | ||
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | + | <WRAP left round tip 100%> |
- | pppd (pid 5273) is running... | + | The payload received by the MQTT client |
- | Session: Rx=58, Tx=163 | + | </WRAP> |
- | Globals: Rx=1130457, Tx=1195592 | + | |
- | Sum: | + | |
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | + | |
- | </code> | + | |
- | ===== -. Backend | + | ===== -. The End-to-End Challenge |
- | ==== -. 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:// | + | ===== -. The Downlink Challenge ===== |
- | [{{ :app-loraserver.png? | + | ===== -. The Radio Challenge ===== |
- | 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 ===== | ||
- | ==== -. 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, | ||
- | 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