exploring_lorawan
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
exploring_lorawan [2017/11/24 19:59] – [3. Devices] samer | exploring_lorawan [2018/10/29 11:48] – [3. Devices] samer | ||
---|---|---|---|
Line 24: | Line 24: | ||
[{{ : | [{{ : | ||
- | Start by choosing the application named '' | + | Start by choosing the application named '' |
- | * A unique | + | * A unique |
- | * The node description | + | * The device |
* A unique device EUI on 64 bits: Random identifiers can be generated on [[https:// | * A unique device EUI on 64 bits: Random identifiers can be generated on [[https:// | ||
- | * The application EUI on 64 bits: '' | ||
* A unique application key on 128 bits also obtained by random generation. | * A unique application key on 128 bits also obtained by random generation. | ||
- | Make sure that the '' | + | Make sure to choose |
<WRAP left round help 100%> | <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? | * 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? | + | |
</ | </ | ||
===== -. Devices ===== | ===== -. Devices ===== | ||
Line 60: | Line 57: | ||
<WRAP left round tip 100%> | <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. | + | Note that the application key is in big endian format. |
</ | </ | ||
Line 107: | Line 104: | ||
</ | </ | ||
===== -. 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. The tool is provided at the beginning of the challenge. After starting the application, | + | |
+ | You can use mqtt-spy to debug the messages received from the LoRaWAN devices. After starting the application, | ||
<WRAP left round help 100%> | <WRAP left round help 100%> | ||
Line 121: | Line 119: | ||
</ | </ | ||
- | If you need to send data to your device, you should publish | + | If you need to send data to your device, you should publish |
< | < | ||
Line 131: | Line 129: | ||
} | } | ||
</ | </ | ||
- | ===== -. Day One Challenges ===== | + | |
+ | <WRAP left round tip 100%> | ||
+ | The payload sent by the MQTT client must be encoded in Base64. | ||
+ | </ | ||
+ | ===== -. LoRaWAN | ||
+ | Implement and provide technical documentation for each of the following challenges. | ||
==== -. The End-to-End Challenge ==== | ==== -. The End-to-End Challenge ==== | ||
Line 140: | Line 143: | ||
==== -. The Radio Challenge ==== | ==== -. The Radio Challenge ==== | ||
- | I can tune the LoRa radio parameters | + | I can tune the LoRa radio parameters. |
These two commands can be helpful when used after the join event: | These two commands can be helpful when used after the join event: | ||
Line 148: | Line 151: | ||
LMIC_setDrTxpow(DR_SF12, | LMIC_setDrTxpow(DR_SF12, | ||
</ | </ | ||
+ | |||
==== -. The Sensor Challenge ==== | ==== -. The Sensor Challenge ==== | ||
I can use different sensors to send data from the device: PIR, moisture, temperature, | I can use different sensors to send data from the device: PIR, moisture, temperature, | ||
- | |||
- | ===== -. Day Two Challenges ===== | ||
- | |||
- | ==== -. The Wind Rises ==== | ||
- | |||
- | This is a mandatory challenge. It consists of using [[https:// | ||
- | |||
- | ^ Provided material ^ | ||
- | | VM with Node-RED installed | | ||
- | | Node-RED example flow | | ||
- | | [[https:// | ||
- | |||
- | ^ Required skills ^ | ||
- | | Basic javascript | | ||
- | | GUI configuration | | ||
- | | Two drops of IoT design | | ||
- | ==== -. Nausicaa Challenge ==== | ||
- | |||
- | You have to take control on the devices. Use some scripting to send commands or tune some parameters on the devices. | ||
- | |||
- | ^ 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. Use Node-RED to inject data in a (influx) database. | ||
- | |||
- | ^ Required skills ^ | ||
- | | Basic database | | ||
- | | Two drops of IoT resilience | | ||
- | |||
- | ==== -. Kiki Challenge ==== | ||
- | |||
- | You have to implement a radio coverage test on the campus. | ||
- | |||
- | ^ Required skills ^ | ||
- | | Basic scripting | | ||
- | | Two drops of IoT ubiquity | | ||
- | ==== -. Mononoke Challenge ==== | ||
- | |||
- | You have to implement a chat bot designed for working with Google Hangouts. The bot answers requests and reveals sensors data. | ||
- | ^ Required skills ^ | ||
- | | Basic scripting with python | | ||
- | | Two drops of IoT robot attitude | |
exploring_lorawan.txt · Last modified: 2021/11/02 06:31 by samer