Map #
Read local object  named Analog Output 2
Write remote object any time local object has changed by  or when  seconds have elapsed with no change.
Otherwise write remote object unconditionally. In any event, when writing remote object, apply local object data as follows:
Apply scale:  and offset:  Then, using index  and priority  proceed to
Write property  encoded as data type
Write to instance # of object type  at device
Repeat this process at least no more than every  seconds.
Enable this map only when index object   is set to a value of
# Client Write Maps Enabled:
Quick Help

Map number simply tells you where you're at on the list of object maps. Click "next" and "prev" to scroll through the list. To advance directly to a specific map, enter the desired number in the "Map #" box, then click Update.

The local object data may be written periodically, or when it changes, or both. To send upon change (send on delta), check the first box and enter the amount by which the local object must change before being written to the remote device. To guarantee that the remote object will be written at least occasionally even if the data does not change, check the second box and enter some amount of time. This time period will be referred to as the "maximum quiet time".

Data from the local object may be manipulated before being written to the remote object. The local data is first multiplied by the scale factor. The offset is then added to it.

For the remote object to be written, enter the propert number, object instance and type, index if applicable (leave at 0 if not), and priority to use of the object being written is commandable. The names in the device list are defined in the Devices page.

The most commonly written property will be Present Value, which is property number 85. For other property codes, refer to the BACnet protocol specification or the User Guide for the Babel Buster Pro V230.

The repeat time may determine how often the remote object will be written. If send on delta and maximum quiet time are not checked above, clicking the "at least" button will establish a periodic update time. If send on delta is used and you wish to limit the network traffic in the event changes are frequent, click the "no more than" button and enter the minumum time that should elapse before another write to the remote device.

You have the option of enabling this map only when a selected object contains a given value. Any local object may be used as the index object. As the name implies, you can write different values to the remote object based on different maps as indexed by the index object.

Delete will remove the map number shown in the "Map #" box. Insert will insert a new map before the map number shown, and is used for placing maps between existing maps. It is not necessary to use Insert to add maps to the bottom of the list or to define any map presently having zero for a source object or "none" for remote type.

Selecting "none" for remote type effectively deletes the map even though it will still appear in the list until deleted. Unused maps at the end of the list will always show none as the type. If you wish to prevent these from being displayed, reduce the number of maps enabled.

The number of maps enabled simply limits the scope of map review so that you do not have to review a lot of unused maps. If the displayed maps are used up and you need more, increase the enabled number.