search for: apc_modbus

...t; > 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! Hi: I got a new APC SRT3000XL and tested the new driver "apc_modbus". the ups works fine with nut+apcupsd. the new driver "apc_modbus" has result below: 1. upsrw can write the variable "battery.date". but the new value will only show after restarting apc_modbus. and in my case the written data will shift one day. eg the command "ups...

...t; > 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! Hi: I got a new APC SRT3000XL and tested the new driver "apc_modbus". the ups works fine with nut+apcupsd. the new driver "apc_modbus" has result below: 1. upsrw can write the variable "battery.date". but the new value will only show after restarting apc_modbus. and in my case the written data will shift one day. eg the command "ups...

...eady be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov <jimklimov+nut at gmail.com> wrote: > 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 and feature suggestions. It is my underst...

...eady be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov <jimklimov+nut at gmail.com> wrote: > 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 and feature suggestions. It is my underst...

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 and feature suggestions. It is my understanding that some tha...

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 and feature suggestions. It is my understanding that some tha...

...here are quite a few architecture and installation documents and README's (maybe a few too many for people just getting started, pull requests for simple entry points are welcome) :) In short, you would either have it installed via packaging prepared by your OS distribution maintainers (for `apc_modbus` in particular, you would need at least NUT v2.8.1), or built by yourself - in case of this driver and USB links, also building the custom libmodbus with USB capability, as per Wiki page linked earlier. Specifically in case of this driver and use-case, your best shot is "built by yourself&quot...

...upstools/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! > > Hi: > I got a new APC SRT3000XL and tested the new driver "apc_modbus". > the ups works fine with nut+apcupsd. the new driver "apc_modbus" has > result below: > > 1. upsrw can write the variable "battery.date". but the new value > will only show after restarting apc_modbus. and in my case the written > data will shift one...

...upstools/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! > > Hi: > I got a new APC SRT3000XL and tested the new driver "apc_modbus". > the ups works fine with nut+apcupsd. the new driver "apc_modbus" has > result below: > > 1. upsrw can write the variable "battery.date". but the new value > will only show after restarting apc_modbus. and in my case the written > data will shift one...

...linked from there as https://networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) should help you get started. Hoping for good news and no blocker issues, Jim Klimov PS: One known problem remains with the recently introduced apc_modbus driver and/or the libmodbus (core or our fork with rtu_usb branch) - that the USB connections tend to fall apart, as tracked at https://github.com/networkupstools/nut/issues/2609 and others linked from it - for now I've exhausted the hardware-less ideas and the time I had; help is welcome. ----...

...linked from there as https://networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) should help you get started. Hoping for good news and no blocker issues, Jim Klimov PS: One known problem remains with the recently introduced apc_modbus driver and/or the libmodbus (core or our fork with rtu_usb branch) - that the USB connections tend to fall apart, as tracked at https://github.com/networkupstools/nut/issues/2609 and others linked from it - for now I've exhausted the hardware-less ideas and the time I had; help is welcome. ----...

...file not found. XML search disabled. Cannot load AVAHI library (libavahi-client.so) : file not found. AVAHI search disabled. Scanning USB bus. No start IP, skipping NUT bus (old connect method) Scanning NUT simulation devices. [nutdev-usb1] driver = "usbhid-ups" # alternately: apc_modbus port = "auto" vendorid = "051D" productid = "0003" product = "Smart-UPS X 2200 FW:UPS 07.4 / ID=01003" serial = "AS2039254737" vendor = "American Power Conversion" # bus = &quo...

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>

...gt; > >> > 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! >> >> Hi: >> I got a new APC SRT3000XL and tested the new driver "apc_modbus". >> the ups works fine with nut+apcupsd. the new driver "apc_modbus" has >> result below: >> >> 1. upsrw can write the variable "battery.date". but the new value >> will only show after restarting apc_modbus. and in my case the written >&...

...gt; > >> > 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! >> >> Hi: >> I got a new APC SRT3000XL and tested the new driver "apc_modbus". >> the ups works fine with nut+apcupsd. the new driver "apc_modbus" has >> result below: >> >> 1. upsrw can write the variable "battery.date". but the new value >> will only show after restarting apc_modbus. and in my case the written >&...

...d. > Cannot load AVAHI library (libavahi-client.so) : file not found. AVAHI > search disabled. > Scanning USB bus. > No start IP, skipping NUT bus (old connect method) > Scanning NUT simulation devices. > [nutdev-usb1] > driver = "usbhid-ups" # alternately: apc_modbus > port = "auto" > vendorid = "051D" > productid = "0003" > product = "Smart-UPS X 2200 FW:UPS 07.4 / ID=01003" > serial = "AS2039254737" > vendor = "American Power Conversi...

.../networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) > should help you get started. > > Hoping for good news and no blocker issues, > Jim Klimov > > PS: One known problem remains with the recently introduced apc_modbus > driver and/or the libmodbus (core or our fork with rtu_usb branch) - that > the USB connections tend to fall apart, as tracked at > https://github.com/networkupstools/nut/issues/2609 and others linked from > it - for now I've exhausted the hardware-less ideas and the time I had; &...

.../networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) > should help you get started. > > Hoping for good news and no blocker issues, > Jim Klimov > > PS: One known problem remains with the recently introduced apc_modbus > driver and/or the libmodbus (core or our fork with rtu_usb branch) - that > the USB connections tend to fall apart, as tracked at > https://github.com/networkupstools/nut/issues/2609 and others linked from > it - for now I've exhausted the hardware-less ideas and the time I had; &...

...5-25 > battery.runtime: 22320 > battery.temperature: 24.69 > battery.voltage: 54.53 > device.mfr: American Power Conversion > device.model: Smart-UPS 2200 > device.serial: AS1848260180 > device.type: ups > driver.debug: 0 > driver.flag.allow_killpower: 0 > driver.name: apc_modbus > driver.parameter.pollinterval: 10 > driver.parameter.port: /dev/ttyS0 > driver.parameter.synchronous: yes > driver.state: quiet > driver.version: 2.8.1.1 > driver.version.internal: 0.10 > experimental.output.energy: 0 > input.transfer.high: 127 > input.transfer.low: 106...

...5-25 > battery.runtime: 22320 > battery.temperature: 24.69 > battery.voltage: 54.53 > device.mfr: American Power Conversion > device.model: Smart-UPS 2200 > device.serial: AS1848260180 > device.type: ups > driver.debug: 0 > driver.flag.allow_killpower: 0 > driver.name: apc_modbus > driver.parameter.pollinterval: 10 > driver.parameter.port: /dev/ttyS0 > driver.parameter.synchronous: yes > driver.state: quiet > driver.version: 2.8.1.1 > driver.version.internal: 0.10 > experimental.output.energy: 0 > input.transfer.high: 127 > input.transfer.low: 106...