I-Am - Knowledge Base

BACnet I-Am service response overview covering device discovery, broadcast response content, and common integration issues.

Categories:

What I-Am Is

I-Am is a BACnet unconfirmed service broadcast by a device in response to a Who-Is request. It is the device’s way of announcing its presence and identity on the network.

What an I-Am Contains

FieldDescription
Object IdentifierDevice object type + Device Instance number
Max APDU LengthMaximum application protocol data unit the device can accept
Segmentation SupportedWhether the device supports segmented messages
Vendor IDNumeric vendor identifier (assigned by ASHRAE)

How Discovery Works

  1. Supervisor broadcasts Who-Is (optionally with a device instance range)
  2. Each matching device broadcasts I-Am
  3. Supervisor collects I-Am responses and builds its device table
  4. Subsequent communication uses the device’s address from the I-Am

[!NOTE] I-Am is broadcast — it reaches all devices on the subnet, not just the original Who-Is sender. On BACnet/IP networks, BBMDs forward I-Am broadcasts across subnets.

Common Issues

  • No I-Am response — device may be offline, misconfigured, or on a different subnet without BBMD forwarding
  • Delayed I-Am — some devices respond slowly; supervisory systems with short discovery timeouts may miss them
  • Duplicate Device Instances — multiple I-Am responses with the same instance cause address conflicts

Need more help?

If this page does not resolve the issue, contact Chipkin support with the product model, protocol details, and any diagnostics you have already captured.

Open Chipkin Support