wikiroute

networking recipes

User Tools

Site Tools

Trace:
deploying_lorawan

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
deploying_lorawan [2017/04/30 16:49] – [Deploying an End-to-End LoRaWAN Platform] samerdeploying_lorawan [2017/04/30 17:04] – [2.1. Single Channel Gateway] samer
Line 4: Line 4:
  
   * 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. 
-  * Gateways or base stations that relay the radio frames to the IP backend. +  * 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 implementing the network server function. +  * A LoRAWAN backend that implements the network server functions and provides frame control and security. 
-  * Application examples that enable to visualize and store the sensor data. +  * 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}}] [{{ :lora-pilot-architecture.png?direct&650 | Figure 2. Architecture of the LoRaWAN Platform}}]
Line 147: Line 147:
 </code> </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! Finally, you can run the packet forwarder as root!
deploying_lorawan.txt · Last modified: 2021/08/28 09:50 by samer