[Nut-upsuser] New intermediate Windows binaries release - 2.6.5-2

[FredericBohe at Eaton.com]

Hello Denis,

> From: nut-upsuser-bounces+fredericbohe=eaton.com at lists.alioth.debian.org [nut-upsuser-bounces+fredericbohe=eaton.com at lists.alioth.debian.org] on behalf of Denis Serov [dns-srv at yandex.ru]
> Sent: Monday, September 17, 2012 9:24 PM
> To: nut-upsuser at lists.alioth.debian.org
> Subject: Re: [Nut-upsuser] New intermediate Windows binaries release -  2.6.5-2
> 
> Hello Frederic!
> 
> Thank you for new version.
> 
> 1. Something is wrong with NUT service. UPSD/UPSMON/USBHID-UPS are still running after service stop. There are the following errors in Event Log:
> 
> "Error stoping upsd."
> "Error sendind CTRL_BREAK to upsmon."

Silly bug from my part, fixed now (maybe worth another release this week...)

> 2. I've found a strange warning in Event Log:
> 
> "usbhid-ups - libusb_get_interrupt: libusb0-dll:err [submit_async] submitting request failed, win error: The device does not recognize the command."
> 
> Here is more details from UBSHID-USB output:
>    0.468000     libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.
>    0.468000     Can't retrieve Report 48: Input/output error [A device attached to the system is not functioning. ]
> 
> I think it is related to issue with APC Back ES UPS (there was no such error in private binary you sent to me).

This is very strange.
I see two report ID raising a libusb error in your logs: 48 and 62. They contains non standard, APC specific, HID data and strange value (as I see them on the old binary logs you have sent me).
I am not sure what are the differences between the released binary and the one that I sent to you. That's because the one I send to you was just an experimental thing to see if I was searching in the right direction, and I have lost its sources now. But from what I remember I don't see what could have changed its behavior the way it is now.
Anyway, from what you are reporting this is only "cosmetic" issue. Just one thing that still bothering me is that you have mentioned that it "repeats iteratively". Do you mean that the libusb error repeats regularly when the usbhid-ups driver is running ? If it is the case, can you send us usbhid-ups logs on a longer run (the attached one is stopped just after the init), please ?

> 
> 3. Little misprint in setup wizard: "Netowrk UPS Tools Installer (WiX)" =)

Fixed, thanks.

Fred

> 
> Device: APC Back UPS ES 525
> OS: Windows 7 x64 Ultimate
> 
> Anyway, UPSSCHED is working, event logging is back and Back UPS ES is supported (the error from item 2 does not terminate the driver as in 2.6.5-1 version, but repeats iteratively).
> 
> Thanks,
> Denis
> 


--
Eaton Opensource Team - http://opensource.eaton.com


-----------------------------

-----------------------------