stefa...@karandreas.gr wrote:
> Can you share a link to where the manual describes ups.delay.start? I
> found
> some information but not the complete description you mention here.
> For ondelay=0 what happens? The load instantly returns on UPS shutdown
> or the bug doesn't trigger?
Hi Stefanos,
On 2022-06-05 09:06, Phil Chadwick wrote:
Hi,
I have a CyberPower CP1500EPFCLCD.
I live in a rural location and experience frequent power failures.
I run a nut server on a FreeBSD host named "sherman". It has a USB
connection to the CP1500EPFCLCD, using the usbhid-ups driver. I don't
use
n
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
On 6/5/2022 7:16 AM, Charles Lepple via Nut-upsuser wrote:
> [snip]
>
> Updates to the DDL can be requested here:
>
>https://github.com/networkupstools/nut-ddl/issues
>
I was not aware of that repository.
Thanks for the pointer...
___
Nut-ups
Hi,
Thanks for the followup.
A hint about pollonly option in the logs would be very helpful.
Automatically changing the mode could be hard to get right and may not
be the proper thing to do in some situations. It would also make
troubleshooting harder if the driver uses options contrary to what i
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
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
