What It Is
Word order defines the arrangement of 16-bit words inside a multi-register Modbus value. When a value spans two or more registers, the order of the words determines how that value is reconstructed by a gateway, scanner, or supervisory system.
This matters most on holding registers and input registers that carry 32-bit integers, floats, totals, and energy values. The protocol link can be completely healthy while the resulting engineering value still looks absurd because the words were assembled in the wrong order.
Why It Matters
Many field complaints labeled as “bad scaling” or “bad sensor data” are actually word-order mistakes. Communication works, but the 32-bit value is being assembled in the wrong order.
Common Patterns
| Pattern | Meaning |
|---|---|
| Big-endian (AB CD) | High word first, then low word |
| Word-swap (CD AB) | Low word first, then high word |
Word order and byte order are related but not identical. A device can use a normal word order with swapped bytes inside each 16-bit word.
Where Word-Order Errors Show Up
| Symptom | What It Often Means |
|---|---|
| Float values are wildly wrong but not random | The registers are valid, but the two words are reversed |
| Counter jumps to impossible magnitudes | Multi-register integer assembly is wrong |
| One tool reads correctly and another does not | The tools are using different default interpretations |
| Scaling changes do not fix the problem | The issue is word reconstruction, not engineering-unit conversion |
How To Validate It
- Read a value you can verify independently from the real device.
- Test the common word-order interpretations.
- Keep the interpretation that produces the known engineering value.
Common Failure Modes
| Failure Pattern | What Usually Happened | Practical Result |
|---|---|---|
| Word order was assumed from vendor family reputation | The installed device revision uses a different layout | Values look wrong despite clean communications |
| Byte order and word order were treated as the same issue | The wrong correction was applied | Troubleshooting chases the wrong layer |
| Validation used an unknown field value | There was no trustworthy real-world reference for comparison | The wrong interpretation survives into production |
Commissioning Notes
Word-order validation should use one independently known value such as a live power reading, temperature, or counter total from the source device display or incumbent system. Without that anchor, the project is still guessing even if one interpretation seems plausible.