similar to: APC Smart-UPS 1500; system shutdown is not initiated.

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

Charles, thanks for your detailed answer. >> Occasionally, i get these in daemon.log: Dec 4 03:11:54 afs1 >> usbhid-ups[21973]: libusb_get_interrupt: could not claim interface >> 0: Device or resource busy > > This isn't great, but I don't think it's related. > > It is normal to get a "could not claim interface 0" error once after >

Hi there... nut 2.4.3 kicks an error at me when I try to talk to my UPS. machine is linux 2.4.21-32.ELsmp with libusb-0.1.8-3 package update. # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: APC HID 0.95 libusb_get_interrupt: error submitting URB: Invalid

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

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All

Hello, we have a problem using APC Back-UPS CS 500 (connected via USB, usbhid-ups-apc) and UPS-NUT. We've tried different Versions of UPS-NUT (2.2.1 and 2.2.2), including the latest from SVN (28th November 2008). We've also tried apcupsd, which works fine for our requirements, but we don't want use it. What we need is simple: The UPS should turn off after power loss and shutdown

Hi all, I use an APC Back-UPS RS 800, overall my experience with NUT is very good but there is one feature I am missing: the ability to ask the UPS for a battery test. upscmd -l shows the following commands available: $ upscmd -l rs800 Instant commands supported on UPS [rs800]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS

> Also, I don't think we have any confirmation of the variables that the AP9620 provides. Here is the list of full 'upsc' output for various APC models: > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/index.html Frantz, Actually, it would be useful if you could send a copy of the output of 'upsc', 'upscmd -l' and

On Dec 17, 2014, at 3:46 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > This seems to me a little bit complicated :-( Instead, can I use the > apcsmart driver with the provided 940-0625a c?ble (RJ45/DB9 connectors) ? Or > do I need to acquire an AP9620 SmartSlot expansion card, as I've seen in the > Hardware compatibility list page ? It sounds like you might

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

On Wed, 8 Jan 2020, Gene Heskett wrote: > On Wednesday 08 January 2020 06:44:03 Roger Price wrote: >> I am surprised that there is no ups.delay.start for this UPS. > My new APC Smart-UPS_1500 doesn't have it either. Hello Gene, The NUT 2.7.2 "device dump library" entry for the APC Smart-UPS 1500 at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html shows an entry

On Feb 1, 2015, at 7:04 AM, Melvin Call <melvincall979 at gmail.com> wrote: > Thank you Charles, for the assistance and the information. Everything is > completely functional here now. Not sure if the APC BackUPS ES550 is on the > list of compatible devices, but it works just fine with the usbhid-ups driver, > and supports several basic commands. You're welcome! We do have

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

I have an APC USB UPS that was working on OpenBSD 5.5 with NUT 2.7.1 When I installed the latest 5.6 snapshot with NUT 2.7.2 the UPS no longer sends status messages when it loses line power. I asked over on the OpenBSD ports list and so far haven't had any luck getting this to work again. I disabled upd at boot as was suggested and that didn't change anything except stopping the

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > >> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG) >> is >> set to /etc/killpower, but I changed that to /tmp and modified my >> umountroot >> script to mount it read only

Hello. I've been running a two machine setup with a mge-shut for some time without problems, and now I'm configuring a three machine setup with an APC Smart 1500. The UPS has three machines connected to it, in a peculiar way: one windows machine is connected via USB. The second windows machine is using an agent to monitor messages from the first windows machine. Then, I have a GNU/Linux

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. > > https://github.com/networkupstools/nut/pull/2184 > > As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and