jan iversen

We do not want to change the default to master, since it would mean that Pull Requests would be raised against master, which is wrong.

You "safe fix' works counter to the automatic retry mechanism. Furthermore it seems as if you are not testing with dev. We do test for - that the buffer is...

your code análisis might be correct, but do not help us at all. We need to see a debug log, that shows what is wrong. Apart from that you need...

there are something wrong in the library: ``` ERROR:pymodbus.logging:General exception: index out of range ``` Should not happen. The app should actually get ModbusIOException("Unable to decode request"), but let me...

Actually your device responds wrongly: ``` DEBUG:pymodbus.logging:send: 0x0 0x4 0x0 0x0 0x0 0x6 0x1 0x4 0x13 0xce 0x0 0x1 DEBUG:pymodbus.logging:recv: 0x0 0x4 0x0 0x0 0x0 0x2 0x1 0x84 0x2 old_data:...

I found the "index out of range", that is because the data byte is missing.

No, we try to make the API as simple as possible, people who wants details activate the debug logging. And the library do not see a response, just garble data....

A register is 16bit and that is what pymodbus return, in order to to see what actually happens please run it with the pymodbus debug logging, then we can see...

hmmm your example is not correct, but works, sort of. If you use Async clients, you should do "rr = await client.read_input_registers" (see our simple_async_client.py example). You will in many...

I have seen that a number of devices have this error, so I will try to implement it, can you assist in testing the pull request ?