Open 81ondo opened 2 months ago
Hi,
Are you sure that the registers in the range 10-16 are readable. Anyway, check your documentation for error 167, this is the number returned in both cases:
2024-04-11 12:20:28.781 ... Querying [10 - 10]...
2024-04-11 12:20:28.781 ... SENT: a5 17 00 10 45 aa 00 12 60 9e 8d 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 0a 00 01 a4 08 70 15
2024-04-11 12:20:29.860 ... RECD: a5 15 00 10 15 aa 55 12 60 9e 8d 02 01 4e ce 29 00 89 03 00 00 1f eb ed 65 01 03 02 00 a7 f9 fe aa 15
2024-04-11 12:20:29.860 ... Querying [10 - 10] succeeded
2024-04-11 12:20:29.861 ... Querying [12 - 16]...
2024-04-11 12:20:29.861 ... SENT: a5 17 00 10 45 ab 00 12 60 9e 8d 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 03 00 0c 00 05 45 ca da 15
2024-04-11 12:20:29.940 ... RECD: a5 15 00 10 15 ab 56 12 60 9e 8d 02 01 4e ce 29 00 89 03 00 00 1f eb ed 65 01 03 02 00 a7 f9 fe ac 15
It is not detected in the first attempt as only one register is requested which satisfies the packet length of the response. The error is raised directly from the umodbus
lib.
Is it possible that the reason is because the wifi stick also sends data to the Zucchetti ZCS cloud?
Highly unlikely. You should see something like:
Querying [<start> - <end>] failed with exception [V5FrameError: V5 frame contains invalid sequence number]
if responses to requests not generated by the current pysolrmanv5 instance are received on the socket.
I get random disconnections. These are the error messages I get during disconnections (with DEBUG activated).
This instead is an example of a successfully completed capture:
I do not understand why it randomly receives as incomplete packets leading to incorrect parsing and thus disconnection.
Is it possible that the reason is because the wifi stick also sends data to the Zucchetti ZCS cloud?