Use one cross-platform Modbus master and test tool for RTU, TCP, or TLS. Discover devices and addresses, decode engineering values, inspect exact frames, log live data, and turn the result into a project your team can reopen.
Four views from the same connected showcase project, captured directly from Busloom.
Use commodity USB-RS485 adapters or standard Ethernet. Discover an unknown route, then keep serial framing, endpoints, retries, and TLS trust in a named profile.
Read all four address spaces and write single or multiple coils and registers through one transport-neutral workflow.
Turn raw words into engineering values while keeping the source bytes visible. Documentation and PDU addresses are always explicit.
Preview CSV, TSV, or XLSX register maps, resolve documentation notation, reuse mapping presets, and merge without silent deletion.
Run source views independently from the UI, watch related values together, and define runtime alarm conditions on decoded tags.
Raw Traffic, Auto Scan, Protocol Diagnostics, Device Info, and Connection Health share the same real transaction stream.
Record finite sessions, export machine-readable data or a finished report, and reopen Trends or traffic captures without a device connection.
Projects keep profiles, source views, tags, Trends, automation, and display semantics in a readable file that works with normal Git.
A suspicious number should lead directly to the request that produced it. Busloom attributes every transaction to its source view, scan, manual operation, or automation step.
Promote a known-good manual workflow into a bounded scenario or sandboxed Lua script. Preview impact, run without writes, then reuse the same project in the desktop app, CLI, CI, or a local MCP client.
Find the port and Unit ID, discover readable ranges, create views, label values, and leave with a reusable project.
Keep decoded values beside exact frames, timings, retries, and exception responses while firmware changes underneath.
Record traffic and trends, export a bounded session, then replay the evidence without reconnecting to the customer's device.
Run guarded scenarios or Lua against RTU, TCP, or TLS and emit JSON, JUnit, or standalone HTML reports.
Busloom joins the tasks that are usually scattered across a poller, spreadsheet, terminal, traffic logger, and test script.
Discover RTU participants or TCP/TLS endpoints, then keep the working route as a named profile.
Scan readable addresses or import a reviewed device definition, then create sources and decoded tags.
Run live views, Trends and alarms beside exact traffic, health metrics and protocol diagnostics.
Save the project, record a session or export a report. Professional can turn the proven procedure into automation.
The difference is not rounded corners. It is how protocol truth, engineering meaning, repeatability, and safety are connected.
Compare Modbus clients →Profiles, views, tags, Trends, alarms, presets and automation stay in one readable project.
Decoded engineering values remain tied to source health, exact frames, recordings and reports.
Find RTU devices or TCP/TLS endpoints, then scan addresses or import a reviewed definition.
Replay captured sessions or promote a manual procedure into guarded automation, CLI/CI or MCP.
Free for non-commercial use
$149 one-time · commercial use · one permanent device
Paid licenses are permanent, device-bound, and verified offline. Every plan receives the same updates and support.
No. It works with commodity USB-RS485 adapters for RTU and normal network interfaces for TCP or Modbus/TCP Security.
Always. Decoding adds context; it never replaces protocol addresses, function codes, TX/RX bytes, timings, exceptions, or errors.
No. Community contains the complete manual Modbus client, diagnostics, projects, imports, Trends, recording, and session replay. It is licensed for non-commercial use.
No. Paid licenses are permanent device-bound certificates verified locally. There is no heartbeat, subscription expiry, or customer-hosted license server.
Windows, macOS, and Linux on x86_64, with ARM64 kept feasible. The first public release still requires final cross-platform packaging validation.
Ask a product question, discuss a pilot, or describe the workflow that your current Modbus tools make harder than it should be.
