Thanks, Charles. I pulled your change and it fixed my segmentation
fault.
I discovered the following code at line 571 in usbhid-ups.c. This is
part of the "checking for alternatives" code:
if (!strcasecmp(cmdname, "shutdown.return")) {
int ret;
On Mar 20, 2018, at 11:53 AM, Ken Olum wrote:
>
> Hi, Charles. Are you by any chance planning to address my problems
> where NUT does not know how to schedule a shutdown of this Tripp-Lite
> UPS? If not, could you point me in the right direction? My best
>
Hi, Charles. Are you by any chance planning to address my problems
where NUT does not know how to schedule a shutdown of this Tripp-Lite
UPS? If not, could you point me in the right direction? My best
understanding of the situation of the moment is that the right control
is
From: Charles Lepple
Date: Tue, 23 Jan 2018 09:02:14 -0500
On Jan 22, 2018, at 3:00 PM, Ken Olum wrote:
>
> I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown
> using Tripp Lite's software, which appears to
On Jan 22, 2018, at 3:00 PM, Ken Olum wrote:
>
> I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown
> using Tripp Lite's software, which appears to be as follows:
>
Theoretically, this should be the same as running the command "upscmd
I tested the effect of setting UPS.OutletSystem.Outlet.DelayBeforeShutdown
using Tripp Lite's software, which appears to be as follows:
1. If you set it when the line power is on, it turns off the UPS after
the delay, and does not turn it back on again, even if you cycle the
line power.
2. If
From: Charles Lepple
Date: Thu, 11 Jan 2018 22:31:54 -0500
The trick will be adding support for this without breaking other
models.
For whatever it's worth, Tripp lite's software does not display the
model number anywhere, so it may be treating all models the
On Jan 11, 2018, at 3:14 PM, Ken Olum wrote:
>
> So I monitored the USB port with wireshark (an interesting endeavor
> since I didn't start out with any knowledge of USB protocols). But I
> have managed to discover that when I ask Tripp Lite's poweralert
> software to schedule a UPS shutdown, it
Thanks again for your help, Charles. I was able to install the Tripp
Lite software on my Ubuntu machine, and it sort of works. It does
something which continually changes the USB device ID of the UPS, and
prints voluminous error messages in the log. However, one of the things
that it can do is
On Dec 20, 2017, at 10:32 AM, Ken Olum wrote:
>
> 0.090564find_nut_info: unknown info type: load.on.delay
> 0.090577find_nut_info: unknown info type: load.on.delay
> 0.090585Initiating UPS shutdown
> 0.090593upsdrv_shutdown...
> 0.090601instcmd(shutdown.return,
Any more thoughts about how I might get this UPS working? I guess I
could try using the software from Tripp-Lite, but it is intended for
ancient versions of Fedora and OpenSUSE, whereas I'm running Ubuntu
16.04. It would be much nicer to use Nut, but I don't know how to
proceed.
Thanks.
Thanks for your help.
From: Charles Lepple
Date: Mon, 18 Dec 2017 19:26:56 -0500
This may sound like an apples-to-oranges comparison, but we did uncover an
issue with CyberPower UPSes where the delay values needed to be greater than or
equal to 60 (seconds), since
[please use reply-all to post to the list - the mailing list does not add a
reply-to header. thanks!]
On Dec 18, 2017, at 11:37 AM, Ken Olum wrote:
>
> I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu
> 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own
>
13 matches
Mail list logo