esib_iot_challenge
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
esib_iot_challenge [2017/05/17 17:32] – [3. Devices] samer | esib_iot_challenge [2017/05/21 21:48] – [5.4. The Sensor Challenge] samer | ||
---|---|---|---|
Line 14: | Line 14: | ||
[{{ : | [{{ : | ||
- | < | + | < |
* Where is the LoRa modulation implemented on the platform? | * Where is the LoRa modulation implemented on the platform? | ||
* What are the advantages of the LoRa modulation? | * What are the advantages of the LoRa modulation? | ||
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:// | 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:// | ||
- | [{{ : | + | [{{ : |
Start by choosing the application named '' | Start by choosing the application named '' | ||
Line 36: | Line 36: | ||
Make sure that the '' | Make sure that the '' | ||
- | <WRAP left help 100%> | + | <WRAP left round help 100%> |
* What does the application EUI mean? How is it used in LoRaWAN? | * 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? | * What does the application key mean? How is it used in LoRaWAN security? | ||
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]]. | 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 '' |
<WRAP left round help 100%> | <WRAP left round help 100%> | ||
Line 54: | Line 54: | ||
</ | </ | ||
+ | Now you should configure your device with the same identifiers '' | ||
- | Download the example sketch, open it with Arduino IDE and compile it. | + | <code c++> |
- | + | static const u1_t PROGMEM APPEUI[8]= | |
- | You can download the following sketch | + | void os_getArtEui (u1_t* buf) { memcpy_P(buf, |
- | Verify that you have the latest Arduino IDE from https://www.arduino.cc/ | + | // This should also be in little endian format, see above. |
- | Install the board files as noted in http:// | + | static const u1_t PROGMEM DEVEUI[8]= { }; |
- | Add the following library sodaq_rn2483_2.zip to your Arduino IDE as explained in https:// | + | void os_getDevEui (u1_t* buf) { memcpy_P(buf, |
- | In order to program the LoRaWAN devices, you should verify the installation one your PC of the following software: | + | static |
- | + | void os_getDevKey (u1_t* buf) { | |
- | * Arduino IDE | + | |
- | * LMIC Library | + | |
- | * | + | |
- | The pin mapping corresponds to the Dragino electronic schematic: | + | |
- | <code c++> | + | |
- | const lmic_pinmap lmic_pins | + | |
- | .nss = 10, | + | |
- | .rxtx = LMIC_UNUSED_PIN, | + | |
- | .rst = 9, | + | |
- | .dio = {2, 6, 7}, | + | |
- | }; | + | |
</ | </ | ||
- | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | + | <WRAP left round tip 100%> |
- | <code c++> | + | Note that the device and application identifiers should be in little endian format, while the application key is in big endian format. For example, '' |
- | case EV_TXCOMPLETE: | + | </WRAP> |
- | Serial.println(F(" | + | |
- | if(LMIC.dataLen) { | + | |
- | // data received | + | |
- | Serial.print(F(" | + | |
- | Serial.write(LMIC.frame+LMIC.dataBeg, LMIC.dataLen); | + | |
- | Serial.println(); | + | |
- | } | + | |
- | // Schedule next transmission | + | |
- | os_setTimedCallback(& | + | |
- | break; | + | |
- | </code> | + | |
- | The send function is initially scheduled here: | + | Let us analyze to radio parameters in the sketch by answering the following questions. |
- | <code c++> | + | |
- | do_send(& | + | |
- | </ | + | |
- | The message containing | + | <WRAP left round help 100%> |
- | <code c++> | + | * In the setup function, which channels are activated |
- | LMIC_setTxData2(1, | + | * What are the different spreading factors on each channel? |
- | </code> | + | * What is the regulation on the radio channels in LoRa? |
+ | </WRAP> | ||
- | === -. Triggered Message Sending === | + | The LMIC library defines a set of events corresponding to the protocol machine state. These events appear in the '' |
- | You can also find another example of sketch to download: {{ : | + | <WRAP left round help 100%> |
+ | * What is the difference between | ||
+ | * When is the EV_TXCOMPLETE event called? | ||
+ | </ | ||
- | < | + | Finally let us look at the message sending on the device. |
- | * OTAA | + | |
- | * ID | + | <WRAP left round help 100%> |
- | * Security | + | * 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? | ||
+ | </ | ||
+ | |||
+ | 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 '' | ||
+ | |||
+ | <WRAP left round tip 100%> | ||
+ | For Arduino Mega 2560, additional drivers can be installed on Windows from http:// | ||
+ | </ | ||
+ | |||
+ | 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? | ||
+ | </ | ||
+ | |||
+ | Getting back to the backend, you can monitor some important information related to your device. Click on the corresponding node session. | ||
+ | |||
+ | < | ||
+ | * 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. | ||
</ | </ | ||
===== -. Applications ===== | ===== -. 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, | 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, | ||
- | You can use mqtt-spy to debug the messages received from the LoRaWAN devices. | + | You can use mqtt-spy to debug the messages received from the LoRaWAN devices. |
+ | |||
+ | <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 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. | ||
+ | </ | ||
+ | |||
+ | If you need to send data to your device, you should publish the encoded message in the corresponding topic '' | ||
+ | |||
+ | < | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | </ | ||
+ | ===== -. 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, | ||
+ | </ | ||
+ | ==== -. The Sensor Challenge ==== | ||
+ | I can use different sensors to send data from the device: PIR, moisture, temperature, | ||
+ | |||
+ | ===== -. Day Two Challenges ===== |
esib_iot_challenge.txt · Last modified: 2021/08/28 09:53 by samer