Edke, let me know if this solution will work with you. What you can do is increase the retry count and then specify that empty responses should count as retries::

client = ModbusTcpClient('localhost', retry_on_empty = True, retries = 5)

from pymodbus.

I've created this option "retry_on_empty" last week. And additionally
creted "retry_on_wrong" when receives on Serial RTU from wrong unit or
function.

On Mon, Jul 15, 2013 at 1:44 AM, Galen Collins [email protected]:

Edke, let me know if this solution will work with you. What you can do is
increase the retry count and then specify that empty responses should count
as retries::

client = ModbusTcpClient('localhost', retry_on_empty = True, retries = 5)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-20951634
.

Alejandro Mesias André Nebra Perez
Java/Python/Js/Something else Developer
Twitter: @meszias
Linux User #442506

Campinas - SP - Brasil - South America

from pymodbus.

@bashwork @mesias No new version, so only have to test it with pip install from git, right ?

from pymodbus.

That is correct.
On Jul 15, 2013 1:13 PM, "Eduard Kracmar" [email protected] wrote:

@bashwork https://github.com/bashwork @mesiashttps://github.com/mesiasNo new version, so only have to test it with pip install from git, right ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-21000201
.

from pymodbus.

@bashwork will test it tomorrow, have 150 devices on Modbus link via TCP/IP converter and really have issues with communication. Will report back if related changes will address the issue for me.

from pymodbus.

@Edke The version i wrote (https://github.com/mesias/pymodbus) reads single bytes on transaction, instead of 1024bytes. It's a bit faster, but never tested on any different connection than Serial RTU.

from pymodbus.

cleaning up old issues. Should be fixed with the latest versions

from pymodbus.