^yeah, that is nearly how it has been for the last couple years.. now this project absolutely requires it, so there is no better time..
i understand what you guys are saying.. ibf, i think the paint program is a excellent example.. and i want custom work, i'm not interested in the copy/paste method-- never have been--hence why i am doing these led projects from scratch in the first place!
best is always relative, i guess i should have said 'preferred' ;) -- like you guys asking me who makes the best speaker ;)
i do have a small breadboard, but if a microcontroller development kit is better for the job, i'll get one--i'm sick of trying to make the wrong stuff work if there is a better solution.
any recommendations for books on learning all of this?
also--looking at getting the DV164120 dev kit..
or possibly the DV164121? not really sure about requiring in-circuit debugging..
PICkit is probably the best for you to start with. Debugger is useful of course.
Dont forget MPLAB also comes with simulator where you can step through your code to make sure it is 100% working.
Books, I bought 2 a while ago and they ended up in the bin. I didnt find it very useful at all, the style just didnt fit me.
Theres plenty of example off the net. The kit you get from microchip should come with tutorials, usually flashing LEDs, reading analog/digital inputs, etc etc.
Once you got the hang of it, bet you wanna play with USB, cant do that with 555s :lol:
Boy this thread has been busy...
Here i the 555 circuit I mentioned (on page 1):
It's only about 400Hz, but should be ok for 4kHz or 40kHz (555 max-freq is ~100kHz).
Changing C1 from 1.8nF to 0.18n should be about 4kHz. Maybe try a .1nF (100pF)?
Changing voltage won't work. The usual problem is that dimming is not proportional to voltage (and the voltage is around the normal operating voltage - not from 0V to 2V etc).
But with different colored LEDs... no go.
LEDs are current (Amps) devices, hence PWM is needed for dimming.
I liked ibf's comments (eg, reply #9. I love ASM for its exactness and simplicity, though "simplicity" is once you are quite familiar with the CPU's commands. I found that intending to use ASM for another CPU was NOT that simple - my older 68HC11 and similar were quite different to the ATMega328 (Arduino) - not that I was too dedicated, and I went for "understanding all" (instructions aka commands) rather than just finding a few for a specific (and simple) application.
If I had to do it tomorrow (aka next year for me), I'd probably use my aforementioned PICAXE-08M - 8 pins with no timebase (crystal) required; a 5V regulator; a FET to power the LEDs (and maybe 2 resistors); plus 2 resistors and 1 wire for serial comms (to a PC SERIAL port) - and various free programming tools. Or so I understand.
Thats what I love about asm, with PIC theres less instructions so its much easier to learn in a way. True what you said about learning one MCU and trying to use that knowledge to another. But once you got the basic its pretty easy to pick up. Old school stuff but I think asm is still important to really appreciate MCUs, make you read and understand the datasheet too :lol:
Originally Posted by OldSpark
I remember my very first MCU experience using the Z80 board when I was a kid. It had 2 rotary hex switch and an enter button, you enter directly in HEX banghead. Its difficult but it was very enjoyable, seeing those LED flashes was like WOW, couldnt used the Z80 I learnt directly on the 68000 in the amigas so had to re learn again. I hated myself for having a big gap in my MCU experience, didnt do anything again until I bought my first PIC demo. The UNI I attended didnt help much either although the degree was called "software engineering for real time system" No idea why my school/colllege/uni kept feeding us with pascal. I learnt more useful things at home doing projects in my spare time than spending years in UNI... ah well.