From: Peter S. <pe...@st...> - 2009-05-16 20:48:03
|
Hugo Solis wrote: > Thanks so much for you quick response. I really appreciate it. You're welcome! Thanks for coming back on list so that others can help you better, and so that replies will be available in archives for your followers! >> libusb is not active in this regard. Recognition happens in the >> operating system kernel and the USB support there. > > Do you mean that I still need a driver for the device I am using. No, not beyond the general USB support in the system. > It's seems -or at least I have not found after hours and hours- a > driver for the usb chip that my device is using. I tough libusb > could replace it. libusb is never a 1:1 replacement for a kernel driver, but maybe it will be suitable for you! > How can I know if my device is been recognized by the Mac computer. > I guess it is because people manage to use it on Mac. It should be recognized. Maybe look for it in "About this Mac" and the device listing available there. >> At best you will be able to communicate with the device by writing >> an application that utilizes libusb. > > I am fine writing the application using libusb -I will use > Javalibusb- but once that I have access to the device I do not know > what to send to it if it's expecting a serial protocol. Maybe I am > totally confuse. Ah yes! This is the key. We have no idea what protocol the device expects. The fact that it shows up as a serial device in some operating systems unfortunately does not mean anything, because the kernel drivers in those systems can communicate in any way with the device via USB. Maybe you can look to the Linux/BSD communities for more information about the particular device? Or even the vendor itself? Maybe the Raven documentation details the USB communication used by the device and/or it's firmware? Recommend looking at the USB specification if you end up writing a libusb application (directly or through wrapper) because there are some things that need to be right, and vendor documentation is not always helpful enough, so getting everything correct requires good understanding of the several USB protocol layers, as well as lots of trial and error. But once every now and then, vendors surprise you and have made simple and efficient designs with good documentation. Maybe you're one of the lucky few - it could happen! :) //Peter |