Differences

This shows you the differences between two versions of the page.

--- deploying_lorawan [2017/04/29 18:44] – [1.1. Autonomo with LoRaBee] samer
+++ deploying_lorawan [2017/05/01 15:16] – [4.1. MQTT spy] samer
@@ Line 1: / Line 1: @@
 ====== Deploying an End-to-End LoRaWAN Platform ======
-Starting from September 2016, Saint-Joseph University of Beirut (USJ) will be deploying the first academic [[http://www.semtech.com/wireless-rf/internet-of-things/what_is_lora.html | LoRa]] network in Lebanon. The network will support monitoring of micro-climate conditions in vineyards. Here below you can find a detailed description of the experimental platform implementing an end-to-end LoRaWAN solution.
+Starting from September 2016, Saint-Joseph University of Beirut (USJ) will be deploying the first academic [[http://www.semtech.com/wireless-rf/internet-of-things/what_is_lora.html | LoRa]] network in Lebanon. The network will support monitoring of micro-climate conditions in vineyards. Here below you can find a detailed description of the experimental platform implementing an end-to-end LoRaWAN solution. The platform consists of the following elements:
-[{{ :e2e-lorawan.png?direct&750 | Figure 2. Architecture of the LoRaWAN Platform}}]
+  * 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.
+  * Gateways or base stations that forward frames between the devices and the network server. Gateways are connected to the network server via IP interfaces.
+  * A LoRAWAN backend that implements the network server functions and provides frame control and security.
+  * Applications that enable to visualize and store the sensor data obtained from the devices.
+[{{ :lora-pilot-architecture.png?direct&650 | Figure 2. Architecture of the LoRaWAN Platform}}]
 ===== -. Devices =====
 ==== -. Autonomo with LoRaBee ====
-For the devices in the LoRaWAN platform, we will use an Autonomo board with a LoRaBee holding the Microchip RN2483 module. According to [[http://shop.sodaq.com]], Autonomo is a matchbox-sized powerhouse which uses the new Atmel Cortex M0+ 32bit micro controller. One advantage of such device is that it can be powered by a smartphone-sized solar panel.
+Starting with the devices in the LoRaWAN platform, we will use an [[http://support.sodaq.com/sodaq-one/autonomо/|Autonomo]] board with a LoRaBee Microchip RN2483 module. According to [[http://shop.sodaq.com]], Autonomo is a matchbox-sized powerhouse which uses the new Atmel Cortex M0+ 32bit micro controller. One advantage of such device is that it can be powered by a smartphone-sized solar panel.
 In order to configure the Autonomo with LoRaBee device, you should follow these steps:
@@ Line 16: / Line 20: @@
     - Add the following library {{ :sodaq_rn2483_2.zip |}} to your Arduino IDE as explained in [[https://www.arduino.cc/en/guide/libraries]].
-Now you are ready to write a sketch for the device. Here is one example sketch {{ :test-lorawan-combined-loraserver-example.zip |}} with the following features:
+Now you are ready to write a sketch for the device. Here is one example sketch {{ :test-lorawan-combined-loraserver-example.zip |}} where the autonomo is connected to three sensors: light, moisture, and temperature. Let us analyse some extracts of the code.
-  * Three sensors connected to the Autonomo on pins A0 (light sensor), A2 (moisture sensor), and D0 (temperature sensor).
+In this part, you should put the keys for Over-The-Air Activation (OTAA) as explained in the {{ :lorawan102-20161012_1398_1.pdf |LoRaWAN specification}}:
-  * OTA join method
+<code c++>
-  * Frequency channels
+// USE YOUR OWN KEYS!
-  * Message sending
+const uint8_t devEUI[8] =
+{ };
+// USE YOUR OWN KEYS!
+const uint8_t appEUI[8] =
+{ };
+const uint8_t appKey[16] =
+{ };
+</code>
+The pins for connecting the sensors are specified in these declarations (A0 for light sensor, A2 for moisture sensor, and D0 temperature sensor):
+<code c++>
+int light_pin = A0;
+int moisture_pin = A2;
+int temperature_pin = 0;
+int temperature_vcc_pin = 1;
+int moisture_vcc_pin = 8;
+int moisture_gnd_pin = 7;
+</code>
+The OTAA method is used for joining the network and Adaptive Data Rate (ADR) is activated:
+<code c++>
+LoRaBee.initOTA(loraSerial, devEUI, appEUI, appKey, true)
+</code>
+Eight different sub channels are activated with data rate ranges from 0 to 5:
+<code c++>
+LoRaBee.configChFreq(0, 868100000L,0,5,1);
+LoRaBee.configChFreq(1, 868300000L,0,5,1);
+LoRaBee.configChFreq(2, 868500000L,0,5,1);
+LoRaBee.configChFreq(3, 867100000L,0,5,1);
+LoRaBee.configChFreq(4, 867300000L,0,5,1);
+LoRaBee.configChFreq(5, 867500000L,0,5,1);
+LoRaBee.configChFreq(6, 867700000L,0,5,1);
+LoRaBee.configChFreq(7, 867900000L,0,5,1);
+</code>
+Finally, the message containing the sensor values is sent in an unconfirmed uplink message:
+<code c++>
+LoRaBee.send(1, (uint8_t*)message.c_str(), message.length())
+</code>
 ==== -. Arduino with Dragino Shield ====
+=== -. Periodic Message Sending ===
+Devices in the LoRaWAN platform can also be 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]]. Similarly to the Autonomo device, you can download the following sketch {{ :test-loraserver-comb-loraserver-dragino.zip |}} and modify it according to your preferences. Below you can find somme commented extracts of the sketch.
+The pin mapping corresponds to the Dragino electronic schematic:
+<code c++>
+const lmic_pinmap lmic_pins = {
+    .nss = 10,
+    .rxtx = LMIC_UNUSED_PIN,
+    .rst = 9,
+    .dio = {2, 6, 7},
+};
+</code>
+The send function is rescheduled TX_INTERVAL seconds after each transmission complete event:
+<code c++>
+        case EV_TXCOMPLETE:
+            Serial.println(F("EV_TXCOMPLETE (includes waiting for RX windows)"));
+            if(LMIC.dataLen) {
+                // data received in rx slot after tx
+                Serial.print(F("Data Received: "));
+                Serial.write(LMIC.frame+LMIC.dataBeg, LMIC.dataLen);
+                Serial.println();
+            }
+            // Schedule next transmission
+            os_setTimedCallback(&sendjob, os_getTime()+sec2osticks(TX_INTERVAL), do_send);
+            break;
+</code>
+The send function is initially scheduled here:
+<code c++>
+do_send(&sendjob);
+</code>
+The message containing the sensor values is transmitted on one of the radio channels (as in the Autonomo case):
+<code c++>
+LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0);
+</code>
+The adaptive data rate is not supported, and the spreading factor is configured as follows:
+<code c++>
+LMIC_setDrTxpow(DR_SF7,14);
+</code>
+=== -. Triggered Message Sending ===
+You can also find another example of sketch to download: {{ :test-loraserver-moisture-on-move.ino.zip |}}. Here the message sending is not periodic but related to an event. For example, an infrared sensor detects a movement and triggers a signal for the device to send a LoRaWAN message. Note also that the join method used in this second sketch is Activation by Personalisation (ABP): the device address, the network session key, and the application session key are directly configured on the device.
 ===== -. Gateways =====
 ==== -. Single Channel Gateway ====
@@ Line 63: / Line 152: @@
 </code>
-Now, you need to configure the single channel packet forwarder. This is done in the ''global_conf.json'' configuration file. Particularly, you need to choose the channel, the spreading factor, the pins for SPI communication, and the address of the backend server. Note that you can specify multiple backends for testing purposes.
+Now, you need to configure the single channel packet forwarder. This is done in the {{ :global_config.json.zip |}} configuration file. Particularly, you need to choose the channel, the spreading factor, the pins for SPI communication, and the address of the backend server. Note that you can specify multiple backends for testing purposes.
-<file | global_config.json>
-{
-  "SX127x_conf":
-  {
-    "freq": 868100000,
-    "spread_factor": 7,
-    "pin_nss": 6,
-    "pin_dio0": 7,
-    "pin_rst": 0,
-    "pin_led1":4
-  },
-  "gateway_conf":
-  {
-    "ref_latitude": 33.86576536772,
-    "ref_longitude": 35.56378662935,
-    "ref_altitude": 165,
-    "name": "ESIB SC Gateway",
-    "email": "cimti@usj.edu.lb",
-    "desc": "Dragino Single Channel Gateway on RPI",
-    "servers":
-    [
-      {
-        "address": "router.eu.thethings.network",
-        "port": 1700,
-        "enabled": true
-      },
-      {
-        "address": "212.98.137.194",
-        "port": 1700,
-        "enabled": true
-      },
-      {
-        "address": "172.17.17.129",
-        "port": 1700,
-        "enabled": false
-      }
-    ]
-  }
-}
-</file>
 Finally, you can run the packet forwarder as root!
@@ Line 161: / Line 207: @@
 ===== -. Applications =====
-==== -. MQTT spy ====
+==== -. mqtt-spy ====
+mqtt-spy is an open source utility intended to help you with monitoring activity on MQTT topics. It's been designed to deal with high volumes of messages, as well as occasional publications. mqtt-spy is a JavaFX application, so should work on any operating system with an appropriate version of Java 8 installed. A very useful tutorial is available on [[https://github.com/eclipse/paho.mqtt-spy/wiki]].
+Start by downloading the software tool from the previous link. After launching, configure a new connection to the MQTT broker by simply adding the IP address of the broker in the ''Server URI'' field.
 ==== -. Emoncms ====