similar to: AVRX750/500 issues

I wouldn't be surprised if they both use the same driver. I think they are essentially the same model, but with one having a slightly larger battery. My issue is primarily with the UPS turning back on after having shut off like it should. @Scott Colby if you take a look at the config files I posted in the github issue I created, perhaps that will give you some hints on your issue. Maybe

David, Thank you. I created a Github issue (https://github.com/networkupstools/nut/issues/808). I don't know who monitors those tickets, but no one has responded to my previous issue on that project repository about the AVRX550U, so it's unclear if the right person is going to see this one. Can you tell me what other models use the 3024 protocol? Listing those may help provide

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

Hi, I can confirm that with my AVR750U connected to my Windows machine using the TrippLite Power Alert software, I can configure it to do the behavior I want: turn off at a low power level and turn back on when the power is reconnected, so I guess it's now a question of if NUT can be adapted to the 3024 protocol. I am not the most experienced C programmer out there, but given there are

Thank you David. I think the end goal of making this UPS compatible with NUT helps both Tripp-Lite and NUT users in that greater compatibility insures more users purchase Tripp-Lite products. I do understand Tripp-Lite wanting to do their due diligence to protect IP, however, it seems like unless NUT devs can get a hold of some sort of documentation, it's more difficult to make this and

>>>Thanks for chiming in @David Zomaya. Tripp Lite replaced my AVRX550U once thinking that the powering back on was a defective unit, but the replacement does the same thing. The SN on the first one is 2935AVHOM87BB00152. >>> NUT has my model listed as protocol 2010, 2935AVHOM87BB00152 is Protocol 2012 That said, 2010 and 2012 should be similar. Off the top of my head,

Did you see what objecttothis posted on GitHub already? In any event, your issue with NUT and the 3024 AVR750U is that the UPS reboots output instead of shutting off when the shutdown command is sent, correct? Good suggestion on the driver authors, thanks. Thank you, David Zomaya From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on

No, I had not! I'll take a look at the protocol docs. My problem is the opposite: all the permutations that NUT can send of "turn off but turn back on later" either do nothing or turn the UPS off in such a way that it requires me pressing the physical power button to bring it back on. (I guess I haven't tested trying commands to turn it back on, but that's not so helpful if

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

Thanks for the quick response! On Sat, Jun 27, 2020, at 22:17, Manuel Wolfshant wrote: > On 6/28/20 4:25 AM, Scott Colby wrote: > > Hello, > > > > I am having difficulty using NUT to shut down my Netgate SG-1100 > > (a pfSense router) when the power level of the UPS gets critically > > low. > > > > Here is some relevant information: > > - OS:

On 6/28/20 4:25 AM, Scott Colby wrote: > Hello, > > I am having difficulty using NUT to shut down my Netgate SG-1100 > (a pfSense router) when the power level of the UPS gets critically > low. > > Here is some relevant information: > - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) > - NUT version: 2.7.4 > - Installed from: pfSense package 2.7.4_7 > - UPS:

Peter, Here are the transitions that I have tested with your latest changes (on the APC/Back-UPS ES 650): 1) OL ==> OB DISCHRG followed by OB DISCHRG ==> OL (no CHRG inbetween) 2) OL CHRG ==> OL 3) OL CHRG ==> OL CHRG LB (by manipulating battery.charge.low) 4) OL CHRG LB ==> OL CHRG (i.e. transition from below) 5) OB DISCHRG ==> FSD OB DISCHRG LB followed by proper shutdown In

I'm running nut 2.0.1 with an MGE pulsar evolution 3000 with the mge-utalk (serial) driver on NetBSD 3.1 . I had a very strange occurance in my basement datacenter this early AM. the following was logged by upslog: 20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00 20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00 20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00 20080219 023622

Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here:

On 6/28/20 5:54 AM, Scott Colby wrote: > > I'm not convinced this is the problem; I think that pfSense has > an alternative way of running the NUT components: > # ps aux | grep ups > root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon > uucp 45751 0.0 0.1 6796 772 - S 02:22 0:00.10 /usr/local/sbin/upsmon > uucp 46796

G'day, all! I installed latest stable nut-2.6.1.tar.gz from source on Xenserver 5.6 SP2 (Linux xen-home 2.6.32.12-0.7.1.xs5.6.100.323.170596xen #1 SMP Fri Apr 8 07:25:07 EDT 2011 i686 athlon i386 GNU/Linux), my UPS is Powercom WOW--500U FW3.A4. All works almost fine but here are some troubles: when I pull the plug then upsd immediately starts (after FINALDELAY delaying) the procedure of

Hello All, I'm trying to establish a MASTER SLAVE configuration of UPS using NUT Driver. I'm able to shutdown the master after UPS is on BATTERY ( POWER BLACKOUT) .However I'm trying to shutdown the other SLAVE MACHINES BEFORE MASTER. But at the remote side ( Slaves ) shutdown after UPS blackout does not happen. My configuration in Master are /usr/etc/upsd.users

>> But I noticed two other details: >> 1. I was a bit wrong with step 7 and 8 - Looks like the UPS is "OL CHRG" (according to display) at first but goes to battery ("OL DISCHRG" according to nut) right when the RasPi (and nut) is booting. >> 2. When I pull the plug of the RasPi after UPS went down before main power comes back (so between step 5 and 6), the UPS

Does the github link not come through (https://github.com/networkupstools/nut/issues/799)? All the documentation that Tripp-Lite sent me on the 2012 protocol and my configuration files are on that issue. I doubt this mailing list will allow me to attach any files. It's the NUT github page. At any rate ups.conf just has this in it. No offdelay or ondelay entries: [ups] driver =

I here is some information I could have provided previously. Here is what I am seeing: ==================================================================== Broadcast message from nut at localhost.localdomain (Fri May 13 22:31:35 2016): UPS myups at localhost on battery upsc myups at localhost battery.charge: 3 battery.charge.low: 10 battery.charge.warning: 30 battery.runtime: 93