On 1/20/2011 9:42 PM, James Y Knight wrote:
> On Jan 20, 2011, at 6:32 AM, Albert Brandl wrote:
>> The main problem seems to be the specification of Modbus RTU. RTU
>> messages are separated by time gaps that are at least 3.5 characters
>> long. Unfortunately, this is the only reliable way for sepa
On Thu, Jan 20, 2011 at 08:42:58AM -0500, James Y Knight wrote:
> I don't think you'll ever be able to do this reliably in Python. At
> 9600 baud, 3.5 characters is just about 275hz (9600/10/3.5). Linux
> schedules process at around 500hz.
Well, that's bad news - I'll have to communicate with t
On Jan 20, 2011, at 6:32 AM, Albert Brandl wrote:
> The main problem seems to be the specification of Modbus RTU. RTU
> messages are separated by time gaps that are at least 3.5 characters
> long. Unfortunately, this is the only reliable way for separating
> messages - there is no length header or
Hi!
I am trying to read Modbus RTU messages over the serial line. There is a
library called pyModbus which is very usable for Modbus TCP/IP, but the
support for RTU is a bit lacking.
The main problem seems to be the specification of Modbus RTU. RTU
messages are separated by time gaps that are at
