IP & Port configuration

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 LoRaWAN 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.

...

µWiotys will use the following port :

LoRaWAN devices

The device must be added in µWiotys with the following parameters:

• Device EUI (DevEUI)

• Device Activation Type (OTAA/ABP)

• Application EUI (AppEUI)

• Application key Key (AppKey)

• Manufacturer model reference (see list device µWiotys Compatible devices)

• Modbus Slave number device_protocol_id [1 to 200] (for Modbus only )

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

Once the configuration is loaded on the Gateway, all devices and corresponding Modbus tables parameters will initialise be initialized 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 registers (see Modbus table)

Type of value used

To read float, see an exemple at FAQ.

Byte order representation

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.

BACnet

µWiotys supports BACnet protocol (from version 3.4.0).

...

Adding a sensor in Bacnet

There are no specific operation to do to add a new sensor for BACnet. You can use the Online support interface (https://app.uwiotys.com/index.php/device/list ) to create your infrastructure.

Only Analog input (AI) and Analog values (AV) are currently supported.

...

Analog values are used to send information to the sensors. Only Classe C sensor are currently supported for this mode.

...

...

.

...

HTTP

...

data server

µwiotys µ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 the web interface.

...

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 or using the data logger CSV output.

MQTT

CSV Data logger

µWiotys provide also 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.data loger locally on the gateway.