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 12:06] – [1.1. Autonomo with LoRaBee] samer | deploying_lorawan [2017/05/01 15:43] – [4.1. mqtt-spy] 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 ==== | ||
- | For the devices in the LoRaWAN platform, we will use an Autonomo board with a LoRaBee | + | Starting with the devices in the LoRaWAN platform, we will use an [[http:// |
In order to configure the Autonomo with LoRaBee device, you should follow these steps: | In order to configure the Autonomo with LoRaBee device, you should follow these steps: | ||
Line 18: | Line 22: | ||
Now you are ready to write a sketch for the device. Here is one example sketch {{ : | Now you are ready to write a sketch for the device. Here is one example sketch {{ : | ||
- | In this part, you should put the keys for Over-The-Air Activation (OTAA) as explained in the LoRaWAN specification: | + | In this part, you should put the keys for Over-The-Air Activation (OTAA) as explained in the {{ : |
<code c++> | <code c++> | ||
// USE YOUR OWN KEYS! | // USE YOUR OWN KEYS! | ||
Line 36: | Line 40: | ||
int light_pin = A0; | int light_pin = A0; | ||
int moisture_pin = A2; | int moisture_pin = A2; | ||
- | |||
int temperature_pin = 0; | int temperature_pin = 0; | ||
int temperature_vcc_pin = 1; | int temperature_vcc_pin = 1; | ||
Line 43: | Line 46: | ||
</ | </ | ||
- | The OTAA method is used for joining the network and adaptive data rate is activated: | + | The OTAA method is used for joining the network and Adaptive Data Rate (ADR) is activated: |
<code c++> | <code c++> | ||
LoRaBee.initOTA(loraSerial, | LoRaBee.initOTA(loraSerial, | ||
Line 50: | Line 53: | ||
Eight different sub channels are activated with data rate ranges from 0 to 5: | Eight different sub channels are activated with data rate ranges from 0 to 5: | ||
<code c++> | <code c++> | ||
- | | + | LoRaBee.configChFreq(0, |
- | LoRaBee.configChFreq(1, | + | LoRaBee.configChFreq(1, |
- | LoRaBee.configChFreq(2, | + | LoRaBee.configChFreq(2, |
- | LoRaBee.configChFreq(3, | + | LoRaBee.configChFreq(3, |
- | LoRaBee.configChFreq(4, | + | LoRaBee.configChFreq(4, |
- | LoRaBee.configChFreq(5, | + | LoRaBee.configChFreq(5, |
- | LoRaBee.configChFreq(6, | + | LoRaBee.configChFreq(6, |
- | LoRaBee.configChFreq(7, | + | LoRaBee.configChFreq(7, |
</ | </ | ||
- | Finally, the message is sent in an unconfirmed | + | Finally, the message |
<code c++> | <code c++> | ||
LoRaBee.send(1, | LoRaBee.send(1, | ||
</ | </ | ||
==== -. Arduino with Dragino Shield ==== | ==== -. 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]]. Similarly to the Autonomo device, you can download the following sketch {{ : | ||
+ | |||
+ | The pin mapping corresponds to the Dragino electronic schematic: | ||
+ | <code c++> | ||
+ | const lmic_pinmap lmic_pins = { | ||
+ | .nss = 10, | ||
+ | .rxtx = LMIC_UNUSED_PIN, | ||
+ | .rst = 9, | ||
+ | .dio = {2, 6, 7}, | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | The send function is rescheduled TX_INTERVAL seconds after each transmission complete event: | ||
+ | <code c++> | ||
+ | case EV_TXCOMPLETE: | ||
+ | Serial.println(F(" | ||
+ | if(LMIC.dataLen) { | ||
+ | // data received in rx slot after tx | ||
+ | Serial.print(F(" | ||
+ | Serial.write(LMIC.frame+LMIC.dataBeg, | ||
+ | Serial.println(); | ||
+ | } | ||
+ | // Schedule next transmission | ||
+ | os_setTimedCallback(& | ||
+ | break; | ||
+ | </ | ||
+ | |||
+ | The send function is initially scheduled here: | ||
+ | <code c++> | ||
+ | do_send(& | ||
+ | </ | ||
+ | |||
+ | The message containing the sensor values is transmitted on one of the radio channels (as in the Autonomo case): | ||
+ | <code c++> | ||
+ | LMIC_setTxData2(1, | ||
+ | </ | ||
+ | |||
+ | The adaptive data rate is not supported, and the spreading factor is configured as follows: | ||
+ | <code c++> | ||
+ | LMIC_setDrTxpow(DR_SF7, | ||
+ | </ | ||
+ | |||
+ | === -. Triggered Message Sending === | ||
+ | |||
+ | You can also find another example of sketch to download: {{ : | ||
===== -. Gateways ===== | ===== -. Gateways ===== | ||
==== -. Single Channel Gateway ==== | ==== -. Single Channel Gateway ==== | ||
Line 103: | 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 201: | Line 207: | ||
===== -. Applications ===== | ===== -. 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, | ||
+ | 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 '' | ||
==== -. Emoncms ==== | ==== -. Emoncms ==== |
deploying_lorawan.txt · Last modified: 2021/08/28 09:50 by samer