Skip to main content

EC-Net Facilities / Niagara 4

Updated this week

πŸ‘ This article will help you:

  • Understand installation and connectivity requirements and data flow

  • Complete full integration setup from prerequisites to data validation

  • Configure and troubleshoot your EC-Net/Niagara integration

Overview

The customer must procure a JACE or a software application called EC-Net Facilities (previously EC-Net 4). This device or software application will be installed on the customer’s Ethernet network and will communicate with the local control system using the Niagara-supported open protocol. The JACE or EC-Net Facilities will then transmit timestamped resource use data to Atrius servers at regular intervals.

Download
Download

Hardware & Network Requirements

Supported platforms:

  • JACE controllers (TITAN series, EC-BOS-8, EC-BOS-9)

  • Supervisor (Windows 8+, Linux)

Installation Requirements

  • Standard 110V power outlet

  • RJ-45 ethernet port

  • DIN rail mountable (for hardware devices)

Network Configuration

The JACE/EC-Net Facilities requires network access for:

BACnet/IP Communication

  • Local network communication over 47808/udp to control system devices

  • Connection options:

    • Option 1: All communications over eth0 (eth1 disabled)

    • Option 2: Isolated WAN/LAN connections via eth0 and eth1

Outbound HTTPS

  • Internet communication over 443/tcp to Atrius cloud servers

  • Destination: https://api.buildingos.com

Inbound Fox/HTTP

  • Internet communication over 1911/tcp, 3011/tcp, and 80/tcp to be provided via externally accessible IP address or VPN

  • Required for: initial setup, additional integrations, point reconfigurations, and troubleshooting

NTP Time Synchronization

  • Internet communication over 37/tcp to NIST time server

  • Recommended: pool.ntp.org or time.nist.gov

  • Alternative: Local network NTP server

Control System Requirements

  • JACE/EC-Net Facilities functions as an automation client

  • All devices must be properly configured per manufacturer specifications

  • Complete the Atrius Data Points Workbook provided by your Project Manager

Prerequisites

Software Requirements

Niagara Version: 4.4.73.24 or higher
​

Step 1: Download and Install the Distech Software Center

Distech Software Center is supported on Windows 10 and Windows 11. A Distech account may be required to access the download page.

  1. Go to Home > Software Center > Download Software Center

  2. Install the Software Center application

Step 2: Download Required Software from Software Center

  1. Open the Software Center installed app

  2. Navigate to the EC-Net platform tab

  3. Select the following applications:

    • EC-Net 4 Pro and Supervisor

    • Atrius Building Insights Niagara Connector

  4. Right-click on the software installed β†’ Open download location

  5. Go through installer steps

Required module files:

These modules will be installed on your designated Niagara platform after install and setup of the Atrius Building Insights Niagara Connector. See the Install Atrius Niagara Connector section below.

  • dcBuildingOS-rt.jar

  • dcBuildingOS-wb.jar

  • dcBuildingOSLexiconFr-rt.jar

Atrius Account Setup

Step 1: Create User Account

Avoid using your personal Atrius account to create API clients. Instead, use a dedicated user for the API to prevent disruptions if a personal user account is deactivated or deleted.

  1. Create an Admin User Account at https://buildingos.com/users/

  2. Add an API Client:

    • Navigate to Settings > Developer API > Add API Client

    • This dedicated client is for API integration only

    • Assign the recently created user

    • Record the Client ID and Client Secret

Step 2: Create a Gateway

  1. Navigate to Settings > Integrations > Add an integration

  2. Select gateway type:

    • EC-Net 4 (for Distech System Integrators)

    • N4 (for non-Distech installers)

  3. Click the dropdown β†’ Set up gateway

  4. Record the Gateway Number from the URL (e.g., https://buildingos.com/gateways/12345)

Save these credentials for later:

  • Gateway Number

  • API Client ID

  • API Client Secret

Install Atrius Niagara Connector

Before installation:

  1. Close Niagara Workbench (EC-Net 4 Pro application)

  2. For Supervisor installations only: Stop the Niagara service

    • Search "Services" in Windows taskbar

    • Locate Niagara service β†’ Click Stop

Installation:

  1. Run Atrius Building Insights Niagara Connector Setup.exe

  2. Follow installation prompts

  3. Verify module files install to correct directories

Commissioning a Station on JACE or Supervisor

For Existing Niagara Controllers

  1. Navigate to JACE Platform > Software Manager

  2. Add dcBuildingOS modules (3 modules total)

  3. Highlight modules β†’ Install β†’ Commit

  4. Proceed to "Enabling the BACnet Driver" section

For New Station Setup

Create new station:

  1. Tools > New Station

  2. Select New Controller Station template

  3. Enter Station Name β†’ Set password

  4. Select Open it in user home β†’ Finish and open the bog file in your user home

Add required drivers:

  1. Expand Palette tool (bottom left)

  2. Drag BACnet Network from palette into Drivers section

  3. Drag Atrius Network (from dcBuildingOS palette) into Drivers

  4. Save the configuration

For New JACE Commissioning

Initial connection:

  1. Locate credential card shipped with JACE (default: username admin, password admin for JACE 9000)

    • ⚠️ These are default credentials that should be changed

  2. Connect computer to JACE via Ethernet

  3. File > Open > Open Platform

  4. Enter default IP (typically 192.168.1.140) β†’ OK

Platform configuration:

  1. Complete Change Platform Defaults Wizard:

    • Configure system passphrase

    • Create Platform Account

  2. Navigate to Platform Administrator > Commissioning

  3. Follow Commissioning Wizard:

    • Accept licenses

    • Set hostname, timezone, admin password

    • Enable Niagara Daemon, File Transfer, and Station services

    • Install dcBuildingOS and BACnet modules

    • Select the recently created station OR create station with name and password

Network configuration:

  • Work with your network administrator to obtain:

    • Fixed IP address

    • Gateway IP

    • Subnet Mask

    • DNS server

  • Configure NIC Interface settings accordingly

  • Reboot JACE if prompted (may take up to 20 minutes)

For Supervisor (PC/Server)

  1. Connect to the Supervisor Host - File > Open > Open Platform

  2. Enter "localhost" β†’ Enter PC credentials β†’ OK

  3. Platform > Station Copier

  4. Select desired station β†’ Copy to right pane (localhost)

  5. Station Transfer Wizard: Enter station name β†’ Next β†’ Finish

  6. Application Director β†’ Confirm Status = Running

  7. Double-click station β†’ Enter credentials

Enabling the BACnet Driver

  1. Open station in Niagara Workbench

  2. Config > Drivers β†’ Right-click β†’ Add New β†’ BACnetNetwork

Configure properties:

  • Device ID: Unique on BACnet network (e.g., 999)

  • Network Number: Match facility's BACnet numbering (e.g., 1)

  • IP Port: Typically 47808 (BAC0 hex)

  • Enable port and save

Discover devices:

  1. Right-click BACnetNetwork β†’ Discover

  2. Locate target devices (power meters, etc.)

  3. Drag into Database or select β†’ Add

  4. Expand device β†’ Navigate to Points β†’ Double-click β†’ Discover

  5. Drag desired points to Database or select β†’ Add

Configuring History Extensions

⚠️ Important: The Atrius driver reads history trends, NOT current values. History Extensions must be configured to push data up to Atrius.

Add history to points:

  1. Palette: History > Extensions > Numeric or Boolean Interval

  2. Drag History Extension onto a BACnet/Modbus point

Configure:

  • History Name: Must be unique

    • We recommend using B-formatting: %parent.parent.parent.name%/%parent.name%

  • Interval: 15 minutes (recommended)

  • Enabled: True

  • Save

Verify:

  • Check Nav Panel > History for the new trend log

  • This confirms the JACE is collecting and storing data

Enabling the Atrius Niagara Connector

Add Atrius Network

  1. Search "dcBuildingOS" in Palette

  2. If you do not see the Atrius Network in your Driver properties, drag and drop Atrius Network from the palette to Station > Config > Drivers in the AX Property sheet

Configure Atrius Client

  1. Navigate to Station > Config > Drivers > Atrius Network > Atrius Client

  2. Enter credentials in BuildingInsightsClient:

    • Client ID

    • Client Secret

    • Gateway ID

  3. Save

Enable and Test

  1. Right-click Atrius Client β†’ Actions > Enable

  2. Test: Right-click Atrius Network β†’ Actions > Ping

  3. Successful ping confirms connectivity

Update units:

  1. Station > Config > Drivers > Atrius Network > Settings > Units

  2. Right-click Units β†’ Actions > Refresh

  3. All organization buildings should appear

Building Setup

Import Existing Buildings

  1. Station > Config > Atrius Network > Organization

  2. Discover β†’ View all buildings in your Atrius org

  3. Drag and drop buildings to Database or select β†’ Add

Create New Buildings

  1. Station > Config > Drivers > Atrius Network > Organization β†’ New

  2. Enter:

    • Post Code

    • Country Code

    • Address

    • Building Name

  3. Save β†’ Highlight building β†’ Push (creates in cloud)

Point Configuration

Discover Points

  1. Open Point Manager: Station > Config > Drivers > Atrius Network > Organization > [Building]

  2. Query History to discover available histories

  3. Drag points to Database or Add

Configure Point Properties

Required fields before pushing to Atrius:

  • Resource Type

  • Scope

  • Reading Type

  • Source Unit

  • Display Unit

Example: Electric meter point

  • Atrius Display Name: Descriptive name

  • Name: Atrius Vendor Point ID
    ⚠️ Unique ID - DO NOT CHANGE

  • Resource Type: Electric

  • Scope: Sub meter

  • Reading Type:

    • KWH = Totalizer

    • KW = Instantaneous

  • Source Unit: From point facet

  • Display Unit: KW (typical for electric)

Push and Enable

  1. Push (bottom right) β†’ Creates point in Atrius

  2. Enable (bottom right) β†’ Begins data streaming

Validate

Navigate to Building > Points page in Atrius to verify:

  • Points appear

  • Data is flowing

  • Values are accurate

Health Monitoring & Alarms

Configure alarm settings: Station > Config > Drivers > AtriusNetwork > Atrius Client > Health

Recommended settings:

  • Inhibit Offline Alarm When Unacked: True

  • Delay For Fault Alarms: 15 minutes

  • Nb Timeouts For Offline Alarm: 3

View alarms: Station > Config > Services > Alarm Service

Time Synchronization

⚠️ Important: Proper time sync is essential for accurate data collection.

Recommended NTP configuration:

  • Enabled: True

  • NTP Host Mode: Client

  • Sync Time At Boot: True

  • Use Local Clock as Backup: False

  • NTP Server: pool.ntp.org

  • Peer Mode: Server

  • Preferred: True

  • Burst: True

Alternative NTP servers: time.nist.gov, time.google.com, ntp.ubuntu.com

Troubleshooting

Points Going Offline

Common causes:

  1. Resource exhaustion

    • Check Station > Resource Monitor > CPU Usage (75%+ is risky)

    • Review Station > Resource Manager for licensing limits

  2. Communication loss

    • Station lost connection to sensor/meter

    • Station lost internet connection

    • Verify in History > [Trend Log] > Views > AX History Table

  3. Configuration issues

    • Atrius Client credentials missing/incorrect

    • Trend logs disabled after device reconnection

    • Outdated driver software

Resolution:

  • Verify license capacity before adding devices

  • Maintain time synchronization

  • Reboot if necessary: Platform Administration > Reboot Station

Connection Issues

If Ping fails or token doesn't generate:

  1. Verify credentials are correct

  2. Check firewall/proxy settings

  3. Test DNS configuration:

    • Command line: ping www.buildingos.com

    • Note the public IP

    • Navigate to /Services/PlatformServices/TcpIpService

    • Under correct NIC card β†’ DNS settings

    • Add DNS servers: 8.8.8.8 and 8.8.4.4

    • Save and retest

Missing Points

  • Review Point Manager for fault/stale states

  • Verify all required properties are configured

  • Confirm history extensions are enabled

Push Errors

  • Use Apply Template or Set button to resolve validation issues

  • Review error messages for specific field requirements

Best Practices

βœ… Pre-installation:

  • Verify license capacity before connecting devices

  • Ensure reliable internet connectivity

  • Configure time synchronization first

βœ… Point configuration:

  • Use descriptive Atrius Display Names

  • Maintain consistent naming conventions

  • Use 15-minute intervals for history

  • Prefer Interval trends over COV trends

βœ… Performance:

  • Monitor CPU usage regularly (keep below 75%)

  • Review resource limits periodically

  • Don't exceed licensed device capacity

βœ… Data quality:

  • Validate accuracy in Atrius after enabling points

  • Monitor alarm status regularly

  • Maintain time synchronization

Checking Software Versions

Supervisor Atrius N4 Driver: Tools > Module Info β†’ Find dcBuildingOS module

JACE Atrius EC-Net 4 Driver: JACE IP > Platform > Software Manager β†’ Find dcBuildingOS module

Niagara Version: Station > Station Summary > Summary Properties β†’ Niagara version field


Additional Resources

Video tutorial

πŸ“˜ Contact Customer Support

For any questions/issues regarding your EC-Net device, connector, or supervisor please contact Distech Support.

For any questions regarding data quality or the EC-Net / Niagara integrations in Atrius, please contact Atrius Customer Support.

Did this answer your question?