I'm just curious, how much of your own expense are you covering right now? I am at the tail end of a project that's taken me over a year, and I will tell you this; people will PLEAD and BEG for you to lower your price, NO MATTER what it is. Also, while money will not seem like a huge deal now, because it's interesting, there's a good chance during the tail end of the process (the mind-numbing stuff) you will be forcing yourself with all your effort just to work on the damn thing, and money is a HUGE reason to keep going.
Set your price high. You can always lower it later but it's VERY hard to raise. You absolutely must make this worth your time and effort. At the end of this project you'll realize how much hidden work / corner case finding / idiot proofing has to be done, NEVER short change yourself or let others do it to you. It's one thing to be an engineer working for someone else, and another entirely to be a one man show.
This is super true, DOCUMENTATION, don't feel like you have to plan every single thing in advance, but you will need docs to retain your sanity. Your mind starts to do weird things under stress.
I have a 12 page PDF that I've been adding to as my project's been progressing, stuff like hardware register definitions, how to use the hardware, pitfalls to be aware of, etc.
Consistency with your docs and your code is crucial. Comment the shit out of your code.
PIC is a good choice, I would stay away from AVRs because Atmel loves to EOL products whenever it feels like it.
Anyway, if you have any questions feel free to PM me, I could write a book with all the numerous things I've had to learn over the past while.





Reply With Quote



was surprised when I opened the package. A breakout board ended up saving me.


Bookmarks