Subject:
|
Re: The Great Ball Contraption
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sun, 9 Jan 2005 21:15:55 GMT
|
Original-From:
|
Russell Nelson <nelson@#antispam#crynwr.com>
|
Viewed:
|
7722 times
|
| |
|
|
Steve Hassenplug writes:
> As you can see, it hangs over it's neighbor a bit.
>
> Of course, if you ass-u-me anything about the neighboring modules
> you could run into problems.
You can assume anything that's in the specification! Speaking of
which, you should probably add a requirement that the top of the input
bin must always be unobstructed. That is, the output part of a module
gets to do anything it wants with the space over the input part of the
next module.
--
--My blog is at angry-economist.russnelson.com | Freedom means allowing
Crynwr sells support for free software | PGPok | people to do things the
521 Pleasant Valley Rd. | +1 315-323-1241 cell | majority thinks are
Potsdam, NY 13676-3213 | +1 212-202-2318 VOIP | stupid, e.g. take drugs.
|
|
Message has 1 Reply:
 | | Re: The Great Ball Contraption
|
| (...) Instead of that, just make sure that your module delivers through the "side" of the downstream module's territory. In other words, using a chute (even a very short one) is a pretty easy solution. And that way the standard isn't further (...) (20 years ago, 10-Jan-05, to lugnet.robotics)
|
Message is in Reply To:
| | Re: The Great Ball Contraption
|
| (...) In our test, when people dump, they usually dump onto a ramp in their own module, that drains onto the next module. Like on John's back hoe: (URL) you can see, it hangs over it's neighbor a bit. Of course, if you ass-u-me anything about the (...) (20 years ago, 8-Jan-05, to lugnet.robotics)
|
94 Messages in This Thread:
 
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Robotics
|
|
|
|
|
|
