deploying_lorawan
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
deploying_lorawan [2017/04/30 14:37] – [1.1. Autonomo with LoRaBee] samer | deploying_lorawan [2017/05/02 17:50] – [3.1. Loraserver] samer | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Deploying an End-to-End LoRaWAN Platform ====== | ====== Deploying an End-to-End LoRaWAN Platform ====== | ||
- | Starting from September 2016, Saint-Joseph University of Beirut (USJ) will be deploying the first academic [[http:// | + | Starting from September 2016, Saint-Joseph University of Beirut (USJ) will be deploying the first academic [[http:// |
- | [{{ : | + | * 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 | ||
+ | * 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. | ||
+ | [{{ : | ||
===== -. Devices ===== | ===== -. Devices ===== | ||
==== -. Autonomo with LoRaBee ==== | ==== -. Autonomo with LoRaBee ==== | ||
Line 64: | Line 68: | ||
</ | </ | ||
==== -. Arduino with Dragino Shield ==== | ==== -. Arduino with Dragino Shield ==== | ||
+ | === -. Periodic Message Sending === | ||
- | Devices in the LoRaWAN platform can also be used 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]]. | + | Devices in the LoRaWAN platform can also be implemented |
- | Do not forget | + | The pin mapping corresponds |
<code c++> | <code c++> | ||
const lmic_pinmap lmic_pins = { | const lmic_pinmap lmic_pins = { | ||
Line 77: | Line 82: | ||
</ | </ | ||
- | The send function is called upon after each transmission complete event: | + | The send function is rescheduled TX_INTERVAL seconds |
<code c++> | <code c++> | ||
case EV_TXCOMPLETE: | case EV_TXCOMPLETE: | ||
Line 92: | Line 97: | ||
</ | </ | ||
- | This is explicitly the send function | + | The send function |
<code c++> | <code c++> | ||
- | LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0); | + | do_send(& |
</ | </ | ||
- | You can modify | + | The message containing |
<code c++> | <code c++> | ||
- | LMIC_setDrTxpow(DR_SF7,14); | + | LMIC_setTxData2(1, (uint8_t*) buffer, message.length() , 0); |
</ | </ | ||
- | Schedule | + | The adaptive data rate is not supported, and the spreading factor is configured as follows: |
<code c++> | <code c++> | ||
- | do_send(& | + | LMIC_setDrTxpow(DR_SF7,14); |
</ | </ | ||
+ | |||
+ | === -. Triggered Message Sending === | ||
+ | |||
+ | You can also find another example of sketch to download: {{ : | ||
===== -. Gateways ===== | ===== -. Gateways ===== | ||
==== -. Single Channel Gateway ==== | ==== -. Single Channel Gateway ==== | ||
Line 143: | Line 152: | ||
</ | </ | ||
- | Now, you need to configure the single channel packet forwarder. This is done in the '' | + | Now, you need to configure the single channel packet forwarder. This is done in the {{ : |
- | + | ||
- | <file | global_config.json> | + | |
- | { | + | |
- | " | + | |
- | { | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | }, | + | |
- | " | + | |
- | { | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | + | ||
- | " | + | |
- | " | + | |
- | " | + | |
- | + | ||
- | " | + | |
- | [ | + | |
- | { | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | }, | + | |
- | { | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | }, | + | |
- | { | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | } | + | |
- | ] | + | |
- | } | + | |
- | } | + | |
- | </ | + | |
Finally, you can run the packet forwarder as root! | Finally, you can run the packet forwarder as root! | ||
Line 238: | Line 204: | ||
===== -. Backend ===== | ===== -. Backend ===== | ||
==== -. Loraserver ==== | ==== -. Loraserver ==== | ||
+ | |||
+ | The Loraserver has a web interface for configuring the applications and devices on the platform. Full details for installing the software are provided on [[https:// | ||
+ | |||
+ | {{ : | ||
==== -. The Things Network ==== | ==== -. The Things Network ==== | ||
===== -. Applications ===== | ===== -. Applications ===== | ||
- | ==== -. MQTT spy ==== | + | ==== -. mqtt-spy ==== |
+ | |||
+ | mqtt-spy is an open source utility intended to help you with monitoring activity on MQTT topics. It has been designed to deal with high volumes of messages, as well as occasional publications. mqtt-spy is a JavaFX application, | ||
+ | You can use mqtt-spy to debug the messages received from the LoRaWAN devices. For this, you should download the software tool from [[https:// | ||
==== -. Emoncms ==== | ==== -. Emoncms ==== |
deploying_lorawan.txt · Last modified: 2021/08/28 09:50 by samer