search for: eaton5

...this? Here is my configuration and in the end are some log snippets: --------------------------------------------------- heartbeat.conf # heartbeat.conf -- 10 minute heartbeat ups.status: OL TIMER 300 ups.status: OB TIMER 300 --------------------------------------------------- hosts.conf MONITOR eaton5s at localhost "Eaton 5S 700" --------------------------------------------------- nut.conf MODE=netserver --------------------------------------------------- ups.conf maxretry = 3 [eaton5s] driver = usbhid-ups port = auto desc = "Eaton 5S 700i UPS"...

Device manufacturer and name: *Eaton 5E 1100i USB* *upsc eaton5e* Init SSL without certificate database eaton5e root at eger:/home/siposg# upsc eaton5e Init SSL without certificate database battery.charge: 100 battery.runtime: 3160 battery.type: PbAc device.mfr: EATON device.model: 5E 1100i device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30...

...is my configuration and in the end are some log snippets: --------------------------------------------------- heartbeat.conf # heartbeat.conf -- 10 minute heartbeat ups.status: OL TIMER 300 ups.status: OB TIMER 300 --------------------------------------------------- hosts.conf MONITOR eaton5s at localhost "Eaton 5S 700" --------------------------------------------------- nut.conf MODE=netserver --------------------------------------------------- ups.conf maxretry = 3 [eaton5s] driver = usbhid-ups port = auto desc = "Eaton 5S 700i UPS...

...is my configuration and in the end are some log snippets: --------------------------------------------------- heartbeat.conf # heartbeat.conf -- 10 minute heartbeat ups.status: OL TIMER 300 ups.status: OB TIMER 300 --------------------------------------------------- hosts.conf MONITOR eaton5s at localhost "Eaton 5S 700" --------------------------------------------------- nut.conf MODE=netserver --------------------------------------------------- ups.conf maxretry = 3 [eaton5s] driver = usbhid-ups port = auto desc = "Eaton 5S 700i UPS...

...clearly truncated; I guess this correlates to approximately floor((100 * 60)/2200)) It took me a while to remember that I needed to configure upsd.users and use a completely different command ( upscmd instead of upsc ) to interact with the UPS and get it to run a battery test. In my case upscmd eaton5e test.battery.start.quick allowed me to see a maximum default.battery.voltage.high of 26.5 (This typically reads at ~27.50 (27.20 - 27.80) while on line power) It took me a bit of effort to arrange a larger load that I don't care about, but after setting it up this weekend I have an initial...

...-reload-rules > > I think I recall hearing systemd ate udev? > > # systemctl daemon-reload > > Then I disconnected/reconnected the UPS, since that was faster than looking up re-triggering udev rules. > > > # cat >> /etc/ups/ups.conf << HEREDOC > > [eaton5e] > driver = blazer_usb > port = auto > vendorid = 06da > productid = 0003 > HEREDOC New work is being done on nutdrv_qx rather than blazer_*, but fortunately it is fairly similar to configure: http://networkupstools.org/docs/man/nutdrv_qx.htm...

...dev1] driver = "usbhid-ups" port = "auto" vendorid = "0463" productid = "FFFF" product = "5E" bus = "002"I have put that exact info into /etc/ups/ups.conf - it's the only info not commented with a # in the file. I changed the name to eaton5e though. When I then run: [root at fedora ~]# /usr/sbin/usbhid-ups -DDDD -a eaton5e Network UPS Tools - Generic HID driver 0.41 (2.7.4)USB communication driver 0.33 0.000000 debug level is '4' 0.002054 upsdrv_initups... 0.017685 Checking device (0463/FFFF) (002/120) 2.024057 - Ven...

...ages and bad power quality. Thanks to its small size the 5E can be installed easily in a business environment or at home." Network UPS Tools upsc 2.7.4-151-g9209e18 The git development version was required to get any communication with the UPS; however a number of surprises awaited me. upsc eaton5e at localhost device.mfr: CTN device.model: USB UPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0003 driver.parameter.synchronous: no driver.parameter.vendorid: 06da driver.version: 2...

...ng the ups [and will shut down the box if needed]. I looked at the upsd and upsmon man pages, but can't see anything like a "status" command that will show me if the connection is healthy (I noticed that when I restart the daemons I get a log line saying "Communications with UPS eaton5s at 127.0.0.1 established", but I can't seem to find a place to access that). I could in theory check if the port is in use/ESTABLISHED, lsof -i:3493, but it's not great. Is there any command I can run that will confirm if upsmon is correctly connected? thanks, Spike --------------...

...t;, GROUP="nut" HEREDOC # udevadm control --reload-rules I think I recall hearing systemd ate udev? # systemctl daemon-reload Then I disconnected/reconnected the UPS, since that was faster than looking up re-triggering udev rules. # cat >> /etc/ups/ups.conf << HEREDOC [eaton5e] driver = blazer_usb port = auto vendorid = 06da productid = 0003 HEREDOC I still need to perform the following calibrations: default.battery.voltage.high = value Maximum battery voltage that is reached after about 12 to 24 hours charging. If you want the dri...

...n the box if > needed]. > > I looked at the upsd and upsmon man pages, but can't see anything like > a "status" command that will show me if the connection is healthy (I > noticed that when I restart the daemons I get a log line saying > "Communications with UPS eaton5s at 127.0.0.1 <mailto:eaton5s at 127.0.0.1> > established", but I can't seem to find a place to access that). I > could in theory check if the port is in use/ESTABLISHED, lsof -i:3493, > but it's not great. > > Is there any command I can run that will confirm if up...

...t; > > vendorid = "0463" > > productid = "FFFF" > > product = "5E" > > bus = "002" > > I have put that exact info into /etc/ups/ups.conf - it's the only info not commented with a # in the file.  I changed the name to eaton5e though. > > When I then run: > > [root at fedora <mailto:root at fedora> ~]# /usr/sbin/usbhid-ups -DDDD -a eaton5e > > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > > USB communication driver 0.33 > >    0.000000 debug level is '4' >...

...1 0 00:00 ? 00:00:00 /usr/sbin/cups-browsed lp 1156748 1156722 0 00:00 ? 00:00:00 /usr/lib/cups/notifier/dbus dbus:// nut 1713117 1 0 14:30 ? 00:00:00 /lib/nut/dummy-ups -a heartbeat nut 1713154 1 0 14:30 ? 00:00:00 /lib/nut/usbhid-ups -a eaton5s nut 1713155 1 0 14:30 ? 00:00:00 /lib/nut/upsd -F root 1713156 1 0 14:30 ? 00:00:00 /lib/nut/upsmon -F root 1713157 1713156 0 14:30 ? 00:00:00 /lib/nut/upsmon -F root 1716171 1 99 14:35 ? 00:05:10 /sbin/upssched UPS heartbeat at loc...

...1 0 00:00 ? 00:00:00 /usr/sbin/cups-browsed lp 1156748 1156722 0 00:00 ? 00:00:00 /usr/lib/cups/notifier/dbus dbus:// nut 1713117 1 0 14:30 ? 00:00:00 /lib/nut/dummy-ups -a heartbeat nut 1713154 1 0 14:30 ? 00:00:00 /lib/nut/usbhid-ups -a eaton5s nut 1713155 1 0 14:30 ? 00:00:00 /lib/nut/upsd -F root 1713156 1 0 14:30 ? 00:00:00 /lib/nut/upsmon -F root 1713157 1713156 0 14:30 ? 00:00:00 /lib/nut/upsmon -F root 1716171 1 99 14:35 ? 00:05:10 /sbin/upssched UPS heartbeat at loc...

...tes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 20 Device Status: 0x0001 Self Powered | Content of |/etc/nut/ups.conf| |[Eaton5E] driver = blazer_usb port = auto | Result of |$ upsdrvctl start| for |usbhid-ups| driver: |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 No matching HID UPS found Driver failed to start (exit status=1) | Result...

.../usr/sbin/cups-browsed > lp 1156748 1156722 0 00:00 ? 00:00:00 > /usr/lib/cups/notifier/dbus dbus:// > nut 1713117 1 0 14:30 ? 00:00:00 /lib/nut/dummy-ups -a > heartbeat > nut 1713154 1 0 14:30 ? 00:00:00 /lib/nut/usbhid-ups -a > eaton5s > nut 1713155 1 0 14:30 ? 00:00:00 /lib/nut/upsd -F > root 1713156 1 0 14:30 ? 00:00:00 /lib/nut/upsmon -F > root 1713157 1713156 0 14:30 ? 00:00:00 /lib/nut/upsmon -F > root 1716171 1 99 14:35 ? 00:05:10 /sbin/upssched...

.../usr/sbin/cups-browsed > lp 1156748 1156722 0 00:00 ? 00:00:00 > /usr/lib/cups/notifier/dbus dbus:// > nut 1713117 1 0 14:30 ? 00:00:00 /lib/nut/dummy-ups -a > heartbeat > nut 1713154 1 0 14:30 ? 00:00:00 /lib/nut/usbhid-ups -a > eaton5s > nut 1713155 1 0 14:30 ? 00:00:00 /lib/nut/upsd -F > root 1713156 1 0 14:30 ? 00:00:00 /lib/nut/upsmon -F > root 1713157 1713156 0 14:30 ? 00:00:00 /lib/nut/upsmon -F > root 1716171 1 99 14:35 ? 00:05:10 /sbin/upssched...

...gt;> lp 1156748 1156722 0 00:00 ? 00:00:00 >> /usr/lib/cups/notifier/dbus dbus:// >> nut 1713117 1 0 14:30 ? 00:00:00 /lib/nut/dummy-ups -a >> heartbeat >> nut 1713154 1 0 14:30 ? 00:00:00 /lib/nut/usbhid-ups >> -a eaton5s >> nut 1713155 1 0 14:30 ? 00:00:00 /lib/nut/upsd -F >> root 1713156 1 0 14:30 ? 00:00:00 /lib/nut/upsmon -F >> root 1713157 1713156 0 14:30 ? 00:00:00 /lib/nut/upsmon -F >> root 1716171 1 99 14:35 ? 00:05:10...

...gt;> lp 1156748 1156722 0 00:00 ? 00:00:00 >> /usr/lib/cups/notifier/dbus dbus:// >> nut 1713117 1 0 14:30 ? 00:00:00 /lib/nut/dummy-ups -a >> heartbeat >> nut 1713154 1 0 14:30 ? 00:00:00 /lib/nut/usbhid-ups >> -a eaton5s >> nut 1713155 1 0 14:30 ? 00:00:00 /lib/nut/upsd -F >> root 1713156 1 0 14:30 ? 00:00:00 /lib/nut/upsmon -F >> root 1713157 1713156 0 14:30 ? 00:00:00 /lib/nut/upsmon -F >> root 1716171 1 99 14:35 ? 00:05:10...

> On Oct 31, 2016, at 10:15 PM, Michael Evans <mjevans1983 at gmail.com> wrote: > > Are there any other tests I can perform or ways that I can help gather data to get the longer tests supported? > The "test.battery.start" command takes a parameter in seconds (defaults to 600): https://github.com/networkupstools/nut/blob/v2.7.4/drivers/nutdrv_qx_blazer-common.c#L286