From firmware v4.x,Offline configuration had been introduced. Now user could configure a BACRouter without device on hand, then export configuration to a file. When commissioning on the field, user just need to import previously exported file, “Save&Reboot” to take effect the configuration.
From v4.04,The object definitions for Modbus gateway could be import/export as CSV format. User could effectively setup object to Modbus address mapping In batches with Excel/WPS/Libreoffice, then import it to WebUI for detailed modify.
Offline configure on our website (IE will not work now)
Download and extract it to disk, open index.html by your web browser (Because IE/Edge doesn’t support Local Storage for file:// URL, the user library for binary text and most used engineering unit will not be kept after leaving the web page)
There are 3 types of configuration file:
BACRouter Configuration File
This type of configuration file keeps all settings in BACRouter. If the firmware version of exporting one is same to importing one, WebUI should not complain of the configuration file.
Modbus Master Configuration File
This type of configuration file keeps setting under the scope of Modbus master. When importing it, collision detecting logic based on current mapping mode will check every enabled slave in this master, if collision is found, the slave will be disabled.
If the master is RTU/ASCII type, it may also be disabled if there are contention for RS485 port.
With these problem, WebUI will prompt user to re-check configuration.
Modbus Slave Configuration File
This type of configuration file keeps setting under the scope of Modbus slave. When importing it, if collision detecting logic based on current mapping mode found problem, the slave will be disabled.
It is allowed to import TCP salve configuration file in RTU/ASCII master, and vice versa, but the slave may be disabled if Modbus parameter setting do not work.
With these problem, WebUI will prompt user to re-check configuration.