wikiroute

networking recipes

User Tools

Site Tools


esib_iot_challenge

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
esib_iot_challenge [2017/05/17 17:29] – [2. Backend] sameresib_iot_challenge [2017/05/17 17:42] – [3. Devices] samer
Line 25: Line 25:
 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 (https://212.98.XX.XX:8080).
  
-[{{ :app-loraserver.png?direct&400 | Figure 5. Loraserver web interface}}]+[{{ :app-loraserver.png?direct&400 | Figure 2. Loraserver web interface}}]
  
 Start by choosing the application named ''NTRE-1617'' to create a new node. You should provide the following information: Start by choosing the application named ''NTRE-1617'' to create a new node. You should provide the following information:
Line 46: Line 46:
 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 [[simple_lora_prototype|Simple Prototype of LoRa Communications]].  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 [[simple_lora_prototype|Simple Prototype of LoRa Communications]]. 
  
-Start by verifying the installation on your PC of the latest Arduino IDE and place the Arduino LMIC library in the corresponding folder. +Start by verifying the installation on your PC of the latest Arduino IDE. Drop the Arduino LMIC library in the corresponding folder. These tools are provided at the beginning of the challenge
  
 <WRAP left round help 100%> <WRAP left round help 100%>
-  * Give the characteristics of the Arduino you are using: number of pins, type of pins, memory sizes, etc.+  * Give the characteristics of the Arduino you are using: model, number of pins, type of pins, memory sizes, etc.
   * Give the main characteristics of the LoRa shield from Dragino (www.dragino.com).   * Give the main characteristics of the LoRa shield from Dragino (www.dragino.com).
   * What type of Antenna are you using? Explain the corresponding characteristics.    * What type of Antenna are you using? Explain the corresponding characteristics. 
 </WRAP> </WRAP>
  
 +Download the example sketch and open it with Arduino IDE. Now you should configure your device with the same identifiers as in the backend. 
  
-Download the example sketchopen it with Arduino IDE and compile it.+<WRAP center round tip 100%> 
 +Note that the device and application identifiers should be in little endian format. The application key is in big endian format. For example,  
 +''0xCA, 0xDE, 0xE2, 0xAF, 0x1C, 0xDE, 0xAD, 0x0B'' 
 +</WRAP> 
 + 
 + 
 +<code c++> 
 +static const u1_t PROGMEM APPEUI[8]= { }; 
 +void os_getArtEui (u1_t* buf) { memcpy_P(buf, APPEUI, 8);} 
 + 
 +// This should also be in little endian format, see above. 
 +static const u1_t PROGMEM DEVEUI[8]= { }; 
 +void os_getDevEui (u1_t* buf) { memcpy_P(buf, DEVEUI, 8);} 
 + 
 +static const u1_t PROGMEM APPKEY[16] = { }; 
 +void os_getDevKey (u1_t* buf) {  memcpy_P(buf, APPKEY, 16);} 
 +</code>
    
 You can download the following sketch {{ :test-loraserver-comb-loraserver-dragino.zip |}} and modify it according to your preferences. Below you can find somme commented extracts of the sketch. You can download the following sketch {{ :test-loraserver-comb-loraserver-dragino.zip |}} and modify it according to your preferences. Below you can find somme commented extracts of the sketch.
Line 112: Line 129:
   * Security   * Security
 </WRAP> </WRAP>
- 
 ===== -. Applications ===== ===== -. Applications =====
 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]]. 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'' 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''
esib_iot_challenge.txt · Last modified: 2021/08/28 09:53 by samer