Clarifications to Modbus docs

@sumitshinde-84

Ref merged PR: #5384

Consider adding a note explaining that device manuals often label Holding Register 0 as 40001, while others label it 0 or 1. This is a common source of confusion for new Modbus users.
Standardise on client/server terminology throughout the docs (more modern terminology). It may also be worth adding a brief note that older device manuals often use master/slave, and explain the equivalent terms.
"array of 16-bit integers" is not technically correct. Consider changing this throughout to "16-bit register values", as registers do not inherently have a data type.
"reading and writing coils and registers over Modbus TCP (including UDP...)" is a little misleading. Perhaps: "over Modbus TCP, Modbus UDP (where supported), and Serial (RTU/ASCII)".
Clarify the wording around "A function node — read the raw values (or the response buffer) and reconstruct the value in JavaScript...". As written, it isn't clear that the node outputs a JavaScript array, so this would either need converting to a Buffer before calling Buffer methods, or the user should instead use msg.responseBuffer.
For the Unit ID section, it may be worth mentioning that on serial buses (e.g. RS-485), Unit ID 0 is the broadcast address. Alternatively, simply stating that RTU slave IDs are normally 1–247 may be sufficient.

I will try to get to these tomorrow (but of course feel free to pick them up / contest them) :)

No response

I have provided an initial effort estimate

Navigation Menu