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:53] – [3. Devices] samer | esib_iot_challenge [2017/05/17 22:55] – [3. Devices] samer | ||
---|---|---|---|
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 72: | Line 72: | ||
</ | </ | ||
+ | Let us analyze to radio parameters in the sketch by answering the following questions. | ||
- | The pin mapping corresponds to the Dragino electronic schematic: | + | <WRAP left round help 100%> |
- | <code c++> | + | * In the setup function, which channels are activated on the device? |
- | const lmic_pinmap lmic_pins = { | + | * What are the different spreading factors on each channel? |
- | .nss = 10, | + | * What is the regulation on the radio channels in LoRa? |
- | .rxtx = LMIC_UNUSED_PIN, | + | </WRAP> |
- | .rst = 9, | + | |
- | .dio = {2, 6, 7}, | + | |
- | }; | + | |
- | </code> | + | |
- | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | + | The LMIC library defines a set of events corresponding to the protocol machine state. These events appear |
- | <code c++> | + | |
- | case EV_TXCOMPLETE: | + | |
- | Serial.println(F(" | + | |
- | if(LMIC.dataLen) { | + | |
- | // data received | + | |
- | Serial.print(F(" | + | |
- | Serial.write(LMIC.frame+LMIC.dataBeg, | + | |
- | Serial.println(); | + | |
- | } | + | |
- | // Schedule next transmission | + | |
- | os_setTimedCallback(& | + | |
- | break; | + | |
- | </ | + | |
- | The send function is initially scheduled here: | + | <WRAP left round help 100%> |
- | <code c++> | + | * What is the difference between the JOINING and the JOINED events? |
- | do_send(& | + | * When is the EV_TXCOMPLETE event called? |
- | </code> | + | </WRAP> |
- | The message | + | Finally let us look at the message |
- | <code c++> | + | |
- | LMIC_setTxData2(1, (uint8_t*) buffer, message.length() | + | <WRAP left round help 100%> |
- | </code> | + | * What is the function for sending messages |
+ | * What is the period | ||
+ | * Is this period guaranteed according to the LoRaWAN specification? | ||
+ | </WRAP> | ||
+ | |||
+ | 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://wch.cn/ | ||
+ | </ | ||
+ | |||
+ | 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. | ||
+ | |||
+ | <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 ===== | ===== -. 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. | ||
+ | </ | ||
+ | |||
+ | ===== -. The Challenges ===== | ||
+ | |||
+ | ==== -. The End-to-End Challenge ==== | ||
+ | ==== -. The Downlink Challenge ==== | ||
+ | ==== -. The Radio Challenge ==== | ||
+ | ==== -. The Sensor Challenge ==== |
esib_iot_challenge.txt · Last modified: 2021/08/28 09:53 by samer