Read & write safely

Writes change real equipment. Busloom keeps the protocol visible and applies write protection at the native boundary so UI actions, automation, CLI, and MCP cannot bypass a read-only profile.

Before the first write

• Confirm the active project, connection profile, Unit ID, address space, and PDU address.
• Read the current value and inspect its raw representation.
• Confirm whether the device expects one coil/register or a multi-value operation.
• Use a read-only profile whenever the task does not require changes.
• Understand the machine state, interlocks, and consequences outside Busloom.

Manual write procedure

1. Open the value editor

   Start from the exact row or decoded tag. The editor shows the target and expected representation.

2. Enter the engineering value

   Busloom validates type, finite numeric input, limits, and the codec's encodable range before producing raw bits or words.

3. Review the confirmation

   Verify profile, Unit ID, address space, PDU address, function, and encoded payload—not only the friendly tag name.

4. Send the write

   Busloom uses FC05/FC06 for a single value or FC15/FC16 for supported multiple-value writes.

5. Verify independently

   Read the target again and inspect Raw Traffic. An echoed write response proves protocol acceptance, not necessarily physical actuation.