Page | 29
Resulting Device Object List:
Device
Instance
Number
Device Object MAC
Address
Device Object
Name
500
10.20.21.100:0xBAC0
System
Controller
501
100.21.20.1:0xBAC0
0-10VDC
502
100.21.20.2:0xBAC0
Banquet EF
503
100.21.20.3:0xBAC0
East Supply
504
100.21.20.4:0xBAC0
Fryer EF
505
100.21.20.5:0xBAC0
Grill EF
506
100.21.20.6:0xBAC0
Island EF
507
100.21.20.7:0xBAC0
West Supply
508
100.21.20.8:0xBAC0
HC-01
509
100.21.20.9:0xBAC0
HC-02
510
100.21.20.10:0xBAC0
HC-03
511
100.21.20.11:0xBAC0
HC-04
If, however, on your network you need to manually assign each Device Instance Number,
that option is also available. Each Exhaust Fan, Auxiliary Airflow, Hood Controller, Virtual
Input Module and Virtual Output Module in the system has a BACnet Device Instance
Number configuration option. When BACnet Auto Number is set to “Yes”, the system
ignores these configuration values for the Exhaust Fans, Auxiliary Airflows, Hood
Controllers, Virtual Input Modules and Virtual Output Modules and auto numbers these
devices. When BACnet Auto Number is set to “No”, the configured BACnet Device
Instance Number for each device is used. Note that these values will be used regardless of
collision; if all Exhaust Fans and Auxiliary Airflows in a system are configured to use
Device Instance Number 0, then that is how the system will operate. Take care to use
unique values when statically assigning the BACnet Device Instance Numbers.
Verifying BACnet Device Instance Numbers
When the system is in operation, there are several ways you can verify the Device
Instance Numbers that were assigned. Depending on your building configuration and
your operator workstation, the simplest method may be to send a Who-Is request to the
expected Device Instance Numbers. If the system is on your network and properly
configured, then your operator workstation should discover all the devices. If this did not
work, you can verify from the Touchpad which Device Instance Numbers were assigned to
all devices.
