Mircom Flex-Net Phase II, Application Manual

Page: 15 / 132

15
BACnet
4.1 Flex-Net Configuration for BACnet
Note that the Flex-Net system is treated as a BACnet field panel and not a workstation. It does
not poll or query other BACnet field panels. Instead it replies to requests from workstations or
sends out notifications of new events.
Before BACnet services can be used with the Flex-Net system, the system must be configured
correctly. Network settings must first be set up as explained in 2.1 Wiring/IP Settings. The rest
of the configuration is performed using the configurator. In the configurator select the node
from the Job Details tree on the left to display the Network Node Info on the right.
From the Network Node Info window pane on the right select Run BACnet Services and Run
TCP Services to enable BACnet. If Run BACnet Services is greyed out then a CodeMeter key
must be used to activate a license using the Import BACnet Services button. Enter a Device ID
and a Base ID in the fields that become available. The value for the Base ID is where object ID
values will start from. To ensure that the value entered for the Device ID is outside the range of
possible object IDs enter a value lower than that of the Base ID. The Device ID defines the ID
of a BACnet device meaning the FACP. Refer to the figure below.
As an example, the following points describe how addresses are assigned to addressable
devices by the configurator:
• The BACnet protocol specifies (2
22
- 1) or 4,194,303 available address IDs.
• Out of these, each FACP node reserves 24,000 IDs.
• Out of these 24,000 IDs, 13,000 are reserved for physical devices and 11,000 are for
statuses and switches.
• Node numbering starts from 0.
• Each node can support 7 CPUs (0-6) with 1,600 IDs available per CPU.
• Each CPU can support 4 loops (0-3) with 400 IDs available per loop.
• The method for identifying fire device address IDs is described by the following:
Base ID + (Node# x 24000) + (CPU# x 1600) + (Loop# x 400) + Fire Device ID