Subject:
|
Re: Design
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 1 Dec 2005 09:58:24 GMT
|
Original-From:
|
PeterBalch <PETERBALCH@COMPUSERVE.stopspammersCOM>
|
Viewed:
|
1458 times
|
| |
|
|
> I'd really like to find out what techniques/notations people
> are using to design their robots and code.
For designing robots, I just search the web to see what other people have
done. As Tom Lehrer said "Plagiarise, plagiarise - but always call it
Reseach".
For the software for mobile robots, I don't think anything beats Rodney
Brooks's subsumption architecture. I draw little diagrams like the ones
that his group draws. Then I do what he suggests: start at the bottom with
the most primitive behaviours and work up. (But I don't think that approach
works for industrial robots.)
My experience is that the overall architecture of robot software is easy.
Getting the low-level stuff to work is what's hard. I don't think there are
any people in the world who have got enough of the low-level stuff working
that they have a big problem integrating it all together.
Most people are happy if their robot can get from A to B without getting
stuck behind the sofa. And that includes 99% of universities. Sure, NASA
may talk about building self-repairing robots that can diagnose their own
faults but no-one has actually built a real robot complicated enough to
benefit from that kind of philosophising. It's fun to speculate but it's a
futile daydream until we've got robots that actually work.
I'm particularly interested in robot-programming languages, especially
languages and HCIs for non-programmers or beginners. I've found the only
way is to write the user interface and try it out.
Peter
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Robotics
|
|
|
|
|
|
