Eaton BreakerVisu NZM-XMC-MDISP35-MOD, Manual

Page: 51 / 88

9 Importing 3rd party Modbus devices
9.1 Device-specific bytes
BreakerVisu 06/16 MN01210001Z-EN www.eaton.com
49
▶ To delete a 3rd party device, first select it and then tap the DELETE
DEVICE button.
▶ To replace a 3rd party device, first delete it, then replace the
corresponding XML configuration file, and finally import the new device.
If the import is completed successfully, you will then be able to connect and
use the corresponding 3rd party devices.
If an error occurs during the import process, check the notification that
appears, correct the XML configuration file, and try to import the device
again.
9.1 Device-specific bytes
It is important for all devices to have their own device-specific identification
data.
Two bytes, which are defined by their offset and value in the XML
configuration file, are used for device identification purposes:
<device_specific_bytes>
<LENGTH>2</LENGTH>
<OFFSET>2</OFFSET>
<FIRST_BYTE_VALUE>0</FIRST_BYTE_VALUE>
<SECOND_BYTE_VALUE>5</SECOND_BYTE_VALUE>
</device_specific_bytes>
Pre-defined Eaton device types will be recognized before 3rd party devices.
In other words, if the device-specific bytes match the bytes pre-defined by
Eaton, the device will be recognized as an Eaton device.
9.2 Device-specific image file
An image file can be assigned to every supported third-party device. The
image file‘s name must have the following syntax: 3
rdparty_X.bmp
, where X
is the number of the corresponding device type. Moreover, the BMP file
must not exceed a size of 65 x 65 pixels. The image file needs to be stored in
the console‘s \
InternalStorage\PlcPrg
directory. The device-specific image will
replace the default file already found in the BreakerVisu console.
9.3 XML configuration file contents
￫
Tables 43 and 44 describe the contents of the XML
configuration file.
￫ Section 15.4, “XML con fi guration for 3rd party devices”,
page 68 provides two sample configuration files.