Lindy Mayfield wrote:

> I'd really like to see that when you finish it!
>
> The reason I asked is because I was curious how you were going to organize the
different Pics.  I've not build a substantial robot myself (except for kits) but
I would like to and in my head I envision Pics controlling the various
subsystems with a master Pic (or something more powerful) that does the
"thinking".  When I get to the how-to I was thinking a bus master/slave
configuration using I2C (or better?) serial protocol for this.
>
> I hope you post here when you have things working and documented. (-:
>

Hi Lindy,

I will post here if the service is still available (there is currently some talk
about it being dropped by MIT). If things do go bad write to me privately I am
always happy to talk to people.

With regards to comms, I was thinking low priority background comms driven by a
virtual clock. I have done some work on this and it looks VERY promising.

Splitting up the robot into several subsystems and using one or more PICs to
control each of these I beleive it should be possible to greatly reduce the
power of the CPU needed to do the actual thinking.

Regards
Sergio Masci

http://www.xcprod.com/titan/XCSB - optimising PIC compiler
FREE for personal non-commercial use





-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist