Astro Orbitor is the second original Lego Great Ball Contraption (GBC) module that Raj Doshi has designed. It is modeled after the ride from Disneyland in Anaheim, California. On the original ride, the rider can use a control to move the vehicle up and down. The idea of this build is that the balls “control” the vehicle, because each vehicle only changes elevation if it contains at least one ball. On the original ride, all of the larger orbs are silver colored, but this model makes use of various planetary-looking orb elements that are available in Lego, which is more reminiscent of the version of the ride at Magic Kingdom.
One of biggest challenges of this build was getting the ride to run smoothly, which is why it is powered by two Power Functions extra large motors. In preparation for Brickworld Chicago 2025, the build has been tested in two 8-hour runs, and seems to be reliable, not requiring much maintenance at this point. It is recommended to build the mechanical components first before buying all of the parts for the full build. Feel free to get in touch to let us know that you are building it or to ask any questions. Here is a Bricklink Studio file for the full build:
Here are a few tips for building and maintaining Astro Orbitor:
In one of the prototypes for the build, there was a problem where the arms became increasingly bent over time, which would ultimately break the loading and unloading functions. The final version has shorter arms, and it’s not clear if this is still an issue, but it may be a good idea to remove the vehicles from the arms when the module isn’t running, to reduce stress on the arms.
On the piston for each arm, there is a series of thin 1x2 liftarms. There is a small gap between the last two liftarms and the other ones (see image below) to ensure that the last liftarm never fully leaves the opening in the vehicle when the piston is in its most retracted state. Note that the end of the black 4L axle that protrudes from these liftarms is positioned so that it protrudes slightly less than the other 3L axle. This helps ensure that balls can unload properly. Also, note that a 3L and 2L axle are used in sequence, instead of a 5L axle. Stacking the two axles results in a total length that is slightly shorter than a 5L axle, which is also to help balls unload.
The timing for a piston can be set by lifting out one of the black “banana” gears and then adjusting the 40-tooth gear that connects to the banana gear. There is some tolerance for variation in the timing, but improper timing can prevent balls from unloading properly because the piston interferes. The timing should be set so that a vehicle with balls in it starts its first ascent before the rear of the vehicle has fully passed under the unloading station platform.
Each motor housing connects to the ride base using two axles. To ensure that the connection can be made, it is best to ensure that both axles are in sync, having the same orientation. This can be done on both the motor housings and ride base by temporarily connecting the axles with a 1 x 5 thin liftarm with axle holes while building, as shown. After the gears are in place, the axles will be interconnected by gears and will stay in sync.
There are several gears that need to be adjusted properly for the loading mechanism. Here are some photos that show the positions of gears and the ball release lever when the loading station is in its resting position, with the counterweight resting against the stopper. The Bricklink Studio file should also show the correct gear connections, but it’s not in the resting position. If extra balls are leaking out when the ball release is triggered, it may mean that the amount of counterweight needs to be increased.