40
6.4.4 XTPro HMI-Based Implementation
A representative implementation based upon a stand-alone HMI client is detailed in Figure 27. In this
scenario, the client application is developed by using tools provided by the HMI manufacturer, and is
hosted independently of the actual server device.
6.4.5 XTPro Supported Commands
For a summary of XTPro commands, refer to Table 17.
Table 17: Supported XTPro Commands
Command
Supported
Notes
noop
Yes
-
vzn
Yes
Supports XTPro specification version 1
id
Yes
-
read_data
Yes
“reference” is the inverter’s parameter (e.g. “01.01” for Output
frequency monitor), while “data_value” is a 16-bit hexadecimal
value (e.g. “1F4” for a decimal value of 500)
write_data
Yes
load_file
Yes
The absolute file path must start with a forward slash ‘/’
store_file
Yes
reinit
No
Reinitializes only the configurable drivers and services (does not
perform a complete device soft reboot)
auth
Yes
Authorization is not required
cov
Yes
COV notification messages are sent every 200ms
Notes
•
Two simultaneous XTPro connections are available.
Server
Device
Content is loaded
onto HMI device
2
XML socket (port 843)
<xreq>
<reMd_dMtM>
<ref>Pr_2<Cref>
<CreMd_dMtM>
<Cxreq>
HMI content
executes and
establishes
XML socket
3
XML socket (port 843)
<xresp>
<reMd_dMtM>
<ref>Pr_2<Cref>
<vMl>123<CvMl>
:
<Cxresp>
6
trogrammer authors
HMI (client) content
1
Client initiates XTtro
requests
4
Server responds to
client’s requests
5
XT
tr
o
Se
rv
er
Figure 27: HMI-Based Implementation