Hi
tis 2006-07-25 klockan 13:49 -0500 skrev John H.:> is there 3110us support yet?
>
No, not for the usb. But it does not do any more on usb then on
the generic contact driver. There is no voltage or current or
battery data, just indication that it is OL or OB.
To support 3110 and the 5115 on usb the driver need a ugly hack.
They don't conform to the bcmxcp standard.
(The strange thing is that the 5115 is working Ok on the serial line,
and follows the standard.)
On an 'ID_BLOCK_REQUEST' it sends a packet that have number 0x01 this
indicate that it should be followed by a new packet 0x02 or 0x82 if
it is the last. This does not happen.
Even the windows driver reset the pipe at this and also have problem
to read the 'STATUS_REQUEST' that follows.
The usb implementation is an early one, done by Powercom.
And if you look at http://www.powerware.com/end_of_life/products.asp
you see that 3110 is out of production and is replaced by the 3105.
And that one runs great on the bcmxcp_usb driver.
So i would not break the driver to support it on usb when it is
supported by the generic driver.
But if you can send me some good SnoopyPro log's on the traffic from
the windows driver i would dig some deeper into the problem.
Regards
Kjell