similar to: Smart-UPS staying in OB after power return

John Morris wrote, On 9/21/2013 11:28 AM: > Hi list, > > UPS is a Smart-UPS 3000 RM (SU3000RM3U, ups.firmware 92.11.D, > ups.mfr.date 12/14/99) with brand-new batteries. NUT is 2.6.5 running > on SL6 (RHEL6 clone) from EPEL packages. 'upsc' output pasted at bottom. > > I'm not very familiar with UPSs in general or this model in particular, > and it's doing

Hi Kris, On 09/21/2013 05:11 PM, Kris Jordan wrote: > John Morris wrote, On 9/21/2013 11:28 AM: >> The most distressing problem is the UPS stays OB after removing and >> reapplying utility power. When power is removed, the UPS goes OB and >> upsmon detects the power failure no problem, reporting >> 's0-ups0 at localhost is on battery'. But when power is

Hi all, I've not been able to find the answer to my timer problem in the faq or the archives. (or google) Basically, I can't get timers to fire. They fire ignoring the timer value, as if the timer was set to 0. I'm using the OpenFiler distribution, patched to the latest and greatest. upsmon 2.2.2 When I pull the power plug, I see the text "Im In Battery" instantly, instead

UPS: http://www.eaton.com/Eaton/ESeriesUPS/DXUPS/index.htm?wtredirect=www.eaton.com/DXUPS I have the same problem on two different computers. The first one is running Ubuntu 12.10 i386 , the second one is running Debian 6.0 x64. Both of them are updated. I tried using different serial cable but the result is the same. The connection to the ups using Windows 7 and Winpower is working fine on

Hi, I'm having problems to configure upssched in order to notify me only when the disconnection exceeds the 30 seconds. Now, I'm getting a mail if it is disconnected just for a second, or even worse, when I got low tension. So, mail notifications are well configured, I guess... I think the problem is in upssched. I'm new to this, so it could be a stupid thing that I'm missing...

Hello! I am currently having issues monitoring a Tripp-Lite AVR900U. First, here are a few system details: > Manjaro Linux - kernel 5.4.30-1 > network-ups-tools 2.7.4-5 (built from Arch User Repository) > (lsusb output) Bus 003 Device 003: ID 09ae:3024 Tripp Lite AVR900U Contents of /etc/ups/ups.conf: > [tripplite] > driver =  usbhid-ups > port = auto Contents of

While fundamentally working, I'm having a few issues with the driver... The default voltage quads (for every model) are way off... Showing ~95v when it should be ~117V. I've changed the 4th/final coefficient to +5.0, but haven't tested extensively (with fluctuating voltages). The input/output voltage appears to be swapped _most of the time_. When doing a battery test, or when

On Nov 8, 2014, at 6:12 PM, Selva Nair <selva.nair at gmail.com> wrote: > Everything works rather well, except that the cgi-interface does not report input/output voltages and load for the C 1500 unit. > upsc also reports these values only for model 1000, not for 1500. Battery charge is and runtime are reported. For the 1000, do the values match this page?

Hi, I have setup NUT in netserver mode on debian wheezy with two APC UPS units connected to it by usb. lsusb identifies the units as Smart-UPS 1000 and Smart-UPS C1500. It appears these do not use the smart protocol and usbhid-ups is the correct driver to use. System: Debian wheezy with stock version of nut (Version: 2.6.4-2.3+deb7u1) Everything works rather well, except that the

On Dec 7, 2013, at 2:38 PM, Christian wrote: > Dear list, > > I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when > we had a power outage, the only entry in the logs was: > > Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery > > and then the machine seems to have run until the battery was empty. It > only notices the "battery

Hi, I'm new to nut. I have some 100 APC Smart-UPS 2200 & 3000's and I'm trying to do some calibration test on them. I've installed nut, with driver = snmp-ups mibs = apcc in ups.conf. I can read the variables using upsc. However it seems, I can't actually execute commands on the UPSses this way. ( upscmd some-ups calibrate.start ) Do I miss something, or are those

Dear list, I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when we had a power outage, the only entry in the logs was: Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery and then the machine seems to have run until the battery was empty. It only notices the "battery low" after I turn the system back on: Dec 3 16:01:39 afs1 usbhid-ups[21973]:

Hi Charles, Thanks for your response. > For the 1000, do the values match this page? > > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/Smart-UPS_1000.html > > Yes it does (except that mine is a 120 V model, so input/output voltage is about 125) It doesn't look like we have an entry for a C1500 yet. Would you care to > submit the output of

Using nut v2.2.2, and the APC serial cable. I have a client who's APC SMART-UPS 1500 (circa 2000) is always reporting LB. The batteries were old so they were replaced two weeks ago with brand new batteries. UPS still reported low batteries... I ran a calibration and a test on the unit (using the nut upscmd utility) During those tests, the battery charge on the unit goes to zero and slowly

Hi, I'm running an old APC Smart UPS 900i. As there isn't any software from APC which supports this UPS anymore, I've installed NUT (Gentoo Ebuilds), but version 2.0.5 and version 2.2.2 loose connection to the UPS while version 2.4.1 and SVN version don't show any settings and there are no instant commands. The only information I can get are: driver.name: apcsmart

For my Smart 2200, a charged battery string is anywhere between 25.6 and 26.8 volts. I'm seeing nut report 13.0 volts, which seems suspicious. Even if the UPS were reporting half of the actual battery voltage to keep protocol compatibility with models having a 12V battery system, the value of exactly 13.0 seems unlikely. According to the page at

http://www.zigor.com/uk/index.php/en/products/upssystems/danubioseries Ships with UPSilon 2000 software, and appears to work with blazer_usb to a certain extent with the following config: [danubio] driver = blazer_usb langid_fix = 0x409 port = stupidly, I seem to have to set this even though it's ignored vendorid=0001 productid=0000 Yes, vendor 0001,

Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this:

On 12/03/2016 08:03 AM, Charles Lepple wrote: > On Dec 2, 2016, at 10:23 PM, Jack McGee <jack at greendesk.net> wrote: >> This is new install on Ubuntu 16.04, using packages from Synaptic, >> Network UPS Tools upsd 2.7.2 >> >> I am getting these messages in the terminal: >> Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): >>

Hi, I'm using a APC Smart UPS with a Mac Mini, connected using a USB serial converter. Works fine so far, the Mac Mini will be shut down, a NAS connected of the network to the nut on Mac Mini will also shut down, perfect. However, the ups will not be shut down. Very unfortunate, since the Mac will not start again, if the power comes back before the batteries are completely empty. I read