search for: pr1500lcdrt2u

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 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 configured correctly or existing at all. I...

...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 test cases. Please correct me if I'm wrong: 1) NAS4Free + NUT 2.7.3 + PR1500LCDRT2U = bad HID report descriptor 2) NAS4Free + usbconfig + PR1500LCDRT2U = good HID report descriptor 3) CentOS 6.7 + NUT 2.7.3 + PR1500LCDRT2U = works 4) FreeBSD + NUT 2.7.3 + CP900VR = works Short of trying all of the combinations, I'd say the most worrisome part is the difference between 1) and...

I'm trying to access a Cyber Power PR1500LCDRT2U via the serial port (because I need the use the USB connection for a windows machine), but not having any luck with the powerpanel driver. Any other suggestions? Thanks! -- Orion Poplawski he/him/his - surely the least important thing about me Manager of IT Systems 720-772...

...sage ----- > From: "Charles Lepple" <clepple at gmail.com> > To: "Joseph Gzesh" <louis at frentzgzesh.info> > Cc: nut-upsuser at lists.alioth.debian.org > Sent: Thursday, September 24, 2015 10:59:12 PM > Subject: Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U > > 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...

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 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

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: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 >> > >>

...rver. ----- Original Message ----- From: "Charles Lepple" <clepple at gmail.com> To: "Joseph Gzesh" <louis at frentzgzesh.info> Cc: nut-upsuser at lists.alioth.debian.org Sent: Wednesday, September 23, 2015 8:04:37 PM Subject: Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U 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? (Proba...

...rver. ----- Original Message ----- From: "Charles Lepple" <clepple at gmail.com> To: "Joseph Gzesh" <louis at frentzgzesh.info> Cc: nut-upsuser at lists.alioth.debian.org Sent: Thursday, September 24, 2015 10:59:12 PM Subject: Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U 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...

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) When i plug the same UPS into CentOS 6.7, It works as expected. I am not sure what the difference between the NUT versions other than the base OS would be.

...set up your own Zimbra server. From: "Charles Lepple" <clepple at gmail.com> To: "Joseph Gzesh" <louis at frentzgzesh.info> Cc: nut-upsuser at lists.alioth.debian.org Sent: Tuesday, September 22, 2015 8:06:33 PM Subject: Re: [Nut-upsuser] FreeBSD backed with a PR1500LCDRT2U 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...

...B communication driver 0.33 > No matching HID UPS found > Driver failed to start (exit status=1) Annoyingly, the USB listeing is for a PR1500 even though it really IS an OR500 > [root at delp ups]# lsusb -d 0764:0601 -v > > Bus 006 Device 002: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS > Device Descriptor: >   bLength                18 >   bDescriptorType         1 >   bcdUSB               1.10 >   bDeviceClass            0 >   bDeviceSubClass         0 >   bDeviceProtocol         0 >   bMaxPacketSize0         8 >   idVendor           0x0764 Cyber P...

...atching HID UPS found >> Driver failed to start (exit status=1) > > > Annoyingly, the USB listeing is for a PR1500 even though it really IS an OR500 > >> [root at delp ups]# lsusb -d 0764:0601 -v >> >> Bus 006 Device 002: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS ^ that is based on the usb.ids database, not what the UPS returns. All of the CPS UPSes seem to be either 0501 or 0601. >> iProduct 1 UPS OR500 ^ this model string (the part after "1") comes from the UPS itself. > > What else can I provide to help deb...

O.S.: Linux LMDE 3 "Cindy" Linux Kernel: 4.9.0-12-amd64 NUT Version: 2.4.7-5 Installed from: Debian package Driver in use: usbhid-ups UPS device: Powerwalker Basic VI 1500 STL. Identifies as Cyberpower PR1500LCDRT2U UPS VendorID 0764 ProductID 0601 Product URL: https://powerwalker.com/?page=product&item=10121076&lang=en Manufactured: 2019 Problem: I have been struggling for several weeks now to get these devices working satisfactorily. I purchased 2 of the units bec...