similar to: Status OB (on battery) when polling a Liebert PSA

Displaying 20 results from an estimated 2000 matches similar to: "Status OB (on battery) when polling a Liebert PSA"

2014 Oct 17
2
Liebert PSA "On Battery" report
Hi, Back in 2011, it was reported that Liebert PSA devices persist in reporting OB (On Battery) when using usbhid-ups regardless of the actual state. Pier Paolo did some work (2011) which reportedly solved the issue. However, that doesn't seem to have reached mainstream and I now face the same problem. I'm using NUT 2.6.3 with a new Liebert PSA 1500Va that only ever reports OB and
2014 Oct 18
0
Liebert PSA "On Battery" report
Likely because 2.6.3 is not a current release. 2.7.2 (or 3?) is rhe current version, and it makes little sense to backport changes. Nut is a trivial compile . . . 'Use the source, Luke . . .' - Tim On October 17, 2014 6:05:35 PM CDT, Derek Harding <derek at lagham.org.uk> wrote: >Hi, > >Back in 2011, it was reported that Liebert PSA devices persist in >reporting OB
2014 Oct 18
0
Liebert PSA "On Battery" report
I guess it's kind of a natural response on my part, working professionally in software. T-Shooting step one: Get current and see if the problem persists. If it does,then step rwo: debug. 2+ years is forever in software, noting that 2.6.3 was mid 2012 . . . - Tim On October 17, 2014 9:38:15 PM CDT, Charles Lepple <clepple at gmail.com> wrote: >On Oct 17, 2014, at 8:31 PM, Tim Dawson
2014 Oct 18
2
Liebert PSA "On Battery" report
On Oct 17, 2014, at 8:31 PM, Tim Dawson <tadawson at tpcsvc.com> wrote: > Likely because 2.6.3 is not a current release. 2.7.2 (or 3?) is rhe current version, and it makes little sense to backport changes. Tim, It's possible that these changes didn't make it in. I admit that would be my knee-jerk reaction to seeing an older version number, but the last occurrence of
2023 Jul 18
0
Liebert PSA 1500 (500, 1000, 650, ...)
Hello The page https://networkupstools.org/ddl/Liebert/PSA_1500.html don't contain all information about UPS series PSA. First, the variable "*device.serial*" is dummy, it is always empty , and "*ups.serial*" also always empty. Second, configuration file for the all UPS "PSA" contain these lines: [PSA] ??? driver = "usbhid-ups" ?? ?port =
2014 Oct 18
2
Liebert PSA "On Battery" report
I downloaded latest source and it compiles ok but the original usbhid-ups.c is unchanged. Pier changed other files, too, and I don't know the changes needed. Simply substituting the modified (as per 2011) usbhid-ups gives a failed connection to the ups. So I have tried a little. I'll uninstall 2.6.3 and try to install 2.7.2 from a fresh compile. Thanks for the responses so far :-) --
2014 Oct 18
0
Liebert PSA "On Battery" report
This is the last post in the old thread: http://lists.alioth.debian.org/pipermail/nut-upsuser/2011-February/006651.html I'm marginally reluctant to install a non-standard release on a customer server because I may not be the next person to have to work on it, however, I do agree the most recent is usually the first port-of-call. Since it seems the fix didn't get followed through,
2009 Nov 10
1
[PATCH] Add support for Liebert PowerSure PSA to liebert-hid.c
This patch adds support for the following ups to liebert-hid.c: $ lsusb | grep Liebert Bus 007 Device 005: ID 10af:0001 Liebert Corp. PowerSure PSA UPS Using this patch, I'm able to obtain information about the ups via upsc: $ upsc upsname battery.charge: 100 battery.runtime: 1012 battery.type: PbAc battery.voltage: 1172 battery.voltage.nominal: 12 driver.name: usbhid-ups
2005 Aug 30
0
Liebert PowerSure PSA 500
[FAQ on USB-connected UPSes] > Remember: this is brand new *experimental* software and is probably > very broken. Do us a favor and report successes or failures to > the mailing lists. No problem ... : UPS: Liebert PowerSure PSA 500 NUT: Version 2.0.2 Kernel: 2.6.11.5, with CONFIG_USB_HID, CONFIG_USB_HIDINPUT, and CONFIG_USB_HIDDEV compiled in (statically)
2013 Aug 11
0
FW: Fwd: Liebert PSA UPS problem.
Anyone have any advice what I need to do next? Regards, Paul. -----Original Message----- From: Nut-upsuser [mailto:nut-upsuser-bounces+paul=smithp.co.uk at lists.alioth.debian.org] On Behalf Of Charles Lepple Sent: 02 August 2013 11:36 To: nut-upsuser list Subject: [Nut-upsuser] Fwd: Liebert PSA UPS problem. Begin forwarded message: > From: "Paul Smith" > Subject: Liebert PSA
2005 Dec 19
0
Liebert PowerSure PSA 500
Jochen Bern wrote: > > Peter Selinger wrote: > > have you been able to get your Liebert UPS to work? If I am correct, > > it should work with the newhidups Belkin subdriver. Could you please > > post your results? I am curious to know if this works or doesn't - and > > if yes, we should add permanent support for Liebert into NUT. > > I'm sorry, but
2013 Aug 02
2
Fwd: Liebert PSA UPS problem.
Begin forwarded message: > From: "Paul Smith" > Subject: Liebert PSA UPS problem. > Date: July 31, 2013 4:42:33 PM EDT > To: <nut-upsuser at lists.alioth.debian.org> > > Hi all, > A brief summary: > > I have a new Liebert PSA UPS which I wanted to help support my FreeNAS box (a FreeBSD 8 variant). Unfortunately the nut-ups implementation here for
2013 Sep 10
0
Fwd: Liebert PSA UPS problem.
Hi all, Sorry for the delay - three business trips abroad and LOTS of head scratching with USB Keys and DVD's of SuSE and FreeBSD... The question about the USB reports from Windows is still unanswered (I am abroad again !), but *think* the Liebert driver had been stopped. I can report the following updates for my linux setups; SuSE/FreeBSD/FreeNAS [remember here I am trying to make nut
2024 Mar 25
0
There is no voltage information
Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <
2024 Mar 25
0
There is no voltage information
Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <
2011 Sep 24
4
LiebertPSP
Apologies for resurrecting an old thread and likely poor formatting - I wasn't subscribed to the list at the time and have copied it out of the archives (http://lists.alioth.debian.org/pipermail/nut-upsuser/2010-July/006104.html). I've been unable to locate any further progress on this UPS (Liebert 10af:0001) - a thread from 2009
2013 Aug 11
2
Fwd: Liebert PSA UPS problem.
On Aug 11, 2013, at 12:04 PM, Paul Smith wrote: > Anyone have any advice what I need to do next? A while back, you sent me the pcap file from the Windows side, but there was an open question as to whether the USB requests were standard Windows HID driver requests, or whether the Liebert software was still running in the background. Also, the SuSE Live CD seems to be the only non-Windows
2024 Mar 21
0
There is no voltage information
Thanks again. So one more bit (other than indeed different libusb versions) that could potentially come into play is bitness - armv7l builds are 32-bit, right? One idea from here is to have you run the driver programs directly with high debug verbosity, e.g. `usbhid-ups -DDDDDD -s Liebert` to compare the two walls of text (at some debug level it spews byte data seen from libusb); this might
2005 Sep 07
3
Liebert PowerSure PSA 500
Hello everyone, Charles suggested (about a week ago) that I repost to this list. I took a moment to run some additional tests ... The basics: -- UPS: Liebert PowerSure PSA 500 (from the 230 VAC / 50 Hz line) -- Kernel: 2.6.11.5 (from sources), USB support (down to and including CONFIG_USB_HIDDEV) compiled in statically (not as a module) -- Rest of OS: Basically still from the original SuSE
2003 Nov 15
2
Special files and Cygwin
Hi, I'm trying to use rsync to backup a linux filesystem to a windows server. I followed the hints that I found at http://www.tiarnan.phlegethon.org/rsyncntdoc.html to run rsync on windows, and it works quite well. The only problem I found is that windows is not able to backup linux special files (/dev/*). I don't know if the problem is in the way rsync has been compiled, or simply in