Nice job Jukeman.
I'm still a D.J. in nightclub here... and yes i remind those yearsI think everybody tried to build their own equipment. At least Mixer and Light Chaser. Mine was made with an old Commodore Vic-20
Good luck!
Nice job Jukeman.
I'm still a D.J. in nightclub here... and yes i remind those yearsI think everybody tried to build their own equipment. At least Mixer and Light Chaser. Mine was made with an old Commodore Vic-20
Good luck!
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Ah! Yes! The Vic20 and the Commodore64, that's what i learned programming on. Wow it's amazing how much we all have in common. I suppose you guys have been into remote control cars etc.
You guys need to keep checking my site, i am going to add a bunch of pictures.
Say what is a good book to learn the 4550 or pic projects?
Kevin
Last edited by jukeman; - 16th February 2007 at 11:38.
now that is is back on topic ( i have had 3 or 4 RC cars.. 'real ones'. commodore -> 286 -> 386 - 386 w hdd -> p1 -> p2 and so on..)
i just picked up jan axelson's 'USB Complete'. The choice was between that and another, more technical looking book.. really, what it comes down to is USB is not a parallel port - it is closer to a serial port, but worse...
Because USB was written to be extensible and provide an 'all inclusive' framework, it is quite complex... The USB Complete book is a good place to start, if you are too lazy to read the USB spec sheets(usb.org), or want something you can take on the commute to work, or something..
really though, the first step is too find a working code example, and get it working on your breadboard. The USBdemo provided by mister_E is a fabulous place to start. It is 'easy' compared to trying to do your own project immediately...
(start a new thread about jukeboxes)
Robert.
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
Bookmarks