Nut upsdev - Jun 2010 - megatec_usb.c modification for UPSONIC PROFFICE 650 USB

Hi Heinz,

2010/5/30 heinz
> Thank you for your nut-2.4.3 system. I had big troubles getting it to work
> with the UPSONIC PROFFICE 650 UPS in USB mode.
>
> I had to rewrite the get_data_phoenix() function in drivers/megatec_usb.c
> file.
> It now appears to be working correctly. I have attached the source of the
> modified function in case you might want to add it to a future version.
>
first, thanks for your report. Though it's always better to report to the
NUT list ;-)
code changes are also better using patch (ie diff against the original
code).
so I've generated one, attached.

that being said, you should give a try to blazer_usb, the successor of the
megatec_usb driver.
we will be interested in a debug output (ie /path/to/blazer_usb -DDDDD -a
<upsname>
along with the output of "lsusb -v" excerpt of your device.

now, since I don't know much about these drivers, I'll let Arjen comment
on
the patch itself.

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/20100630/f10066c3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: megatec-upssonic.diff
Type: text/x-patch
Size: 1175 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100630/f10066c3/attachment.bin>

Citeren Arnaud Quette <arnaud.quette op free.fr>:
> that being said, you should give a try to blazer_usb, the successor of the
> megatec_usb driver.
> we will be interested in a debug output (ie /path/to/blazer_usb -DDDDD -a
> <upsname>
> along with the output of "lsusb -v" excerpt of your device.
For the blazer_usb driver, -DDD (debug level 3) is enough. Unless you  
also want to debug the communication on the driver socket (for upsd),  
running a driver with debug level 5 (-DDDDD) is usually a bad idea.
> now, since I don't know much about these drivers, I'll let Arjen
comment on
> the patch itself.
At the very least, we'll need the USB ID of this device. Back in 2007,  
this model used the 0665:5161 (Cypress Semiconductor) USB to serial  
converter. If this is still used today, you should be fine running the  
blazer_usb driver. Be sure to read 'man 8 blazer' before asking for  
help.

The megatec_usb driver is a legacy driver that is not being actively  
maintained. We won't accept patches for megatec_usb at this time. Your  
modification also breaks the driver for USB to serial converters that  
require reading until a timeout occurs.

Best regards, Arjen
-- 
Please keep list traffic on the list