similar to: Can't make Smart-UPS 1500 shutdown over serial

Hello, I can get nut to work with this UPS using the apcsmart driver, but only with limited functionality. It is only reporting the OL/OB status and that's about it. None of the other useful variables such as run time, load etc are reported and initiating battery tests does not work either. Has anyone managed to get nut to report more than these variables with a Matrix type UPS? I see

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

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

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

Hi All, I've got two APC SmartUPS's that behave differently with nut, I have a SmartUPS1400 & a SmartUPS1250. I'm fairly sure this isn't a nut problem but more likely a problem with the age of the SmartUPS1250 and the apcsmart driver not being able to identify it. Under the APC Powerchute software the same monitoring & command parameters are available for both

Hi friends. Package: nut Version: 2.4.1-1 Depends: libusb, openssl, neon, libgd, net-snmp Status: install user installed Section: admin Architecture: mipsel maintainer: NSLU2 Linux <nslu2-linux at yahoogroups.com> MD5Sum: c8c55a6021fea2b5f194ce4623eb2dfe Size: 1246363 Filename: nut_2.4.1-1_mipsel.ipk Source: http://eu1.networkupstools.org/source/2.4/nut-2.4.1.tar.gz Description: Network UPS

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

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

Hello, I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. Quite sympathetic UPS, I must say from first glance. I have made a proper serial cable (btw i hate all those constructor's decisions to make distinct serial wiring for each and every UPS type from each and every manufacturer!) I use [tripplite] driver for NUT and I can use upsc to get report from UPS, but

Hello, I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups. Without any reason, nut/upsmon shut down my PC: >>> Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

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

G'day y'all, Here's a tiny patch set for drivers/apcsmart.c and drivers/apcsmart.h. Adds APC SmartUPS 1250 ("8QD" case) + 940-0024C recognition to apcsmart. (Unpatched apcsmart.c v1.99.8 misidentifies the SmartUPS 1250 as a "dumb" UPS.) For NUT 2.0.5+. NUT 2.0.5: Patches apply successfully. Builds successfully. Works as expected under Ubuntu 7.04. NUT 2.2:

Hello, We have a APC SMART-UPS 2200 which gives the following status information: battery.alarm.threshold: 0 battery.charge: 089.0 battery.charge.restart: 00 battery.date: 01/10/04 battery.packs: 000 battery.runtime: 21180 battery.runtime.low: 120 battery.voltage: 52.95 battery.voltage.nominal: 048 driver.name: apcsmart driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0

Hello, My APC Ups uses nut to manage all systems connected to it. But if online power failed until it shutdown, it not restart automatically after the power returned. It stay down until i restart it. When i execute the command: # upsc siUps1 it output me this: battery.alarm.threshold: L battery.charge: 018.0 battery.charge.restart: 15 battery.date: 03/31/07 battery.runtime: 120

Michal, I ran across this Debian bug today: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707223 It's a bit of a corner case, and it's for NUT 2.6.4 (apcsmart driver v3.04), but I was wondering if it was still applicable for the latest code? "nut reports 100% battery charge after unplugging the battery on a Smart-UPS 2200 RM (SUA2200RMI2U) using apcsmart. Powerchute correctly

Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode

[Please subscribe to the mailing list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ] On Nov 28, 2013, at 4:10 PM, Danijel ?ili wrote: > Since the provided drivers come with absolutely no installation instructions, I turned to NUT. > > The compatibility list says "blazer_usb" should be used for PowerWalker's devices, so that's what I put in my