search for: bcpers450

[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 > /lib/systemd/system-shutdown/nutshutdown, but now everything is working > except for powering on and off the UPS. Regardless of the settings of > offdelay and ondelay in upsconf, and r...

...ould be useful. For completeness, would you mind sending the output of "upsrw" and "upscmd -l"? Below. Thanks again for your help. I will be away until Monday afternoon, so please forgive delay in answering e-mails. Ken % upsrw bcpers450 at localhost [ups.delay.shutdown] Interval to wait after shutdown with delay command (seconds) Type: STRING Maximum length: 10 Value: 200 % upscmd -l bcpers450 at localhost Instant commands supported on UPS [bcpers450]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper...

...things up to rebuild the driver? I was able to build it following your directions. Some things went in the same place as the Ubuntu packages had used, but others did not, so I removed the Ubuntu packages, and installed from source. Most things seem to work, though "/lib/nut/usbhid-ups -a bcpers450 -k" now gets a segfault instead of doing the (wrong) thing it did before. Ken

On Jan 22, 2018, at 3:00 PM, Ken Olum <kdo at cosmos.phy.tufts.edu> 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 bcpers at localhost -u <upsd.user> load.off.delay <delay>". >

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 to schedule a UPS shutdown, which Nut does not know how to do. So I monitored the USB port with

On Dec 20, 2017, at 10:32 AM, Ken Olum wrote: > > 0.090564 find_nut_info: unknown info type: load.on.delay > 0.090577 find_nut_info: unknown info type: load.on.delay > 0.090585 Initiating UPS shutdown > 0.090593 upsdrv_shutdown... > 0.090601 instcmd(shutdown.return, [NULL]) > 0.090614 find_nut_info: unknown info type: shutdown.return > 0.090624

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 does it by using the SET_REPORT > function of the USB HID protocol with

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 you set it when the UPS is running on battery, wait for the UPS to turn off, and turn back on the

On Mar 20, 2018, at 11:53 AM, Ken Olum <kdo at cosmos.phy.tufts.edu> 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 > understanding of the situation of the moment is that the right control > is

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; /* Ensure "ups.start.auto" is set to "yes", if supported */ if

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 UPS.OutletSystem.Outlet.DelayBeforeShutdown but that NUT does not know to use that. Thanks.

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 /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether...

...r seen ups.timer.shutdown change from the value above. After shutting off the load, ups.timer.reboot changes to 10, regardless of the setting of driver.parameter.ondelay. It then counts down to 0 and turns the load back on. What log messages do you get with "/lib/nut/usbhid-ups -DD -a bcpers450 -k"? See below. For future reference, was this UPS manufactured recently? I have just purchased it new, so presumably yes. Ken ---------------------------------------------------------------------- # /lib/nut/usbhid-ups -DD -a bcpers450 -k Netw...

Hi, Layne. I had a similar problem with my Tripp-Lite BCPERS450. You can see the previous correspondence by searching for site:alioth-lists.debian.net/pipermail/nut-upsuser BCPERS450 shutdown with Google. In particular, I fixed (well, worked around) the problem, as I wrote in https://alioth-lists.debian.net/pipermail/nut-upsuser/2018-March/011082.html I...

...is might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan 2, 2020, 11:38 AM Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: > Hi, Layne. I had a similar problem with my Tripp-Lite BCPERS450. You > can see the previous correspondence by searching for > > site:alioth-lists.debian.net/pipermail/nut-upsuser BCPERS450 shutdown > > with Google. > > In particular, I fixed (well, worked around) the problem, as I wrote in > > https://alioth-lists.debian.net/pipermai...

When running 'sudo upsmon -c fsd' UPS turns off then back on after a delay as expected. But when power is disconnected and the command is ran, the UPS turns off but still turns back on again. Changing 'ondelay' to -1 or 0 does not change the behavior. How can I get the UPS load to stay turned off if there is no power? Or am I misunderstanding how to test this functionality?

.... Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ______________________________________________________________________ Hi, David. Thanks for the offer of help. I have BCPERS450 serial number 2701DVHBC809300177. Unfortunately I'm about to go on a trip and will be away until the end of the month, so I don't have much time to discuss these things at the moment, but maybe Layne will have something to say. My understanding from when I was working on this a couple yea...

If you'd like, shoot me over your serial number and the corner-cases you don't have answers for and I can look into it. Thank you, David Zomaya Tripp Lite david_zomaya at tripplite.com -----Original Message----- From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> On Behalf Of Ken Olum Sent: Tuesday, January 14, 2020 11:24 AM To: Layne

I have a TrippLite AVR550U that my company uses several individual Linux boxes in one large system, all running Ubuntu 18.04LTS, and all will be using the package version of nut - 2.7.4. In my scenario, our usage case is for the PCs to all shut down, followed by the individual UPSes, when mains power is removed from the whole system. (This isn't a typical setup for UPS, but it's what

Hi, David. Thanks for the offer of help. I have BCPERS450 serial number 2701DVHBC809300177. Unfortunately I'm about to go on a trip and will be away until the end of the month, so I don't have much time to discuss these things at the moment, but maybe Layne will have something to say. My understanding from when I was working on this a couple yea...