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/17 20:19] – [7. The Radio 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: | ||
[{{ : | [{{ : | ||
- | ===== -. Devices | + | <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:// | ||
- | ==== -. PC Configuration ==== | + | [{{ :app-loraserver.png? |
- | In orde to program the LoRaWAN devices, you should verify the installation one your PC of the following software: | + | |
- | | + | Start by choosing the application named '' |
- | * LMIC Library | + | |
+ | * 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 '' | ||
- | ==== -. Arduino with Dragino Shield | + | <WRAP left round help 100%> |
- | === -. Periodic Message Sending | + | * 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 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]]. You can download the following sketch {{ : | + | 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]]. |
- | The pin mapping corresponds to the Dragino electronic schematic: | + | Start by verifying |
- | <code c++> | + | |
- | const lmic_pinmap lmic_pins = { | + | |
- | | + | |
- | | + | |
- | | + | |
- | .dio = {2, 6, 7}, | + | |
- | }; | + | |
- | </code> | + | |
- | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | + | <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. |
- | case EV_TXCOMPLETE: | + | * Give the main characteristics of the LoRa shield from Dragino |
- | Serial.println(F(" | + | * What type of Antenna are you using? Explain the corresponding characteristics. |
- | if(LMIC.dataLen) { | + | </WRAP> |
- | // data received in rx slot after tx | + | |
- | Serial.print(F(" | + | Now you should configure your device with the same identifiers '' |
- | Serial.write(LMIC.frame+LMIC.dataBeg, | + | |
- | | + | |
- | } | + | |
- | | + | |
- | | + | |
- | 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> | + | Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages. |
- | apt-get update | + | |
- | apt-get install wiring | + | |
- | </ | + | |
- | Compile the packet forwarder: | + | <WRAP left round help 100%> |
- | <code bash> | + | * What is the radio transmit parameters of the captured debug messages? |
- | make all | + | * What is the radio receive parameters of the captured debug messages for the two receive windows? |
- | </code> | + | </WRAP> |
+ | ===== -. 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. For this, you should download the software tool from [[https:// | ||
- | For gcc version 4.6.3, a compilation error results in the following warning '' | + | ===== -. The End-to-End Challenge ===== |
- | < | + | |
- | CFLAGS | + | |
- | </ | + | |
- | Now, you need to configure the single channel packet forwarder. This is done in the {{ : | + | ===== -. The Downlink Challenge ===== |
- | Finally, you can run the packet forwarder as root! | + | ===== -. The Radio Challenge ===== |
- | + | ||
- | <code bash> | + | |
- | nohup ./ | + | |
- | </ | + | |
- | ==== -. Kerlink IoT Station | + | |
< | < | ||
- | # activates eth0 at startup | + | // LMIC_disableChannel(1); |
- | ETHERNET=yes | + | // LMIC_disableChannel(2); |
- | # claims dhcp request on eth0 | + | // LMIC_disableChannel(3); |
- | ETHDHCP=yes | + | // LMIC_disableChannel(4); |
- | + | // LMIC_disableChannel(5); | |
- | # Selector operator APN | + | // LMIC_disableChannel(6); |
- | GPRSAPN=gprs.touch.com.lb | + | // LMIC_disableChannel(7); |
- | # Enter pin code if activated | + | // |
- | GPRSPIN=0000 | + | // LMIC_setDrTxpow(DR_SF10,14); |
- | # Update | + | |
- | GPRSDNS=yes | + | |
- | # PAP authentication | + | |
- | GPRSUSER= | + | |
- | GPRSPASSWORD= | + | |
- | + | ||
- | # Bearers priority order | + | |
- | # | + | |
- | BEARERS_PRIORITY=" | + | |
</ | </ | ||
< | < | ||
- | ./gps-pkt-fwd.sh > /dev/null & | + | { |
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }], | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | }, | ||
+ | " | ||
+ | } | ||
+ | } | ||
</ | </ | ||
- | |||
- | < | ||
- | 3270 root 2548 S /bin/sh ./ | ||
- | 3288 root 34908 S ./ | ||
- | </ | ||
- | |||
- | < | ||
- | / | ||
- | |||
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | ||
- | pppd (pid 5273) is running... | ||
- | Session: Rx=58, Tx=163 | ||
- | Globals: Rx=1130457, Tx=1195592 | ||
- | Sum: | ||
- | [root@Wirgrid_0b03008c demo_gps_loramote]# | ||
- | </ | ||
- | |||
- | ===== -. Backend ===== | ||
- | ==== -. 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:// | ||
- | |||
- | [{{ : | ||
- | |||
- | Start by creating and application as in Figure 5. Then create a node in this application and provide the following information: | ||
- | * 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 '' | ||
- | |||
- | |||
- | ==== -. 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