Differences

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

--- deploying_lorawan [2017/05/01 15:00] – [1.2. Arduino with Dragino Shield] samer
+++ deploying_lorawan [2017/05/02 17:52] – samer
@@ Line 8: / Line 8: @@
   * 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 1. Architecture of the LoRaWAN Platform}}]
 ===== -. Devices =====
 ==== -. Autonomo with LoRaBee ====
@@ Line 114: / Line 114: @@
 === -. Triggered Message Sending ===
-You can also find another example of sketch to download: {{ :test-loraserver-moisture-on-move.ino.zip |}}. Here the message sending is not periodic but related to an event. For example, an infrared sensor detects a movement and triggers a signal for the device to send a LoRaWAN message.
+You can also find another example of sketch to download: {{ :test-loraserver-moisture-on-move.ino.zip |}}. Here the message sending is not periodic but related to an event. For example, an infrared sensor detects a movement and triggers a signal for the device to send a LoRaWAN message. Note also that the join method used in this second sketch is Activation by Personalisation (ABP): the device address, the network session key, and the application session key are directly configured on the device.
 ===== -. Gateways =====
 ==== -. Single Channel Gateway ====
-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 2. 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.
+In order to assemble the gateway, start by making the wire connections: the connection pins are identified in Figures 3 and 4.
-[{{ :schema-single-channel-pi3.png?direct&300 |Figure 2. Dragino pin mapping}}]
+[{{ :schema-single-channel-pi3.png?direct&300 |Figure 3. Dragino pin mapping}}]
-[{{ :schema-pins-pi3.png?direct&300 |Figure 3. Raspberry pi 3 pins}}]
+[{{ :schema-pins-pi3.png?direct&300 |Figure 4. Raspberry pi 3 pins}}]
 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:
@@ Line 204: / Line 204: @@
 ===== -. Backend =====
 ==== -. 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://www.loraserver.io]]. Start by creating and application as in the Figure 5.
+[{{ :app-loraserver.png?direct&400 | Figure 5. Loraserver web interface}}]
 ==== -. The Things Network ====
 ===== -. 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, so it should work on any operating system with an appropriate version of Java 8 installed. A very useful tutorial is available on [[https://github.com/eclipse/paho.mqtt-spy/wiki]].
+You can use mqtt-spy to debug the messages received from the LoRaWAN devices. For this, you should download the software tool from [[https://github.com/eclipse/paho.mqtt-spy/wiki]]. After starting the application, configure a new connection to the MQTT broker by simply adding the IP address of the broker in the ''Server URI'' field. Now you can subscribe to any MQTT topic. If you want to receive all messages arriving at the backend, you can use the generic topic ''#''. You can also limit to the topic including the messages of any specific device: ''application/APPLICATION_ID/node/DEVICE_EUI/rx''.
 ==== -. Emoncms ====