them in an autonomous robot. I'm 'fairly' comfortable with using one,
but the magic '86 bytes' limits how many sensors, servos etc. can be
controlled simultaneously.
I thought that basically using one for motor control and navigation,
and the other for extra sensors etc. (LCD, lasers, LEDs, compass,
alcohol sensors) might be the best, but I bow to the combined wisdom
of this forum.
I think using I2C for communication between them is the right method
(as per manual and docs) but I'm kind of hazy on the particulars in
spite of the examples available.
Could someone with a larger brain outline, in block format, the
easiest/most useful methodology for this? I can fill in the code
specifics (the fun part!) myself, but some direction and advice would
be greatly appreciated. I don't want to waste hours (days?) on code
only to find a simpler solution exists somewhere else.
Something like:
{Oopic 1 code - controls motors/nav}
Interface code between Oopics
{Oopic 2 code - sensors and whatever else can be wedged in}
Am I ANYWHERE near a workable solution?
Thanks in advance!
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment