Differences

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

--- deploying_lorawan [2016/12/20 09:09] – [2.1. Single Channel Packet Forwarder] samer
+++ deploying_lorawan [2017/04/29 17:45] – [1. End-nodes] samer
@@ Line 3: / Line 3: @@
 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.
-[{{ :e2e-lorawan.png?direct&750 | Figure 1. Architecture of the LoRaWAN Platform}}]
+[{{ :e2e-lorawan.png?direct&750 | Figure 2. Architecture of the LoRaWAN Platform}}]
-===== -. End-nodes =====
+===== -. Devices =====
 ==== -. Autonomo with LoRaBee ====
+For the end-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. It can be powered by a smartphone-sized solar panel.
+In order to configure the end-
 ==== -. Arduino with Dragino Shield ====
@@ Line 13: / Line 16: @@
 ==== -. Single Channel Gateway ====
-The single channel gateway includes a LoRa transmission module (the Dragino Shield) connected to a Raspberry Pi (2 or 3).
+The single channel gateway includes a LoRa transmission module (Dragino Shield) connected to a Raspberry Pi (2 or 3) as shown in Figure 1. Communication between the two modules is done over an SPI interface.
+[{{ :2017-01-04_11.34.54.jpg?direct&300 |Figure 2. LoRa single channel gateway}}]
+In order to assemble the gateway, start by making the wire connections: the connection pins are identified in Figures 2 and 3.
+[{{ :schema-single-channel-pi3.png?direct&300 |Figure 2. Dragino pin mapping}}]
+[{{ :schema-pins-pi3.png?direct&300 |Figure 3. Raspberry pi 3 pins}}]
+Connect the Raspberry Pi to the Internet and install the packet forwarding software. The source code of the single channel packet forwarder is available on: [[https://github.com/samerlahoud/single_chan_pkt_fwd]]. In order to install it, you need to:
+  * Enable SPI on the Raspberry Pi using raspi-config
+  * Download and unzip the source code:
+<code bash>
+wget https://github.com/hallard/single_chan_pkt_fwd/archive/master.zip
+unzip master.zip
+</code>
+  * Install the wiring library:
+<code bash>
+apt-get update
+apt-get install wiring
+</code>
+Compile the packet forwarder:
+<code bash>
+make all
+</code>
+For gcc version 4.6.3, a compilation error results in the following warning ''unrecognized command line option '-std=c++11'''. Replace ''-std=c++11'' by ''-std=c++0x'' in the Makefile and recompile:
+<code>
+CFLAGS = -std=c++0x -c -Wall -I include/
+</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.
+<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!
+<code bash>
+nohup ./single_chan_pkt_fwd &
+</code>
 ==== -. Kerlink IoT Station ====
+<code>
+# activates eth0 at startup
+ETHERNET=yes
+# claims dhcp request on eth0
+ETHDHCP=yes
+# Selector operator APN
+GPRSAPN=gprs.touch.com.lb
+# Enter pin code if activated
+GPRSPIN=0000
+# Update /etc/resolv.conf to get dns facilities
+GPRSDNS=yes
+# PAP authentication
+GPRSUSER=
+GPRSPASSWORD=
+# Bearers priority order
+#BEARERS_PRIORITY="eth0,ppp0,eth1"
+BEARERS_PRIORITY="ppp0,eth0,eth1"
+</code>
+<code>
+./gps-pkt-fwd.sh > /dev/null &
+</code>
+<code>
+root      2548 S    /bin/sh ./gps-pkt-fwd.sh
+root     34908 S    ./gps_pkt_fwd
+</code>
+<code>
+/etc/init.d/gprs start
+[root@Wirgrid_0b03008c demo_gps_loramote]# /etc/init.d/gprs  status
+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]#
+</code>
 ===== -. Backend =====
@@ Line 23: / Line 150: @@
 ==== -. MQTT spy ====
 ==== -. Emoncms ====