Start here
The Busloom workflow and your first successful read.
Start here
Busloom is a project-based Modbus engineering tool. The project describes a device and how to interpret it; the native runtime talks to the device; views schedule reads; tags decode the returned bits or words; diagnostics retain the evidence. These are separate layers on purpose.
The five objects you need to understand
- Project
- The portable description of one device or device family: profiles, views, tags, Trends, automation, and display rules.
- Connection profile
- A named physical route to the device. It answers where and how to connect, not what the registers mean.
- View
- A read source. It defines an address space, addresses, and interval, then produces raw bits or 16-bit words.
- Tag
- Meaning attached to one starting address: name, data type, byte/word order, scale, unit, limits, and labels.
- Session data
- Live values, traffic, chart samples, and run output. It disappears unless you record or export it.
Your first verified read
Create an empty project
Use the start screen, File → New Project, the project menu, or the command palette. Busloom intentionally creates no placeholder view.
Add a connection profile
Open Project Settings → Connection profiles, choose RTU, TCP, or TLS, and enter the physical connection parameters.
Connect
Select the profile in the app bar and connect. A connected transport alone does not start polling.
Find an address
If the map is unknown, open Auto Scan and run Quick. If the map is known, skip scanning and create a view directly.
Create and start a view
Add a view for the correct address space and range. Start it from the floating bar. The status changes from stopped to running.
Verify one value
Open Register Inspector for the address. Compare the raw word or bit with the device manual before adding data type, order, and scale.
Save the project
Save as .busloom.json. Close and reopen it once; a reusable setup is only proven when it survives a new session.