YABE Download: Where to Get Yet Another BACnet Explorer Safely

The Scenario: A Free BACnet Browser, Buried Under Mirror Sites

Someone on the project told you to "just grab YABE" to check a device, read a point, or confirm a controller is answering Who-Is. You searched for the download and got a wall of results: SourceForge, an unofficial GitHub mirror, a handful of freeware aggregators, and a couple of "safe download" portals that clearly wrap the file in their own installer. None of them is obviously the real one.

This is a common trap for a free, community-maintained tool. The download itself is trivial once you know the correct source — the risk is grabbing a repackaged copy from a mirror. This entry covers exactly where to get YABE, what you need to run it, and the handful of things that trip people up on the first launch.

What YABE Actually Is

YABE stands for Yet Another BACnet Explorer. It is a graphical BACnet client written in C# for discovering devices, browsing objects, and reading and writing properties. It is free and open source, and it is one of the most widely used no-cost tools in the BACnet ecosystem.

The tool is maintained by Frédéric Chaxel along with other contributors, and it is built on the System.IO.BACnet library — the C# BACnet stack from the same project. Understanding that lineage matters for one reason: the authentic YABE binaries are published by that project on SourceForge, and everything else on the internet is a copy of those files.

On the wire, YABE supports the transports you would expect from a general-purpose BACnet tool:

• BACnet/IP — IPv4 and IPv6 over UDP. Standard BACnet/IP uses UDP 47808 (0xBAC0); YABE lets you bind to a specific network interface and port.
• BACnet MS/TP — over a serial port, so you can talk directly to an RS-485 trunk with a USB-to-RS-485 adapter.
• BACnet/SC (Secure Connect) — hub and direct connections over WebSocket with TLS (TCP 443), which the standard requires; YABE also exposes a plain-WebSocket option for local testing, but that is not spec-conformant transport.
• Raw Ethernet — ISO 8802-3 BACnet, which requires a pcap capture driver installed on the machine.

For services, it covers Who-Is/I-Am discovery, ReadProperty and WriteProperty, the "multiple" variants, COV subscription, TimeSync, atomic file read/write, and object create/delete. That is more than enough for the everyday tasks most technicians reach for it: confirm a device is online, read a stuck value, or write a test command to a commandable object.

Where to Download YABE (The Only Source You Should Use)

Download YABE from the official SourceForge project:

• SourceForge project page: sourceforge.net/projects/yetanotherbacnetexplorer

The Files section of that project offers two forms of the same release, and either is fine:

• Windows installer — named in the pattern SetupYabe_v<version>.exe. This runs a normal setup wizard and puts YABE in Program Files with a Start-menu shortcut.
• Portable ZIP — named in the pattern Yabe_v<version>.zip. Unzip it anywhere and run the executable directly. This is the better choice on a locked-down machine or a shared commissioning laptop where you would rather not install anything.

There is also an unofficial GitHub mirror of the source (the dechamps/yabe repository), which states plainly that it is not the official repository and that pull requests there are not reviewed. It is useful for reading the code, but treat SourceForge as the source of truth for release downloads.

Skip the freeware aggregators and "download manager" portals entirely. They tend to re-host an older copy behind their own wrapper installer, and you have no way to know what else that wrapper does. When the authentic file is a one-click download from the project itself, there is no reason to accept a repackaged one.

Download, Install, and First Launch

1. Open the SourceForge project page above and go to the Files tab. Pick the newest SetupYabe_v….exe for a standard install, or the matching Yabe_v….zip if you want the portable copy.
2. On Windows, expect a SmartScreen or antivirus prompt. YABE is community-built and the binaries are not code-signed, so an "unknown publisher" warning is normal — it is not by itself a sign of tampering. The safeguard that matters is having downloaded from SourceForge rather than a mirror.
3. Make sure the .NET Framework is present. YABE is a .NET application; modern Windows builds generally already have a compatible runtime, but an older or freshly imaged machine may need it installed.
4. If you plan to use raw Ethernet capture, install a pcap driver first (for example Npcap). This is only required for the Ethernet transport — plain BACnet/IP over UDP does not need it.
5. Launch YABE. Add a transport that matches how you are connected: a BACnet/IP transport bound to the correct network interface, or an MS/TP transport on the right serial port. Then click Send WhoIs. Devices that answer appear in the tree on the left, and the log pane at the bottom shows the raw I-Am responses arriving.

Common Pitfalls

• Grabbing a repackaged copy from a mirror. This is the single biggest risk with a "yabe download" search. Aggregator sites often bundle an adware-laden installer around an outdated YABE build. Download from SourceForge and you sidestep the whole problem.
• Binding to the wrong network interface. On a laptop with Wi-Fi, a wired NIC, and maybe a VPN adapter, YABE will happily bind to whichever interface you pick — including one with no path to the BACnet network. If Who-Is returns nothing, confirm the transport is on the interface that actually reaches the controllers.
• A firewall silently dropping the traffic. BACnet/IP discovery relies on broadcasts, and host or network firewalls frequently block UDP 47808. If devices you know are online never answer, the firewall is a prime suspect. See our BACnet device discovery troubleshooting guide for the full checklist.
• Expecting a signed installer. YABE is open source and its releases are not code-signed. The "unknown publisher" warning is expected; the mistake is reacting to that warning by hunting for a "trusted" mirror instead. The trustworthy copy is the unsigned one straight from the project.
• Running the portable ZIP from a restricted folder. Unzipping into a location the account cannot write to, or leaving files inside the ZIP without extracting, can cause the executable to fail to start or fail to save logs. Extract the full archive to a normal working folder first.

When to Escalate

A download problem is rarely a BACnet problem — but a few situations call for more than a retry:

• Corporate policy blocks unsigned executables. If IT security prevents you from running an unsigned installer, ask them to allow the portable ZIP on an approved commissioning laptop, or point them to the open-source project so they can review or build it themselves. Do not work around the policy with a random mirror.
• YABE downloads and runs, but still finds nothing. At that point the issue has moved from the tool to the network — interface binding, firewall rules, or cross-subnet discovery. If your devices live on other subnets, discovery needs a BBMD or router in the path, which is its own topic.
• You want a guided walkthrough of the tool itself. Once YABE is installed, our YABE (Yet Another BACnet Explorer) tutorial covers discovery, object browsing, and reading and writing values step by step.

Source Attribution

The details in this entry are drawn from the tool's own project page and repository:

• Yet Another BACnet Explorer — SourceForge — the official project and release downloads, supported transports, and feature list.
• dechamps/yabe — GitHub — an unofficial, read-only source mirror; explicitly not the official repository.
• ASHRAE Standard 135 — BACnet—A Data Communication Protocol for Building Automation and Control Networks. The normative reference for the Who-Is/I-Am discovery mechanism and BACnet/IP transport that YABE implements.

Additional testing and field validation by SiteConduit.