>
> Why not use PIC chips for control:-
>
> PIC 1 could run motor control and tracking /avoidance, etc.
>
> The oopic would put out a single command to PIC 1 FORWARD or
REVERSE.
>
> PIC 2 could handle sensors, etc.
>
> PIC 3 ........?
>
> Just a thought into the pot :-)
>
> Gordon.
> >
>
Hi Gordon
2 reasons: first, I have 2 Oopic Rs, second, I'm not familiar with
PICs per se. My programming skills don't extend to C, I'm only
moderately comfortable with VB. I like the Oopics because I can
leverage my (limited) programming skills into them much easier. Otto
(my robot) has no crying need for super-quick responses (as yet.) I'm
sure a skilled programmer could optimize material usage and make me
look like an egg, but I'm doing this all by my lonesome and starting
on a new (to me) language might push Otto's completion date into the
next millenium.
Still, I will take some time to look into that, as well as the
(simpler) solutions recommended by DLC. I'm leaning towards DLC's
ideas, since it may mean I can accomplish something without grafting
on a new brain (on ME!)
Otto Says:
"Remember, it ain't a real robot unless it has lasers coming out of
its eyes!"
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