7 Visualisation
The module has an internal memory for storing the content of the visualization in the
form of a website.
The site can be built in HTML + CSS. Data for visualization is available through the AJAX
mechanism.
7.1
The configuration of the Modbus points
The definition of groups of MODBUS points is included in the file POINTS.XML.
Sample content for Modbus RTU:
<
group
>
<
id
>node
_
<
/id
>
<
id_start
>
5
</
id_start
>
<
len
>
3
</
len
>
<
protocol
>
RTU
</
protocol
>
<
dev_addr
>
1
</
dev_addr
>
<
cmd
>
MB_MULTIHOLD
</
cmd
>
<
address
>
4000
</
address
>
<
access
>
rw
</
access
>
<
pool
>
50
</
pool
>
</
group
>
•
<group> the group description,
•
<id> defines the name of the point group,
•
<id_start> defines the start number of the point group numbering,
•
<len> determines the number of points in the group,
•
<protocol> specifies the access protocol to the point
◦
RTU – Modbus RTU via RS485,
◦
TCP – Modbus TCP via the LAN port,
•
<dev_addr> specifies the Modbus device number (for TCP it is always 1),
•
<cmd> ustawia komendę Modbus:
◦
MB_HOLD – Holding Registers
◦
MB_INPUT – Input Registers
◦
MB_COIL – Coil
◦
MB_MULTIHOLD – Holding Registers
•
<address> the Modbus address,
•
<access> access (r – read, w – write, rw – read and write).
Additional parameters are required for the MODBUS TCP protocol:
•
<ip_addr> IP address Modbus device
•
<ip_port> port of the MODBUS device (no tag sets port no. 502).
After each change in the POINTS.xml, or CONFIG.xml file, it is necessary to
reset the device for the changes to be updated.
User manual
μSCADA
Page
12
of
15
[B03]