π 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.
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
ortime.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.
Go to Home > Software Center > Download Software Center
Install the Software Center application
Step 2: Download Required Software from Software Center
Open the Software Center installed app
Navigate to the EC-Net platform tab
Select the following applications:
EC-Net 4 Pro and Supervisor
Atrius Building Insights Niagara Connector
Right-click on the software installed β Open download location
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.
Create an Admin User Account at https://buildingos.com/users/
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
Navigate to Settings > Integrations > Add an integration
Select gateway type:
EC-Net 4 (for Distech System Integrators)
N4 (for non-Distech installers)
Click the dropdown β Set up gateway
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:
Close Niagara Workbench (EC-Net 4 Pro application)
For Supervisor installations only: Stop the Niagara service
Search "Services" in Windows taskbar
Locate Niagara service β Click Stop
Installation:
Run Atrius Building Insights Niagara Connector Setup.exe
Follow installation prompts
Verify module files install to correct directories
Commissioning a Station on JACE or Supervisor
For Existing Niagara Controllers
Navigate to JACE Platform > Software Manager
Add dcBuildingOS modules (3 modules total)
Highlight modules β Install β Commit
Proceed to "Enabling the BACnet Driver" section
For New Station Setup
Create new station:
Tools > New Station
Select New Controller Station template
Enter Station Name β Set password
Select Open it in user home β Finish and open the bog file in your user home
Add required drivers:
Expand Palette tool (bottom left)
Drag BACnet Network from palette into Drivers section
Drag Atrius Network (from dcBuildingOS palette) into Drivers
Save the configuration
For New JACE Commissioning
Initial connection:
Locate credential card shipped with JACE (default: username
admin
, passwordadmin
for JACE 9000)β οΈ These are default credentials that should be changed
Connect computer to JACE via Ethernet
File > Open > Open Platform
Enter default IP (typically
192.168.1.140
) β OK
Platform configuration:
Complete Change Platform Defaults Wizard:
Configure system passphrase
Create Platform Account
Navigate to Platform Administrator > Commissioning
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)
Connect to the Supervisor Host - File > Open > Open Platform
Enter "localhost" β Enter PC credentials β OK
Platform > Station Copier
Select desired station β Copy to right pane (localhost)
Station Transfer Wizard: Enter station name β Next β Finish
Application Director β Confirm Status = Running
Double-click station β Enter credentials
Enabling the BACnet Driver
Open station in Niagara Workbench
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:
Right-click BACnetNetwork β Discover
Locate target devices (power meters, etc.)
Drag into Database or select β Add
Expand device β Navigate to Points β Double-click β Discover
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:
Palette: History > Extensions > Numeric or Boolean Interval
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
Search "dcBuildingOS" in Palette
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
Navigate to Station > Config > Drivers > Atrius Network > Atrius Client
Enter credentials in BuildingInsightsClient:
Client ID
Client Secret
Gateway ID
Save
Enable and Test
Right-click Atrius Client β Actions > Enable
Test: Right-click Atrius Network β Actions > Ping
Successful ping confirms connectivity
Update units:
Station > Config > Drivers > Atrius Network > Settings > Units
Right-click Units β Actions > Refresh
All organization buildings should appear
Building Setup
Import Existing Buildings
Station > Config > Atrius Network > Organization
Discover β View all buildings in your Atrius org
Drag and drop buildings to Database or select β Add
Create New Buildings
Station > Config > Drivers > Atrius Network > Organization β New
Enter:
Post Code
Country Code
Address
Building Name
Save β Highlight building β Push (creates in cloud)
Point Configuration
Discover Points
Open Point Manager: Station > Config > Drivers > Atrius Network > Organization > [Building]
Query History to discover available histories
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 CHANGEResource 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
Push (bottom right) β Creates point in Atrius
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:
Resource exhaustion
Check Station > Resource Monitor > CPU Usage (75%+ is risky)
Review Station > Resource Manager for licensing limits
Communication loss
Station lost connection to sensor/meter
Station lost internet connection
Verify in History > [Trend Log] > Views > AX History Table
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:
Verify credentials are correct
Check firewall/proxy settings
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.