similar to: Looking for a UPS Driver

I have an Smart-UPS X 1500 (SMX1500I, USB) USB. I am looking for the APC_MODBUS driver. Thanks James -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20231209/e81b0a7d/attachment-0001.htm>

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

Hello, fellow NUTs! This October proved to be a rather productive month, with several developments wrapped up, as well as some issues with master codebase behavior created, reported, fixed and tested :) While we were not part of some official Hacktoberfest this year, it pretty much felt like one - great thanks to everyone involved! The month is also ending soon, so if we're to follow

Hello, fellow NUTs! This October proved to be a rather productive month, with several developments wrapped up, as well as some issues with master codebase behavior created, reported, fixed and tested :) While we were not part of some official Hacktoberfest this year, it pretty much felt like one - great thanks to everyone involved! The month is also ending soon, so if we're to follow

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

I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Thanks in advance, Jim Klimov On Wed, Nov 22, 2023 at 3:20?PM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Great! Thanks for the info, and hope the driver author can address the > nits (forwarding now...) > > Jim

I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Thanks in advance, Jim Klimov On Wed, Nov 22, 2023 at 3:20?PM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Great! Thanks for the info, and hope the driver author can address the > nits (forwarding now...) > > Jim

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

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

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

Great! Thanks for the info, and hope the driver author can address the nits (forwarding now...) Jim On Wed, Nov 22, 2023, 15:05 d tbsky <tbskyd at gmail.com> wrote: > 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

Great! Thanks for the info, and hope the driver author can address the nits (forwarding now...) Jim On Wed, Nov 22, 2023, 15:05 d tbsky <tbskyd at gmail.com> wrote: > 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

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

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' ??

<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

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

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