[Nut-upsdev] Re: [Nut-upsuser] Ablerex 625L USB version

[Jon Gough]

Alexander,
    I have tried stopping and starting the driver a couple of times 
and it all seems to work OK. No error messages.

    As for using the usb_control_msg, the details on using it seem a 
little obscure. I think you have to read the HID manual and then 
guess. The online help in the libusb-devel is next to useless, as it 
does not describe the parameters or their settings. Anyway, if you 
have the details of how to use this call then can you let me have a 
copy so that I can better understand it.

Regards
    Jon

At 09:27 3/02/2007, Alexander I. Gordeev wrote:
>Hi Jon,
>
>Jon wrote:
> >  Alexander,
> >     I have just done a test with your code and it does work.
>
>My primary concern is an error, I was talking about in my previous
>posts.
>Did you have it?
>It only appears when you start the driver, then stop it and start it
>again.
>
> >     I was doing my work on the latest stuff from SVN to see if that
> > would help in my investigations. I did not apply the patches from
> > previous mails, just used the code in the later modules (the 
> patch process produced errors).
>
> >     It does not matter which version we use as both work for me,
> > now. We just need to implement a few more commands into your code,
> > if we use that, and work out how to implement the code that sends
> > data to the UPS, ie the S<n>, S<n>R<m> and T<n> commands. I also
> > want to implement the TL, C and  CT commands, but I whilst I can see
> > the reaction to these it is a little difficult to work out the code to use.
>
>I'll try to figure it out. usbsnoop will help me :)
>
> >     I think the F command may need a little more work as I think it
> > may need to issue the '0x01' command first to get the manufacturer.
>
>I think it won't be very hard to make it universal for both our
>devices.
>
> >     Anyway, both sets of code work, for me at least, so it is up to
> > the powers that be to decide which way to go.
>
>It's no need to throw away any code.
>Since you've already written a working driver it can be used as well.
>I think we should merge our subdrivers into one.
>
>Jon wrote:
> >  Peter,
> >     The only changes that were needed was the addition of the
> > get/set Ablerex code, or the using of the Krauler stuff for Ablerex.
> > The 'usb_get_string_simple' does the same job as
> > 'usb_get_descriptor', the former just has one less parameter, and
> > during my investigations the simpler the better.
>
>Thwy are slightly different as I know. Anyway I have a plan to change
>'usb_get_descriptor' to 'usb_control_msg' to test if it can help to
>reduce "USB No Ack" responses. There is yet another parameter you can
>specify in that function - timeout. I tnik, it could help.
>
>--
>  Alexander                          mailto:lasaine at lvk.cs.msu.su




---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 000709-2, 01/02/2007
Tested on: 3/02/2007 10:41:30 AM
avast! is copyright (c) 2000-2007 ALWIL Software.
http://www.avast.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070203/15c9c6b4/attachment.html