[Nut-upsdev] Supporting APC 5G UPSs

Arnaud Quette aquette.dev at gmail.com
Fri Jun 25 18:46:36 UTC 2010


Hi,

you're definitly too fast Arjen ;-)

2010/6/25 Arjen de Korte <nut+devel at de-korte.org <nut%2Bdevel at de-korte.org>>

> Citeren Chris.Collins at apcc.com:
>
>
>  I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs.
>> The current usbhid-ups driver recognises APC UPSs by the Vendor ID and
>> Product ID of 0x051D and 0x0002.  This needs to be amended with the new
>> Product ID of 0x0003.
>>
>> (See attached file: apc-hid.patch)
>>
>
> Thanks for the patch.
>
>
>  Secondly, when Nut polls the UPS via the interrupt channel, these will
>> time
>> out, resulting in frequent lost comms.  The USB Interrupt channel is being
>> reserved in 5G UPSs for a proprietary protocol.  In order to enable Nut to
>> communicate with the UPS, a poll only configuration is required.  The
>> details of my ups.conf file are as follows:
>>
>> [apc]
>>    driver = usbhid-ups
>>    port = auto
>>    pollonly = 1
>>
>
> The 'pollonly' is a flag, so just listing 'pollonly' here would be enough
> (the '= 1' part is not used). Assuming this is important for this device, we
> should probably automatically disable the interrupt pipe, so this is what
> the revised patch will do upon detecting a 5G UPS.
>

I came to the same conclusion. now to set "use_interrupt_pipe = FALSE;", the
content of r1853 should be moved to upsdrv_initups(), before the claim()
calls.
and the new apc-hid->usb_device_id_t entry (from Chris' patch) should have a
fun pointer to set it.
though that last one was obvious!

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100625/9a463e12/attachment.htm>


More information about the Nut-upsdev mailing list