similar to: [HCL] Liebert GXT4-1500RT120 supported by usbhid-ups

On Jun 2, 2017, at 8:28 AM, zefanjas <nut at zefanjas.de> wrote: > I couldn't get the GXT4 working with usbhid-ups driver. So I need some > advise to continue to get this device working. The GXT3 seems to be > working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). > > Here is my ups.conf > > [ups] > driver = usbhid-ups > port =

Hello, we have a Emerson Liebert GXT4, that we like to connect to our servers to shut them down if there is a power failure (which happens quite often in our area). I couldn't get the GXT4 working with usbhid-ups driver. So I need some advise to continue to get this device working. The GXT3 seems to be working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). Here is my

Hi, thanks for your helpful reply. I've added the productid in the ups.conf and it seems to work (better) now. > After starting the driver and upsd, what does "upsc ups" return? If you can also include "upsrw ups" and "upscmd -l ups" output, we can update the DDL. #upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 20

Hi UPS List members, I have purchased a number of Emerson Power / Liebert GXT4 UPS units. I have these working correctly under nut, but limited detsils are being reported. I am happy to supply information on the USB communications to improve the reported details I can use WireShark to capture the comms between the supplied Windows GUI tool and the UPS Please advise the best way I can

On Jun 4, 2017, at 8:32 PM, zefanjas <nut at zefanjas.de> wrote: > > Hi, > > thanks for your helpful reply. I've added the productid in the ups.conf > and it seems to work (better) now. > > >> After starting the driver and upsd, what does "upsc ups" return? If you can also include "upsrw ups" and "upscmd -l ups" output, we can

Hi, >> #upsc ups >> >> Init SSL without certificate database >> battery.charge: 100 >> battery.charge.low: 20 >> battery.charge.warning: 0 >> battery.type: PbAc >> battery.voltage: 1.0 >> battery.voltage.nominal: 0.0 > > Similar to Mike's report on the CPS UPS, the HID descriptor for this device is buggy: > > Logical

I have a device that seems almost, but not quite supported, I'd like very much to help get it working, though I am no programmer. Feel free to ask me to test :) This could probably go in https://networkupstools.org/ddl/ : -------file: Salicru__SPS_2000_ADV_T__usbhid-ups__2.8.1-94-gd59c05349__01.dev , or maybe 1__2000__usbhid-ups__2.8.1-94-gd59c05349__01.dev # DEVICE:URL:VENDOR:

Cleanline L-1000C upsc output: Init SSL without certificate database battery.charge: 100 battery.voltage: 13.2 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.type: ups driver.debug: 0 driver.flag.allow_killpower: 0 [driver.name](http://driver.name/): nutdrv_qx driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.

Jim Klimov <jimklimov+nut at gmail.com> > > 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? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

Jim Klimov <jimklimov+nut at gmail.com> > > 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? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

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

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

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

Hi, [ There is also a github issue about this here: https://github.com/networkupstools/nut/issues/2347 ] I have an APC Back-UPS BX1600MI purchased in January, attached by its supplied USB cable to a Debian 10 machine. Initially using the nut packaged in Debian 10 (2.7.4-8) this was unusable as the usbhid-ups driver kept disconnecting every few seconds. I upgraded to the git HEAD of nut and

Good morning, I just had the chance this morning to get my linux box tied into our network and talking to the UPS. I can now confirm that in NUT v2.4.3 snmp-ups (ietf) works with the Liebert Intellislot Web Card for the GXT2 family of UPS'. upsc output: tux ~ # upsc workups at localhost battery.charge: 100.00 battery.runtime: 2760.00 battery.runtime.low: 5 battery.voltage: 54.60 device.mfr: