How do I find the BACnet points list for my equipment?

Updated 4 November 2026

1. Identify the controller, not just the unit

The same rooftop or chiller can ship with different controllers, and each one has its own object list. A Carrier 48/50LC can have SystemVu or, on the VAV "B" models, a VAV-RTU Open board. The two lists share almost nothing. Get these off the unit before you start searching:

• Full model number from the nameplate, including the revision or vintage letter. Daikin and York lists change between vintages.
• Controller name from the board, the display or the start-up sheet: SystemVu, Symbio 800, MicroTech, UPC Open, Prodigy, CORE and so on.
• Firmware or software version if the display shows it. Newer software often adds points, and sometimes renumbers them.
• Any gateway between the unit and the network. If BACnet comes from a ProtoNode, an Intesis box or a VRF gateway, the list belongs to that gateway and often numbers points per unit.

2. Search the library first

The BACnet points list library covers everything from rooftops and chillers to VAV boxes, boilers, drives, humidifiers and meters. Type a model number, a controller name or a manufacturer document number into the search box. Other names a product is sold under are searchable too, so 48LC, SystemVu and S-VU-LC-4-26-06T all land on the same list. You can also browse by manufacturer or by equipment type.

Each list page gives you:

• Every object with its type, instance, name, units and read/write access, filterable by object type and access.
• A short set of minimum points to map (enable, mode, setpoints, key temperatures, alarm), plus notes on network setup and things that catch integrators out.
• An object ID lookup, handy when a front end shows you only AV 7012 and you need to know what it is.
• Downloads as CSV and as an EDE file for tools that import one.
• A link straight to the manufacturer's own PDF, so you can check the source.

3. If it isn't there, know what the document is called

Manufacturers rarely call it a "points list". Search their documentation site for these instead:

A PICS (Protocol Implementation Conformance Statement) is not a points list. It says which BACnet services and object types the device supports, usually with no instance numbers (see how to read a PICS). If the manufacturer only publishes a PICS, the device itself is your list: scan it.

If you call the rep, ask for the "BACnet integration guide" for the exact controller and software version. You'll get the right document faster than asking for "the points".

4. Check the list against the live unit

A published list tells you what the controller can expose. The unit on the roof exposes what was ordered and configured. Points for options that aren't installed are often missing or out of service, and some controllers switch between English and metric units with a single setting.

Easy BACnet does this check from an Android phone. Connect to the controls network, scan, open the device and you'll see every object it actually has, with live values. Compare that with the published list, then export the result to a spreadsheet for whoever is doing the mapping. If the scan finds nothing, see why can't I find my BACnet IP devices.

Things that trip people up

• Wrong revision. Match the document's software version to the unit's. A newer list on an older controller shows points that don't exist.
• Gateway formulas. Multi-unit gateways (VRF, boiler cascades, ProtoNodes) number each unit's points with a formula. The document prints one unit; work out the rest from the formula, not by guessing.
• Network inputs need refreshing. Many controllers drop a BMS-written value back to its own default if it isn't rewritten within a timeout. The library notes say so where the manufacturer documents it.
• Writing is not free. Read is it safe to write to BACnet before commanding anything off a list you just found.