Great ball contraption
|
A great ball contraption (GBC) is a machine which receives soccer balls[1] or basketballs[2] from one module and passes them to another module, rather like a bucket brigade. Modules built according to the GBC standard can be assembled into a collaborative display without modification. The GBC standard is minimal, permitting the builder great flexibility in designing the mechanism by which balls are moved from the input to the output. The otherwise pointless handling of balls, and the myriad ways this is accomplished, gives great ball contraptions the impression of a Rube Goldberg machine.
Contents |
Standard
This is a condensed version of the rules. The full, authoritative version of the standard is hosted at Team Hassenplug[TH].
- Each module should have an "in" basket, and will move balls to the next module's "in" basket.
- The IN basket should be 10 studs by 10 studs (outside dimension) with an 8x8 opening, and should be 10 bricks (beams) tall.
- The In basket should be located on the left side of the module, and output should go to the right.
- Each module should be able to accept balls at an average rate of 1 ball per second. Balls can be passed continuously, or in a batch. A batch should not exceed 30 balls.
Terminology
Strictly speaking, a great ball contraption is two or more modules which pass balls one module to another. Informally, the abbreviation GBC is often used to refer to a single module. Because of this ambiguity, a series of modules may be specified as a GBC loop, GBC collaboration, or GBC layout.
Collaboration
|
The Balls
Soccer balls are typically used. Basketballs are also common. These were both available in various designs (search x45? and x493? on Peeron). Unfortunately, these were last sold in 2006. Some can still be found for sale on BrickLink (try searching for bb84* and x45*). However, in 2013 an orange soccer ball appeared in Heartlake City Pool.
pmichael has tried using plain plastic beads.
Functions
The functions of a module can be divided chronologically into loading, lifting, doing something interesting (with a widget), and unloading. Another key function is driving the module, or producing the motions required to load, lift, run the widget, and unload. Many modules will blend some of these functions together in the same mechanism.
Loading
Loading means receiving balls from the previous module and feeding them into the current module's lifting mechanism. Standard modules will receive balls through an 8 x 8-stud opening that is 10 bricks above the module base. This section will address means of getting balls received this way into a flow that works for different lifter requirements.
Single File
Often a lifter requires that balls arrive single file. Here is a list of mechanisms that achieve this.
- Rotating floor with downward side exit.
| MOC | builder | explanation given | image available | video available | instructions available | follows GBC standard |
|---|---|---|---|---|---|---|
| The Witch | pg52 | English French | no | YouTube | no | Type 1 |
- step feeder lift mechanism
- conveyor lift mechanism
- sweep into slot
| MOC | builder | explanation given | image available | video available | instructions available | follows GBC standard |
|---|---|---|---|---|---|---|
| Pump module | Philippe Hurbain | no | yes | yes | no | Type 1 |
Lifting
Lifting mechanisms are detailed in the lift mechanism category.
Doing Something Interesting
Widgets are mechanisms that exist solely for interest. They should be detailed in the widget category.
Unloading
Unloading is receiving balls from the widget (or the lift mechanism if there is no separate widget) and providing them to the next module's in basket. In general, this is the easiest function. But there are cases, such as with shooters, where this is problematic.
Driving
Driving is supplying kinetic energy to the mechanisms. That is, it is making your module move. Variations:
- Direct drive: an electric motor is directly connected to the lift mechanism. This is by far the most common method.
- Shared drive: an electric motor drives a mechanical linkage, and individual modules connect to the linkage.
- Water-wheel drive: a falling or descending stream of balls turns a paddle wheel, which in turn runs a lift mechanism.
Building Tips
Because GBC modules necessarily involve mechanisms, Technic elements and building techniques are frequently the basis of a GBC. However, creative use of non-Technic elements can substantially increase how well a GBC is received by both the public and AFOLs. Another key design factor is reliability, especially if the GBC will be part of a collaborative display. A GBC that works for 15 minutes before breaking down is fine at home, but at a 6-hour show it would break down 24 times--a significant hassle. Another common problem is "leakiness", that is, having balls travel anywhere outside their intended path (usually onto the floor). Before taking a GBC MOC to a public show, run it non-stop for about an hour to get a good predictor of its reliability and leakiness. Some rules of thumb:
- Batches behave differently than singles. A GBC's behavior when receiving a batch of 30 balls can be very different than when receiving balls one at a time. Test both conditions.
- If it can jam, it will. Design modules so that they clear themselves, tolerate a few stuck balls, or fail gracefully. Avoid designing such that when there's a jam, something has to break. Use of clutch gears, belt drives and flexible elements can help keep disaster at bay.
- Funnels jam. Avoid passages that narrow. If unavoidable, provide some kind of agitation to keep balls moving.
- Dead spots bother people. Frequently there will be places in a GBC where balls will park themselves. This isn't technically a problem as long as a stopped ball doesn't block the flow. However, onlookers will invariably let you know a ball is "stuck" and will instinctively reach out to free it. Modelers who don't want people touching their MOCs may want to eliminate such dead spots.
- Gears break. Smaller ones are especially prone, such as the 8-tooth
and 12-tooth bevel 
gears. They should either be used where the maximum possible torque is limited or where they are easy to replace. - Display tables aren't level. Modules which work great on a level table can suffer horribly when tilted slightly. Test with each edge lifted by one or two plates, or be prepared to fiddle with leveling it when on display.
- Recirculation helps. A module which can feed balls to itself is not only cool, but it simplifies testing and allows it to be displayed as a stand-alone GBC.
History
The idea was first publicly proposed by Steve Hassenplug on a LUGNET forum on October 7, 2004[SMART]. The GBC started as a "Ping Pong ball handoff" within the Lafayette LEGO Robotics Club, and was combined with SMART's Crate Contraption[Crate] to become The Great Ball Contraption. Other early participants included Bryan Bonahoom and Brian Davis.[TH] One of the early appearance of this collaboration was at Brickfest 2005.
Records
Most modules
- World: 139 modules at LEGOWorld CPH, Bella Center, Copenhagen, 2013
- Western hemisphere: 80 LEGO modules at Brickworld Chicago 2014
Longest
- World: in excess of 584.43 meters at Brickfair NE 2013
Examples
- A Simple, Sample GBC by Steve Hassenplug
- Shovel with instructions by Philippe E. Hurbain.
See the GBC catalog for more.
Some Great Ball Contraption Collaborations
- First Team Hassenplug GBC setup
- Legoworld 2005
- BeLUG LegoWorld 2007
- Brickworld 2007
- akiyuki 2012
Example Lift Mechanisms
- Main article: category:lift mechanism
A long list of possible methods to lift balls up from the in basket before passing them on (either to a widget or to the next in basket), can be found at Team Hassenplug[TH]. Some examples are given here.
- clock lift[TH]: picture a slightly tipped-back clock face, with a “C” shaped cup on the end of the minute hand. At the bottom (“6 o’clock”) it scoops a ball (or balls) into the cup from a bin, rotating them up the face of the clock. Near the top (say between 11 & 12 o’clock) the face is cut away, allowing the balls to fall out and into a chute or receiver.
- conveyor: moves balls up incline (or horizontally). May use idler wheels/gears to change shape of path. To ensure feeding from hopper, “bumpers” or “sweeps” might be used to stir the hopper.
|
- wave: a wave motion propels balls forward, like nico71's The Wave.
- wheel lift: perhaps based on the Hailfire Droid wheels, the wheel lays in a slightly inclined cavity with the bottom having a shallow trench to lower the inner rim level with the attached hopper floor. At the top of the cavity the rear wall is missing, allowing balls to roll out of the open cells attached rigidly to the wheel’s inner rim. A hub-less wheel like the Hailfire wheel can be rotated by resting it on regular driven wheels on the inner border of the cavity. A second wheel can be used as a second stage, set above and just behind the lower wheel/cavity assembly.
Inspiration
- Roy Nelson's marble machines
- Matthias's Marble Machines page
- Juergen Kintscher marble works (German)
- Cooperative Cybernetic Crate Contraption by SMART
- SMART Crate Contraption at NWBrickCon
See Also
External References
- [Crate] Cooperative Cybernetic Crate Contraption by SMART
- [TH] Team Hassenplug's The Great Ball Contraption
- GreatBallContraption.com has basic information and links
- [SMART] Crate Contraption Standard discussion thread
- Philippe E. Hurbain's GBC page
- Akiyuki's machines, mostly GBCs
- [ALS] GBC handout in PDF format, or Open Document format
