Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
styledefault
typelist
printablefalse

...

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.

...

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

  • Device EUI (DevEUI)

  • Application Type (OTAA/ABP)

  • Application EUI (AppEUI)

  • Application key (AppKey)

  • 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 LoRa parameters are managed by Wi6labs.

...

µWiotys supports write single register (function code 6) only for several register registers (see Modbus table ) Warning, writing

Note

Writing register will trigger LoRaWAN downlink

...

. Please kindly wait ~10s 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.

Note that our µWiotys Modbus registers are formatted with Big-Endian Representation & Zero-based numbering

Type of value used

Data type

register size

description

range

U16

1

unsigned integer

[ 0 : 65 535 ]

U32

2

unsigned integer word swapping

[ 0 : 4 294 967 295 ]

U64

4

unsigned integer word swapping

[ 0 : 18 446 744 073 709 551 615 ]

S16

1

signed integer

[ -32 768 : +32 767 ]

S32

2

signed integer word swapping

[ -2 147 483 648 : +2 147 483 647 ]

S64

4

signed integer word swapping

[ -9 223 372 036 854 775 808 : +9 223 372 036 854 775 807 ]

floatFloat (F64/F32)

2

Floating point byte swapping non-swap (abcd)

NA

To read float, see an exemple at FAQ.

Byte order representation

Swap Mode

Source 4-Byte

Target Bytes

 Modbus Register Order

N/A

[ a b c d ]

[ a b ][ c d ]

=> Wi6labs format

Expand
titleDetail of Byte order and Big-Endian representation

Swap Mode

Source 4-Byte

Target Bytes

 

N/A

[ a b c d ]

[ a b ][ c d ]

=> Wi6labs format

Swap Byte

[ a b c d ]

[ b a ][ d c ]

 

Swap Word

[ a b c d ]

[ c d ][ a b ]

Swap Byte and Word

[ a b c d ]

[ d c ][ b a ]

=> Representation of Float < v3.5.0


Info

1 word/register Modbus = 2 bytes (16 bits)

(MSB)

Big-Endian Modbus Representation

(LSB)

Byte

7

6

5

4

3

2

1

0

Modbus Register Order

a

b

c

d

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

...

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.

...

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

...