search for: pr6000lcdrtxl5u

CyberPower Systems PR6000LCDRTXL5U http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/pp-series/PR6000LCDRTXL5U.html I had to create the following udev rule (on RHEL6): ATTR{idVendor}=="0764", ATTR{idProduct}=="0601", MODE="664", GROUP="dialout" Shutdown testing successful....

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 been running apcupsd, but if I go with the CyberPower unit I'll be installing NUT 2.7.4. Would anyone anticipate any possible...

...t; > (is the USBHID worth using?) It's hit-or-miss. I have a different CyberPower unit (no LCD, kind of like a big power strip) and there are some scale issues, similar to this entry: http://buildbot.networkupstools.org/~buildbot/docker-debian-jessie/docs/latest/ddl/Cyber_Power_Systems/PR6000LCDRTXL5U.html Also, there are some permissions issues on the /dev/bus/usb nodes that can be fixed, but they are annoying to track down if your distribution has a bad combination of NUT and udev versions. - - - Sounds like you are on the right track with the text protocol. There are two different sscanf(...

...gt; { USB_DEVICE(CPS_VENDORID, 0x0005), NULL }, > - /* Dynex DX-800U? */ > + /* Dynex DX-800U?, CP1200AVR/BC1200D, CP825AVR-G, CP1000AVRLCD, CP1000PFCLCD, CP1500C, CP550HG, etc. */ > { USB_DEVICE(CPS_VENDORID, 0x0501), &cps_battery_scale }, > /* OR2200LCDRM2U, OR700LCDRM1U, PR6000LCDRTXL5U */ > { USB_DEVICE(CPS_VENDORID, 0x0601), NULL }, > @@ -59,12 +66,48 @@ static usb_device_id_t cps_usb_device_table[] = { > { -1, -1, NULL } > }; > > +/*! Adjusts @a battery_scale if voltage is well above nominal. > + */ > +static void cps_adjust_battery_scale(doub...

...> bNumConfigurations = 0x0001 > > Right now, I selected " Cyber Power Systems ups 3 OR2200LCDRM2U USB (usbhid-ups)" in the dropdown menu, in order to shift away from powerpanel-driver to usbhid-driver. Thanks, good to know. PR6000LCDRTXL5U would probably also work. > However, when choosing this driver, freenas shows this log: > > Nov 10 23:04:45 storageunit upsd[17599]: mainloop: Interrupted system call > Nov 10 23:04:45 storageunit upsmon[17621]: upsmon parent: read > > I guess, interrupted system call shows up,...

On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: >> >>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage

On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: > >> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:

Dear Charles, thanks for your quick answer and your information! I didn't know there is a difference in the PR-series between old and new. So thanks for this valuable information! usbconfig dump_device_desc shows: ugen0.2: <CyberPower Systems product 0x0601> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA)

Hey all, I ended up picking up the module listed in Subject line. I switched over my config but apparently not all going smoothly. My config is: [office] driver = powerpanel port = /dev/ttyS0 desc = "Office UPS" When I test the driver running power-panel as a test, I get: > [root at cornelius init.d]# powerpanel -a office -D -D -D -D >