User guide

BB2-7040 User Guide – Rev. 1.2 Page 20
Selecting "none" for remote device 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.
Local Object is internally a coded number consisting of BACnet object type multiplied by 1000, then added to the object
number starting from #1. These are translated into abbreviations that are easy to interpret on the web page as follows:
AI n = Analog Input #n
AO n = Analog Output #n
AV n = Analog Value #n
BI n = Binary Input #n
BO n = Binary Output #n
BV n = Binary Value #n
MI n = Multi-state Input #n
MO n = Multi-state Output #n
MV n = Multi-state Value #n
Object numbers start at #1. The maximum available number varies by object type, and these limits may be found on
the System Capacities link from the home/index page (click graphic at top).
Clicking the map number in the first column of the tabular map list gets you to this view. Rule 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 check 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, enter a
time value in minutes for periodic write.
Data from the local object may be manipulated before being written to the remote register. The local data is first
multiplied by the scale factor. The offset is then added to it. The data is then converted to integer/binary in preparation