NEW to usb programming, lot of reading and long microsoft program examples.
Your articles in USB, clear and easy to read.
My questions only due to not having any programming experience with usb, (Only RS232)
1- all writing refer to host. I could not be sure the reference to host means app or driver or OS.
2- this statement "After successful enumeration, the device will be known to the host and an application will be needed to make use of the USB communication."
That the only sentence I found that separate the term host form app....
3- simple answers yes or no would go long way:
can we define the host: host = OS which sense the usb device D+/- connection,
then the driver selected by OS.
now configuration by driver or by app?
Sample very long programs not clear they driver sample only or app included in the code (super MUTT)?
enumeration, configuration, etc.. proper sequence by host: define host as driver or this an app do all that?
App control transfer = start asking for info to get configuration and setup config, interface,?
Where this starts and doe the app called "Host" while sense device and set up its nformation, using host = driver, till finally the app become aware of USB device driver loaded and USB-comm now possible ... start with control transfer, then stream data, ....
lor of question but one unclear , what the host means = OS, driver combination and where app begins it function.
Specifically, the auto-play sample, I can understand that the driver (I assume) will trigger
the app to starts.. that also, means that the app itself has such code/not obvious/ and it begins the configuration setup interface selection, ....
MY last question: I am trying to access CMOS-camera-C-mount type, for vision.
The vendor SW proprietary:
1- does this code can accept another cameras from different vendors, and apply their api as #include?
2- if we build standard usb program: does the different vendor(s) driver(s) can be installed and used with the standard app to mix different usb cameras and devices, and thus each enumeration "discover=detect" the component and address through its vendor driver and set up and issue commands for each addressed known component.? Does this scheme valid and will work correctly.
This will be appreciated greatly,
wolvel
Your articles in USB, clear and easy to read.
My questions only due to not having any programming experience with usb, (Only RS232)
1- all writing refer to host. I could not be sure the reference to host means app or driver or OS.
2- this statement "After successful enumeration, the device will be known to the host and an application will be needed to make use of the USB communication."
That the only sentence I found that separate the term host form app....
3- simple answers yes or no would go long way:
can we define the host: host = OS which sense the usb device D+/- connection,
then the driver selected by OS.
now configuration by driver or by app?
Sample very long programs not clear they driver sample only or app included in the code (super MUTT)?
enumeration, configuration, etc.. proper sequence by host: define host as driver or this an app do all that?
App control transfer = start asking for info to get configuration and setup config, interface,?
Where this starts and doe the app called "Host" while sense device and set up its nformation, using host = driver, till finally the app become aware of USB device driver loaded and USB-comm now possible ... start with control transfer, then stream data, ....
lor of question but one unclear , what the host means = OS, driver combination and where app begins it function.
Specifically, the auto-play sample, I can understand that the driver (I assume) will trigger
the app to starts.. that also, means that the app itself has such code/not obvious/ and it begins the configuration setup interface selection, ....
MY last question: I am trying to access CMOS-camera-C-mount type, for vision.
The vendor SW proprietary:
1- does this code can accept another cameras from different vendors, and apply their api as #include?
2- if we build standard usb program: does the different vendor(s) driver(s) can be installed and used with the standard app to mix different usb cameras and devices, and thus each enumeration "discover=detect" the component and address through its vendor driver and set up and issue commands for each addressed known component.? Does this scheme valid and will work correctly.
This will be appreciated greatly,
wolvel