Configuration interfaces

Two interfaces are available to customize µWiotys.

• FTP interface for:

  • Management of the device fleet

  • Configuration of outputs

  • Support

• Web Interface for:

  • Network configuration

  • Lora Downlink management

  • Support

Gateway

The Gateway needs a dedicated IP address on the same VLAN as the Modbus automate. It can be set up as DHCP or static IP.
The default configuration is static IP:

• address: 192.168.1.100

• netmask: 255.255.255.0

• gateway: 192.168.1.1

The Gateway should be synchronized to a NTP server in order to have valid timestamps of the Lora payload.
The default NTP servers configured are 0.pool.ntp.org and 1.pool.ntp.org, however this won't be valid if the Gateway doesn't have internet access.

You can modify NTP configuration using Web interface Administration > Gateway

µWiotys will use the following port :

LoRaWAN devices

The device must be declared in µWiotys with following parameters:

• Device EUI

• Application Type (OTAA/ABP)

• Application EUI

• Application key

• Manufacturer model reference (see list device)

• Modbus Slave number [1 to 200]

Only class A and C devices are supported. OTAA configuration is the default configuration. All advanced Lora parameters are managed by Wi6labs.

See FTP configuration for LoRaWAN device provisioning.

Once the configuration is loaded on the Gateway, all devices and corresponding Modbus tables will initialise after reboot.

Output Data

Modbus

The modbus starts on the VLAN IP address with the standard modbus port 502. Each device will be seen by the controller as an individual slave, available slave ID are 1 to 200.

µWiotys can be requested by several controllers, however keep in mind that it is useless to pull the registers too often. The LoRaWAN devices will update the registers approximately between 1 hour and 1 day depending on their configuration and type.

µWiotys supports read holding register (function code 3)

µWiotys supports write single register (function code 6) only for several register (see Modbus table ) Warning, writing register will trigger LoRaWAN downlink command, therefore it is best to have a few second of delay between each command in order to avoid radio collision.

Common table

All slaves share a common table with these informations:

• DevEUI

• Reference ID

• Last timestamp

Measurement table

The Measurement table is specific to each device type (Temperature, Industrial,...) without any differences between manufacturer. The data specific to each device type (temperature, voltage,...) will only be available after the first Lora payload is received and will be updated with each new payload.

All the register information is defined in modbus dictionary.

Type of value used

To read float, see an exemple at FAQ.

HTTP REST data server

µwiotys provide an http rest output. This output is configurable by FTP (see Output configuration). An HTTP request will be sent for each frame received in µWiotys, your server must respond with 200 OK.
The json sent will contain informations of the common table and the measured value.

{
  "RSSI": -22,
  "SF": 12,
  "SNR": 9,
  "deveui": "0000000000000008",
  "device_battery_percent": 99,
  "error": "",
  "id_reference": 78,
  "payload": "048ea5942c000044444444",
  "temperature_0": 199,
  "temperature_1": 5119,
  "timestamp_uplink": 1709051995,
  "uplink_fcnt": 1,
  "version": 30300
}   

If your server miss the request, all the data sent can be retrieve using the FTP in /uwiotys/log/uwiotys_functionnal.log ou using the data logger CSV output.

Data logger

µWiotys provide a CSV output. This output is configurable by FTP (see output-configuration).

You can retrieve the CSV files in the FTP under /uwiotys/log/$END_DEVICE_ID/. Each sensor has its own folder with its own data.