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 "PSA" in the drivers/ Git log is 2009.> 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 (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.Derek, Do you have a link to the message where the problem was solved?> I'm using NUT 2.6.3 with a new Liebert PSA 1500Va that only ever reports > OB and hence, when the power fails it doesn't trigger a shutdown (Ubuntu > 12.04 servers). Latching power fail through upsc works as it should.Not sure what you mean by "Latching power fail" - setting FSD through upsd?> Any advice would be gratefully received but I would prefer not to have > to rebuild/build. I don't mind replacing with a different, more up to > date usbhid-ups.It's hard to tell without seeing the results of upsc for the combination of your UPS and NUT version, but if you have a valid battery charge level, you can use the "ignorelb" setting to synthesize a low battery notification. -- Charles Lepple A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
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 <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 "PSA" in the drivers/ Git log is 2009. > >> 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 (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. > >Derek, > >Do you have a link to the message where the problem was solved? > >> I'm using NUT 2.6.3 with a new Liebert PSA 1500Va that only ever >reports >> OB and hence, when the power fails it doesn't trigger a shutdown >(Ubuntu >> 12.04 servers). Latching power fail through upsc works as it should. > >Not sure what you mean by "Latching power fail" - setting FSD through >upsd? > >> Any advice would be gratefully received but I would prefer not to >have >> to rebuild/build. I don't mind replacing with a different, more up to > >> date usbhid-ups. > >It's hard to tell without seeing the results of upsc for the >combination of your UPS and NUT version, but if you have a valid >battery charge level, you can use the "ignorelb" setting to synthesize >a low battery notification. > >-- >Charles Lepple > >A: Because it messes up the order in which people normally read text. >Q: Why is top-posting such a bad thing? >A: Top-posting. >Q: What is the most annoying thing on usenet and in e-mail?-- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141017/f1b9a4ff/attachment.html>
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 :-) -- Best wishes, Derek On 18 October 2014 16:03:09 GMT+13:00, Tim Dawson <tadawson at tpcsvc.com> wrote:>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 <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 "PSA" in the drivers/ Git log is 2009. >> >>> 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 (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. >> >>Derek, >> >>Do you have a link to the message where the problem was solved? >> >>> I'm using NUT 2.6.3 with a new Liebert PSA 1500Va that only ever >>reports >>> OB and hence, when the power fails it doesn't trigger a shutdown >>(Ubuntu >>> 12.04 servers). Latching power fail through upsc works as it should. >> >>Not sure what you mean by "Latching power fail" - setting FSD through >>upsd? >> >>> Any advice would be gratefully received but I would prefer not to >>have >>> to rebuild/build. I don't mind replacing with a different, more up >to >> >>> date usbhid-ups. >> >>It's hard to tell without seeing the results of upsc for the >>combination of your UPS and NUT version, but if you have a valid >>battery charge level, you can use the "ignorelb" setting to synthesize >>a low battery notification. >> >>-- >>Charles Lepple >> >>A: Because it messes up the order in which people normally read text. >>Q: Why is top-posting such a bad thing? >>A: Top-posting. >>Q: What is the most annoying thing on usenet and in e-mail?