search for: upsdriv

Displaying 5 results from an estimated 5 matches for "upsdriv".

Did you mean: upsdrv
2012 Mar 16
1
Centos 6.1, BNT400AP and immediate shutdown of ups
...lo. I just googled and tried some general news lists. There is hard to compose good question to google, cause shutdown and poweroff are standard ups jobs. Then. I've upgraded some computer Centos 5.3 to Centos 6.1. It is powered with Powercom BNT-400AP ups. A problem is, when I try to start upsdriver - powercom. While connecting to the ups (via ttyS) it (powercom driver) causes ups poweroff. Perfect black-out. UPS is going out. I tried to debug it connecting LCD instead of computer. LCD load is about 15 Watt. And then anything worked perfectly (upsmon, upssched, automatic shutdown etc.)....
2015 Sep 26
1
Incorrect values returned from usbhid-ups
...device.serial and ups.serial are both all zeroes? battery.mfr.date is ?CPS? rather than a date string? battery.voltage should indeed be higher than the nominal of 24.0 if they are being charged? It appears that incorrect data structure elements as returned by the UPS are being used in this usbhid-upsdriver. Of course, it?s possible that CyberPower is providing incorrect values to your driver. They sicced me onto you folks as a driver issue, not a UPS issue. Aren?t we lucky... THANKS for all your work! We out here in userland appreciate it! battery.charge: 100 battery.charge.low: 10 battery.charge...
2016 Oct 12
4
Data Stale at random intervals
On Oct 11, 2016, at 10:07 PM, Daniel Shields wrote: > > No joy. Reverted. A wrong number for the udev rules file would prevent the driver from starting at all due to permissions errors. It is possible that 52 and 62 are currently in the acceptable range. > > From: Daniel Shields <grungelizard9 at hotmail.com> > Sent: Tuesday, October 11, 2016 9:19 PM > To: nut-upsuser
2019 Nov 04
2
UPS not recognized
Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.serviceā—
2012 Mar 08
18
some fixes, improvements, and new features (EPO and DYING) for NUT
Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by