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:36] – [2.1. Arduino with Dragino Shield] samer | esib_iot_challenge [2017/05/22 18:25] – [6.1. The Wind Rises] 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 ===== | ||
- | ==== -. PC Configuration ==== | + | Devices in the LoRaWAN |
- | In orde to program | + | |
- | * Arduino IDE | + | Start by verifying the installation on your PC of the latest |
- | * LMIC Library | + | |
- | ==== -. Arduino | + | <WRAP left round help 100%> |
- | === -. Periodic Message Sending === | + | * Give the characteristics of the Arduino |
+ | * Give the main characteristics of the LoRa shield from Dragino | ||
+ | * What type of Antenna are you using? Explain the corresponding characteristics. | ||
+ | </ | ||
- | Devices in the LoRaWAN platform are implemented on Arduino boards with Dragino shields. The combined module | + | Now you should configure your device with the same identifiers '' |
- | The pin mapping corresponds to the Dragino electronic schematic: | ||
<code c++> | <code c++> | ||
- | const lmic_pinmap lmic_pins | + | static |
- | .nss = 10, | + | void os_getArtEui (u1_t* buf) { memcpy_P(buf, APPEUI, 8);} |
- | .rxtx = LMIC_UNUSED_PIN, | + | |
- | .rst = 9, | + | |
- | .dio = {2, 6, 7}, | + | |
- | }; | + | |
- | </ | + | |
- | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | + | // This should also be in little endian format, see above. |
- | <code c++> | + | static const u1_t PROGMEM DEVEUI[8]= { }; |
- | case EV_TXCOMPLETE: | + | void os_getDevEui |
- | Serial.println(F(" | + | |
- | if(LMIC.dataLen) { | + | |
- | | + | |
- | Serial.print(F(" | + | |
- | Serial.write(LMIC.frame+LMIC.dataBeg, LMIC.dataLen); | + | |
- | | + | |
- | } | + | |
- | // Schedule next transmission | + | |
- | os_setTimedCallback(& | + | |
- | break; | + | |
- | </ | + | |
- | The send function is initially scheduled here: | + | static const u1_t PROGMEM APPKEY[16] = { }; |
- | <code c++> | + | void os_getDevKey (u1_t* buf) { memcpy_P(buf, APPKEY, 16);} |
- | do_send(& | + | |
</ | </ | ||
- | The message containing the sensor values is transmitted on one of the radio channels (as in the Autonomo case): | + | <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, '' |
- | LMIC_setTxData2(1, (uint8_t*) buffer, message.length() | + | </WRAP> |
- | </code> | + | |
- | The adaptive data rate is not supported, and the spreading factor is configured as follows: | + | Let us analyze to radio parameters in the sketch by answering the following questions. |
- | <code c++> | + | |
- | LMIC_setDrTxpow(DR_SF7, | + | |
- | </ | + | |
- | === -. Triggered Message Sending === | + | <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? | ||
+ | </ | ||
- | You can also find another example | + | The LMIC library defines a set of events corresponding |
- | ===== -. 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 | + | <WRAP left round help 100%> |
+ | * What is the difference | ||
+ | * When is the EV_TXCOMPLETE event called? | ||
+ | </ | ||
- | [{{ : | + | Finally let us look at the message sending on the device. |
- | In order to assemble | + | <WRAP left round help 100%> |
- | [{{ : | + | * 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? | ||
+ | </ | ||
- | Connect the Raspberry Pi to the Internet | + | Now you are ready to compile |
- | * Enable SPI on the Raspberry Pi using raspi-config | + | |
- | * Download | + | |
- | <code bash> | + | <WRAP left round tip 100%> |
- | wget https://github.com/hallard/single_chan_pkt_fwd/ | + | For Arduino Mega 2560, additional drivers can be installed on Windows from http://wch.cn/download/CH341SER_ZIP.html. |
- | unzip master.zip | + | </WRAP> |
- | </code> | + | |
- | * Install | + | Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages. |
- | <code bash> | + | <WRAP left round help 100%> |
- | apt-get update | + | * What is the radio transmit parameters of the captured debug messages? |
- | apt-get install wiring | + | * What is the radio receive parameters of the captured debug messages for the two receive windows? |
- | </code> | + | </WRAP> |
- | Compile | + | Getting back to the backend, you can monitor some important information related to your device. Click on the corresponding node session. |
- | <code bash> | + | |
- | make all | + | |
- | </ | + | |
- | For gcc version | + | <WRAP left round help 100%> |
- | < | + | * What are the different fields that appear in the node session corresponding to you device? |
- | CFLAGS = -std=c++0x -c -Wall -I include/ | + | * Explain how each field is created according to the LoRaWAN specification. |
- | </code> | + | * 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, configure | ||
- | Now, you need to configure | + | <WRAP left round help 100%> |
+ | * Summarize | ||
+ | * What are the possible strengths | ||
+ | * 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. | ||
+ | </ | ||
- | Finally, you can run the packet forwarder as root! | + | <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. | ||
+ | </ | ||
- | <code bash> | + | If you need to send data to your device, you should publish the encoded message in the corresponding topic '' |
- | nohup ./single_chan_pkt_fwd & | + | |
- | </code> | + | |
- | ==== -. Kerlink IoT Station ==== | + | |
< | < | ||
- | # activates eth0 at startup | + | { |
- | ETHERNET=yes | + | " |
- | # claims dhcp request | + | " |
- | ETHDHCP=yes | + | " |
+ | " | ||
+ | } | ||
+ | </ | ||
+ | ===== -. Day One Challenges ===== | ||
- | # Selector operator APN | + | ==== -. The End-to-End Challenge ==== |
- | GPRSAPN=gprs.touch.com.lb | + | I can send data from the device to the application. |
- | # Enter pin code if activated | + | |
- | GPRSPIN=0000 | + | |
- | # Update /etc/resolv.conf to get dns facilities | + | |
- | GPRSDNS=yes | + | |
- | # PAP authentication | + | |
- | GPRSUSER= | + | |
- | GPRSPASSWORD= | + | |
- | # Bearers priority order | + | ==== -. The Downlink Challenge ==== |
- | # | + | I can send data from the application to the device. |
- | BEARERS_PRIORITY=" | + | |
- | </ | + | |
- | < | + | ==== -. The Radio Challenge ==== |
- | ./gps-pkt-fwd.sh > /dev/null & | + | I can tune the LoRa radio parameters and assess the results. |
- | </ | + | |
- | < | + | These two commands can be helpful when used after the join event: |
- | 3270 root 2548 S /bin/sh ./ | + | |
- | 3288 root 34908 S ./ | + | < |
+ | 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 ===== |
- | /etc/init.d/gprs start | + | |
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | + | ==== -. The Wind Rises ==== |
- | pppd (pid 5273) is running... | + | |
- | Session: Rx=58, Tx=163 | + | |
- | Globals: Rx=1130457, Tx=1195592 | + | |
- | Sum: Rx=1130515, Tx=1195755 | + | |
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | + | |
- | </ | + | |
- | ===== -. Backend ===== | + | This is a mandatory challenge. It consists of using [[https:// |
- | ==== -. 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://www.loraserver.io]]. | + | ^ Provided material ^ |
+ | | VM with Node-RED installed | | ||
+ | | Node-RED example flow | | ||
+ | | [[https://emoncms.org/ | ||
- | [{{ : | + | ^ Required skills ^ |
+ | | Basic javascript | | ||
+ | | GUI configuration | | ||
+ | | Two drops of IoT imagination | | ||
+ | ==== -. Nausicaa Challenge ==== | ||
- | Start by creating and application as in Figure 5. Then create a node in this application and provide the following information: | + | ==== -. Totoro Challenge ==== |
- | * 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: 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 '' | + | ==== -. Kiki Challenge ==== |
+ | ==== -. Mononoke Challenge ==== | ||
- | ==== -. The Things Network ==== | ||
- | ===== -. 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