Introduction

The LORIOT cloud is a powerful, secure and easy to use cloud for LoRa network. The LORIX One gateway is pre-installed and pre-configured to start a LORIOT client application at boot time. 

Basic usage and configuration

The configuration is very simple if you want to use it, simply do the following steps:

  1. Create a free account on LORIOT
  2. Add a new gateway and select the LORIX One as type
  3. Enter the MAC address located under your LORIX One and the geographical address where it will be located
  4. Once your account created and the gateway registered, power on the LORIX One or restart it using the reset button
  5. If all is going well, you should see a green tip on the Status box in the LORIOT web interface under your new LORIX One registered gateway, that's all

Since the clouds-manager script is configured to use the LORIOT application, you can stop, start or get its status using this script as explained in the Clouds manager page.

Advanced usage and configuration

Prerequisites

If you want to use directly the LORIOT init script without using the clouds-manager one, be sure there is no other cloud running by stopping it before using the Clouds manager script with stop argument.

Init script

The LORIOT specific init script is /etc/init.d/loriot-gw and can be used as follow:

Usage: /etc/init.d/loriot-gw {start|stop|restart|force-reload|status}
CODE

Application directory

The LORIOT directory which contains the binary is located under /opt/lorix/clouds/loriot and contains the binary loriot-gw.

Debugging the client

To debug the configuration and get the log output, you can directly start the LORIOT client application in foreground mode and keep the terminal open to get the output log.

$ cd /opt/lorix/clouds/loriot
$ sudo ./loriot-gw -f
CODE

 The log output will looks as follow:

sama5d4-lorix-one:/opt/lorix/clouds/loriot$ sudo ./loriot-gw -f
 INFO: LORIOT.io Gateway Version 1.0.1
 INFO: Acquired EUI XX-XX-XX-FF-FF-XX-XX-XX from interface eth0
 INFO: Connecting to gateway configuration server ... 
 CFG: HTTP response HTTP/1.1 200 OK
 CFG: Timestamp Sun, 22 Oct 2017 16:04:33 GMT
 CFG: Content-type application/json; charset=utf-8
 INFO: Parsing configuration file ... 
 INFO: 5 configuration parameters found
BOARD: running PUBLIC network, clock fed from radio #1
RADIO: radio 0 enabled, SX1257, center frequency 867500000, RSSI offset -164.0, TX enabled
RADIO: radio 1 enabled, SX1257, center frequency 868500000, RSSI offset -164.0, TX disabled
 INFO: LoRa Multi-SF channel 0 >> Radio 1, IF -400000 Hz, 125 kHz BW Enabled
 INFO: LoRa Multi-SF channel 1 >> Radio 1, IF -200000 Hz, 125 kHz BW Enabled
 INFO: LoRa Multi-SF channel 2 >> Radio 1, IF 0 Hz, 125 kHz BW Enabled
 INFO: LoRa Multi-SF channel 3 >> Radio 0, IF -400000 Hz, 125 kHz BW Enabled
 INFO: LoRa Multi-SF channel 4 >> Radio 0, IF -200000 Hz, 125 kHz BW Enabled
 INFO: LoRa Multi-SF channel 5 >> Radio 0, IF 0 Hz, 125 kHz BW Enabled
 INFO: LoRa Multi-SF channel 6 >> Radio 0, IF 200000 Hz, 125 kHz BW Enabled
 INFO: LoRa Multi-SF channel 7 >> Radio 0, IF 400000 Hz, 125 kHz BW Enabled
 INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7
 INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
 INFO: Connecting to gateway update server ... 
 CFG: HTTP response HTTP/1.1 400 Bad Request
ERROR: Invalid response from gateway server
ERROR: Coudn't contact update server
 INFO: Gateway HAL Version: 4.0.0;
 INFO: Starting LoRa Concentrator
 INFO: Concentrator started, daemonizing ...
 NWK: Connecting to network server ... 
 NWK: HTTP response HTTP/1.1 101 Switching Protocols
 NWK: Connection to network server established.

 The cloud application and the log output will be available as long as you keep this terminal open. You can stop it when you want by using the CTRL+C command to send a kill signal to the application.

When the debugging is done, you can simply start the LORIOT application using the normal way with the Clouds manager script.