Description
There are a number of items that may prevent the CopperCube from functioning correctly on a JCI site.
It is important to ensure the following situations are resolved appropriately so trend logs and objects can be archived and sent to Kaizen reliably.
BACnet vs N2
Not all Johnson equipment is BACnet.Though Johnson Controls supports and produces a range of BACnet products, many will be using the “Johnson Controls N2” protocol for use with Metasys. The CopperCube, however, speaks BACnet and will not be able to interface with the N2 device.
Process to Fix
There must be a device used to translate the N2 protocol to BACnet.Typically, this device is an NAE (Network Automation Engine) which will allow BACnet data to be passed to the CopperCube.
BACnet Routing
By default, NAE devices will not have BACnet routing enabled.BACnet routing allows the BAS data to be passed to the CopperCube in a protocol it understands. Without this setting enabled the Cube will see the devices but no trend logs or objects.
Process to Fix
To enable BACnet routing, set the “Routing Mode” attribute on the “Network” tab of the “Device object” view to “Enable”.BACnet routing will now occur as data is passed from the IP side of the device to the MS/TP side.
BACnet Device ID
In a Johnson Controls system, each device can have the same identifier and by default, this value will be 500.
In true BACnet, each device must have a unique device object identifier.
Process to Fix
The “BACnet Object Identifier” can be edited in the “Focus” view after selecting “Advanced” during the NAE installation.
Additional information
For more information on JCI NAE devices and using them in a BACnet setting, you may refer to the following document. The “Troubleshooting” section provides a number of symptoms of improper BACnet configuration as well as how to resolve them.https://cgproducts.johnsoncontrols.com/met_pdf/1201531.pdf?ref=binfind.com/web
