[Nut-upsuser] Generic UPS driver

Charles Lepple clepple at gmail.com
Sun Jan 12 19:32:22 UTC 2014

On Jan 12, 2014, at 11:07 AM, Ariel Wainer wrote:

> On 11/01/14 15:27, Charles Lepple wrote:
>> On Jan 10, 2014, at 4:46 PM, Ariel Wainer wrote:
>>> On 10/01/14 01:53, Charles Lepple wrote:
>>>> I am curious about why the Interrupt Out packet is sent by the Windows software if it isn't to turn off the UPS. Is it possible to do some more testing with shorter timeouts so that the battery doesn't get depleted? You would need to record the exact time when it shuts down, I think.
> Ok, I did some more testing, with or without load and the observed
> result is that te UPS completly powers down arround 30 seconds after the
> interrput out packet that is sent during windows shutdown process.

Hmm, then the driver should be doing the same thing.

What does the debug output look like when you run ./nutdrv_atcl_usb -a ups -DDD -u root -k ?

> Strangely, when this happens I don't see any new packets on the capture.
> The settings used for this test are: 1 minute both for shutdown on AC
> fail and shutdown on low battery (I don't thing this one has any effect).

Where do you mean? It looks like the host resets the USB port about 7 seconds after sending the Interrupt Out (packet #221 in the latest capture). If the Windows application doesn't reconnect, that would explain the lack of Interrupt In packets after it is finished enumerating.

>> If it's not too late for your tests, I committed a v0.03 to the 'atcl' branch, with string matching to avoid confusion with other 0001:0000 devices.
> It wasn't, the output of the new driver:

If it works for you, then that works for me.

Thanks for testing,

Charles Lepple
clepple at gmail

More information about the Nut-upsuser mailing list