Differences

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

--- esib_iot_challenge [2017/05/17 18:50] – [3. Devices] samer
+++ esib_iot_challenge [2017/05/22 18:36] – [6.3. Totoro Challenge] samer
@@ Line 96: / Line 96: @@
 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%>
+  * 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>
+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 graphic design |
+==== -. Nausicaa Challenge ====
+You have to take control on the devices. Use some scripting to send commands and do some actions or tune some parameters on the devices.
+^ Provided material ^
+| Python example script |
+^ 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.
+==== -. Kiki Challenge ====
+==== -. Mononoke Challenge ====