similar to: Experiences With NUT Eaton & Cyberpower UPS

Hello Jeff, `upsstats` by itself only relays and renders the information provided by a NUT data server (upsd) and the NUT driver for the device. So you can revise the specific reported values with e.g. `upsc` command-line client to be sure. What I think happens here is that the driver uses a `battery.voltage.low/nominal/high` group of readings which does not match the hardware circumstances

Well, for a bit of devil's advocate - if the battery swelled, it might hace leaked or fumed, contaminating the device and contacts. The safe approach (for their liability, and for end-users' fire hazard really) is to not claim the device is safe to use anymore. Jim On Tue, Apr 2, 2024, 07:11 Ben <bkamen at benjammin.net> wrote: > On 4/1/24 7:37 PM, Phil Stracchino via

Hello, I am using Nut 2.8.0 (2.8.0-7 packages) Debian 'Bookworm' in it's Devuan form 'Daedalus'. When I look at my Eaton (ex-MGE Powerware) E5115 UPS boxes in NUT 'upsstats" I am confused by the battery readings. Under the 'System' column I can click on the link and obtain a GUI with a few meters. The NUT 'upsstats' battery voltage meter for these

Charles, It starts out good, then goes into a Connection timed out loop. If I can provide any information to fix a driver I'll do my best. Here's the output: # /usr/local/ups/bin/usbhid-ups -DD -a eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 debug level is '2' 0.002550 upsdrv_initups... 0.288229 Checking device

I've been running the Debian packaged 2.4.3 for a while, working find. When 2.6.0-1 just pushed through to debian, things have stopped working :( I checked what had been the usual suspects in past problems, namely permissions problems in /dev/bus/usb, but all seems in order: $ lsusb ... Bus 009 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS $ ls -l /dev/bus/usb/009/002

My UPS is a Eaton Ellipse 1000S (But its identified as MGE Ellipse 0463:ffff). I have been using the usb interface with the usbhid-ups driver, but I found that sometimes (too much times) the driver doesn't respond and NUT doesn't receive changes nor notifications from the UPS. The kernel lose the connections with USB device, in the kernel logs appears: Dec 30 11:24:12 rei kernel:

Hello guys, I have to manage an Eaton Ellipse ASR 750 VA UPS under a FreeBSD 8.2 server. I used nut from ports collection but I'm unable to detect the UPS by USB cable. Here is the output of 'usbconfig -u 4 -a 2 dump_device_desc' : ugen4.2: <ELLIPSE EATON> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110

Here is a Compatibility Report for the Eaton Ellipse ECO 1600 UPS. Roger battery.charge: 100 battery.charge.low: 20 battery.runtime: 1575 battery.type: PbAc device.mfr: EATON device.model: Ellipse ECO 1600 device.serial: 000000000 device.type: ups driver.name: usbhid-ups driver.parameter.lowbatt: 37 driver.parameter.offdelay: 30 driver.parameter.ondelay: 40 driver.parameter.pollfreq: 30

Thanks for the info! First, regarding the later detail about starting `usbhid-ups`: the "Resource busy" indicates that likely an earlier instance of the NUT driver (in its own service unit) is still running and holding the device. In a worse case, some other programs might consider this a HID device (same class family as keyboards and mice) and grab it somehow, or it gets passed through

Hi there, I've replaced yesterday my old UPS with a brand new "Eaton Ellipse MAX 600 USBS". I've choosed the Eaton (previously MGE) both because I've always been extremely satisfied with MGE UPSes of all kinds at work, and because of the involvement of MGE (with Arnaud) in nut development, which made me quite sure that I would have no trouble with an Eaton (MGE) UPS and

So, I just rebuilt the battery packs in my PR3000LCDRTXL2U and its expansion unit. You don't want to KNOW. If the internal batteries have overheated and bulged, you CANNOT remove the battery pack intact even by partially disassembling the UPS, you have to pry the batteries out via the top of the chassis one by one. It's not pretty. Three and a half hours of work including

Hi all, I am trying to communicate to this Eaton Ellipse (see above) using nut from a Debian Squeeze system on Armel architecture. But have not succeeded so far. Version: Linux b3 2.6.39.4-11 #1 Tue Apr 3 21:45:12 FET 2012 armv5tel GNU/Linux Nut version is 2.4.3-1.1squeeze2 this information if from dpkg. NUT installation method:from debian package for armel. The problem is I cannot

Hi! Info OS: TinyCore Linux 4.5.6 NUT version: 2.6.4 NUT innstallation method: source tarball Device name: Eaton Ellipse ups eco 1600 usb din (EL1600USBDIN) /usr/local/ups/etc/ups.conf file: [eaton] driver = usbhid-ups port = auto When I run: root at Dalen:/usr/local/ups/bin/upsdrvctl start eaton I get this error message: Network UPS Tools - UPS driver controller 2.6.4

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Hello everybody, Our supoprt team is facing a problem which froze the CPU. They suspect that this happens after an automatic battery test, which lets the battery goes down to 30% and then stop the test. At this level of charge, our kernel also triggers a shutdown (CPU and UPS). I saw (in the doc found here : tools.*mge*ops.net/download/intl/products/*ellipse*-asr/28-umeasr_08.pdf) that this

2017-03-11 4:55 GMT+01:00 Spike <spike at drba.org>: > Hi, > Hi Spike, sorry for the lag in answering, I was collecting the needed information. I have a eaton 1500 that connects to an Ubuntu Xenial box via USB. The UPS > works, however exactly *ever 5 minutes* it disconnects and reconnects and I > see this in syslog: > > Mar 10 19:50:32 spike kernel: usb 4-5: USB

Hi, I have a eaton 1500 that connects to an Ubuntu Xenial box via USB. The UPS works, however exactly *ever 5 minutes* it disconnects and reconnects and I see this in syslog: Mar 10 19:50:32 spike kernel: usb 4-5: USB disconnect, device number 103 Mar 10 19:50:33 spike kernel: usb 4-5: new low-speed USB device number 104 using ohci-pci Mar 10 19:50:34 spike kernel: usb 4-5: New USB device found,

Hi, This might be a simple thing to fix, but I can?t figure it out. We replaced the battery for the first time in our Eaton 5PX a couple of weeks ago, but we haven?t been able to clear the ?ups.alarm: replace battery!? status. Details of our installation are: OS: Debian 6 NUT version: 2.7.4 Installation method: from source tarball UPS device: Eaton 5PX2000IRT, 240V, 1800W, 2000VA, bought in

Arno, thanks for taking the time to write back and no worries about lag, we're all busy and I'm grateful there is a community to interact with to begin with. You're right - the problem went away once I actually configured nut. I guess I was too "cautious" and when I saw the errors I thought something was wrong with the usb connection and didn't try to get nut going