This article will help you:
Understand installation and connectivity requirements and data flow
Troubleshoot your Niagara JACE CSV integration
To view your current Niagara JACE CSV integration details and status, go to Settings on the left side menu, select Integrations, then select Niagara JACE CSV.
Overview
A Tridium Niagara JACE is a piece of controls hardware that sits on a Building Management System (BMS), Building Automation System (BAS), or Energy Management System (EMS) network and pushes real-time BACnet data to Atrius.
A Niagara JACE CSV integration is used when there is an existing Niagara AX system in place with BACnet points present to push data to Atrius. This integration is able to push a large number of points’ data to Atrius, depending on the setup of your BACnet system.
The BACnet compatible point(s) measures the resource and submits that value over BACnet to the Niagara AX controller (often a JACE). The Niagara system pushes that value and timestamp to Atrius via a CSV driver installed on the AX device. The interval of data, also known as resolution, is determined by the point.
Responsibilities
Customer Responsibilities | Customer Support Responsibilities |
BAS/BMS/EMS: Ensure BACnet system is properly calibrated and configured. | Configure Atrius: Open up a gateway to receive point data. |
Point configuration: Configure the points in the controls backend to send accumulated (also referred to as “totalized”) values to Atrius. | Provide useful tools: Collect, store, and display point data. |
Confirm connectivity: Confirm connectivity between point and controls system with correct BACnet IDs, values, etc. | Verify data mapping: Ensure the customer provided the correct JACE mapping with necessary point details. |
JACE installation: Ensure the JACE is installed correctly, has power, and has an ethernet connection. | JACE configuration: Program JACE to map correct BACnet points into CSV driver. |
Allow outbound communication: Confirm networking details with IT to allow JACE outbound communication to Atrius servers over the correct port. |
|
Troubleshooting
Review common troubleshooting steps that may restore communication between an offline Niagara JACE controller and Atrius.
📘 Troubleshoot your Niagara JACE integration
Open the interactive Decision Tree tool below to diagnose problems with your JACE integration, or scroll down the page for instructions and additional resources.
If all JACE points are offline
Physically reboot your JACE controller. Turn the unit off or disconnect the power cable from the power source for 5-7 minutes. Do not unplug the network cable. If you're using a Niagara Server in place of a JACE, you may need to restart the process(es) or reboot the server hosting the software.
Verify that the JACE controller has outbound connection to the IP range: 13.83.71.72/29 via http (port 80) or https (port 443). If there were any recent network/firewall changes, these may have impacted the communication between your JACE and Atrius.
If all JACE points are offline but confirmed online in BAS control system
Verify that the JACE controller has local connectivity with BAS controllers and/or points (Modbus TCP Port 502 and/or BACnet UDP Port 47808) and that no recent network changes have occurred.
Verify that no recent changes to the BAS control system have occurred. In some instances, BAS vendors will replace controllers or change static IDs that can interrupt communications between the BAS controller(s) and the JACE. Please contact Customer Support for assistance with re-mapping new device and/or point identifiers.
If a partial list of JACE points are offline
Verify that the individual offline metering hardware/devices are reporting expected values. To view a detailed list of offline points and locations, go to Settings > Integrations.
Verify that the individual metering hardware/devices are communicating with the BAS controller.
If any JACE points are flatlined
Verify that the individual metering hardware/devices are reporting expected values.
Additional resources
A Facilities or Controls point of contact would be able to determine if the controller has either lost power or lost network connectivity. The point of contact may also be able to locate the JACE controller and physically reboot the device, if necessary, and additionally schedule a BAS site visit if re-configuration is required with the local BAS controllers and/or metering hardware.
A Network or IT point of contact would be able to determine if the JACE controller is impacted by any recent network/firewall changes and or network hardware changes.
🚧 Forward this information to your points of contact
Please forward this information to any additional Facilities, Controls, Network, or IT points of contact at your organization for on-site support.
📘 Contact Customer Support
For additional questions regarding your integration with Atrius, please contact Customer Support.