The Molex CoreSync server includes a software BACnet gateway service that exposes the lighting groups as virtual BACnet devices and the lighting data as BACnet objects. This BACnet gateway follows standard BACnet/IP rules and requires proper configuration of the BACnet/IP communication settings to ensure a successful integration with the Metasys network engine.
From the CoreSync server, a person can log into the BACnet Configuration tool to configure or verify the BACnet settings including: Device ID, UDP Port Number, Local and Virtual Network Numbers, and BBMD. These settings are described in the following table.
| Setting | Description |
|---|---|
|
Device ID |
The starting BACnet instance number for all the virtual BACnet devices that represent the lighting groups configured within the CoreSync server. Set the Device ID to a value that will not conflict with other BACnet device IDs on the network or communication issues may occur. Default value is 5001 which may or may not be safe on the site’s network. Check with the site’s BACnet network expert to be sure. |
| UDP Port Number |
The UDP port restricts BACnet communications to devices that are also communicating on the same UDP port. This value must match the BACnet UDP port number set in the network engine you are integrating to or communication between devices will not occur. Default value is 47808 which is a common value on most BACnet networks, but check with the site’s BACnet network expert to be sure. |
| Local Network Number |
The BACnet network number that communicates with the network engine and the rest of the BACnet network. This value must match the BACnet network number set in the network engine you are integrating to. Default value is 1. The default network number of a network engine is 1001. Change one or both of these values so that they match. Check with the site’s BACnet network expert to identify the correct value. |
| Virtual Network Number |
The BACnet network number that communicates virtually with the lighting network internal to CoreSync. The BACnet gateway acts as a router to this virtual network. The Virtual Network Number must be unique amongst all the other BACnet network numbers in use across the network, or sporadic communication issues may occur. Note: If there are more than one Molex
BACnet gateways configured on the same or different CoreSync server,
the Virtual Network Numbers must be unique between them.
The default value is 2 and it is likely that you need to change it to ensure that it is unique. Check with the site’s BACnet network expert to be sure. |
| BBMD |
BACnet Broadcast Management Device (BBMD) is a BACnet feature that enables communications across IP subnets. Any BACnet device on the network may have the capability of being a BBMD for any particular IP subnet, and any IP subnet should have at most one BBMD. CAUTION When BBMDs are configured properly,
the BACnet network is extended across IP subnet boundaries so more
BACnet devices can be discovered and communicate. When BBMDs are NOT
configured properly, high BACnet traffic may result and slow down
the entire IP network. Metasys network engines perform the BBMD function automatically with other network engines. If the Molex CoreSync server is on an IP subnet that does not contain any Metasys network engines and no other BBMD devices are already functioning on the subnet, this BBMD feature will likely need to be configured and used in order to enable the Molex CoreSync Gateway and the network engine to communicate. Always check with the site’s BACnet network expert before enabling this feature. |
For complete instructions and a description of all the configuration options in the Molex BACnet Configuration Tool, refer to the BACnet Configuration Tool User Manual, available from Molex.