RECORDING & REPLAY

Record the Modbus evidence you will need later

A screenshot proves what the UI looked like once. A Busloom session preserves the samples or frames needed to inspect the event again, on another machine, without touching the live device.

01

Choose the evidence, not just the file format

Trend recording is appropriate when the question is how engineering values changed over time. Raw Traffic recording is appropriate when the question is which request, response, exception, or latency produced the result.

02

Replay is intentionally read-only

Opening a .busloom-session.json file creates a Replay tab with its own timeline. It does not open a project, connect a profile, or restart source views. That separation prevents old evidence from being mistaken for current device state.

03

Export for analysis, keep the session for context

CSV or spreadsheet exports are convenient for calculations. The native session artifact retains Busloom-specific context such as series definitions or decoded frame information, so keep it beside any derived report.

TRY THE WORKFLOW

Start with one device and one known value.

Choose a download