similar to: FreeBSD backed with a PR1500LCDRT2U

>> >> I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) > >Which version of FreeBSD is this based on? I also included the Motherboard and processor so if there is anything those

On Sep 25, 2015, at 9:21 AM, Louis G. <louis at frentzgzesh.info> wrote: > > For what it is worth, I also have a Cyber Power CP900AVR laying around that I can test with. That could certainly help narrow down whether it is a problem with the UPS or with the OS. -- Charles Lepple clepple at gmail

----- On Sep 23, 2015, at 9:26 AM, Charles Lepple clepple at gmail.com wrote: > On Sep 23, 2015, at 9:22 AM, Louis G. <louis at frentzgzesh.info> wrote: >> >> >Can you open up a root shell, kill the old `usbhid-ups` process, and run it from >> >the command line? >> > >> > /usr/local/libexec/nut/usbhid-ups -a ups -DDD >> > >>

> >> usbconfig -u 4 -a 2 dump_curr_config_desc > > Here is output of the command. Thank you for your help with this. > > ugen4.2: <product 0x0601 CyberPower Systems> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA) > [...] > bLength = 0x09 > bDescriptorType = 0x21 > bDescriptorSubType = 0x10 >> RAW dump: >> 0x00 | 0x09, 0x21,

>> >> The output was also not as big as you made it out to be. > > Well, I didn't expect the driver to fail *that* badly :-) > > Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) > > usbconfig -u 4 -a 2 dump_curr_config_desc Here is output of the command. Thank you for

On Sep 22, 2015, at 1:43 PM, Louis G. <louis at frentzgzesh.info> wrote: > > I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) Which version of FreeBSD is this based on? > When i plug the

On Oct 9, 2015, at 8:19 AM, Louis G. <louis at frentzgzesh.info> wrote: > > Charles, > > That was the PR1500LCDRT2U on the FreeBSD. I have not tried the CP900VR on the FreeBSD box yet. I can tell you that the CP900VR does work as expected on the Nas4Free one though. I am thinking it is the way the driver parses the USB hex identifier. There might be a filter that is not

Charles, For what it is worth, I also have a Cyber Power CP900AVR laying around that I can test with. Joe Gzesh Sent from Zimbra Open Source Mail Server. Hosted at my House. Ask me how to set up your own Zimbra server. ----- On Sep 25, 2015, at 7:34 AM, Joseph Gzesh louis at frentzgzesh.info wrote: >> >>> usbconfig -u 4 -a 2 dump_curr_config_desc >> >> Here is

On Oct 8, 2015, at 9:55 PM, Louis G. <louis at frentzgzesh.info> wrote: > > I finally got the FreeBSD box up and running. I can do testing now when you have time. I have ran through the tests that you asked me to do previously and attached them here. Let me know what you find. Thank you. The CyberPower HID report descriptor looks fine, but I think I'm losing track of the various

On Sep 23, 2015, at 9:39 AM, Louis G. <louis at frentzgzesh.info> wrote: > > The output was also not as big as you made it out to be. Well, I didn't expect the driver to fail *that* badly :-) Assuming the UPS is still at /dev/ugen4.2, can you try the following command? (Probably needs to be run as root, with the driver stopped.) usbconfig -u 4 -a 2 dump_curr_config_desc --

On Sep 24, 2015, at 10:28 AM, Louis G. <louis at frentzgzesh.info> wrote: > >> usbconfig -u 4 -a 2 dump_curr_config_desc > > Here is output of the command. Thank you for your help with this. > > ugen4.2: <product 0x0601 CyberPower Systems> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA) > [...] > bLength = 0x09 > bDescriptorType =

On Sep 23, 2015, at 9:22 AM, Louis G. <louis at frentzgzesh.info> wrote: > > >Can you open up a root shell, kill the old `usbhid-ups` process, and run it from the command line? > > > > /usr/local/libexec/nut/usbhid-ups -a ups -DDD > > > >(Adjust the "-a ups" for the name that NAS4Free uses.) > > > >It will indefinitely, but we only

I have the same issue of incorrect output voltage being reported by usbhid-ups, as run on NAS4Free (FreeBSD). UPS is as shown below. There is a thread on this list from 2014 that has these same issues, apparently never addressed by any of the later usbhid-ups releases. I?m using 2.7.3. The value I am especially concerned with is the output voltage; if ANY thing should be right on the report, it?s

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm in the process of upgrading my solution to spread the load over two ups'es. Both are Cyberpower, where one is the classic "Intelligent" 1500LCD, the other a "Value" 2200E Both connect via UPS, and both work using the ups-hid driver. So far so good. The idea is to connect both of them via USB to the same FreeBSD 8

OS = NAS4Free (FreeBSD Revision: 199506) NUT Version = 2.7.3 for other parts of NUT version is listed below NUT is part of the NAS4Free distribution Device = Tripp Lite SMART1300LCDT URL http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/ PROBLEM: NUT is ABLE to see the UPS BUT it is not getting the right(?) descriptor? I am using

[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

I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

I'm playing with a new CentOS 8 with a cyperpower OR500 (a smaller sibling to the OR700) plugged in via USB. GNOME sees the UPS... but NUT does not (even if I shut down gnome). > [root at delp ups]# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > No matching HID UPS found

Hello, I am having a heck of a time with false low battery alarms right now.  It has been going on for the last couple of months.  I originally started getting them with a UPS that was 1-2 years old so I thought it was time to change it out and buy a new one.  I'm still getting the false alarms with the brand new one.  The status is "OL LB" which is strange to me. I have a