|
Well just want add one more thing.
I a both thankful and regretful for starting out using the PIC. Thankful that it was easy to get into and regretful that I invested so much time and oney on a platform that is not as great as other platforms. If I had started out with AVR maybe I would of given up doing anything in ebedded systems because of the learning curve and just done everything using discrete electronics.
|
Good comparison, but there are many issues to consider beyond simple "what is the fastest" or "best bang for buck". There's always going to be a "new kid on the block", but you might not want to hastily jump into bed with him!
|
I beg to differ, I love jumping into beds with new kids. AVR is not a new kid on the block really since they were avialable in the early to mid 90s. You are right that there are alot of other factors involved. Pic does have excellent datasheets, i perfer the pic datasheets over atmel datasheets. Also pics are very tough, it can take a good wack of voltage or force and still perform, they also offer very high flash write cycles. Pics also have lots of goodies for motor control and offer an abundance of A/D ports. My biggest biggest dissapointment is that I have yet to find a pic that can offer PWM of 2 or more frequencies, i really needed that bad.
But honestly everywhere I go people ask why I use the PIC and not the AVR or ARM platform, the simple truth was that I already bought a programmer, bought many PICS, bought several language suites, invested so much time in them that I really did not have the luxury of switching. I can not tell you how many times i had to comprimise my design objectives because the PIC just could not cut the mustard. Most comprimises worked out very well, but sometimes I wonder what I would of achieved with a more powerful platform.
Not all is peaches and cream with the AVR, the documentation of the C language suites is very bad, and to top it off I really knew very little about object oriented C to begin with. For a harware platform that is so good the software sure is nasty. Man imagine what I could do if I had a great toolsuite with excellent documentation and a good forum. Yup the grass is always greener on the other side.
The biggest thing I want to get across to anyone reading this is to try out different platforms and different languages.
|
Umm after re-reading my post I think I came across as "dissing" PICBASIC and its like. Picbasic really is a decent language, I am so comfortable coding in Picbasic and in all truthfullness with a bit more work picbasic would be "all that and a bag of chips". A much more detailed manual would be nice, the manual is something like 300 pages, it sound like alot but the font and the spacing is huge. If the authors put alot more detail in there then that would be fantastic. How bout a book mark tab in the PDF manual? Better support for hardware is another thing that is required, for example most PWM hardware on PICs support 10 bit but PICbasic only offers 8 bit, or how bout having a real interrupt routine. Maybe getting rid of some routines that are a bit odd, the RC time thing was odd, and what is the real difference between SERIN and SERIN 2?
|
Hi, Toalan
I've found Mel very very kind in her answer ...
you just have to know what you really want ... should be difficult !!!
... for your charge pump: this is simply called a capacitor ...
Alain
|
Whats this "Proteus" compiler? I know they offer support for a number of compilers including AVR's and VSM's but I have never seen there compiler.
Do you have a URL?
|
As i know, Proteus is not a compiler but a simulator. Voted to be one of the best on the market... as i heard....Originally Posted by OXIMBIT
here's the link http://www.labcenter.co.uk/
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
Capacitor wont' work in my case, i already considered it.
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks