We really like the mega168, so we’ll probably have some form of robot controller based on it for as long as they are available.
We had an AVR programmer in the works (including first revision PCBs and code) way before the X2, but I think the thing that initially stalled us was consideration for multiple operating voltages and the necessary clock speeds to run at low voltages but support 115 kpbs like the AVRISP. But supporting all kinds of different AVRs wasn’t something we really wanted to do, and we couldn’t compete with Atmel’s low-cost tools. The thing that really justified a built-in programmer on the X2 was the realization that it could also serve as a co-processor when the target device was running. Once we had the code working on the X2, we made a new programmer; it’s completely different from the original unit we were working on, and it only works at 5 V and 20 MHz.
We like AVR Studio and expect to use it for our examples. For me, setting up the IDE is something I do once in a long while, so I tend to forget if there were any issues getting things running. I think the problems often revolve around support for new programmers and processors, and since we’re not changing either, I hope we’ll be set.
The LCD we’re using isn’t from Crystalfontz. I just looked at the one they have (they didn’t have that last year, I think), and it looks similar, so we’ll have a backup if our current source runs out. We don’t intend to discontinue the Orangutan, but we are thinking of a few modifications we’d like to see on future revisions. Would you mind a slightly bigger unit if it meant a bigger operating voltage range and higher-power motor drivers?
- Jan