Troubleshooting Discovery

Onboard's Edge Software can connect to the IP devices in your building communicating over BACnet or Modbus (supported templates only) protocols. Successful discovery ensures the Edge Node can read metadata, and begin collecting live telemetry. Occasionally, you may see incomplete results, stalled discoveries, or missing devices..

This guide outlines the most common issues and how to resolve them.

BACnet

Status stuck at NEW or IN_Progress

• If discovery does not progress, Confirm the Edge Node is Online
  • On the Deployments page verify that the deployment shows Online
• If its Offline, please check that the Edge Node VM is running and has internet connectivity on-site.

Status shows SUCCESS but no devices appear or expected devices weren't found‍

• Check Subnet Alignment
  
  • BACnet/IP discovery only works for devices on the same subnet
  • If controllers are on a different subnet, the Edge Node cannot see them
  • Ensure the site meets all items in the Network & Connectivity Requirements guide
• Ensure Devices are discoverable on BACnet
  
• Verify Discovery Range (for Targeted Discovery)
  
  • If you entered a device-range manually, confirm that device expected in the range exist on the network
  • ‍A mismatched range may cause devices to be skipped
• Controller or Meter Firmware may Be Outdated‍‍
  
  • If controllers run outdated firmware, they may not respond to BACnet requests
  • Ensure the device firmware is update with the latest firmware

Status shows FAILED‍

If the discovery status shows FAILED, please contact support@onboarddata.io

Modbus‍

if a Modbus device connection shows FAILED status, here are some common issues and how to fix them:‍

Controller IP Issues‍

• Double-check the device IP in your BAS or device front-end.

Port Configuration

• Default Modbus TCP port is 502. Confirm this port is open and accessible.

Unit Identifier (Slave ID)

• Verify the unit identifier in the device’s configuration or vendor manual.
• If multiple devices share the same controller IP, each must have a unique unit ID.

Unsupported Vendor Device

• Check the Connectivity Requirements documentation for supported models.
• If unsupported, request a template in the Online Community with vendor name and model