[exposition]
So if anyone’s willing to stay with me on this? I’m trying to brainstorm all possible methods to actually produce this capability. It would greatly help in completing my Master’s thesis. I want to be able to send and interpret the USB signals wirelessly from a Canon Digital Rebel camera. I’m building a portable image capturing system to gather data as part of a system. Currently I’m just using a cheap wired webcam, but the use of a professional camera lends more credibility to the experiment, if I’m just SOL, oh well.
[/exposition]
MGP:
There are a few manufacturers that make host controller chips for embedded applications (Cypress, TransDimension are a couple that come to mind). They offload a lot of the USB stack to hardware but it still takes a lot of CPU horsepower to keep up with USB packets. They are made more for applications like embedded Linux where you have a real OS but no chipsets with USB controller hardware.
I have a platform I could develop on (an ARM chip running uClinux.) I’d have to add USB drivers to the device, though, but maybe there’s a direction…
MGP:
There is also the issue of drivers for the host side – you need a specific driver for every client device.
Alright, let’s narrow the field to my very specific device, a digital camera with USB interface. I have the SDK for the camera including all drivers and libraries for accessing information on the camera (C++ code, ect.) But yeah, it’s still aimed at USB communication, I’ll look into the comm libraires for the device, though… Maybe there is room for other protocols. Then again I’d rather not crack the case on my expensive camera to get to the data lines.
MGP:
Sadly, the developers of USB really made the assumption that any device on the bus would be connected to a PC host. As much as they’d like to sell it as a replacment for RS-232, it’s not since it’s a host-client arrangement and RS-232 isn’t.
It figures. So there are USB controller, trancievers and other devices, but they are meant to back up to a processor with a driver, and all conversions to other protocols require driver policing because it’s host/clent and has a packet structure.
Right, more googling and forumn searching for me.
Thanks for at least humoring me so far. If anyone does contribute information that moves me significantly forward, they will recieve credit in all publications for the project. (ooh! ahh!)