All Articles Problem/Solution

New Equipment Won't Talk to Your BMS — Now What?

Troubleshooting and solutions when new HVAC equipment won't integrate.

December 19, 2025 10 min read Controls NYC
New Equipment Won't Talk to Your BMS — Now What?

You've installed new HVAC equipment with "BACnet communication" and tried to connect it to your BMS. It's not working. The BMS doesn't see the equipment, or it sees it but can't read data, or the data doesn't make sense.

"This is frustrating but common. Here's how to troubleshoot and resolve it."

Step 1: Verify Physical Connectivity

IP
For BACnet/IP
  • ☐ Equipment connected? (check link lights)
  • ☐ Can you ping the IP address?
  • ☐ Same network/VLAN as BMS?
  • ☐ Firewalls blocking traffic?
MB
For Modbus
  • ☐ Serial wiring correct (A/B, +/-)?
  • ☐ Termination correct?
  • ☐ Baud rates match?
  • ☐ Settings (parity, stop bits) match?

Step 2: Verify Equipment Configuration

BACnet Settings to Check
  • Device instance: Must be unique on the network
  • Network number: Must match your BACnet config
  • BBMD settings: Required if crossing subnets
  • Port number: Typically 47808 (0xBAC0)

Step 3: Test Communication Independently

Use diagnostic tools to test communication separately from your BMS:

  • BACnet: Use Yabe or CAS BACnet Explorer to discover the device
  • Modbus: Use ModPoll or QModMaster to read registers
Key Insight
If visible in the diagnostic tool but not in BMS → the problem is BMS configuration.
If not visible in the diagnostic tool → the problem is equipment or network.

Step 4: Check for Common Issues

Common Problems

Discovery Problems: BACnet broadcasts may be blocked; foreign device registration needed for cross-subnet

Data Not Readable: Incorrect object references, access permissions, or points not implemented

Data Doesn't Make Sense: Scaling issues, data type mismatch, or wrong register addresses

Step 5: Get Manufacturer Help

If basic troubleshooting doesn't resolve the issue:

  • Contact equipment manufacturer's technical support
  • Provide specific error messages or symptoms
  • Ask for protocol documentation verification
  • Request factory support call if needed

Step 6: Alternative Approaches

Protocol Gateways

Dedicated devices that translate between protocols — may work when direct communication fails.

Hardwired Integration

Traditional analog/digital I/O always works. More labor but guaranteed compatibility.

Different Protocol

If BACnet isn't working, try Modbus. Check for optional communication cards.

When to Call for Help

If you've worked through these steps and still have problems, it's time for professional help. At Controls NYC, we troubleshoot integration problems regularly.

Contact us when you need expert integration support.

Ready to Discuss Your Building?

Whether you're evaluating an upgrade, dealing with a failing system, or just want a second opinion — we're happy to talk through your options.

Schedule a Free Consultation

Continue Reading