Differences

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

--- esib_iot_challenge [2017/05/17 17:49] – samer
+++ esib_iot_challenge [2017/05/22 18:25] – [6.1. The Wind Rises] samer
@@ Line 25: / Line 25: @@
 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).
-[{{ :app-loraserver.png?direct&400 | Figure 2. Loraserver web interface}}]
+[{{ :app-loraserver.png?direct&600 | Figure 2. Loraserver web interface}}]
 Start by choosing the application named ''NTRE-1617'' to create a new node. You should provide the following information:
@@ Line 46: / Line 46: @@
 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]].
-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.
+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.
 <WRAP left round help 100%>
@@ Line 54: / Line 54: @@
 </WRAP>
-Download the example sketch and open it with Arduino IDE. Now you should configure your device with the same identifiers as in the backend.
+Now you should configure your device with the same identifiers ''APPEUI'', ''DEVEUI'', and ''APPKEY'' as in the backend:
-<WRAP left round tip 100%>
-Note that the device and application identifiers should be in little endian format. The application key is in big endian format. For example, ''0badde1cafe2deca'' is written as ''0xCA, 0xDE, 0xE2, 0xAF, 0x1C, 0xDE, 0xAD, 0x0B''.
-</WRAP>
 <code c++>
@@ Line 72: / Line 67: @@
 void os_getDevKey (u1_t* buf) {  memcpy_P(buf, APPKEY, 16);}
 </code>
-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 tip 100%>
-Install the board files as noted in http://support.sodaq.com/sodaq-one/autonomо/getting-started-autonomo/.
+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.
-Add the following library sodaq_rn2483_2.zip to your Arduino IDE as explained in https://www.arduino.cc/en/guide/libraries.
+</WRAP>
-In order to program the LoRaWAN devices, you should verify the installation one your PC of the following software:
+Let us analyze to radio parameters in the sketch by answering the following questions.
-  * Arduino IDE
+<WRAP left round help 100%>
-  * LMIC Library
+  * In the setup function, which channels are activated on the device?
-  *
+  * What are the different spreading factors on each channel?
-The pin mapping corresponds to the Dragino electronic schematic:
+  * What is the regulation on the radio channels in LoRa?
-<code c++>
+</WRAP>
-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:
+The LMIC library defines a set of events corresponding to the protocol machine state. These events appear in the ''onEvent()'' function.
-<code c++>
-        case EV_TXCOMPLETE:
-            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:
+<WRAP left round help 100%>
-<code c++>
+  * What is the difference between the JOINING and the JOINED events?
-do_send(&sendjob);
+  * When is the EV_TXCOMPLETE event called?
-</code>
+</WRAP>
-The message containing the sensor values is transmitted on one of the radio channels:
+Finally let us look at the message sending on the device.
-<code c++>
-LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0);
-</code>
-=== -. Triggered Message Sending ===
+<WRAP left round help 100%>
+  * What is the function for sending messages on the device? How it is called?
+  * What is the period of message sending? Explain the implementation choice.
+  * Is this period guaranteed according to the LoRaWAN specification?
+</WRAP>
-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.
+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!
+<WRAP left round tip 100%>
+For Arduino Mega 2560, additional drivers can be installed on Windows from http://wch.cn/download/CH341SER_ZIP.html.
+</WRAP>
+Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages.
 <WRAP left round help 100%>
-  * OTAA
+  * What is the radio transmit parameters of the captured debug messages?
-  * ID
+  * What is the radio receive parameters of the captured debug messages for the two receive windows?
-  * Security
+</WRAP>
+Getting back to the backend, you can monitor some important information related to your device. Click on the corresponding node session.
+<WRAP left round help 100%>
+  * What are the different fields that appear in the node session corresponding to you device?
+  * Explain how each field is created according to the LoRaWAN specification.
+  * 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, 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''.
+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''.
+<WRAP left round help 100%>
+  * 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>
+<WRAP left round tip 100%>
+The payload received by the MQTT client is decrypted but encoded in Base64. You should decode it to get the original message.
+</WRAP>
+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:
+<code>
+{
+    "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>
+===== -. Day One Challenges =====
+==== -. The End-to-End Challenge ====
+I can send data from the device to the application.
+==== -. The Downlink Challenge ====
+I can send data from the application to the device.
+==== -. The Radio Challenge ====
+I can tune the LoRa radio parameters and assess the results.
+These two commands can be helpful when used after the join event:
+<code c++>
+LMIC_disableChannel(N);
+LMIC_setDrTxpow(DR_SF12,14);
+</code>
+==== -. The Sensor Challenge ====
+I can use different sensors to send data from the device: PIR, moisture, temperature, light, etc.
+===== -. Day Two Challenges =====
+==== -. The Wind Rises ====
+This is a mandatory challenge. It consists of using [[https://nodered.org|Node-RED]] to receive data from the sensors (via MQTT) and send it to [[https://emoncms.org|emoncms]] for visualization.
+^ Provided material ^
+| VM with Node-RED installed |
+| Node-RED example flow |
+| [[https://emoncms.org/dashboard/view&id=37655|Dashboard example]] |
+^ Required skills ^
+| Basic javascript |
+| GUI configuration |
+| Two drops of IoT imagination |
+==== -. Nausicaa Challenge ====
+==== -. Totoro Challenge ====
+==== -. Kiki Challenge ====
+==== -. Mononoke Challenge ====