Differences

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

--- esib_iot_challenge [2017/05/17 15:27] – [2. Devices] samer
+++ esib_iot_challenge [2017/05/17 20:18] – [4. Applications] samer
@@ Line 3: / Line 3: @@
 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 =====
 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:
@@ Line 14: / Line 14: @@
 [{{ :lora-pilot-architecture.png?direct&650 | Figure 1. Architecture of the LoRaWAN Platform}}]
-<WRAP center help 100%>
+<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?
-  * Where is LoRaWAN implemented in the platform?
-  * Where does the IP layer start in the platform? Comment your answer considering the trends in IoT.
   * 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>
-===== -. Devices =====
+===== -. 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).
-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]].
+[{{ :app-loraserver.png?direct&600 | Figure 2. Loraserver web interface}}]
-Start by verifying the installation on your PC of the latest Arduino IDE and place the Arduino LMIC library in the corresponding folder.
+Start by choosing the application named ''NTRE-1617'' to create a new node. You should provide the following information:
+  * 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.
-<WRAP left round help 10%>
+<WRAP left round help 100%>
-help box
+  * 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]].
-Download the example sketch
+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.
-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.
-Verify that you have the latest Arduino IDE from https://www.arduino.cc/en/Main/Software on your computer.
+<WRAP left round help 100%>
-Install the board files as noted in http://support.sodaq.com/sodaq-one/autonomо/getting-started-autonomo/.
+  * Give the characteristics of the Arduino you are using: model, number of pins, type of pins, memory sizes, etc.
-Add the following library sodaq_rn2483_2.zip to your Arduino IDE as explained in https://www.arduino.cc/en/guide/libraries.
+  * Give the main characteristics of the LoRa shield from Dragino (www.dragino.com).
+  * What type of Antenna are you using? Explain the corresponding characteristics.
+</WRAP>
-In order to program the LoRaWAN devices, you should verify the installation one your PC of the following software:
+Now you should configure your device with the same identifiers ''APPEUI'', ''DEVEUI'', and ''APPKEY'' as in the backend:
-  * Arduino IDE
-  * LMIC Library
-  *
-The pin mapping corresponds to the Dragino electronic schematic:
 <code c++>
-const lmic_pinmap lmic_pins = {
+static const u1_t PROGMEM APPEUI[8]= { };
-    .nss = 10,
+void os_getArtEui (u1_t* buf) { memcpy_P(buf, APPEUI, 8);}
-    .rxtx = LMIC_UNUSED_PIN,
-    .rst = 9,
-    .dio = {2, 6, 7},
-};
-</code>
-The send function is rescheduled TX_INTERVAL seconds after each transmission complete event:
+// This should also be in little endian format, see above.
-<code c++>
+static const u1_t PROGMEM DEVEUI[8]= { };
-        case EV_TXCOMPLETE:
+void os_getDevEui (u1_t* buf) { memcpy_P(buf, DEVEUI, 8);}
-            Serial.println(F("EV_TXCOMPLETE (includes waiting for RX windows)"));
-            if(LMIC.dataLen) {
-                // 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:
+static const u1_t PROGMEM APPKEY[16] = { };
-<code c++>
+void os_getDevKey (u1_t* buf) {  memcpy_P(buf, APPKEY, 16);}
-do_send(&sendjob);
 </code>
-The message containing the sensor values is transmitted on one of the radio channels:
+<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, ''0badde1cafe2deca'' is written as ''0xCA, 0xDE, 0xE2, 0xAF, 0x1C, 0xDE, 0xAD, 0x0B'' in the Arduino sketch.
-LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0);
+</WRAP>
-</code>
-=== -. Triggered Message Sending ===
+Let us analyze to radio parameters in the sketch by answering the following questions.
-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.
+<WRAP left round help 100%>
+  * In the setup function, which channels are activated on the device?
+  * What are the different spreading factors on each channel?
+  * What is the regulation on the radio channels in LoRa?
+</WRAP>
-<WRAP center help 100%>
+The LMIC library defines a set of events corresponding to the protocol machine state. These events appear in the ''onEvent()'' function.
-  * OTAA
-  * ID
+<WRAP left round help 100%>
-  * Security
+  * What is the difference between the JOINING and the JOINED events?
+  * When is the EV_TXCOMPLETE event called?
 </WRAP>
-===== -. Backend =====
-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]].
-[{{ :app-loraserver.png?direct&400 | Figure 5. Loraserver web interface}}]
+Finally let us look at the message sending on the device.
-Start by creating and application as in Figure 5. Then create a node in this application and provide the following information:
+<WRAP left round help 100%>
-  * A unique node name
+  * What is the function for sending messages on the device? How it is called?
-  * The node description
+  * What is the period of message sending? Explain the implementation choice.
-  * A unique device EUI on 64 bits: Random identifiers can be generated on [[https://www.random.org/bytes/]]
+  * Is this period guaranteed according to the LoRaWAN specification?
-  * The application EUI on 64 bits: this can be a common identifier for all nodes using the same application.
+</WRAP>
-  * 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.
+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!
-===== -. Applications =====
+Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages.
-==== -. mqtt-spy ====
+<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>
+===== -. 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. 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 ====
+===== -. The End-to-End Challenge =====
+===== -. The Downlink Challenge =====
+===== -. The Radio Challenge =====
+//      LMIC_disableChannel(1);
+//      LMIC_disableChannel(2);
+//      LMIC_disableChannel(3);
+//      LMIC_disableChannel(4);
+//      LMIC_disableChannel(5);
+//      LMIC_disableChannel(6);
+//      LMIC_disableChannel(7);
+//      LMIC_disableChannel(8);
+//      LMIC_setDrTxpow(DR_SF10,14);