[Nut-upsuser] Cyber power CP1500AVR required pollonly?

[gene heskett]

On Monday, 6 June 2022 12:15:10 EDT Dave Williams wrote:
> IMHO adding to the logging to suggest pollonly would be a good start.
> I wouldnt advocate changing on the fly - thats likely to lead to
> instability or confusion.
> 
> On my CP900EPFCLCD I need to run pollonly albeit when connected to old
> USB 1.5 ports. I thought it was the port not the UPS that was the
> problem - maybe I was jumping to conclusions.
> 
> Dave
> 
> On 17:30, Mon 06 Jun 22, Jim Klimov via Nut-upsuser wrote:
> > According to issues discussed over the past year or so on github,
> > seems so - that at least some models and/or OSes and/or chipsets
> > have a problem with libusb interrupt mode; more often failing during
> > device discovery than after some successful uptime.
> > 
> > I don't think there was reliable statistics to incriminate certain
> > situations enough to hardcode some preferences however.
> > 
> > Maybe it could help generally to at least log the suggestion for
> > pollonly (or interruptonly) when the preferred method fails. Or at
> > best try to change the preference on the fly if not bolted by
> > explicit config. Question to community: would such change
> > (especially if also of default behavior) be beneficial?
> > 
> > Jim

Jim: since cyberpower seems to operate in their own local vacuum and the 
-torr rating varies with every different model, I'd say that using your 
bully pulpit as the defacto standard to encourage a more co-operative 
attitude might be productive. But it won't happen overnight.  They've got 
more lawyers than techs.

I'll use the $39.90 at Tiger Direct, CP-650 I hve running a pi as an 
example, load registers as 8% (when it even deigns to show it) but the 
shutdown time is fixed at 2 minutes but the battery at 2 minutes is still 
99.9% charged. With that reprogrammed, it could probaly run that pi for a 
couple hours. Fortunately for the pi, my standby is making usable power 5 
seconds after the lights go out. Uptimes depend on me, not the power 
supply.

> > On Sat, Jun 4, 2022, 19:16 Selva Nair via Nut-upsuser <
> > 
> > nut-upsuser at alioth-lists.debian.net> wrote:
> > > Ubuntu 22.04
> > > NUT 2.7.4
> > > CYberPower CP1500AVRLCDa  using usbhid-ups
> > > 
> > > Hello,
> > > 
> > > The above combination works well for a few minutes -- including
> > > shutdown on pulling power or on upsmon -c fsd, notifications etc.
> > > Until the driver starts reporting error in libusb_get_string,
> > > kernel messages on USDEVFS_CONTROL failures and upsmon logs 'Data
> > > stale'
> > > 
> > > It seems the UPS does not support interrupt transfer (or is buggy).
> > > On
> > > adding pollonly=enabled to ups.conf, everything appears to be
> > > working
> > > fine again.
> > > 
> > > Is this a known issue? I have seen a number of success reports on
> > > this
> > > model, none mentioning the need for pollonly, so wondering whether
> > > I
> > > should troubleshoot this further.
> > > 
> > > Thanks,
> > > 
> > > Selva
> > > 
> > > _______________________________________________
> > > Nut-upsuser mailing list
> > > Nut-upsuser at alioth-lists.debian.net
> > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuse
> > > r
> > 
> > _______________________________________________
> > Nut-upsuser mailing list
> > Nut-upsuser at alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> .


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis