Differences

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

--- deploying_lorawan [2017/04/30 16:19] – [Deploying an End-to-End LoRaWAN Platform] 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:
-[{{ :lora-pilot-architecture.jpg?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 ====
@@ Line 64: / Line 68: @@
 </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]]. As for 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.
+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:
@@ Line 92: / Line 97: @@
 </code>
-This send function is initially scheduled here:
+The send function is initially scheduled here:
 <code c++>
 do_send(&sendjob);
@@ Line 106: / Line 111: @@
 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 143: / 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 241: / 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 ====