As I was writing the last email I just saw this a message that communications with the UPS was lost, followed a bit later that it had been restored.
[ 7883.236755] usb 1-10: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 [ 7884.140431] usb 1-10: USB disconnect, device number 9 [ 7885.050902] usb 1-10: new low-speed USB device number 10 using xhci_hcd [ 7885.662851] usb 1-10: New USB device found, idVendor=0463, idProduct=ffff [ 7885.662859] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 7885.662864] usb 1-10: Product: 5E [ 7885.662868] usb 1-10: Manufacturer: EATON [ 7885.663100] usb 1-10: ep 0x81 - rounding interval to 128 microframes, ep desc says 160 microframes [ 7887.625203] hid-generic 0003:0463:FFFF.0005: hiddev0,hidraw2: USB HID v1.10 Device [EATON 5E] on usb-0000:00:14.0-10/input0 [ 7889.538816] usb 1-10: ep 0x81 - rounding interval to 128 microframes, ep desc says 160 microframes Now this is almost identical to the Eaton Nova error and the linux-usb error. I have now set up usbmon to dump all USB messages 24/7 and will leave it running to see if I can capture more info. Thanks, Leith Bade [email protected] On 10 August 2014 17:27, Leith Bade <[email protected]> wrote: > A final note: > http://lists.alioth.debian.org/pipermail/nut-upsuser/2014-April/008977.html > > That message talks about the Eaton Nova AVR which on the Eaton 5E > product page it says the 5E replaces the Nova. Do they perhaps share > hardware/firmware? > Thanks, > Leith Bade > [email protected] > > > On 10 August 2014 10:16, Charles Lepple <[email protected]> wrote: >> On Jul 26, 2014, at 9:58 AM, Leith Bade <[email protected]> wrote: >> >>> First the beeper is annoying and loud and I worry it will wake everyone up >>> at night. I read that you can mute the beeper temporarily (and this works) >>> but that most UPSs do not allow you to permanently turn it off (I tried >>> using upsrw but it said beeper.status was read only). >> >> Can you send the variable list of upsrw and the command list of upsc for >> reference? I don't have any information on the 5E. >> >> I think there should be "beeper.mute" and "beeper.off" commands. >> >>> So is there a way to auto-mute the beeper? e.g on system boot or on power >>> failure? >> >> That is an interesting point - we have scripting for power failures, but not >> for startup. >> >>> Next I did some testing and I think I have a power race (is that the right >>> term?). Basically if I switch off the AC, wait for battery to drain and the >>> system to shutdown and turn off (the PC only so far). If I then turn the AC >>> back on before the ~20 sec delay before the UPS turns off and on again the >>> computer never boots automatically (I have set BIOS to power on after AC >>> back). >>> >>> If I let the UPS turn off before I turn AC back on the computer will boot >>> automatically. >>> >>> I think the problem is that either the UPS is now power cycling the load >>> when AC is on and it reboots, or it is not turning it off for long enough >>> for the PSU/computer to register this as a AC off and on event. >> >> It's probably the latter, but if you don't hear the relay in the first case, >> that's a problem. >> >>> When the UPS reboots it beeps and I can hear a relay click so it must do >>> something when it reboots with power on. >>> >>> How can I add a delay between UPS power off, and power on? >> >> The output of upsrw will confirm this, but many HID UPSes have separate >> timers for delay before shutdown, and delay before turn-on (ups.delay.start). >> >> -- >> Charles Lepple >> clepple@gmail >> >> >> _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
