wikiroute

networking recipes

User Tools

Site Tools


esib_iot_challenge

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
esib_iot_challenge [2017/05/17 22:27] – [4. Applications] sameresib_iot_challenge [2017/05/22 18:19] – [6.1. The Wind Rises] 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! 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. Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages.
Line 102: Line 106:
   * What is the radio transmit parameters of the captured debug messages?   * 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?   * 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> </WRAP>
 ===== -. Applications ===== ===== -. Applications =====
Line 111: Line 123:
   * What are the possible strengths and weaknesses in terms of security of MQTT?   * 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.   * 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.+  * Explain the different fields in a captured MQTT message received from you device. 
 </WRAP> </WRAP>
-===== -. The End-to-End Challenge ===== 
  
-===== -. The Downlink Challenge =====+<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>
  
-===== -. The Radio Challenge ===== +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> +
-//      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); +
-</code>+
  
 <code> <code>
 { {
-          "applicationID": "2", +    "reference": "abcd1234",                  // reference which will be used on ack or error (this can be a random string) 
-          "applicationName": "NTRE-1617", +    "confirmed": false                       // whether the payload must be sent as confirmed data down or not 
-          "data": "eyJMIjogMzcwLCAiTSI6IDM2NywgIlQiOiAtMTI3LjAwfQ==", +    "fPort": 10                             // FPort to use (must be > 0) 
-          "devEUI": "0ce03fb4fcab65ed", +    "data": "....                           // base64 encoded data (plaintextwill be encrypted by LoRa Server)
-          "fCnt": 26, +
-          "fPort": 1+
-          "nodeName": "NTRE-G1", +
-          "rxInfo": [{ +
-                    "loRaSNR": 8.8, +
-                    "mac": "7276ff000b03008c", +
-                    "rssi": -71, +
-                    "time": "2017-05-17T17:16:35.973982Z" +
-          }], +
-          "txInfo":+
-                    "adr": true, +
-                    "codeRate": "4/5", +
-                    "dataRate":+
-                              "bandwidth": 125, +
-                              "modulation": "LORA", +
-                              "spreadFactor": 10 +
-                    }, +
-                    "frequency": 868100000 +
-          }+
 } }
 </code> </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]]. The dashboard facility on emoncms is used to visualize the sensor data.
 +
 +
 +^ Provided material ^
 +| VM with Node-RED installed |    
 +| Node-RED example flow |
 +
 +^ Required skills ^
 +| Basic javascript |    
 +| GUI configuration |
 +| Two drops of IoT imagination |
 +
 +=== Provided material ===
 + 
 +  * VM with Node-RED installed 
 +  * Node-RED example flow 
 +
 +=== Required skills ===
 +
 +  * Basic javascript 
 +  * GUI configuration
 +  * Two drops of IoT imagination
 +==== -. Nausicaa Challenge ====
 +
 +==== -. Totoro Challenge ====
 +
 +==== -. Kiki Challenge ====
 +
 +==== -. Mononoke Challenge ====
 +
 +
esib_iot_challenge.txt · Last modified: 2021/08/28 09:53 by samer