So where does this leave things regards Eaton and shut down? Has anyone managed graceful shut down from an Eaton unit with either of the ushhid or bcmxcp drivers? Perhaps I should be coming at this from the other end of the stick. What manufactures have the best support in NUT that I can look at and be confident I'm likely to have a successful deployment? Really the only deal breaker for me is graceful shut down communications with Debian servers and/or an exorbitant price. Maybe I missed some replies but I'm still not sure if anyone has been able to actually do this. thanks again for the input. *Paul O'Rorke* On 9/19/2013 8:32 AM, Luke-Jr wrote:> On Thursday, September 19, 2013 7:16:23 AM Chris Boot wrote: >> Eaton actually employs the NUT project lead, Arnaud Quette, so yes it's >> safe to say someone is working on NUT and the bcmxcp driver. > If that's the case, I'm hopeful that NUT will gain support for these > fundamental expectations (mainly battery level/runtime) on Eaton devices, and > that I will then be very glad to have purchased a unit that > actively/financially supports the NUT team. > > Luke > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130919/e6354ce3/attachment.html>
On Sep 19, 2013, at 12:11 PM, Paul O'Rorke wrote:> So where does this leave things regards Eaton and shut down? Has anyone managed graceful shut down from an Eaton unit with either of the ushhid or bcmxcp drivers?Generally speaking, the UPS will signal when it reaches a low battery state, regardless of whether the UPS publishes runtime statistics, battery percentages, or any other such values. The real difference between a "smart" and "dumb" UPS is not just the protocol, but how advanced the battery monitoring and charging circuitry is. I have an old MGE UPS that uses the usbhid-ups driver, and I have no problems shutting down the system via the LB signal in NUT. The non-Powerware-based Eaton units can be considered "descendants" of this hardware, from what I understand, and provide similar variables. (Note that I am not affiliated with Eaton. Along those lines, the developers of NUT would not know if a new Eaton model would not work with NUT until someone reports it to the mailing list, but that has not been an issue to date.) Alf has already commented on the bcmxcp side. -- Charles Lepple clepple at gmail
On 9/19/2013 at 10:49 PM Charles Lepple wrote: |On Sep 19, 2013, at 12:11 PM, Paul O'Rorke wrote: | |> So where does this leave things regards Eaton and shut down? Has anyone |managed graceful shut down from an Eaton unit with either of the ushhid or |bcmxcp drivers? | |Generally speaking, the UPS will signal when it reaches a low battery |state, regardless of whether the UPS publishes runtime statistics, battery |percentages, or any other such values. The real difference between a |"smart" and "dumb" UPS is not just the protocol, but how advanced the |battery monitoring and charging circuitry is. | |[snip] ============ Maybe we need a semantic sync-up here. When I think of "graceful shut down" from a UPS, I think of the following sequence occurring reliably: 1) the UPS signals the NUT software that the battery is low 2) The NUT software tells the UPS to shutdown after some [hopefully, configurable] number of seconds. 3) the NUT software shuts down the system(s) dependent upon tht UPS. The number of seconds specified in (2) is dependent upon how long the system(s) take to shut down. 4) the UPS then shuts down at the specified time.>From what I've seen, step (2) is the stickler for many (most?) UPS's.I'd like to see the ~shutdown after some [hopefully, configurable] number of seconds~ capability noted on any compatibility list that is generated. My $0.02 Thanks!
Charles Lepple wrote, On 9/19/2013 7:49 PM:> On Sep 19, 2013, at 12:11 PM, Paul O'Rorke wrote: > >> So where does this leave things regards Eaton and shut down? Has anyone managed graceful shut down from an Eaton unit with either of the ushhid or bcmxcp drivers? > Generally speaking, the UPS will signal when it reaches a low battery state, regardless of whether the UPS publishes runtime statistics, battery percentages, or any other such values. The real difference between a "smart" and "dumb" UPS is not just the protocol, but how advanced the battery monitoring and charging circuitry is. > > I have an old MGE UPS that uses the usbhid-ups driver, and I have no problems shutting down the system via the LB signal in NUT. The non-Powerware-based Eaton units can be considered "descendants" of this hardware, from what I understand, and provide similar variables.I was able to change battery.charge.low to 50 (*) on an Evolution 850. I tested that the setting took, even if the UPS was rebooted. Because it's powering Win2k3, I changed the offdelay to 600 and the ondelay to 615. I then disabled the beeper. It all works, so I'm pretty happy with the driver capability with this UPS. Driver: usbhid-ups. (*) You don't have to neccessarily use a timeout script to keep from draining the battery.