> > Sending a control message to an interrupt endpoint? Looks suspicious. > The message should be sent to the control endpoint. > > > gcc usb-cashdrawer.c and never looked back. > > At least if you want to use the interrupt endpoint, that's the right > approach. But for just sending control messages, try libusb. If you > know C better than perl, use libusb directly instead of the perl module. >
Thanks for your comments. The information I provided (and interpretation) was purely for your enjoyment :) I dont really know what I am talking about but I am willing to learn. In the commands I have provided how would I get the value for the control endpoint? (minor request) The real question is, can anyone provide me with a c program or modifications to my tries (earlier email) that will compile that would mimic this simple communication and open my drawer? If there is any more information anyone needs, I will be happy to submit it. Actually, let me post the whole log on the net... just in case someone is willing (wow would that make my day! ;). http://www.aero.und.edu/~caylan/cashdrawer_usbSniff.log All I need is a starting point and I can take it from their. I can decipher my own logs, its just the initial communication. Remember, "fb" is used to open the drawer in some way, they are toward the end, (just in case you do take on this challenge). Thanks to anyone who can help, Caylan ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
