similar to: NUT supporting Modbus TCP

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

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

Hello Ted, 2013/9/11 Ted Mittelstaedt <tedm at mittelstaedt.us> > Hi All, > > About a month ago APC announced they were including MODBUS protocol > support in their new APC UPSes. The technical note on this is here: > > http://www.apcmedia.com/**salestools/MPAO-98KJ7F/MPAO-**98KJ7F_R0_EN.pdf<http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf>

Hi All, About a month ago APC announced they were including MODBUS protocol support in their new APC UPSes. The technical note on this is here: http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf "Application Note #176 Modbus Implementation in APC Smart-UPS" The APC "announcement" appeared on their site in their user blogs by an APC employee, here:

On 7/9/2014 4:16 PM, Charles Lepple wrote: > On Jul 9, 2014, at 11:24 AM, Ted Mittelstaedt<tedm at mittelstaedt.us> > wrote: > >> Someone could write a driver for MODBUS for NUT, all of the >> information and materials are available to do it. The simple fact >> of it is that the reason no one has done so is that the apcupsd >> program is available. > >

On 7/9/2014 6:51 AM, Charles Lepple wrote: > On Jul 9, 2014, at 6:31 AM, Eric S. Raymond<esr at thyrsus.com> wrote: > >> What I'd like to do is this: confer in real-time, perhaps via IRC, >> with someone who knows this process. Ask about every step >> (thought processes and diagnostics). *Write them down* and turn >> this into a document on how to qualify

I attach a patch for phoenixcontact_modbus.c This patch does the following: * Marks driver as DRV_BETA * Fixes stale data detection when cable is disconnected I can open a pull request if needed. Kind Regards, -Spiros p.s. please consider a faster tag/release schedule as currently linux repositories include old versions. Sure we can make packages ourselves, but it's better to have support

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

On Jul 9, 2014, at 11:24 AM, Ted Mittelstaedt <tedm at mittelstaedt.us> wrote: > Someone could write a driver for MODBUS for NUT, all of the information > and materials are available to do it. The simple fact of it is that the > reason no one has done so is that the apcupsd program is available. You're right, it's the microlink protocol that they have been promising to

Hello, this is to let you know I will start working on a modbus driver for the PhoenixContact QUINT-UPS industrial DC UPS, model 2320461. https://www.phoenixcontact.com/online/portal/us?uri=pxc-oc-itemdetail:pid=2320461&library=usen&pcck=P-22-07-01-01&tab=1 I will reuse some parts of the nutdrv-modbus branch, but this will be a model specific driver, not a generic one. Unfortunately

Hello, I have tried to use the blazer_ser driver to interface with my UPS. nut is not able to detect the UPS. I have not been able to find much info regarding Socomec UPS support in nut. Socomec does publish a description of the serial protocol for these UPS's, which can be found here: http://www.socomec.com/download-jbus-modbus.html(select UPS OTHER for device model, 1-5KVA for device power

Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov

Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov

Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your

Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

Hello all, During holiday revision of issues (hoping to tie up loose ends and get to NUT v2.8.1 soonish), an old https://github.com/networkupstools/nut/issues/50 ticket came to my attention - that some years ago "we" (as NUT community) wanted to create an unified driver for devices with a Modbus connection -- similar to `nutdrv_qx` doing everything about Megatec Qx protocol family

Hello all, During holiday revision of issues (hoping to tie up loose ends and get to NUT v2.8.1 soonish), an old https://github.com/networkupstools/nut/issues/50 ticket came to my attention - that some years ago "we" (as NUT community) wanted to create an unified driver for devices with a Modbus connection -- similar to `nutdrv_qx` doing everything about Megatec Qx protocol family

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. > > https://github.com/networkupstools/nut/pull/2184 > > As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and