serial communication is really much 'simpler' than USB, but so far as i can tell also similar in many ways... with usb, like serial, you setup variables to store incoming and outgoing data. you have interrupts deal with data you are not quite ready for.. then you parse the data and do it all over... just like RS232..

USB gets confusing quickly because the framework requires certain 'environmental standards', such as endpoints, product ids, vendor ids, device class definitions, packet size settings..

again, sir, please, checkout a) the wikipedia entries on USB and HID b)www.mecanique.co.uk c)usb 1.1 spec at usb.org d)mister e's demo

if you cannot make progress in this manner, i would recommend you abandon 'USB', and look into FTDI type solutions... USB => serial chips\adapters\boards/



programming these devices in not for the faint of heart, nor does it take a genius.. but you do need able to comprehend a+b+c= abc. (this of course being a metaphor.. not pseudo-code)


and the new thread for jukeboxes.. it could be in the sandbox... as it would be 'off topic'. and now it is time to enter the fridgid chicago night to drink in public. ciao. ciao.

Robert