Differences

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

--- deploying_lorawan [2016/12/20 12:24] – [2.1. Single Channel Gateway] samer
+++ deploying_lorawan [2017/04/29 18:04] – [1.1. Autonomo with LoRaBee] samer
@@ Line 5: / Line 5: @@
 [{{ :e2e-lorawan.png?direct&750 | Figure 2. Architecture of the LoRaWAN Platform}}]
-===== -. End-nodes =====
+===== -. 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.
+In order to configure the Autonomo with LoRaBee device, you should follow these steps:
+    - Verify that you have the latest Arduino IDE from [[https://www.arduino.cc/en/Main/Software]] on your computer.
+    - Install the board files as noted in [[http://support.sodaq.com/sodaq-one/autonomо/getting-started-autonomo/]].
+    - 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.
 ==== -. Arduino with Dragino Shield ====
@@ Line 13: / Line 22: @@
 ==== -. Single Channel Gateway ====
-The single channel gateway includes a LoRa transmission module (the Dragino Shield) connected to a Raspberry Pi (2 or 3). The connection pins are identified in Figures 2 and 3. Communication is done on an SPI communication interface.
+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}}]
-After making the correct connection, you need to install the packet forwarder software on the Raspberry Pi. The source code is available on: [[https://github.com/samerlahoud/single_chan_pkt_fwd]]. In order to proceed, you need to :
+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:
@@ Line 33: / Line 46: @@
 </code>
-  * Compile and run the packet forwarder as root.
+Compile the packet forwarder:
+<code bash>
+make all
+</code>
-gcc version 4.6.3
+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:
-unrecognized command line option '-std=c++11'
+<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 =====