Nut upsuser - Jun 2017 - NUT supporting Modbus TCP

Hi!

I was wonering if there is a driver that supports communicating with a Modbus
aware device over IP. I have a solar/wind invertor that can broadcast its state
and I would like to monitor the batteries. If they discarge to a certain voltage
or come to a defined state, I would perform a shutdown. All of this information
id provided in Modbus holding registers. This could of course be done placing a
Modbus-to-SNMP gateway but they seem to be somewhat pricey.

Can anyone clarify? Thanks in advance,

-- Sergei
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170624/5577a9cd/attachment.html>

On Jun 24, 2017, at 10:57 AM, Sergei Naumov wrote:
> I was wonering if there is a driver that supports communicating with a
Modbus aware device over IP. I have a solar/wind invertor that can broadcast its
state and I would like to monitor the batteries. If they discarge to a certain
voltage or come to a defined state, I would perform a shutdown. All of this
information id provided in Modbus holding registers. This could of course be
done placing a Modbus-to-SNMP gateway but they seem to be somewhat pricey.
There is a GitHub issue tracking the general idea of a NUT MODBUS driver:
https://github.com/networkupstools/nut/issues/50

The skeleton code on the referenced branch uses libmodbus, which as I
understand, can communicate over TCP.

However, since you have a specific device in mind, you might be better served by
creating a new driver based on the phoenixcontact_modbus driver (which also uses
libmodbus): https://github.com/networkupstools/nut/pull/404 and
https://github.com/networkupstools/nut/blob/7bd8971db89eec51fa55bbb75c8a54ca4a46e7dc/drivers/phoenixcontact_modbus.c

Do you have a datasheet or protocol document for this device?

Yeah, I have its datasheet (it's a Xantrex XW invertor by the way). I do not
know why creating a more-or-less generic driver is an issue. Of course, there
are Modbus beasts that can scare everyone but mostly one would need to read
either intreger or float numbers out of Modbus registers in order to decide
whether or not to start or stop the shutdown process.

24 ???? 2017 ?. 19:25:14 GMT+03:00, Charles Lepple <clepple at gmail.com>
?????:
>On Jun 24, 2017, at 10:57 AM, Sergei Naumov wrote:
>
>> I was wonering if there is a driver that supports communicating with
>a Modbus aware device over IP. I have a solar/wind invertor that can
>broadcast its state and I would like to monitor the batteries. If they
>discarge to a certain voltage or come to a defined state, I would
>perform a shutdown. All of this information id provided in Modbus
>holding registers. This could of course be done placing a
>Modbus-to-SNMP gateway but they seem to be somewhat pricey.
>
>There is a GitHub issue tracking the general idea of a NUT MODBUS
>driver: https://github.com/networkupstools/nut/issues/50
>
>The skeleton code on the referenced branch uses libmodbus, which as I
>understand, can communicate over TCP.
>
>However, since you have a specific device in mind, you might be better
>served by creating a new driver based on the phoenixcontact_modbus
>driver (which also uses libmodbus):
>https://github.com/networkupstools/nut/pull/404 and
>https://github.com/networkupstools/nut/blob/7bd8971db89eec51fa55bbb75c8a54ca4a46e7dc/drivers/phoenixcontact_modbus.c
>
>Do you have a datasheet or protocol document for this device?
>_______________________________________________
>Nut-upsuser mailing list
>Nut-upsuser at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
-- 
???????? ?? ?????????, ??????? ? K-9 Mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170629/740ef5ba/attachment.html>