top of page
Solutions & Project Planning
Planning monitoring projects, comparing system architectures and scoping practical solutions.


A Modbus Device Went Silent After Diagnostics: Check Listen-Only History
A serial device stops replying after diagnostic work, while other devices remain reachable. Before treating this as proof of broken wiring, inspect the authorised diagnostic history. Listen-only mode is one possible documented cause of silence; it must be distinguished from power loss, framing errors and other communication failures.
1 day ago3 min read


Modbus Read/Write Multiple Registers: The Write Happens Before the Read
A combined Modbus request is expected to capture a value before changing a setting, but the returned data appears to include the change. Check transaction order before adjusting timestamps. Function 23 combines operations with a defined write-before-read order; it is not a pre-change snapshot mechanism.
1 day ago3 min read


Modbus Memory Parity Exception 08: Keep File Integrity Separate from Serial Parity
A diagnostic log says Memory Parity Error, and someone changes the serial port parity setting. That may address the wrong layer. Modbus exception 08 describes a memory consistency problem in a specialised file-record context. Preserve the request and the device's integrity evidence before changing communication settings.
3 days ago4 min read


Modbus Exception 06: Check the Programming Command Before Retrying
A client receives Modbus exception 06 and immediately repeats the request. If the server is still processing a long-duration programming command, that retry loop may obscure the operation's real state. Identify the request and the device's documented completion method before deciding when another command is appropriate.
3 days ago4 min read
bottom of page
.png)