Differences

This shows you the differences between two versions of the page.

--- esib_iot_challenge [2017/05/17 10:24] – [2.2. Arduino with Dragino Shield] samer
+++ esib_iot_challenge [2017/05/18 09:52] – [5.3. The Radio Challenge] samer
@@ Line 1: / Line 1: @@
 ====== 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? =====
+===== -. 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 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:
   * 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: @@
 [{{ :lora-pilot-architecture.png?direct&650 | Figure 1. Architecture of the LoRaWAN Platform}}]
-===== -. 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?
+</WRAP>
+===== -. 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://www.loraserver.io. A web interface is available for configuring the applications and devices on the platform (https://212.98.XX.XX:8080).
-==== -. PC Configuration ====
+[{{ :app-loraserver.png?direct&600 | Figure 2. Loraserver web interface}}]
-In orde to program the LoRaWAN devices, you should verify the installation one your PC of the following software:
-  * Arduino IDE
+Start by choosing the application named ''NTRE-1617'' to create a new node. You should provide the following information:
-  * LMIC Library
+  * A unique node name: ''NTRE-GX'' (where ''X'' is your group number)
+  * The node description
+  * A unique device EUI on 64 bits: Random identifiers can be generated on [[https://www.random.org/bytes/]]
+  * The application EUI on 64 bits: ''0badde1cafe2deca''.
+  * A unique application key on 128 bits also obtained by random generation.
+Make sure that the ''ABP activation'' button is unchecked, in order to enable OTAA join method. Finally, in advanced network settings, choose the receive window RX2.
-==== -. Arduino with Dragino Shield ====
+<WRAP left round help 100%>
+  * 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?
+</WRAP>
+===== -. 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 {{ :test-loraserver-comb-loraserver-dragino.zip |}} and modify it according to your preferences. Below you can find somme commented extracts of the 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 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 ''example-code-ntre-iot-challenge.ino'' with Arduino IDE.
-<code c++>
-const lmic_pinmap lmic_pins = {
-    .nss = 10,
-    .rxtx = LMIC_UNUSED_PIN,
-    .rst = 9,
-    .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 (www.dragino.com).
-            Serial.println(F("EV_TXCOMPLETE (includes waiting for RX windows)"));
+  * 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("Data Received: "));
-                Serial.write(LMIC.frame+LMIC.dataBeg, LMIC.dataLen);
-                Serial.println();
-            }
-            // Schedule next transmission
-            os_setTimedCallback(&sendjob, os_getTime()+sec2osticks(TX_INTERVAL), do_send);
-            break;
-</code>
-The send function is initially scheduled here:
+Now you should configure your device with the same identifiers ''APPEUI'', ''DEVEUI'', and ''APPKEY'' as in the backend:
-<code c++>
-do_send(&sendjob);
-</code>
-The message containing the sensor values is transmitted on one of the radio channels:
 <code c++>
-LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0);
+static const u1_t PROGMEM APPEUI[8]= { };
-</code>
+void os_getArtEui (u1_t* buf) { memcpy_P(buf, APPEUI, 8);}
-=== -. 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, DEVEUI, 8);}
-You can also find another example of sketch to download: {{ :test-loraserver-moisture-on-move.ino.zip |}}. Here the message sending is not periodic but related to an event. For example, an infrared sensor detects a movement and triggers a signal for the device to send a LoRaWAN message. Note also that the join method used in this second sketch is Activation by Personalisation (ABP): the device address, the network session key, and the application session key are directly configured on the device.
+static const u1_t PROGMEM APPKEY[16] = { };
-===== -. Gateways =====
+void os_getDevKey (u1_t* buf) {  memcpy_P(buf, APPKEY, 16);}
-==== -. Single Channel Gateway ====
+</code>
-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.
+<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, ''0badde1cafe2deca'' is written as ''0xCA, 0xDE, 0xE2, 0xAF, 0x1C, 0xDE, 0xAD, 0x0B'' in the Arduino sketch.
+</WRAP>
-[{{ :2017-01-04_11.34.54.jpg?direct&300 |Figure 2. LoRa single channel gateway}}]
+Let us analyze to radio parameters in the sketch by answering the following questions.
-In order to assemble the gateway, start by making the wire connections: the connection pins are identified in Figures 3 and 4.
+<WRAP left round help 100%>
-[{{ :schema-single-channel-pi3.png?direct&300 |Figure 3. Dragino pin mapping}}]
+  * In the setup function, which channels are activated on the device?
-[{{ :schema-pins-pi3.png?direct&300 |Figure 4. Raspberry pi 3 pins}}]
+  * What are the different spreading factors on each channel?
+  * What is the regulation on the radio channels in LoRa?
+</WRAP>
-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://github.com/samerlahoud/single_chan_pkt_fwd]]. In order to install it, you need to:
+The LMIC library defines a set of events corresponding to the protocol machine state. These events appear in the ''onEvent()'' function.
-  * Enable SPI on the Raspberry Pi using raspi-config
-  * Download and unzip the source code:
-<code bash>
+<WRAP left round help 100%>
-wget https://github.com/hallard/single_chan_pkt_fwd/archive/master.zip
+  * What is the difference between the JOINING and the JOINED events?
-unzip master.zip
+  * When is the EV_TXCOMPLETE event called?
-</code>
+</WRAP>
-  * Install the wiring library:
+Finally let us look at the message sending on the device.
-<code bash>
+<WRAP left round help 100%>
-apt-get update
+  * What is the function for sending messages on the device? How it is called?
-apt-get install wiring
+  * What is the period of message sending? Explain the implementation choice.
-</code>
+  * Is this period guaranteed according to the LoRaWAN specification?
+</WRAP>
-Compile the packet forwarder:
+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 ''Arduino/Genuino Mega 2560'' and select the corresponding port. Compile and upload!
-<code bash>
-make all
-</code>
-For gcc version 4.6.3, a compilation error results in the following warning ''unrecognized command line option '-std=c++11'''. Replace ''-std=c++11'' by ''-std=c++0x'' in the Makefile and recompile:
+<WRAP left round tip 100%>
-<code>
+For Arduino Mega 2560, additional drivers can be installed on Windows from http://wch.cn/download/CH341SER_ZIP.html.
-CFLAGS = -std=c++0x -c -Wall -I include/
+</WRAP>
-</code>
-Now, you need to configure the single channel packet forwarder. This is done in the {{ :global_config.json.zip |}} configuration file. Particularly, you need to choose the channel, the spreading factor, the pins for SPI communication, and the address of the backend server. Note that you can specify multiple backends for testing purposes.
+Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages.
-Finally, you can run the packet forwarder as root!
+<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?
+</WRAP>
-<code bash>
+Getting back to the backend, you can monitor some important information related to your device. Click on the corresponding node session.
-nohup ./single_chan_pkt_fwd &
-</code>
-==== -. Kerlink IoT Station ====
-<code>
+<WRAP left round help 100%>
-# activates eth0 at startup
+  * What are the different fields that appear in the node session corresponding to you device?
-ETHERNET=yes
+  * Explain how each field is created according to the LoRaWAN specification.
-# claims dhcp request on eth0
+  * What are the different counters visible at the backend? Explain how they get incremented and how they are used.
-ETHDHCP=yes
+</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, so it should work on any operating system with an appropriate version of Java 8 installed. A very useful tutorial is available on [[https://github.com/eclipse/paho.mqtt-spy/wiki]].
+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, configure a new connection to the MQTT broker by simply adding the IP address of the broker in the ''Server URI'' field. Now you can subscribe to any MQTT topic. If you want to receive all messages arriving at the backend, you can use the generic topic ''#''. You can also limit to the topic including the messages of any specific device: ''application/APPLICATION_ID/node/DEVICE_EUI/rx''.
-# Selector operator APN
+<WRAP left round help 100%>
-GPRSAPN=gprs.touch.com.lb
+  * Summarize the concepts and functionalities of the MQTT protocol.
-# Enter pin code if activated
+  * What are the possible strengths and weaknesses in terms of security of MQTT?
-GPRSPIN=0000
+  * What are the different types of topics used by the backend? Explain.
-# Update /etc/resolv.conf to get dns facilities
+  * Explain the different fields in a captured MQTT message received from you device.
-GPRSDNS=yes
+</WRAP>
-# PAP authentication
-GPRSUSER=
-GPRSPASSWORD=
-# Bearers priority order
+<WRAP left round tip 100%>
-#BEARERS_PRIORITY="eth0,ppp0,eth1"
+The payload received by the MQTT client is decrypted but encoded in Base64. You should decode it to get the original message.
-BEARERS_PRIORITY="ppp0,eth0,eth1"
+</WRAP>
-</code>
-<code>
+If you need to send data to your device, you should publish the encoded message in the corresponding topic ''application/APPLICATION_ID/node/DEVICE_EUI/tx'' as follows:
-./gps-pkt-fwd.sh > /dev/null &
-</code>
 <code>
-root      2548 S    /bin/sh ./gps-pkt-fwd.sh
+{
-root     34908 S    ./gps_pkt_fwd
+    "reference": "abcd1234",                  // reference which will be used on ack or error (this can be a random string)
+    "confirmed": false,                        // whether the payload must be sent as confirmed data down or not
+    "fPort": 10,                              // FPort to use (must be > 0)
+    "data": "...."                            // base64 encoded data (plaintext, will be encrypted by LoRa Server)
+}
 </code>
+===== -. The Challenges =====
-<code>
+==== -. The End-to-End Challenge ====
-/etc/init.d/gprs start
+I can send data from the device to the application.
-[root@Wirgrid_0b03008c demo_gps_loramote]# /etc/init.d/gprs  status
+==== -. The Downlink Challenge ====
-pppd (pid 5273) is running...
+I can send data from the application to the device.
-Session: Rx=58, Tx=163
-Globals: Rx=1130457, Tx=1195592
-Sum:     Rx=1130515, Tx=1195755
-[root@Wirgrid_0b03008c demo_gps_loramote]#
-</code>
-===== -. Backend =====
+==== -. The Radio Challenge ====
-==== -. Loraserver ====
+I can tune the LoRa radio parameters and assess the results.
-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://www.loraserver.io]].
+These two commands can be helpful:
-[{{ :app-loraserver.png?direct&400 | Figure 5. Loraserver web interface}}]
+<code c++>
+LMIC_disableChannel(N);
-Start by creating and application as in Figure 5. Then create a node in this application and provide the following information:
+LMIC_setDrTxpow(DR_SF12,14);
-  * A unique node name
+</code>
-  * The node description
+==== -. The Sensor Challenge ====
-  * A unique device EUI on 64 bits: Random identifiers can be generated on [[https://www.random.org/bytes/]]
+I can use different sensors to send data from the device.
-  * 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 ''ABP activation'' button is unchecked.
-==== -. 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, so it should work on any operating system with an appropriate version of Java 8 installed. A very useful tutorial is available on [[https://github.com/eclipse/paho.mqtt-spy/wiki]].
-You can use mqtt-spy to debug the messages received from the LoRaWAN devices. For this, you should download the software tool from [[https://github.com/eclipse/paho.mqtt-spy/wiki]]. After starting the application, configure a new connection to the MQTT broker by simply adding the IP address of the broker in the ''Server URI'' field. Now you can subscribe to any MQTT topic. If you want to receive all messages arriving at the backend, you can use the generic topic ''#''. You can also limit to the topic including the messages of any specific device: ''application/APPLICATION_ID/node/DEVICE_EUI/rx''.
-==== -. Emoncms ====