Re: Talking to USB

From: roland (roland.demeester_at_skynet.be)
Date: 11/28/04

  • Next message: Yuri O: "Re: OpenFileDialog.DereferenceLinks property does not work?" 
    Date: Sun, 28 Nov 2004 17:56:32 +0100

    Don
    You don't have to "talk" to the USB Bus, but to the driver. The driver is
    your interface to the bus. For you it's irrelevant whether the scanner is
    connected to the USB bus or to some wire: the driver is taking care about
    that.
    roland

    "Don" <phoney.email@yahoo.com> wrote in message
    news:41a9d4a7.9483976@news.individual.net...
    > Hi Roland,
    >
    > I do have the SDK but it's provided on "as is" basis. However, the SDK
    > does *not* address the actual USB communications! In other words, I
    > know all the low level commands and what to expect back.
    >
    > The missing piece is how do I send these commands down the USB pipe?
    >
    > In theory, that should be the most elementary bit but it's turning out
    > to be a veritable nightmare.
    >
    > Don.
    >
    > On Sun, 28 Nov 2004 13:05:43 +0100, "roland"
    > <roland.demeester@skynet.be> wrote:
    >
    > >Don
    > >Have you "contacted" the supplier of the driver (not the device, I found
    out
    > >that a lot of hardware vendors are not developing their own driver, but
    are
    > >buying it from a company developing drivers)? What you need (I assume,
    don't
    > >take it for granted!) is the documentation and library to help you
    > >communicating with the API's of your driver. I think the only
    standardized
    > >protocol is the lowest level communication protocol over the USB bus, but
    it
    > >doesn't go much further than that I'm afraid.
    > >Roland
    > >
    > >"Don" <phoney.email@yahoo.com> wrote in message
    > >news:41a88c32.11305000@news.individual.net...
    > >> Hi Roland,
    > >>
    > >> In my case it's a scanner but I can't use TWAIN because it's too high
    > >> level. I have a list of low level commands which I wish to send to the
    > >> scanner directly because they go beyond TWAIN capabilities.
    > >>
    > >> I'm beginning to realize that USB is not as simple as I thought but I
    > >> expected at least some common approach to the most basic level i.e.
    > >> identifying devices and then simple sending and receiving of bytes.
    > >>
    > >> Don.
    > >>
    > >> On Sat, 27 Nov 2004 13:42:20 +0100, "roland"
    > >> <roland.demeester@skynet.be> wrote:
    > >>
    > >> >Don
    > >> >I recently had to write an interface with a serial device that was
    > >connected
    > >> >through a usb-to-serial convertor. I spent some time browsing the net
    and
    > >I
    > >> >learned that there is no such thing as as a USB port and a USB
    protocol:
    > >you
    > >> >have to interface directly with the API's the USB driver for the
    device
    > >> >provides for.
    > >> >In my case the USB2COM convertor provided for a virtual serial port
    that
    > >I
    > >> >could communicate with, so it was fairly transparent. Unfortunately I
    > >cannot
    > >> >point you to any exemple that interfaces directly with the API's of a
    USB
    > >> >driver.
    > >> >Greetings, Roland
    > >> >
    > >> >"Don" <phoney.email@yahoo.com> wrote in message
    > >> >news:41a74dba.8602887@news.individual.net...
    > >> >> Environment: VB6 under W98
    > >> >>
    > >> >> I have a USB hardware device I wish to program directly. The
    original
    > >> >> software installed a low level driver and the hardware is both
    > >> >> registered and operational.
    > >> >>
    > >> >> Now then, I'd like to have access to this device directly. In other
    > >> >> words, I'd like to enumerate all devices on the USB bus, pick the
    one
    > >> >> I want, and then communicate with it (send commands, get data, etc).
    > >> >>
    > >> >> So, how does one go about talking to the USB? VB6/W98 combo doesn't
    > >> >> seem to have any dedicated USB routines.
    > >> >>
    > >> >> What I need - I guess - is the USB equivalent of the MSComm control.
    > >> >> Is there such a thing as a "USB Control"? What's the canonical way
    of
    > >> >> talking to USB from VB?
    > >> >>
    > >> >> I did google around a bit but couldn't find anything applicable.
    Most
    > >> >> sites and pages I came across seem to focus on actually writing a
    low
    > >> >> level USB driver.
    > >> >>
    > >> >> Thanks!
    > >> >>
    > >> >> Don.
    > >> >
    > >> >
    > >>
    > >
    > >
    >

  • Next message: Yuri O: "Re: OpenFileDialog.DereferenceLinks property does not work?"

    Relevant Pages

    • Re: how the vmware windows virtual machine connect the usb device from
      ... I know a USB bus filter driver can modify the device IDs reported ... Let us move our eyes to the virtual machine side. ... the Microsoft usb host controller driver does the actual ...
      (microsoft.public.development.device.drivers)
    • PROBLEM: no Compaq USB on 2.4.22
      ... following in dmesg: ... usb.c: registered new driver usbdevfs ... new USB bus registered, ... Libranet 2.8 configuration which includes almost everything as modules. ...
      (Linux-Kernel)
    • Re: [SLE] Modules at startup
      ... Probably at the point that the usb bus gets looked at. ... >>But the dmesg should show you that. ... > usbcore: registered new driver usbfs ... > Linux Kernel Card Services ...
      (SuSE)
    • Re: [SLE] Modules at startup
      ... Probably at the point that the usb bus gets looked at. ... > But the dmesg should show you that. ... Uniform CD-ROM driver Revision: 3.20 ... usbcore: registered new driver usbfs ...
      (SuSE)
    • [git pull] Input updates for post-2.6.21
      ... psmouse - allow disabing certain protocol extensions ... cobalt buttons - separate device and driver registration ... wistron - add support for TravelMate 610 ... ads7846 - add support for the ads7843 touchscreen ...
      (Linux-Kernel)