![Eaton BreakerVisu NZM-XMC-MDISP35-MOD Manual Download Page 52](http://html1.mh-extra.com/html/eaton/breakervisu-nzm-xmc-mdisp35-mod/breakervisu-nzm-xmc-mdisp35-mod_manual_3727397052.webp)
9 Importing 3rd party Modbus devices
9.3 XML configuration file contents
50
BreakerVisu
06/16 MN01210001Z-EN
www.eaton.com
Table 43: XML configuration file contents
Parameter
Subparameters
Description
Notes
Device designation
Description of the AUX TYPE
device
Device family
Description of the AUX TYPE
device
Device-specific
words
Up to two consecutive words can
be used for recognizing device
types from other manufacturers.
Length
No device-specific words
should be read via Modbus
RTU
Offset
Modbus RTU offset of the first
device-specific word.
The offset starts from 1; if the
documentation for your device
uses a zero-based offset, make
sure to add 1 to the parameter.
Value of first byte
The expected value of the first
device-specific word
Value of second
byte
The expected value of the
second device-specific word.
If both the first and second (if
defined) values match the
device type, the type will be
recognized.
Do not use this parameter if
using a single byte for device
type recognition purposes would
be enough.
Group parameters
Device data is read from the
device in defined data blocks
(groups). Up to four groups can
be used.
If fewer than four groups are
used for the device, the groups
will still retain their structure in
the XML file. Their specific
length and offset need to be set
to 0.
Length
No bytes are read via Modbus
RTU in the defined group.
Use a 0 for groups that are not
used
Offset
Modbus RTU offset for the first
byte. The offset starts from 1.
If the documentation for your
device uses a zero-based
offset, make sure to add 1 to
the parameter.
Use a 0 for groups that are not
used.
Mod_fc
The Modbus RTU function
code is used to read the group
data.
Please consult your device
documentation to find the value
that needs to be set here.
Summary of Contents for BreakerVisu NZM-XMC-MDISP35-MOD
Page 4: ...2...