Eaton BreakerVisu NZM-XMC-MDISP35-MOD Manual

Also see for BreakerVisu NZM-XMC-MDISP35-MOD: Manual Instruction leaflet Instruction leaflet Instruction leaflet

9 Importing 3rd party Modbus devices9.1 Device-specific bytesBreakerVisu 06/16 MN01210001Z-EN www.eaton.com 49▶ To delete a 3rd party device, first select it and then tap the DELETEDEVICE button.▶ To replace a 3rd party device, first delete it, then replace thecorresponding XML configuration file, and finally import the new device.If the import is completed successfully, you will then be able to connect anduse the corresponding 3rd party devices.If an error occurs during the import process, check the notification thatappears, correct the XML configuration file, and try to import the deviceagain.9.1 Device-specific bytesIt is important for all devices to have their own device-specific identificationdata.Two bytes, which are defined by their offset and value in the XMLconfiguration file, are used for device identification purposes:2205Pre-defined Eaton device types will be recognized before 3rd party devices.In other words, if the device-specific bytes match the bytes pre-defined byEaton, the device will be recognized as an Eaton device.9.2 Device-specific image fileAn image file can be assigned to every supported third-party device. Theimage file‘s name must have the following syntax: 3rdparty_X.bmp, where Xis the number of the corresponding device type. Moreover, the BMP filemust not exceed a size of 65 x 65 pixels. The image file needs to be stored inthe console‘s \InternalStorage\PlcPrg directory. The device-specific image willreplace the default file already found in the BreakerVisu console.9.3 XML configuration file contents￫ Tables 43 and 44 describe the contents of the XMLconfiguration file.￫ Section 15.4, “XML configuration for 3rd party devices”,page 68 provides two sample configuration files.