Nut upsdev - May 2011 - NUT: new blazer_usb subdriver proposal

Hello,

I've recently bought two cheap UPS
(http://www.ldlc.com/fiche/PB00109242.html).
They're not supported natively by NUT (even though the monitoring
software is UPSilon from megatec).
After some investigation, they almost use the krauler-type
communication already supported in the blazer_usb driver. However, the
UPS won't reply if the language ID is not 0x4095...
Therefore, I cloned the krauler_command, adding the language ID and
unicode to ASCII conversion (taken from libusb). I also enhanced the
error!retry mechanism, as the UPS fails to reply quite often.

Please see the attached patch file.

Any comment would me more than welcome.

Rgds,
Aur?lien
-------------- section suivante --------------
A non-text attachment was scrubbed...
Name: ldlc.patch
Type: application/octet-stream
Size: 2856 bytes
Desc: non disponible
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110514/6917905b/attachment.obj>

Aur?lien Grenotton <agrenott <at> gmail.com> writes:
> 
> Hello,
> 
> I've recently bought two cheap UPS 
(http://www.ldlc.com/fiche/PB00109242.html).
> They're not supported natively by NUT (even though the monitoring
> software is UPSilon from megatec).
> After some investigation, they almost use the krauler-type
> communication already supported in the blazer_usb driver. However, the
> UPS won't reply if the language ID is not 0x4095...
> Therefore, I cloned the krauler_command, adding the language ID and
> unicode to ASCII conversion (taken from libusb). I also enhanced the
> error!retry mechanism, as the UPS fails to reply quite often.
> 
> Please see the attached patch file.
> 
> Any comment would me more than welcome.
> 
> Rgds,
> Aur?lien
> 
Hi Aur?lien!

I'll try your patch... I'm very interested in a UPSilon replacement!

Please, see my posts at:    
http://comments.gmane.org/gmane.comp.monitoring.nut.devel/5012


I suggest two changes:

1) Rename the dialet from "ldlc" to "upsilon", as SEVERAL
no-name UPS uses this
(horrible) software.

2) Add the USB ID "0001:0000" (vendorid=0001 productid=0000) to map
directly
"upsilon" in "blazer_usb"

Finally, can someone accept the patch and can add it to the main branch?

Au revoir!

Citeren Aur?lien Grenotton <agrenott op gmail.com>:
> After some investigation, they almost use the krauler-type
> communication already supported in the blazer_usb driver. However, the
> UPS won't reply if the language ID is not 0x4095...
> Therefore, I cloned the krauler_command, adding the language ID and
> unicode to ASCII conversion (taken from libusb).
Thanks for this patch.
> I also enhanced the error!retry mechanism, as the UPS fails to reply quite
> often.
This will put you at risk for (much more severe) timeout problems with  
the upsd server, so this part of the patch will not be included. But  
since this seems to be a problem for other devices as well, there is  
some merit in the problem you're trying to fix. We probably shouldn't  
complain in the syslog for intermittent problems and only report once  
we have reached the MAXTRIES limit. This needs to be fixed in the  
'blazer.c' base driver (which I did).

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)