Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Home
  • Contact Us
English (US)
MX Spanish (Mexico)
CA French (Canada)
US English (US)
  • BACnet
    York BACnet
  • Controllers
    1204/3612 EC100 EC1000 EC2000 EDGE
  • GridPoint Software Platforms
    GridPoint Energy Manager (GEM) GridPoint Intelligence
  • Lighting
    LCA LCP Microlite Lighting Siemens Lighting Square D Lighting
  • Meters
    1204EX Meter 3612 Meter AcuRev Meter AcuVim Meter
  • Peripherals
    Dishwashers Door Switches Refrigeration Zone Heaters Duct Probes
  • Thermostats
    TS101 TS150 TS150W TS200
  • Home
  • BACnet
  • Process – BACnet – Confirm BACnet Controller Compatibility Before Integration

Process – BACnet – Confirm BACnet Controller Compatibility Before Integration

Written by Brian Matheron

Updated at November 2nd, 2026

Table of Contents

Purpose When this applies Procedure Step 1 – Gather equipment information Step 2 – Check the supported controller list Step 3 – Decide how to proceed Step 4 – Document the case Red flags during an active integration Supported BACnet controllers Suggested customer / vendor wording Baud Rate Policy Update (November 2026)

Purpose

Before any BACnet integration begins, Support must confirm that the HVAC unit's BACnet controller or card is one GridPoint currently supports. Not all BACnet-capable equipment works with the GridPoint EMS. Some controllers need specific boards, firmware, or configuration, and some are not supported yet.

When this applies

  • New installs or commissioning where HVAC will be controlled via BACnet
  • RTU replacements or HVAC upgrades at existing sites (new units often ship with newer controllers)
  • Any request to move a site from thermostat control to BACnet
  • Troubleshooting cases where BACnet equipment was recently replaced

Procedure

Step 1 – Gather equipment information

Before scheduling or starting any BACnet work, collect the following from the customer, vendor, or technician:

  • HVAC manufacturer and unit model number (nameplate photo preferred)
  • Controller / BACnet interface model (photo of the control board)
  • Install or replacement date of the unit
  • How the unit is currently controlled (thermostat, BACnet, other)

Tip: If the technician can't identify the controller, ask for a clear photo of the main control board and any add-on cards. Don't proceed on assumptions.

Step 2 – Check the supported controller list

Compare the controller against the Supported BACnet Controllers table below. Match the exact controller, not just the manufacturer. Two units from the same manufacturer can use completely different controllers.

Step 3 – Decide how to proceed

  • Supported: Proceed with the standard integration article for that manufacturer.
  • In development, not supported, or unknown: Stop. Do not begin integration or dispatch a technician for BACnet work.
    • Escalate to Support leadership with the equipment details and photos.
    • Engineering will confirm compatibility or provide a timeline.
    • Offer thermostat control as the fallback so the site keeps EMS control.

Step 4 – Document the case

  • Record the unit model, controller model, and compatibility decision in the case notes
  • Attach the nameplate and board photos
  • Note the control method used (BACnet or thermostat)

Red flags during an active integration

If any of these come up after work has started, pause and re-verify the controller before continuing to troubleshoot:

  • The board looks different from what our BACnet articles show
  • Setup requires a phone app, Bluetooth, or a tool we don't normally use
  • Points communicate only partially (for example, some units or points never come online)
  • Troubleshooting has gone past 60 minutes without progress

Rule: Partial communication after extended troubleshooting means verify the controller first, not keep troubleshooting.

Supported BACnet controllers

Manufacturer Controller / interface Status Notes
Trane ReliaTel with BACnet Communication Interface (BCI)  Supported Standard Trane BACnet integration.
Trane Symbio 700 (onboard BACnet MS/TP) Not Supported  
York/Johnson Controls Series 5, 10, 20 and 40 Supported See York BACnet articles (baud 19200, Adaptive Tune setting).
Carrier RTU Open Supported  
Carrier SystemVu Supported  
Lennox Prodigy Supported  

 

Suggested customer / vendor wording

Before we begin the BACnet integration, we need to confirm the controller installed in these units is compatible with GridPoint. Could you send a photo of the unit nameplate and the main control board? If the controller isn't currently supported, we can keep the site under GridPoint control using our thermostats while our engineering team reviews it.

 

Baud Rate Policy Update (November 2026)

  • New installations (GEM): All new GEM installations will be configured at 38400 baud by default.
  • Troubleshooting on site: When a technician is on site troubleshooting offline devices or communication issues, the MS/TP network should be updated to 38400 baud as part of the corrective work.
  • It will be vital to check that the proper Baud Rate is used both at the device and in GEM to ensure BACnet units function as intended.

Did you find this article helpful?

Yes
No

More Information

  • Equipment - BACnet - Carrier & York Setup with Single EC2000

See More On

unlabeled unnamed
Privacy Policy | Terms & Conditions

©2025 All Rights Reserved

Expand