Hi Alexander,<br>Thanks for getting back to me on this. Unfortunately it's still a no-go. The driver still fails in the same manner - only it takes longer to do so:<br>---snippet---<br>Q1 detail: (0 bytes) =><br>Asking for UPS status [Q1]...
<br>Q1 => FAILED [short read]<br>Q1 detail: (0 bytes) =><br>Asking for UPS status [Q1]...<br>Q1 => FAILED [short read]<br>Q1 detail: (0 bytes) =><br>Asking for UPS status [Q1]...<br>Q1 => FAILED [short read]
<br>---snippet---<br>
<br>Let me know if there's anything else you want me to try and/or if you want to instrument a debug driver to provide us with further output.<br><br>Thanks,<br><br>Joe<br>P.S. I should still have a USB capture (taken from Windows) some two years when I had originally tried to get this to work with Charles. If that's of any use, I can dig it up and forward it.
<br><br><div class="gmail_quote">On Jan 16, 2008 3:36 PM, Alexander I. Gordeev <<a href="mailto:lasaine@lvk.cs.msu.su">lasaine@lvk.cs.msu.su</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Tue, 15 Jan 2008 02:05:31 +0300, Joseph Borg <<a href="mailto:juu.borg@gmail.com">juu.borg@gmail.com</a>> wrote:<br><br>> Pls ignore the previous email; I had subdriver=agiler configured in
ups.conf.<br>> It still fails however as follows:<br>> -------------<br>> Checking device (0F03/0001) (001/002)<br>> - VendorID: 0f03<br>> - ProductID: 0001<br>> - Manufacturer: Ver 1.0<br>> - Product: USB To RS232 Interface (
V1.0) BaudRate 2400bps<br>> - Serial Number: unknown<br>> - Bus: 001<br>> Trying to match device<br>> Device matches<br>> Starting UPS detection process...<br>> Asking for UPS status [Q1]...<br>> Q1 => FAILED [short read]
<br>> Q1 detail: (0 bytes) =><br>> Asking for UPS status [Q1]...<br>> Q1 => FAILED [short read]<br>> Q1 detail: (0 bytes) =><br>> Asking for UPS status [Q1]...<br>> Q1 => FAILED [short read]<br>
> Q1 detail: (0 bytes) =><br>> Asking for UPS status [Q1]...<br>> Q1 => FAILED [short read]<br>> Q1 detail: (0 bytes) =><br>> Asking for UPS status [Q1]...<br>> Q1 => FAILED [short read]<br>> Q1 detail: (0 bytes) =>
<br>> 5 out of 5 detection attempts failed (minimum failures: 2).<br>> Megatec protocol UPS not detected.<br>> -----------------------<br>><br><br></div></div>[off-topic]<br>I've reviewed both an old agiler subdriver from
2.2.0 and the new phoenix<br>subdriver from the trunk. IMO the old subdriver looks cleaner. Also I don't<br>like the way some commands are cut out. There is only one model known that<br>doesn't support them and it has unique VID:PID combination (06da:0003).
<br>This should be fixed. I'm going to add some flag for that.<br>[/off-topic]<br><br>I think this problem is caused by reduced timeout in new phoenix driver.<br>Joseph, please try this patch:<br><br>Index: drivers/megatec_usb.c
<br>===================================================================<br>--- drivers/megatec_usb.c (revision 1225)<br>+++ drivers/megatec_usb.c (working copy)<br>@@ -449,7 +449,7 @@<br> for (count = 8; count <= buffer_size; count += 8) {
<br><br> /* Read data in 8-byte chunks, break on a timeout */<br>- if (usb->get_interrupt(udev, (unsigned char *)&buffer[count-8], 8, 1000) < 0) {<br>+ if (usb->get_interrupt(udev, (unsigned char *)&buffer[count-8], 8, 5000) < 0) {
<br> return count-8;<br> }<br><br><br>--<br><font color="#888888"> Alexander<br></font></blockquote></div><br>