Rule number simply tells you where you're at on the list of register maps. Click "next" and "prev" to scroll
through the list. To advance directly to a specific map, enter the desired number in the "Showing" box,
then click Update.
Rules entered on this page only write data to remote devices. Go to the Client Read Map to read data from
those devices. The full parameter set is different for read versus write.
An abbreviated version of a list of rules is shown on this page. Any of the parameters shown may be
changed here and registered by clicking the Update button. To view and/or modify the complete set of
parameters, click on the map number in the left most column.
Data from the local object given will be multiplied by the scale factor before being written. For each
remote register to be written, enter the register type, format, number, and location (device). The names
in the device list are defined in the Devices page. The name is optional and used only for display purposes.
Selecting "none" for remote type effectively deletes the rule even though it will still appear in the list until
deleted. Unused rules 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).
6. Configuring BB2-7010 as a Modbus TCP Client
file:///C:/AAA_CSI/Literature/2015 User Guides/BB2-7010/BB2-7010 ...
5 of 8
10/16/2015 12:32 PM