7
Configuration
Configuring the Fire network
52
Building Technologies
A6V10854379_a_en
CPS Fire Safety
25.01.2019
–
Destination and Netmask, addressing a subnet (recommended) or a single
address according to IP addressing rules. For example, Destination =
192.168.2.0 and Netmask = 255.255.255.0 define any address in the range
192.168.2.1 through 254. Instead, Destination = 192.168.2.10 and Netmask
= 255.255.255.0 define the single IP address 192.168.2.10.
–
IP address of the Gateway (GAP) that can provide connectivity to the
destination subnet.
TIP: Use the Ping button in the Tools tab to check that the IP connectivity is
properly established between the NK823x and the routing gateway.
–
If multiple routes are available for the same destination, use the Metric field
to indicate the cost (for example, the number of devices along the network
path) of each route: the higher the number (cost), the lower the
corresponding priority.
4. Repeat the steps above to add as many routes as required.
Use the Routing between ETH1 and ETH2 check box (available when both
Ethernet ports are used) to enable a general routing across the two NK823x lines.
Note that ETH1/ETH2 routing is not required for supporting the NK823x
communications across the two Ethernet lines, for example, between a
management station network on ETH1 and a subsystem network on ETH2.
Instead, the NK823x-controlled routing is required to enable the IP connectivity for
other units operating on the two separated subnets. Furthermore, by enabling the
NK823x firewall function, this field is handled automatically.
Configuring the NK823x BACnet/IP connectivity
1. Select the Protocols node.
2. In the toolbar on the left, select the BACnet Client Protocol icon (violet).
The BACnet client protocol node is created under the Protocols folder.
By default, the new node is named “BACnet Client Protocol”.
3. Select the new BACnet Client Protocol node.
4. Drag-and-drop the selection to the appropriate Ethernet node.
A link node is created under the Ethernet node.
5. Select the BACnet Client Protocol link under the Ethernet node.
6. Select the Node tab.
7. In the form on the right pane, configure the BACnet parameters:
–
UDP Port (must match the UDP port configuration configured in the fire
GAP unit; default value is 47808 or BAC0 hex).
–
Device Identifier (must match one of the valid client identifiers configured
in the fire system. Note that NK823x units do not support BACnet IDs
greater than 65533).
–
Virtual Network Number (the default value 1 may need to be changed if
there is already a foreign BACnet network with virtual network number 1 in
place. In any case, remember to keep the NK823x and FS20/FS720
configuration consistent).
–
Process Id (in general, the default value is 1 and must not be changed).
8. If the NK823x acts as BACnet Foreign Device, enable the Foreign Device
check box and configure the BBMD router settings:
–
Remote BBMD IP address
