At Thu, 20 Oct 2011 17:41:46 -0400 Alan Ott <
[hidden email]> wrote:
>
> On 10/20/2011 04:53 PM, Robert Heller wrote:
> > At Thu, 20 Oct 2011 16:16:29 -0400 Robert Heller <
[hidden email]> wrote:
> >
> >> I am getting LIBUSB_ERROR_IO (-1) from libusb_interrupt_transfer on an
> >> input endpoint. What are the reasons for getting this error?
> >>
> >> The code *used* to work with the libusb-0.1 API, but now fails with the
> >> libusb-1.0 API and I am trying to figure out why.
> > BTW: I am using CentOS 5.6, 2.6.18-274.el5xen on a x86_64,
> > libusb-1.0.8, libstdc++-4.1.2-51.el5, and gcc-4.1.2-51.el5.
> >
> > (libusb_interrupt_transfers to the the output endpoint just fine, no
> > problems at all there.)
> >
> > This is with a PI Engineering Rail Driver Console.
> >
>
> I recently implemented the PIEHid API for PI Engineering on Linux.
>
> Github code is here:
>
https://github.com/piengineering/xkeys/>
> It provides the same API as PI's Windows DLL and works with the X-Keys
> devices so that code written for their Windows libraries can easily port
> over. I assume RailDriver is similar to X-Keys.
>
> The X-Keys SDK actually provides a couple of extra features beyond what
> HIDAPI normally does that you might be interested in, such as
> callback-delivered reports, and the ability to look at the latest report
> which has arrived (without clearing the buffer). It is of course based
> on HIDAPI, and comes with a test GUI program. I think this is what you
> want instead of using libusb directly.
I am not sure. My RailDriver code is meant to run as a daemon, allowing
for several *different* processes access different parts of the
interface. One oddness with the RailDriver is that it is also an output
device: it has a three digit 'speedometer' (three 7-segment LED digits)
and has a switch for a powered speaker.
The RailDriver driver has 4 levers (reverser, throttle/dynamic brake,
auto (trainline) brake , indepentent (loco only) brake, plus a switch
for the horn, switches for wipers and lights, lever switches for range
and e-stop, push buttons for Alert, Sand, Pantograph, and bell. Plus a
whole pile of random buttons, an up/down control and a 4-way control.
The thing is, I had it all working with the libusb-0.1 library and don't
understand why it is not working with the libusb-1.0 library. The
*output* endpoint is working just fine, but the input is just getting a
-1 status (LIBUSB_ERROR_IO) for no descernable reason.
I'll download your code and see if it prodvides enlightenment...
>
> If you try it, let me know how it works for you.
>
> Alan.
>
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
>
http://p.sf.net/sfu/cisco-dev2dev> _______________________________________________
> Libusb-devel mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/libusb-devel>
>
--
Robert Heller -- 978-544-6933 /
[hidden email]
Deepwoods Software --
http://www.deepsoft.com/() ascii ribbon campaign -- against html e-mail
/\ www.asciiribbon.org -- against proprietary attachments
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Locked
