The success of the read test carried out in the previous tutorial "Modbus register read test" validates the following parameters :
Serial link: Register to be searched:
- baud rate: 19200 - Register address: 19843 or 0x4D83
- Parity: None (N) - Number of words: 2
- Bits stop: 1 - type: holding (0)
- Slave address: 1
To configure a Modbus sensor, you need:
- That the sensor is connected to a power supply between 6-36V DC
- Access to IoT configurator maintenance mode (PC or Android phone + connection cables)
General configuration:
- Product mode: PRODUCTION (the product is in operation)
- Period for sending periodic frame No.1 = 360 (360*10 secs = 3600sec i.e. 1 hour)
The sensor is in "activated" mode, sending periodic frame 1 every hour.
Configuration Modbus:
- Baud rate: 19200
- Parity: None (N)
- Bits stop: 1
- External power supply configuration: NA
The serial link parameters are identical to those defined by the previous read test.
Reading period 1:
- Slave address: 1
- Address of first register: 19843
- Registration names: 2
- Type of register: 0
- Number of the associated periodic frame: Periodic frame 4
The parameters for read period 1 are identical to those defined by the previous read test.
All you must do is associate this register reading with one of the 6 periodic frames available on the Modbus. Each of these periodic frames has its own frame name:
- Frame 0x44 is frame 0
- Frame 0x5F is frame 1
- Frame 0x60 is frame 2
- Frame 0x61 is frame 3
- Frame 0x62 is frame 4
- Frame 0x63 is frame 5
The product will send a periodic frame 0x62 every hour with the value of register 19843 (Total active energy: Ea+) in U32 format coded in hexadecimal.
Exemple : 0x6260000000ED
Several read periods can be associated with a periodic frame within the limit of the bytes available, i.e. a total of 49 bytes of data.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article