search for: 3aopen

I'm looking at switching from an APC UPS to a different brand after having had my third SU3000RM in a row blow up power transistors. I'm looking at the Cyperpower PR3000LCDRTXL2U. I see the PR3000E and the PR6000LCDRTXL5U listed as supported, but not the PR3000LCDRTXL2U. Howeverit seems likely that if the PR6000LCDRTXL5U is supported, the PR3000LCDRTXL2U ought to work as well. I've

Looking at the project site the latest Windows Binary is a few back - 2.6.5.6 Has any one built a more recent version that they can upload and update the Project site ? Looking for Windows 7 / Windows 8, not running Windows 10 on any of my tool Laptops and I need to check some battery packs and overall status on a series of UPS units in shelters, The build 2.6.5.6 gives my grirf in a number of

On 1/27/19 9:13 PM, Charles Lepple wrote: > On Jan 27, 2019, at 2:36 PM, Phil Stracchino <phils at caerllewys.net > <mailto:phils at caerllewys.net>> wrote: >> The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power >> factor, considers this same load to be 43% load. >> >> I wasn't expecting that much of a reduction. > > So... 50%

...n NUT SVN trunk (now Git master branch) during development, so it is effectively stuck at 2.6.5.x. There was talk of rewriting the Windows compatibility layer for later versions of NUT. Some status is scattered across the following GitHub issues. https://github.com/networkupstools/nut/issues?q=is%3Aopen+is%3Aissue+label%3AWindows If your issue is mostly with USB, you might consider using an embedded Linux system as a NUT server, and running NUT 2.6.5-6 or ntUPSd on the clients. Also, if you know of anyone willing to help out with the NUT Windows port, that would be most useful. (The intent is to...

...battery alert, then there is a good chance that the PR3000LCD* models are all supported equally well by the usbhid-ups driver. However, you may want to check the issue list if you are planning to depend on another threshold for shutdown: https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 Also, you mentioned serial monitoring. I am not as familiar with serial CyberPower models, but take note of the support description here: https://networkupstools.org/docs/man/powerpanel.html#_support_status Most of the serial-connected CPS models have lower com...

...ause there's only two back-panel USB ports on this server and I now > need three (KVM, GPS receiver, and UPS). You might be lucky with this particular model, but definitely beware of the USB issues I mentioned in another thread: https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 The output of upsc is sorted alphabetically by key, so it isn't immediately obvious which values come from earlier in the report descriptor. However, after the values for input.transfer.low and input.transfer.high, the other values might end up being scaled t...

...have a number of CyberPower issues whose root cause is a disagreement as to how the HID descriptor (and therefore, the HID reports) should be parsed and interpreted. Link to the whole mess (which includes some other non-HID CPS issues): https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 That said, I don't think that differing load when on/off AC is going to fall into the HID category, but there are certainly a lot of open questions surrounding some of the reported values. As Roger suggested, doing a manual self-test on the batteries may be...

On 1/27/19 9:49 PM, Charles Lepple wrote: > You might be lucky with this particular model, but definitely beware of the USB issues I mentioned in another thread: > > https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 > > The output of upsc is sorted alphabetically by key, so it isn't immediately obvious which values come from earlier in the report descriptor. However, after the values for input.transfer.low and input.transfer.high, the other values might end up bein...

[shutdown sequence] I have tested and verified the shutdown sequence works. [manufacturor] https://www.cyberpowersystems.com/product/ups/ec350g/ mbeisser at nas:~$ upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1575 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 9.3

To those interested in AVR backend additions to LLVM, the LLVM review tools "Phabricator" ( don't ask me to say that 3 times fast ), allows easy searching. Go to http://reviews.llvm.org/ and type in AVR in the search entry. This will give you a list of the commits, and resolutions. From my understanding ( NO Expert ), a large part of the skeleton code has been added. The leave

On 2019-12-17 06:18, Roger Price wrote: > > I definitely need to check that the vile daemon is present and running. > > In upsmon.conf there are no NOTIFYFLAG declarations, especially for events > ONBATT and LOWBATT. When ONBATT and LOWBATT occur nothing will happen. There > are no NOTIFYMSG declarations and in particular no messages for the ONBATT and > LOWBATT events.

I've searched the listserv archive, to no avail, so I hope I'm not duplicating a previous problem. I am anxious to get this working, so I'm open to uninstalling what I have and starting over. One note which may not be meaningful is that this UPS pre-dates the Raspberry Pi I've got connected to it, and I used to use it with the CyberPower software, which requires logging in with a

...ve > multiple network interfaces, firewall rules are probably a better place to > exclude one or more of the interfaces. > > Note also that the CyberPower UPSes have a number of mostly cosmetic > errors in the output: > https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 > < > https://github.com/networkupstools/nut/issues?q=is:issue+is:open+label:%22CyberPower+(CPS)%22 > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://alioth-lists.debian.net/pipe...