njs-modbus 1.5.0 → 2.0.1

package/README.md

@@ -178,6 +178,22 @@ modbusSlave
 
 For more advanced examples, check out [examples](/examples) included in the repository. If you have created any utilities that meet a specific need, feel free to submit them so others can benefit.
 
+## Broadcasts (unit = 0)
+
+Slaves never respond to broadcast requests, so the master's `write*(0, ...)` Promise resolves as soon as the bytes are flushed to the wire.
+
+If you broadcast over serial (RTU or ASCII), per Modbus over Serial Line V1.02 §2.4.1 you must wait a **turnaround delay** before sending the next request — slow slaves need time to apply the broadcast write that produced no response. The library does not insert this delay automatically because the right value is workload-specific (fast sensors vs. PLCs writing to flash differ by orders of magnitude). Insert it yourself in your call site:
+
+```typescript
+const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
+
+await master.writeSingleRegister(0, 0x0000, 0x1234); // broadcast
+await sleep(100);                                     // turnaround — tune per devices
+await master.writeSingleRegister(1, 0x0000, 0x5678); // unicast to next slave
+```
+
+A safe lower bound is the RTU t3.5 inter-frame silence (e.g. ~4 ms at 9600 baud, ~1.75 ms above 19200 baud). Many real-world PLCs need 50–100 ms after a broadcast write. Modbus TCP/UDP do not require this delay (TCP gives synchronous acks; broadcasting on TCP is uncommon anyway).
+
 ## Contributing
 
 Please read our [contributing guide](/CODE_OF_CONDUCT.md) first.