Hi, Thanks for your answer, I'll be interested in your feedback. No problem to change the subdriver name, I had no imagination to choose one. Concerning the auto registration, the buggy 0001:0000 code is already used for another model/subdriver, and I wasn't sure we could declare it twice.
Rgds, Aurelien 2011/5/17 trantore <[email protected]>: > 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! > > > > _______________________________________________ > Nut-upsdev mailing list > [email protected] > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
