Manual Modbus v1.1
Manual Modbus v1.1
The RTU will allow the reading of incoming values (PQ) and line values through Modbus-
TCP. The enabling of this service will be configurable.
There will be Modbus functions for reading “input registers” (function 4) to obtain
measurement data, and reading “coils” (function 1) to obtain the status of the alarms.
The register addresses used for the information of the different cards will always be the
same, that is, they will have an identical mapping all of them. Access to the data of an
specific card will be performed by using the "unit id" field defined in the Modbus TCP
protocol. In this way, the variables associated with the RTU (connection) will be available
with the unit id 100, the variables from cards, with the “unit id” equal to the line address
configured in their encoders, or the 99 in case of being VTN.
For Modbus functionality to work properly, the configuration of a repeated line number
is NOT allowed among different cards.
Configuration
For enabling Modbus, the following parameters must be configured:
• modbusEnabled. Set to Y.
• modbusPort. Listening port for RTU modbus server. Default: 502.
• IP address.
• Mask for network configuration.
• Default gateway (not strictly needed if Modbus client is in the same LAN as the
RTU).
Apart from that, the following points must be considered:
• The Modbus client will need to connect to the IP and port configured in the
parameters listed above.
• The minimal refresh time for PQ data (unit id 100) is 15 seconds. The recommended
refresh time is 60 seconds.
• The minimal refresh time for meter data is 15 seconds. However, it is not
recommended to interrogate multiple cards at the same time or with a period
lower than 60 seconds, as it implies communication through the shared RS485
bus and could cause the delay of other RTU tasks.
• For the system to start measuring, it is needed that a correct date and time is set
on it. It can be done manually, but it is recommended that an NTP server is
configured to ensure a correct and permanent date availability.
• As stated above, it is not allowed that multiple cards share their line address.
• In a VTN is installed, no other card can be configured with line equal to 99.
Modbus Map
The next Modbus Map lists all the measurements that are possible to read through
Modbus, along with their Modbus functions, register addresses, unit id, data type and
corresponding units.
37 h1_1 cV uint16
38 h1_2 0,01% uint16
39 h1_3 0,01% uint16
40 h1_4 0,01% uint16
41 h1_5 0,01% uint16
42 h1_6 0,01% uint16
43 h1_7 0,01% uint16
44 h1_8 0,01% uint16
45 h1_9 0,01% uint16
46 h1_10 0,01% uint16
47 h1_11 0,01% uint16
48 h1_12 0,01% uint16
49 h1_13 0,01% uint16
50 h1_14 0,01% uint16
51 h1_15 0,01% uint16
52 h1_16 0,01% uint16
53 h1_17 0,01% uint16
54 h1_18 0,01% uint16
55 h1_19 0,01% uint16
56 h1_20 0,01% uint16
57 h1_21 0,01% uint16
58 h1_22 0,01% uint16
59 h1_23 0,01% uint16
60 h1_24 0,01% uint16
61 h1_25 0,01% uint16
62 THD1 0,01% uint16
63 h2_1 cV uint16
64 h2_2 0,01% uint16
65 h2_3 0,01% uint16
66 h2_4 0,01% uint16
67 h2_5 0,01% uint16
68 h2_6 0,01% uint16
69 h2_7 0,01% uint16
70 h2_8 0,01% uint16
71 h2_9 0,01% uint16
72 h2_10 0,01% uint16
73 h2_11 0,01% uint16
74 h2_12 0,01% uint16