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 09:17] – [2.1. Autonomo with LoRaBee] samer | esib_iot_challenge [2017/05/22 18:38] – [6.3. Totoro Challenge] samer | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== ESIB IoT Challenge ====== | ====== ESIB IoT Challenge ====== | ||
- | Welcome to the ESIB IoT Challenge. In this challenge, you will designing and prototyping the first IoT services based on a LoRaWAN network. | + | Welcome to the ESIB IoT Challenge. In this challenge, you will be designing and prototyping the first IoT services based on a LoRaWAN network. |
- | ===== -. What is a LoRaWAN | + | ===== -. Platform ===== |
- | In this challenge, you will benefit from the first experimental platform implementing an end-to-end LoRaWAN solution in Lebanon. The platform consists of the following elements: | + | During |
* Devices that communicate to one or more gateways via a wireless interface using single hop LoRa and implementing the LoRaWAN protocol. These devices are physically connected to sensors that generate data. | * Devices that communicate to one or more gateways via a wireless interface using single hop LoRa and implementing the LoRaWAN protocol. These devices are physically connected to sensors that generate data. | ||
Line 14: | Line 14: | ||
[{{ : | [{{ : | ||
+ | <WRAP center round help 100%> | ||
+ | * Where is the LoRa modulation implemented on the platform? | ||
+ | * What are the advantages of the LoRa modulation? | ||
+ | * How LoRa is compatible with LPWAN requirements and constraints? | ||
+ | * What is LoRaWAN? What is the difference between LoRaWAN and LoRa? | ||
+ | * Illustrate the protocol stacks on the LoRaWAN platform. | ||
+ | * What elements are IP enabled in the platform? What do you think about IP support in IoT? | ||
+ | </ | ||
+ | ===== -. Backend ===== | ||
+ | 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 '' | ||
+ | * A unique node name: '' | ||
+ | * The node description | ||
+ | * 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. | ||
+ | |||
+ | Make sure that the '' | ||
+ | |||
+ | <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. | ||
+ | * What is the difference between the two receive windows in LoRaWAN? What are they used for? | ||
+ | </ | ||
===== -. Devices ===== | ===== -. Devices ===== | ||
- | ==== -. Arduino with Dragino | + | Devices in the LoRaWAN platform are implemented on Arduino |
- | === -. Periodic Message Sending === | + | |
- | Devices in the LoRaWAN platform can also be implemented | + | Start by verifying |
- | The pin mapping corresponds to the Dragino electronic schematic: | + | <WRAP left round help 100%> |
- | <code c++> | + | * Give the characteristics of the Arduino you are using: model, number of pins, type of pins, memory sizes, etc. |
- | const lmic_pinmap lmic_pins = { | + | * Give the main characteristics of the LoRa shield from Dragino (www.dragino.com). |
- | .nss = 10, | + | * What type of Antenna are you using? Explain the corresponding characteristics. |
- | | + | </WRAP> |
- | .rst = 9, | + | |
- | .dio = {2, 6, 7}, | + | |
- | }; | + | |
- | </code> | + | |
- | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | + | Now you should configure your device with the same identifiers '' |
- | <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: | ||
<code c++> | <code c++> | ||
- | do_send(& | + | static const u1_t PROGMEM APPEUI[8]= { }; |
- | </ | + | void os_getArtEui |
- | The message containing the sensor values is transmitted on one of the radio channels (as in the Autonomo case): | + | // This should also be in little endian format, see above. |
- | <code c++> | + | static const u1_t PROGMEM DEVEUI[8]= { }; |
- | LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0); | + | void os_getDevEui |
- | </ | + | |
- | The adaptive data rate is not supported, and the spreading factor is configured as follows: | + | static const u1_t PROGMEM APPKEY[16] = { }; |
- | <code c++> | + | void os_getDevKey |
- | LMIC_setDrTxpow(DR_SF7,14); | + | |
</ | </ | ||
- | === -. Triggered Message Sending === | + | <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, '' | ||
+ | </ | ||
- | You can also find another example of sketch | + | Let us analyze |
- | ===== -. Gateways ===== | + | |
- | ==== -. Single Channel Gateway ==== | + | |
- | The single channel gateway includes a LoRa transmission module (Dragino Shield) connected to a Raspberry Pi (2 or 3) as shown in Figure 2. Communication between | + | <WRAP left round help 100%> |
+ | * In the setup function, which channels are activated on the device? | ||
+ | * What are the different spreading factors on each channel? | ||
+ | * What is the regulation on the radio channels in LoRa? | ||
+ | </ | ||
- | [{{ : | + | The LMIC library defines a set of events corresponding to the protocol machine state. These events appear in the '' |
- | In order to assemble | + | <WRAP left round help 100%> |
- | [{{ : | + | * What is the difference between |
- | [{{ : | + | * When is the EV_TXCOMPLETE event called? |
+ | </ | ||
- | Connect | + | Finally let us look at the message sending on the device. |
- | * Enable SPI on the Raspberry Pi using raspi-config | + | |
- | * Download and unzip the source code: | + | |
- | <code bash> | + | <WRAP left round help 100%> |
- | wget https:// | + | * What is the function for sending messages on the device? How it is called? |
- | unzip master.zip | + | * What is the period of message sending? Explain the implementation choice. |
- | </code> | + | * Is this period guaranteed according to the LoRaWAN specification? |
+ | </WRAP> | ||
- | * Install | + | Now you are ready to compile |
- | <code bash> | + | <WRAP left round tip 100%> |
- | apt-get update | + | For Arduino Mega 2560, additional drivers can be installed on Windows from http:// |
- | apt-get install wiring | + | </WRAP> |
- | </code> | + | |
- | Compile | + | Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages. |
- | <code bash> | + | |
- | make all | + | |
- | </ | + | |
- | For gcc version 4.6.3, a compilation error results in the following warning '' | + | <WRAP left round help 100%> |
- | <code> | + | * What is the radio transmit parameters of the captured debug messages? |
- | CFLAGS = -std=c++0x -c -Wall -I include/ | + | * What is the radio receive parameters of the captured debug messages for the two receive windows? |
- | </code> | + | </WRAP> |
- | Now, you need to configure | + | Getting back to the backend, you can monitor some important information related |
- | Finally, you can run the packet forwarder as root! | + | <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. | ||
+ | </ | ||
+ | ===== -. 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, | ||
+ | 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, | ||
- | <code bash> | + | <WRAP left round help 100%> |
- | nohup ./ | + | * Summarize the concepts and functionalities of the MQTT protocol. |
- | </code> | + | * What are the possible strengths and weaknesses in terms of security of MQTT? |
- | ==== -. Kerlink IoT Station ==== | + | * 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> | ||
- | <code> | + | <WRAP left round tip 100%> |
- | # activates eth0 at startup | + | The payload received by the MQTT client is decrypted but encoded in Base64. You should decode it to get the original message. |
- | ETHERNET=yes | + | </ |
- | # claims dhcp request on eth0 | + | |
- | ETHDHCP=yes | + | |
- | # Selector operator APN | + | If you need to send data to your device, you should publish the encoded message in the corresponding topic '' |
- | GPRSAPN=gprs.touch.com.lb | + | |
- | # Enter pin code if activated | + | |
- | GPRSPIN=0000 | + | |
- | # Update | + | |
- | GPRSDNS=yes | + | |
- | # PAP authentication | + | |
- | GPRSUSER= | + | |
- | GPRSPASSWORD= | + | |
- | + | ||
- | # Bearers priority order | + | |
- | # | + | |
- | BEARERS_PRIORITY=" | + | |
- | </code> | + | |
< | < | ||
- | ./gps-pkt-fwd.sh | + | { |
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
</ | </ | ||
+ | ===== -. Day One Challenges ===== | ||
- | < | + | ==== -. The End-to-End Challenge ==== |
- | 3270 root 2548 S / | + | I can send data from the device to the application. |
- | 3288 root 34908 S | + | |
- | </ | + | |
- | < | + | ==== -. The Downlink Challenge ==== |
- | /etc/init.d/gprs start | + | I can send data from the application to the device. |
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | + | ==== -. The Radio Challenge |
- | pppd (pid 5273) is running... | + | I can tune the LoRa radio parameters and assess the results. |
- | Session: Rx=58, Tx=163 | + | |
- | Globals: Rx=1130457, Tx=1195592 | + | These two commands can be helpful when used after the join event: |
- | Sum: Rx=1130515, Tx=1195755 | + | |
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | + | <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, | ||
- | ===== -. Backend | + | ===== -. Day Two Challenges |
- | ==== -. Loraserver | + | |
- | The Loraserver has a web interface for configuring the applications and devices on the platform. Full details for installing the software are provided on [[https:// | + | ==== -. The Wind Rises ==== |
- | [{{ :app-loraserver.png? | + | 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:// |
- | Start by creating and application as in Figure 5. Then create a node in this application and provide the following information: | + | ^ Provided material ^ |
- | * A unique node name | + | | VM with Node-RED installed | |
- | * The node description | + | | Node-RED example flow | |
- | * A unique device EUI on 64 bits: Random identifiers can be generated on [[https://www.random.org/bytes/]] | + | | [[https://emoncms.org/dashboard/view& |
- | * The application EUI on 64 bits: this can be a common identifier for all nodes using the same application. | + | |
- | * A unique application key on 128 bits | + | |
- | In order to enable OTAA join method, you have to make sure that the '' | + | ^ Required skills ^ |
+ | | Basic javascript | | ||
+ | | GUI configuration | | ||
+ | | Two drops of IoT graphic design | | ||
+ | ==== -. Nausicaa Challenge ==== | ||
+ | You have to take control on the devices. Use some scripting to send commands and do some actions or tune some parameters on the devices. | ||
- | ==== -. The Things Network | + | ^ 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 ==== | ||
+ | |||
+ | ==== -. Mononoke Challenge | ||
- | ===== -. Applications ===== | ||
- | ==== -. mqtt-spy ==== | ||
- | 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. For this, you should download the software tool from [[https:// | ||
- | ==== -. Emoncms ==== |
esib_iot_challenge.txt · Last modified: 2021/08/28 09:53 by samer