LoRaWAN MODBUS MASTER - Guide utilisateur / User guide version V1.0.0
4. DESCRIPTION OF THE FRAMES
4.1. Uplink frame
The uplink frames of the product to the network have a different size depending of the transmitted data.
4.1.1 Fixed bytes
FR
The first two bytes of the frame are systematically dedicated to indicate the frame code and the status as presented below:
0
1
Code
Statut
4.1.1.01
Byte code
EN
This byte contains the code associated with the frame to facilitate its decoding by the data system.
4.1.1.02
Status byte
The status byte is broken down in the following way:
Alarm Status
No Error
Configuration
done
Low bat
HW Error
Modbus
config error
Slave read
error
Details of the fields:
•
Frame counter: Frame counter, it increments at each transmission and allows the user to see quickly if a frame has been lost. It counts from
0 to 7 before looping back.
•
HW: This bit is set to 1 when a hardware error has occurred, for example a writing problem in the EEPROM, a reading problem on the ADC,
etc. The product must be returned to the service dept.
•
Confg: bit at 1 if a confguration was carried out during the last downlink frame, otherwise 0. This bit returns to 0 as from the next frame
•
Config error : bit set to 1 to indicate that the application configuration is wrong. For example, the total number of Modbus registers is more
than 5 in the periodic setup.
•
Read error : bit set to 1 to indicate a Modbus read error. For example, a slave that does not respond to the master request.
E.g.:
A value of the status byte equal to 0xB1 (= 10110001 in binary) gives:
•
Bit 7 at 5 = 101 = 0x05 i.e. a frame counter at 5
•
Bit 4 at 0 = 10001 (binary) ie a read error on a slave and the validation of the configuration.
2
3
Bit 7
Bit 6
Frame Counter
0x00 to 0x07
4
5
6
PAYLOAD
Bit 5
Bit 4
Read error
Config error
0
0
0
0
0
1
7
8
Bit 3
Bit 2
HW
Low Bat
0
0
0
0
0
0
0
1
1
0
0
0
9
10
Bit 1
Bit 0
Config
0
0
0
1
1
0
0
0
0
0
0
0
Page
64
of 80