On Mar 18, 2015, at 3:57 AM, Philip Taylor <[email protected]> wrote:
> Charles, to your specific points : > >> The other HID drivers seem to trigger shutdown by writing to the various >> timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to >> have UPS.PowerSummary.PresentStatus.ShutdownRequested, which according to >> the HID PDC spec, is read/write. I wonder if the firmware responds to this? > > So are you suggesting if I modify openups-hid.c to include this specific > command as an instant command, it may respond? I could give it a try if you > confirm that’s what you mean. It's a thought. Looking further into the code, I'm not sure how well usbhid-ups will handle writing to a single bit, since the reports are collections of bytes. And it would depend how the firmware interprets it (if it is writable at all). >> Out of curiosity, which notifications? In the openups_drv_start_onbatt log, >> the PresentStatus values look the same as the online log. Or do you mean you >> got that from the ignorelb configuration? > > The notifications are : ONLINE ONBATT FSD COMMOK COMMBAD SHUTDOWN (following > FSD from command line). I believe it notified LOWBATT too when I used > ignoreLB and over-rode battery.charge.low. But I’ve never seen the OpenUPS > notify LB via USB. If I use the scenario I proposed I would monitor > battery.voltage by polling the online log. Maybe it took a little while longer to get the ONBATT status; in both of the logs you sent, ACPresent is 0.01 (more scaling issues, but the code only cares about zero or nonzero). > I’m a little surprised that I seem to be the only person interested in this > issue - as some others were interested in the OPENUPS2, in fact you added it > to the ‘supported devices’ list fairly recently. I think the inclusion of the > OpenUPS as ‘fully supported’ in the hardware compatibility list over-states > the capabilities! Well, we did add the openups2 recently, but it was mainly because it requires a different set of scale values to fix the voltage and current readings. "Supported" is an overloaded term. I would agree that given what we know now, the Hardware Compatibility List (HCL) rating of five stars for the openUPS is a bit optimistic. But that was updated in 2012 when the first patches came in, and it was more of a tip-o-the-hat to Mini-Box for providing the driver for NUT. The idea with the Device Dump Library (DDL) was to provide more quantitative information as to what people can expect from a given combination of UPS and NUT: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/Mini-Box.com/OPEN-UPS.html We might consider adding a warning if the UPS does not support basic commands such as shutdown, although we can't do that automatically now, since some of the older dump files simply do not contain the list of commands (even if they support them) since they were collected from mailing list posts. > Thanks once again., you have been most helpful. You're welcome! -- Charles Lepple clepple@gmail
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
