Hi Stefan,
I too found that it must have been an intermittent connection issue so I
started to look at the code.
I went back to the original modbus.c file from the 3.0.2 distribution and found
that there is currently a for loop which does the connection (I am not a C
programmer), but this
Hi Stefan,
I thought I would give your modified modbus.c file a try. It worked fine for
awhile, but then it started reporting:
[2012-02-01 14:00:47] plugin_read_thread: Handling `modbus-10.1.2.2'.
[2012-02-01 14:00:47] Modbus plugin: modbus_read_registers (10.1.2.2) failed.
Giving up.
Hi,
I am trying to get collectd working with the modbus plugin but I am getting a
segfault each time collectd runs:
Dec 16 01:20:55 vmunix: [1074386.330565] collectd[29149]: segfault at 20 ip
b7e03bcc sp b6fa1270 error 4 in libmodbus.so.4.0.0[b7e02000+6000]
Using Collectd version 5.0.1 with
to currently support Modbus RTU and Modbus/TCP.
Regards,
Matt
Hi Matt,
On Fri, Jan 07, 2011 at 10:33:34PM +1030, Matt Baker wrote:
Unfortunately though I discovered that the device I am using to do the
Modbus conversion supports Modbus/TCP for interfaces connected
directly, but provides
was wondering if you had any thoughts
on how difficult it would be to modify collectd to do this?
Cheers,
Matt
Hi Matt,
On Wed, Jan 05, 2011 at 09:25:00PM +1030, Matt Baker wrote:
Initially I tried against the latest unstable version of libmodbus,
4.9.2 but found that running configure
direct modbus/tcp to the gateway with
collectd, and then use collectd-nagios to send through to Nagios warnings if
values fall out of range.
cheers,
Matt
[0] http://www.barix.com/Barionet_100/511/
Hi Matt,
On Wed, Jan 05, 2011 at 09:25:00PM +1030, Matt Baker wrote:
Initially I tried
