similar to: [HCL] Eaton 5E1100i supported by usbhid-ups

On 2020-08-19 17:36, Louis van Dyk wrote: > Hi > > BACKGROUND INFO: > I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux.  They don't provide software for it for Linux, only for Windows. > Referring links: > https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html >

Hi BACKGROUND INFO:I have a new Eaton 5E 1100i USB UPS which their website claims is supported on Linux. They don't provide software for it for Linux, only for Windows.Referring links: https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html It was manufactured in May 2020

I can't seem to get the longer battery tests to actually run: test.battery.start test.battery.start.deep Both appear to leave the battery voltage at line-power levels; while the quick test does have a notable voltage delta. Are there any other tests I can perform or ways that I can help gather data to get the longer tests supported? I borrowed a 60W light bulb (instead of one of the

It seems that the UPS I bought is actually served by the blazer_usb driver. USB ids 06da:0003 (lsusb DB thinks it's a "Phoenixtec Power Co., Ltd 1300VA UPS", but this has apparantly been re-used by Eaton 5E2200USB-LA) It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS SKU: 147140 Mfr Part #: 5E2200USB-LA UPC: 743172064875

On Oct 25, 2016, at 8:08 PM, Michael Evans wrote: > > It seems that the UPS I bought is actually served by the blazer_usb driver. > > USB ids 06da:0003 (lsusb DB thinks it's a "Phoenixtec Power Co., Ltd 1300VA UPS", but this has apparantly been re-used by Eaton 5E2200USB-LA) > > It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS > > SKU: 147140 Mfr

I was unable to setup |nut| on a server for the UPS Eaton 5E with USB connection. All results what did I get was that driver is not running and UPS is not recognized. What kind of driver is suitable for me and what kind of settings? Unit is Eaton 5E. result of |$ lsusb -v| |Bus 004 Device 007: ID 0463:ffff MGE UPS Systems UPS Device Descriptor: bLength 18 bDescriptorType

I recently purchased a UPS from http://www.microcenter.com/product/470131/5E_1,100W_2,200VA_6-Outlet_UPS It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS SKU: 147140 Mfr Part #: 5E2200USB-LA UPC: 743172064875 "The Eaton 5E is an essential line interactive UPS that provides cost effective and reliable power protection against power outages and bad power quality. Thanks to its small

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

I was getting a glicthy checkerboard mess at the cursor in some programs (konsol+) with # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=UUID=4107d1db-62a3-427c-8515-c954a103ce25 ro text quiet changed the command line in a blind attempt to: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=UUID=4107d1db-62a3-427c-8515-c954a103ce25 ro nouveau.config=NvForcePost=1

Lyonn CTB-1200 root at frambuesa:~# upsc lyonn at localhost battery.voltage: 27.20 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 5.0 input.frequency: 49.9 input.frequency.nominal: 50 input.voltage: 213.3

Hello, I'm sorry if i'm not sending to the good email adress, please transfer this mail to the good one if necessary... I have tested and run the driver named "blazerd_usb" with differents products from the infosec company (tested on the following UPS : X2, X3, X4, E2, E3, E4) Is it possible to add the to the Hardware compatibility list ? Thank you, Regarde, Jeremy

Hi, another UPS piece supported by blazer_usb: ALLSAI model LV 2K upsc output: battery.voltage: 82.08 battery.voltage.nominal: 72.0 beeper.status: enabled device.mfr: device.model: LV 2K device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 18.0 input.frequency: 59.9

Hi All! Just an update! The snmp driver seems quite happy with an APC AP9618 managment card in an APC Smart-UPS RT 5000 XL UPS. I have an APC AP9630 to test in the near future so will give and update on that one too! Cheers Ang -- Angela Williams angierfw at gmail dot com Linux/Networking Hacker Blog http://angierfw.wordpress.com Smile! Jesus Loves You!

2011/11/5 Arnaud Quette <aquette.dev at gmail.com> > Hi Greg, > > 2011/11/4 Charles Lepple <clepple at gmail.com> > >> On Thu, Nov 3, 2011 at 12:23 AM, Greg Trounson <gregt at maths.otago.ac.nz> >> wrote: >> > These Socomec units have RS-232 connectors and claim to support JBUS. >> > On the nut compatibility page I only see one Socomec

Atlantis Land A03-P551(V1.2) battery.charge: 100 battery.voltage: 13.70 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.langid_fix: 0x0409 driver.parameter.pollinterval: 2 driver.parameter.port: x driver.version: 2.6.4 driver.version.internal: 0.08 input.current.nominal: 0.0

Greets... ..just bought a cheap UPS today, works in debian 7.0 wrt nut 2.6.4 using richcomm_usb driver... ....output of upsc..... //// root at debian7:~# upsc starpower at localhost device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto

On Aug 7, 2013, at 10:43 AM, Matthew Lenz wrote: > Tripp Lite SMART1300LCDT > > # upsc ups [...] > battery.voltage: 0.0 > battery.voltage.nominal: 24.0 [...] > input.frequency: 5990.0 > input.transfer.high: 150.0 > input.transfer.low: 92.0 > input.voltage: 0.0 > input.voltage.nominal: 120 > output.current: 100.00 > output.frequency: 5990.0 >

On Aug 8, 2013, at 9:14 AM, Matthew Lenz wrote: > On Wed, Aug 7, 2013 at 6:47 PM, Charles Lepple wrote: >> Could you please stop the NUT services (or just the driver, whatever is easiest) and run "sudo /lib/nut/usbhid-ups -a ups -DDD" ? > > How much output would you like from this? Want me to just stick it on > a pastebin somewhere? > Just a few kB from the