search for: pwrstat

On Mar 28, 2014, at 9:08 AM, Bill S wrote: > On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: > > <<Snip>> >> >> I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs.

On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: <<Snip>> > > I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V:

...make sure you have an up-to-date version of NUT. If this does not help, try running the driver with at least 'subdriver', 'vendorid' and 'productid' options specified. Please refer to the man page for details about these options (man 8 nutdrv_qx). 4. [root at mustang ups]# pwrstat -status The UPS information shows as following: Current UPS status: State........................ Lost Communication My ups.config has: [nutdev1] driver = "nutdrv_qx" port = auto vendorid = 0001 productid = 0000 b...

...aps there will be other problems with NUT? The /etc/killpower flag isn't deleted, for instance. I've attached the output of *usbhid-ups -DDD -a 2200LCD* as there seem to be several errors reported in there. I can see the subdriver doesn't find the serial number, for example, while the pwrstat code supplied by CyberPower does. Cheers, David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101216/8a8d89aa/attachment-0001.htm> -------------- next part -------------- Results for CyberP...