 | | RE: TGBC - The Weakest Link?
|
|
<SNIP> (...) Like a train layout, how about routing/switching module to create multiple ball routes? This way, if any one module acts up, only modules affected in that path need to be dealt with. Given the standards (regarding input/output bin (...) (22 years ago, 10-Jan-05, to lugnet.robotics)
|
| |
 | | Re: The Great Ball Contraption
|
|
(...) Not to oversimplify, but I mean if the 'standard' for the ball contraption is 32 studs from the front of the hopper to the back edge of the baseplate, and thus I personally would probably grab a 32 x 32 stud baseplate to build on, thus the (...) (22 years ago, 10-Jan-05, to lugnet.robotics)
|
| |
 | | Re: The Great Ball Contraption
|
|
(...) Is there something that a module builder can not do because the standard is too simple? Steve (22 years ago, 10-Jan-05, to lugnet.robotics)
|
| |
 | | Re: The Great Ball Contraption
|
|
Steve Baker writes: > So simply write into the rules that everyone who submits a left hand > turn has to submit a corresponding right hand turn or they won't > be accepted. Excellent idea! But it's even easier than that!! Do NOT change the (...) (22 years ago, 10-Jan-05, to lugnet.robotics)
|
| |
 | | Re: The Great Ball Contraption
|
|
tmassey@obscorp.com writes: > Or not: leave the standard as it is (except for specifying that the space > above the input belongs to the previous module), and have the organizers > build (or specificially request) out-of-spec modules to accomplish (...) (22 years ago, 10-Jan-05, to lugnet.robotics)
|