One tool for mixed buildings · Windows 10/11

One tool for
every device
in the building

The AHU speaks BACnet. The energy meters and drives speak Modbus. Stop carrying two tools. BACManager discovers, browses and writes BACnet/IP, MS/TP and Modbus RTU/TCP devices — property browser, schedule & calendar editor, EDE export, COV — all from one native Windows window. No BMS, no engineering workstation, no per-point licensing.

BACnet● IP+MS/TP
Modbus● RTU+TCP
Tools neededJust one
LicenseONE-TIME
Windows 10/11 BACnet/IP + MS/TP Modbus RTU + TCP One app, one window One-time license
bacmanager — discovery
→ scan · BACnet whoIs + Modbus poll
  device 4321  "AHU-Controller-1"  BACnet MS/TP
  device 1201  "VAV-Zone-North"   BACnet/IP
  unit 3     "Power-Meter-Main" Modbus RTU
  10.0.0.44  "Solar-Inverter-1"  Modbus TCP
  schedule 17:0 · Room_Sched · 7 days
// one tool, every device

BACnet and Modbus, one app

Real buildings are mixed. The AHU talks BACnet; the energy meters and drives talk Modbus. BACManager speaks both.

Real buildings are mixed. The air handlers and controllers talk BACnet; the energy meters, VFDs and solar inverters talk Modbus. Every other tool forces you to pick a side — a BACnet explorer that ignores your meters, or a Modbus poller that can't see your controllers. BACManager does both natively: discover and browse BACnet/IP and MS/TP devices, and poll Modbus RTU or TCP devices on the same site, each on its own port, side by side. Walk into a plant room, plug in, and read everything with one window open.

BACnet● IP + MS/TP
Modbus● RTU + TCP
PortsSimultaneous
Tools neededJust one

Need advanced Modbus features — dashboards, alarms, historian, scripting? Our dedicated Modbus tool ModbusManager goes deeper. BACManager covers the everyday Modbus reads you hit during BACnet commissioning.

// what it does

Everything for on-site commissioning

One native Windows tool for discovering, inspecting and configuring the BACnet and Modbus devices on a site.

🔍

Device discovery

Broadcast or directed whoIs across BACnet/IP and MS/TP. Find every device, its ID, name and address — including devices behind routers via BBMD foreign-device registration.

📁

Property browser

Browse the full object list of any device. Read and write any property, see the raw decoded values, and inspect priority arrays — not just present-value.

📅

Schedule & calendar editor

Read and write weekly Schedule objects and Calendar objects directly — an editable grid for daily times and values, exception schedules and calendar dates.

📤

EDE & CSV export

Export a device object list as BACnet EDE 2.3 — importable by other BACnet tools and BMS engineering software — or as plain CSV for documentation.

COV subscriptions

Subscribe to Change-of-Value notifications and watch values update live, without polling — exactly as a real BMS would receive them.

🔢

BACnet and Modbus

BACnet/IP, MS/TP over RS-485, and Modbus RTU/TCP — all in one app. Commission the BACnet controllers and read the Modbus energy meters on the same site without switching tools.

// RS-485 field devices

Real MS/TP, not just IP

Most BACnet tools only speak BACnet/IP. The field devices — VAV boxes, room controllers, thermostats — are often MS/TP only.

BACManager includes a full MS/TP master-node implementation over RS-485: it joins the token ring, answers Poll-For-Master, and reads and writes confirmed requests just like a native device. Point a USB-RS485 adapter at an MS/TP segment, pick the baud rate and MAC, and the same property browser, schedule editor and EDE export work exactly as they do over IP. And because Modbus RTU and BACnet MS/TP each run on their own COM port, you can even run alongside a Modbus session on a second adapter.

DatalinkMS/TP RS-485
Baud9.6k–115k
RoleMaster node
MAC0–127
// schedule + calendar

Read and write schedules

View and edit BACnet Schedule and Calendar objects directly on the device — no engineering tool required.

Open a Schedule object and BACManager shows an editable weekly grid: time and value pairs for each day, the schedule default, what it writes to, and its exception schedules. Calendar objects show their date entries — specific dates, ranges and recurring weekdays — all editable and writable back to the device. The schedule and calendar codec has been validated byte-for-byte against independent reference BACnet stacks, so what you write is exactly what the standard specifies.

// why one tool

Two tools, or one

Most engineers carry a BACnet explorer and a Modbus tool. On a mixed site that means two apps, two windows, two workflows. BACManager is one.

On a mixed BACnet + Modbus siteBACnet explorerModbus toolBACManager
Discover BACnet devices (whoIs)
Browse / write BACnet properties
BACnet schedule & calendar editorVaries
Read Modbus RTU meters & drives
Read Modbus TCP devices
One window for the whole site
Apps to buy, learn & carryTwoOne — $149
// questions

Honest answers

The things a careful buyer asks before paying for a commissioning tool.

Aren’t there free BACnet tools already?

Yes — and they are good at BACnet. But they are BACnet-only. The moment your site also has Modbus energy meters, VFDs or inverters — which most buildings do — a BACnet-only tool leaves you switching to a second app. BACManager is the one tool that reads both, so you are not paying for BACnet you can get free; you are paying to stop carrying two tools.

Is the BACnet side a real implementation?

Yes. Full device discovery (whoIs, including devices behind routers via BBMD/FDR), complete object-list browsing, read and write of any property, COV subscriptions, and a Schedule & Calendar editor. The schedule and calendar codec is validated byte-for-byte against independent reference BACnet stacks.

Does it do MS/TP, or just BACnet/IP?

Full MS/TP master-node support over RS-485, alongside BACnet/IP. Point a USB-RS485 adapter at an MS/TP segment, pick the baud rate and MAC, and the same browser, schedule editor and EDE export work exactly as they do over IP. The field devices that are MS/TP-only — VAV boxes, room controllers — are reachable too.

How deep is the Modbus support?

Modbus RTU and TCP polling — the everyday reads you hit during commissioning: registers, coils, common data types and scaling. If you need heavy Modbus work — dashboards, alarms, historian, scripting — our dedicated tool ModbusManager goes further. BACManager covers the Modbus you meet while commissioning BACnet.

One-time price, or subscription?

One-time. $149 buys the tool with free updates within the major version. No subscription, no per-point fees, no cloud dependency — it runs entirely on your Windows machine.

// pricing

Simple, honest pricing

One-time license. No subscription, no per-point fees, no cloud dependency.

Trial
Free trial
Try BACManager before you buy. Full features, time-limited.
  • All commissioning features
  • Test against real devices
  • Built-in device simulator
  • No account required
Download trial
// launching soon

Be first to know

BACManager is in final testing. Leave your email and we’ll notify you the moment the trial and purchase go live — early subscribers get launch pricing.