Tridium JACE 8000

Building integration controller

JACE 8000 aggregates field devices in a Niagara station. Edge can read selected points that the station exposes over BACnet/IP or Modbus TCP. The station owner supplies the exported point list and configures the server; the controller has no universal energy-meter register map.

Tridium JACE 8000
  • BACnet/IP
  • Modbus TCP

Building integration controller

Compatibility

Compatible through BACnet/IP or Modbus TCP

Edge can read a configured Niagara Modbus TCP server over the site network. The BACnet/IP path requires an Edge build containing its BACnet client. Tridium includes both server driver roles in its standard driver offering, subject to the installed licence and capacity.

A JACE reading a meter is not automatically a server for that meter. Its Niagara station must deliberately expose the selected points. Obtain the station owner’s access, export list and driver licence details before commissioning.

Connect it with

Route into Edge

When the Niagara station exposes the required measurements as BACnet objects

  • BACnet
  • Edge
  • Platforms
Building integration controller
Interface
Gateway
Edge
Output
JACE 8000JACE 8000 BACnet/IP server
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge BACnet client
Customer platformMQTT · API · files
BACnet/IP
Protected Ethernet
Runs locally
Optional onward data
Use an Edge build containing the BACnet/IP client. Use the station’s BACnet device instance and exported object identifiers. Keep the measurement units and point status alongside each value; BACnet object numbers are assigned by the station, not by the JACE hardware model. The customer-platform output is optional; Edge remains the local system of record.

When the station owner supplies a fixed export register map

  • Modbus
  • Edge
  • Platforms
Building integration controller
Interface
Gateway
Edge
Output
JACE 8000JACE 8000 Modbus TCP server
Protected EthernetSegmented LAN
ZGW-20 GatewayHosts Edge locally
EpiSensor EdgeEdge Modbus client
Customer platformMQTT · API · files
Modbus TCP
Protected Ethernet
Runs locally
Optional onward data
Read the station’s agreed register map with its configured port, unit ID, function, data type and scaling. Preserve that map as part of the station backup so a replacement controller does not silently change the meaning of the readings. The customer-platform output is optional; Edge remains the local system of record.

Models

Download
ModelsInterfaceRoute into Edge
JACE 8000Two 10/100 Ethernet ports; two isolated RS-485 ports; Niagara 4.1 or laterUse a configured BACnet/IP or Modbus TCP server on the installed station.
JACE 8000 non-Wi-FiSame controller form and function without the Wi-Fi moduleUse wired Ethernet; a Wi-Fi access point is not required for the integration.
JACE 9000Different hardware generation, requiring Niagara 4.13 or laterReview the 9000 hardware, installed Niagara version and station export configuration separately.

Specifications

JACE 8000 is an integration controller, rather than a direct energy meter. Its two isolated RS-485 ports connect field networks and its two Ethernet ports provide IP connectivity. Optional I/O and communications modules expand the hardware. Driver inclusion does not remove Niagara device and point capacity limits.12

Processor and memory
1 GHz ARM Cortex-A8; 1 GB DDR3; removable microSD with 2 GB user storage1
Supply
24 VAC rated at least 24 VA, or 24 VDC rated at least 1 A1
Serial ports
Two isolated RS-485 ports with selectable bias and termination1
Environment
-20 to +60 °C; 5–95% relative humidity, non-condensing; panel or 35 mm DIN-rail mounting1
Licensing
Installed drivers need a valid licence and sufficient global capacity; optional drivers and software maintenance are separate considerations2

Interface

Documented measurements and integration boundaries for JACE 8000.

  • Exported electrical energy and power readings from connected meters, with the original engineering units.
  • Temperatures, equipment run states and other building points selected by the Niagara station owner.
  • BACnet object type and instance, Present_Value, Units and Status_Flags where supported by the exported object.
  • For Modbus, the station-specific register address, function, data type, word order and scale for each exported point.
  • A freshness or health point that distinguishes a field-device failure from a healthy JACE network connection.

Assessment

JACE 8000 running a licensed Niagara 4 station with deliberately configured read-only exports. Measurement accuracy belongs to the connected field instruments.

InteroperabilitySupported with conditions
BACnet/IP client/server and Modbus TCP master/slave are documented included drivers; station exports and licence capacity determine what can be read.2
AccuracyNot applicable
This controller aggregates points. Measurement range and accuracy are properties of the upstream meter or sensor, not the JACE chassis.1
SecuritySupported with conditions
The hardware specifies secure boot. The selected plain BACnet/IP or Modbus TCP connection still needs a controlled network and explicit read-only point exposure.12
ReliabilitySupported with conditions
The manufacturer documents the 24 V supply requirements, batteryless design, removable storage and USB backup/restore support. Protect the supply and retain a compatible station backup.1
RuggednessWell supported
Published panel/DIN-rail mounting, -20 to +60 °C operation and non-condensing humidity limits define the building-controls installation envelope.1
ScalabilitySupported with conditions
Multiple field networks and standard drivers support aggregation; licensed global capacity must cover the configured devices and points.23
LifecycleSupported with conditions
Tridium publishes backup/restore and software-maintenance requirements, with a separate migration path to JACE 9000. Record the station version and licence before replacement.14

Setup

Verify one exported BACnet measurement

This check uses a real exported point selected from the station handover. There is no fixed JACE object instance or register address to copy from a hardware datasheet.

Target
The configured BACnet device instance at the agreed JACE IP endpoint
Object
The exact object type and instance supplied by the station owner; do not assume analogue input 1
Read
Present_Value, Units and Status_Flags where supported; no WriteProperty operation
Reference
The corresponding Niagara point and, where accessible, the source meter display at the same time
Freshness
A changing value or source timestamp/health indication; a reachable controller can still expose a stale upstream value

Acceptance: Accept only when identity, unit, value and source health agree. A successful device discovery proves network reachability, not that the station has exported the required measurements.

  1. Get the station handover

    Ask the building-system owner for the JACE model, Niagara version, station backup, authorised engineering access and a point list. Identify the upstream meter or sensor behind each required value, its units and normal update interval.

  2. Choose the server interface

    Confirm that BACnet/IP server or Modbus TCP slave functionality is licensed and configured in this station. Check available device and point capacity. A working downstream client connection to a meter does not by itself expose that meter to Edge.

  3. Agree the export contract

    For BACnet, record device instance, object type, object instance, property and units. For Modbus, obtain the complete station-specific register table, address convention, function, length, data type, byte/word order and scale. Select read-only measurements and include point health.

  4. Connect one point in Edge

    Use the agreed IP endpoint on a permitted site network. In the BACnet client, discover the intended device and select its exported objects; in the Modbus client, add the supplied register definition. Start with one changing measurement rather than importing every station point.

  5. Prove freshness and preserve the mapping

    Compare the source device, Niagara point and Edge value at the same time. Ask the station owner to demonstrate how a stale or disconnected source is represented, using a controlled test. Save the export map with the station backup and repeat the check after a station change or controller replacement.

Common questions

Can I import a universal JACE 8000 Modbus template?
No universal register list exists for a programmable Niagara station. Obtain the map configured by the station owner. A reusable template is useful after that mapping has been agreed and kept consistent across sites.23
Does connecting Edge replace the existing BMS?
A read-only export can sit alongside the existing Niagara station and its controls. The station owner chooses what to expose; preserve the existing control logic and field-network ownership.12
Is a Niagara licence needed?
The JACE must have the relevant driver licensed and enough capacity. Tridium’s included-driver list names BACnet IP client/server and Modbus TCP master/slave, but the licence and capacity of the installed station remain the deciding evidence.2
Is JACE 9000 the same hardware?
No. JACE 9000 is a newer controller with a quad-core processor and increased memory and storage. Its Niagara version requirements and migration process are separate from this JACE 8000 guide.4

Sources

  1. JACE 8000 controller datasheet, 2024-0028 (opens in a new tab) (PDF) Tridium
  2. Niagara included drivers and licence requirements, 2024-0007 (opens in a new tab) (PDF) Tridium
  3. JACE 8000 frequently asked questions, 2023-0021 (opens in a new tab) (PDF) Tridium
  4. JACE 8000 and JACE 9000 controller family (opens in a new tab) Tridium

Further reading

Product names and trademarks belong to their owners. Publication does not imply endorsement or a commercial relationship.