Differences

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

--- exploring_lorawan [2017/11/24 14:34] – [1. Platform] samer
+++ exploring_lorawan [2017/11/24 20:37] – samer
@@ Line 24: / Line 24: @@
 [{{ :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:
+Start by choosing the application named ''RCTE-1718'' to create a new node. You should provide the following information:
-  * A unique node name: ''NTRE-GX'' (where ''X'' is your group number)
+  * A unique node name: ''RCTE-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/]]
@@ Line 41: / Line 41: @@
 ===== -. 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]].
+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 [[exploring_lora|Exploring LoRa lab]].
-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.
+Start by verifying the installation on your PC of the latest Arduino IDE. Unzip the Arduino {{ :arduino-lmic-master.zip |LMIC library}} and copy it to your sketchbook library folder as detailed in [[https://www.arduino.cc/en/Guide/Libraries]]. Then, download and open the example sketch {{ :example-code-rcte-iot-lab.zip |example-code-rcte-iot-lab.ino}} with Arduino IDE.
-<WRAP left round help 100%>
-  * Give the characteristics of the Arduino you are using: model, number of pins, type of pins, memory sizes, etc.
-  * 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>
 Now you should configure your device with the same identifiers ''APPEUI'', ''DEVEUI'', and ''APPKEY'' as in the backend:
@@ Line 113: / Line 107: @@
 </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]].
+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]]. The tool can be directly downloaded from this {{ :mqtt-spy-1.0.0.jar.zip |link}}.
-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''.
+You can use mqtt-spy to debug the messages received from the LoRaWAN devices. 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%>
@@ Line 127: / Line 122: @@
 </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:
+If you need to send data to your device, you should publish an encoded message in the corresponding topic ''application/APPLICATION_ID/node/DEVICE_EUI/tx'' as follows:
 <code>
@@ Line 137: / Line 132: @@
 }
 </code>
-===== -. Day One Challenges =====
+<WRAP left round tip 100%>
+The payload sent by the MQTT client must be encoded in Base64.
+</WRAP>
+===== -. LoRaWAN Challenges =====
+Implement and provide technical documentation for each of the following challenges.
 ==== -. The End-to-End Challenge ====
@@ Line 146: / Line 146: @@
 ==== -. The Radio Challenge ====
-I can tune the LoRa radio parameters and assess the results.
+I can tune the LoRa radio parameters.
 These two commands can be helpful when used after the join event:
@@ Line 154: / Line 154: @@
 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 design |
-==== -. Nausicaa Challenge ====
-You have to take control on the devices. Use some scripting to send commands or tune some parameters on the devices.
-^ Required skills ^
-| Basic scripting (for example python) |
-| Basic electronics |
-| Two drops of IoT autocracy |
-==== -. Totoro Challenge ====
-You have to store the sensor data in a database. Use Node-RED to inject data in a (influx) database.
-^ Required skills ^
-| Basic database |
-| Two drops of IoT resilience |
-==== -. Kiki Challenge ====
-You have to implement a radio coverage test on the campus.
-^ Required skills ^
-| Basic scripting |
-| Two drops of IoT ubiquity |
-==== -. Mononoke Challenge ====
-You have to implement a chat bot designed for working with Google Hangouts. The bot answers requests and reveals sensors data.
-^ Required skills ^
-| Basic scripting with python |
-| Two drops of IoT robot attitude |