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/01/04 10:52] – [2.1. Single Channel Gateway] samer | deploying_lorawan [2017/04/30 12:59] – [1.2. Arduino with Dragino Shield] samer | ||
---|---|---|---|
Line 5: | Line 5: | ||
[{{ : | [{{ : | ||
- | ===== -. End-nodes | + | ===== -. Devices |
==== -. Autonomo with LoRaBee ==== | ==== -. 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:// | ||
+ | |||
+ | In order to configure the Autonomo with LoRaBee device, you should follow these steps: | ||
+ | |||
+ | - Verify that you have the latest Arduino IDE from [[https:// | ||
+ | - Install the board files as noted in [[http:// | ||
+ | - Add the following library {{ : | ||
+ | |||
+ | 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: | ||
+ | <code c++> | ||
+ | // USE YOUR OWN KEYS! | ||
+ | const uint8_t devEUI[8] = | ||
+ | { }; | ||
+ | |||
+ | // USE YOUR OWN KEYS! | ||
+ | const uint8_t appEUI[8] = | ||
+ | { }; | ||
+ | |||
+ | const uint8_t appKey[16] = | ||
+ | { }; | ||
+ | </ | ||
+ | |||
+ | The pins for connecting the sensors are specified in these declarations (A0 for light sensor, A2 for moisture sensor, and D0 temperature sensor): | ||
+ | <code c++> | ||
+ | int light_pin = A0; | ||
+ | int moisture_pin = A2; | ||
+ | |||
+ | int temperature_pin = 0; | ||
+ | int temperature_vcc_pin = 1; | ||
+ | int moisture_vcc_pin = 8; | ||
+ | int moisture_gnd_pin = 7; | ||
+ | </ | ||
+ | |||
+ | The OTAA method is used for joining the network and adaptive data rate is activated: | ||
+ | <code c++> | ||
+ | LoRaBee.initOTA(loraSerial, | ||
+ | </ | ||
+ | |||
+ | Eight different sub channels are activated with data rate ranges from 0 to 5: | ||
+ | <code c++> | ||
+ | LoRaBee.configChFreq(0, | ||
+ | LoRaBee.configChFreq(1, | ||
+ | LoRaBee.configChFreq(2, | ||
+ | LoRaBee.configChFreq(3, | ||
+ | LoRaBee.configChFreq(4, | ||
+ | LoRaBee.configChFreq(5, | ||
+ | LoRaBee.configChFreq(6, | ||
+ | LoRaBee.configChFreq(7, | ||
+ | </ | ||
+ | |||
+ | Finally, the message is sent in an unconfirmed uplink message: | ||
+ | <code c++> | ||
+ | LoRaBee.send(1, | ||
+ | </ | ||
==== -. Arduino with Dragino Shield ==== | ==== -. Arduino with Dragino Shield ==== | ||
+ | Devices in the LoRaWAN platform can also be used on Arduino boards with Dragino shields as presented in [[simple_lora_prototype|Simple Prototype of LoRa Communications]]. In the latter reference, you can also find the basic steps for working with the IDE. Similarly to the Autonomo device, you can download the following sketch {{ : | ||
+ | |||
+ | <code c++> | ||
+ | const lmic_pinmap lmic_pins = { | ||
+ | .nss = 10, | ||
+ | .rxtx = LMIC_UNUSED_PIN, | ||
+ | .rst = 9, | ||
+ | .dio = {2, 6, 7}, | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | <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; | ||
+ | </ | ||
+ | |||
+ | <code c++> | ||
+ | LMIC_setTxData2(1, | ||
+ | </ | ||
+ | |||
+ | <code c++> | ||
+ | LMIC_setDrTxpow(DR_SF7, | ||
+ | </ | ||
+ | |||
+ | <code c++> | ||
+ | do_send(& | ||
+ | </ | ||
===== -. Gateways ===== | ===== -. Gateways ===== | ||
==== -. Single Channel Gateway ==== | ==== -. Single Channel Gateway ==== | ||
Line 15: | Line 107: | ||
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. | 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. | ||
- | [{{ : | + | [{{ : |
In order to assemble the gateway, start by making the wire connections: | In order to assemble the gateway, start by making the wire connections: | ||
Line 37: | Line 129: | ||
</ | </ | ||
- | Now you can compile and run the packet forwarder | + | Compile |
<code bash> | <code bash> | ||
make all | make all | ||
- | nohup ./ | ||
</ | </ | ||
- | < | + | For gcc version 4.6.3, a compilation error results in the following warning '' |
+ | < | ||
+ | CFLAGS = -std=c++0x -c -Wall -I include/ | ||
+ | </ | ||
+ | |||
+ | Now, you need to configure the single channel packet forwarder. This is done in the '' | ||
+ | |||
+ | < | ||
{ | { | ||
" | " | ||
Line 85: | Line 183: | ||
} | } | ||
</ | </ | ||
+ | |||
+ | Finally, you can run the packet forwarder as root! | ||
<code bash> | <code bash> | ||
- | gcc version 4.6.3 | + | nohup ./single_chan_pkt_fwd & |
- | unrecognized command line option ' | + | |
- | CFLAGS = -std=c++0x -c -Wall -I include/ | + | |
</ | </ | ||
==== -. Kerlink IoT Station ==== | ==== -. Kerlink IoT Station ==== |
deploying_lorawan.txt · Last modified: 2021/08/28 09:50 by samer