Differences

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

--- exploring_lorawan [2017/11/24 20:02] – samer
+++ exploring_lorawan [2018/10/29 11:48] – [3. Devices] samer
@@ Line 24: / Line 24: @@
 [{{ :app-loraserver.png?direct&600 | Figure 2. Loraserver web interface}}]
-Start by choosing the application named ''RCTE-1718'' to create a new node. You should provide the following information:
+Start by choosing the application named ''IDOE-1819'' to create a new device. You should provide the following information:
-  * A unique node name: ''RCTE-GX'' (where ''X'' is your group number)
+  * A unique device name: ''IDOE-GX'' (where ''X'' is your group number)
-  * The node description
+  * The device 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.
+Make sure to choose ''lora-profile'' as a ''Device-profile'' in order to enable OTAA join method.
 <WRAP left round help 100%>
-  * 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.
+  * Compare the two device activation methods used in LoRaWAN by giving the advantages and shortcomings.
-  * What is the difference between the two receive windows in LoRaWAN? What are they used for?
 </WRAP>
 ===== -. Devices =====
@@ Line 60: / Line 57: @@
 <WRAP left round tip 100%>
-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.
+Note that the application key is in big endian format. Hence, the key ''0badde1cafe2deca'' should be written as ''0xCA, 0xDE, 0xE2, 0xAF, 0x1C, 0xDE, 0xAD, 0x0B'' in the Arduino sketch.
 </WRAP>
@@ Line 107: / Line 104: @@
 </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 121: / Line 119: @@
 </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 131: / Line 129: @@
 }
 </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 140: / Line 143: @@
 ==== -. 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 148: / Line 151: @@
 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.