Overview
This article explains why Modbus values may remain fixed (e.g., at 0) after communication interruptions.
FAQ
Q. Why does the Modbus value stay at 0?
In earlier versions, when a communication interruption occurred (such as packet loss), the system did not always restore the data state properly.
As a result, values could remain unchanged until manually reset.
👉 Status:
This behavior has been significantly improved in v3.5.2 and v3.6.
Troubleshooting
▶ Symptom
- Modbus value remains fixed (e.g., 0)
- Data does not update after interruption
▶ Possible Cause
- Temporary communication loss
- Incomplete recovery of data state
▶ Recommended Action
- Restart task or communication cycle
- Verify communication stability
- ✅ Upgrade to v3.6 to reduce occurrence
Comments
0 comments
Please sign in to leave a comment.