The BACnet IP Client allows this device to interact with other BACnet IP devices. Any other client may read and write any objects in the local device. However, for the local device to read and write object properties in remote devices, it is necessary to make that remote device known in the BACnet IP Client device table, and to set up a map that results in reading or writing that remote object. Once data is read from a remote device and placed into a local object for holding, any of the action rules such as event thresholds may be applied to the data obtained from the remote device. This effectively means one AddMe III or AddMe Jr may function as an alarm monitoring or scheduling device for multiple BACnet IP devices.

To identify a remote device, you need only know its device instance. Enter the device instance along with a local name that will be referenced in the maps that follow. Once the remote device has replied to a "who is", its IP address will be indicated here.

Reading data from a remote BACnet IP device is invoked periodically by setting up a read map as illustrated below. Data is periodically read from the remote object indicated, and that data is placed in the local object indicated.

Writing remote objects via BACnet IP is invoked by a write map as illustrated here. Data is periodically (or upon sufficient delta) taken from the local object indicated, and written to the remote object indicated.