You might think of this small but important section of the screen as the "shortcuts section" if you have more than one AddMe and want to duplicate a configuration. It is also very useful for recreating a configuration if a device is replaced.

Read Config from File: Click to bring up the Windows file dialog which lets you select a previously saved configuration file. The file read will "load" all of the object configuration properties. A config file looks like this.

Write Config to File: Click to bring up the Windows file dialog which lets you enter a file name to be written. The file name should have a *.xml suffix. Any existing file by the same name will be overwritten. All object configuration properties will be stored in the file in XML format.

Read NV Data from File: The PL/i programming environment includes 512 bytes of EEPROM for program use. You can create an XML file that stores the contents read from EEPROM using the "Read Nonvolatile Data" Program Request. This can then be used to initialize another device with the same data.

Write NV Data to File: The PL/i program EEPROM area may be initialized from a file. Click this button to read the file into the configuration tool buffer, then use the "Write Nonvolatile Data" Program Request to actually send it to the device via BACnet. A nonvolatile data file looks like this.

Read All from Device: Click to begin the sequence of property reads to retrieve all configuration information from the device.

Write All to Device: Click to begin the sequence of property writes to send all configuration information to the device.

The log box at the bottom of the screen will show the following at the end of the read-all (write-all) sequence, and started with "Config I/O #1 done". If you get "unknown property" or "bad data type" at I/O #14, check to see that you have the right device model selected at the top right of the screen. (The first 14 objects are identical. After that, an incorrect model selection will generate errors.)