wikiroute

networking recipes

User Tools

Site Tools


exploring_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
exploring_lorawan [2019/10/23 14:16] – [8. Backend] samerexploring_lorawan [2019/11/28 07:38] – [5.4. The Sensor Challenge] samer
Line 22: Line 22:
 </WRAP> </WRAP>
 ===== -. Backend ===== ===== -. Backend =====
-In a LoRaWAN network, the devices communicate with a Network Server through the gateway. The backend installed in the platform is based on an open-source LoRaWAN network-server https://www.loraserver.io. A web interface is available for configuring the applications and devices on the platform (https://212.98.XX.XX:8080).+In a LoRaWAN network, the devices communicate with a Network Server through the gateway. The backend installed in the platform is based on an open-source LoRaWAN network-server https://www.loraserver.io. A web interface is available for configuring the applications and devices on the platform (http://212.98.XX.XX:8080).
  
 [{{ :app-loraserver.png?direct&600 | Figure 2. Loraserver web interface}}] [{{ :app-loraserver.png?direct&600 | Figure 2. Loraserver web interface}}]
Line 29: Line 29:
   * A unique device name: ''IoT-GX'' (where ''X'' is your group number)   * A unique device name: ''IoT-GX'' (where ''X'' is your group number)
   * The device description   * The device description
-  * A unique device EUI on 64 bits: Random identifiers can be generated on [[https://www.random.org/bytes/]]+  * A unique device EUI on 64 bits: click on the circular arrow to generate a random EUI.
   * A unique application key on 128 bits also obtained by random generation.   * A unique application key on 128 bits also obtained by random generation.
    
Line 42: Line 42:
 Devices in the LoRaWAN platform are implemented on Arduino boards with Dragino shields. The combined module as well as the basic configuration steps are presented in [[exploring_lora|Exploring LoRa lab]].  Devices in the LoRaWAN platform are implemented on Arduino boards with Dragino shields. The combined module as well as the basic configuration steps are presented in [[exploring_lora|Exploring LoRa lab]]. 
  
-Start by verifying the installation on your PC of the latest Arduino IDE. Unzip the Arduino {{ :arduino-lmic-master.zip |LMIC library}} and copy it to your sketchbook library folder as detailed in [[https://www.arduino.cc/en/Guide/Libraries]]. Then, download and open the example sketch {{ :example-code-idoe-iot-lab.zip |example-code-idoe-iot-lab.ino}} with Arduino IDE.+Start by verifying the installation on your PC of the latest Arduino IDE. Unzip the Arduino {{ :arduino-lmic-mcci.zip |LMIC library}} and copy it to your sketchbook library folder as detailed in [[https://www.arduino.cc/en/Guide/Libraries]]. Then, download and open the example sketch {{ :example-code-idoe-iot-lab.zip |example-code-idoe-iot-lab.ino}} with Arduino IDE.
  
 Now you should configure your device with the same identifiers ''DEVEUI'' and ''APPKEY'' as in the backend: Now you should configure your device with the same identifiers ''DEVEUI'' and ''APPKEY'' as in the backend:
Line 85: Line 85:
  
 Now you are ready to compile the sketch and upload it to the LoRaWAN device. Connect the device to a USB port on your PC, choose the board type as presented in [[exploring_lora|Exploring LoRa lab]] and select the corresponding port. Compile and upload! Now you are ready to compile the sketch and upload it to the LoRaWAN device. Connect the device to a USB port on your PC, choose the board type as presented in [[exploring_lora|Exploring LoRa lab]] and select the corresponding port. Compile and upload!
 +
 +<WRAP center round todo 60%>
 +Debugging causes memory problems on Arduino One and duemilanove. Debug level should stay 0.
 +</WRAP>
  
 Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages. Open the serial monitor in the Arduino IDE at 115200 baud and analyse the debug messages.
Line 101: Line 105:
 </WRAP> </WRAP>
 ===== -. Applications ===== ===== -. Applications =====
 +
 +<WRAP center round todo 60%>
 +Prefer mqtt-fx and put user credentials
 +</WRAP>
 +
 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]]. The tool can be directly downloaded from this {{ :mqtt-spy-1.0.0.jar.zip |link}}. 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]]. The tool can be directly downloaded from this {{ :mqtt-spy-1.0.0.jar.zip |link}}.
  
-You can use mqtt-spy to debug the messages received from the LoRaWAN devices. 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''+You can use mqtt-spy to debug the messages received from the LoRaWAN devices. 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/device/DEVICE_EUI/rx''
  
 <WRAP left round help 100%> <WRAP left round help 100%>
Line 116: Line 125:
 </WRAP> </WRAP>
  
-If you need to send data to your device, you should publish an encoded message in the corresponding topic ''application/APPLICATION_ID/node/DEVICE_EUI/tx'' as follows:+If you need to send data to your device, you should publish an encoded message in the corresponding topic ''application/APPLICATION_ID/device/DEVICE_EUI/tx'' as follows:
  
 <code> <code>
Line 156: Line 165:
 ==== -. The Sensor Challenge ==== ==== -. The Sensor Challenge ====
 I can use different sensors to send data from the device: PIR, moisture, temperature, light, etc.  I can use different sensors to send data from the device: PIR, moisture, temperature, light, etc. 
 +<WRAP center round important 100%>
 +When connecting sensors, check the pin mapping for unused pins https://wiki.dragino.com/index.php?title=Lora_Shield
 +</WRAP>
  
  
exploring_lorawan.txt · Last modified: 2021/11/02 06:31 by samer