How it works
- A clear tube on a V-slot spine fires a teardrop with a steel ball sealed in its nose. A braided tether runs from the teardrop’s tail back through the cannon to a spool. We started with a 32 mm tube pointing 60 degrees down at a chime tube hung level; the choices below cover the alternatives.
- Cocked, a spring behind the piston is squeezed, and the teardrop’s tail sits in a cone in the piston’s front, matched to its taper. A light carbon rod runs from the piston out through the breech block, and the tongue of a lock-style solenoid holds a collar on the rod.
- A short pulse fires it. The pulse pulls the tongue in, the spring throws the piston and the teardrop forward 30 mm, the collar stops on a rubber washer, and the teardrop flies on, nose first, pulling its tether off the spool.
- The spool spins free on a one-way bearing while the tether pays out, about 50 turns a second. As the teardrop lands, a small servo presses a felt pad on the spool’s rim, so the spool doesn’t spin on and throw loose tether.
- A gearmotor reels it home and re-cocks it. As it winds the spool, the tether pulls the teardrop home tail first, and its taper steers it into the muzzle and down the bore into the cone. The motor keeps winding, so the teardrop pushes the piston back and squeezes the spring, until the collar rides up the tongue’s slanted face and the tongue drops in front of it. A switch behind the collar says it’s cocked, and the motor stops.
- Only the teardrop and the holders are printed. The tube, the spring, the rod, the catch, the gearmotor, the bearings and the sensors are bought.
- An ESP32 runs it. It listens for the wireless signal, fires the catch, drives the brake and the gearmotor, and reads the switch and the spool’s sensor. It runs from the shared power-tool battery.
After a hit
The teardrop hangs from the muzzle on its tether, like a pendulum. Reeling it in shortens the pendulum, and a shortening pendulum swings faster and wider, the way a lure whips around a rod’s tip when it’s reeled right up. That decides how the cannon has to aim.
- Hit level with the muzzle, the teardrop starts its swing level, and the simulation has it wrap round the muzzle one to three times before it gets home, at any reel speed.
- Hit from well above, it starts within about 30 degrees of hanging straight down, swings under the muzzle and comes back up into it. So the cannon fires about 60 degrees down, at targets below and in front of it.
- Hit square on. A hit that only grazes the target leaves the teardrop falling fast past it, and that speed becomes a wide swing when the tether takes hold. The target’s struck face has to point back at the muzzle, so the teardrop bounces back up its own path.
- Keep the space below the muzzle clear. In the model, the swing reaches 60 degrees either side of straight down and passes about 3 cm under the cannon.
What it can hit
- Anything that rings and can be hung or held with its struck face pointing back at the muzzle. A chime tube hung level across the shot by cords at its nodes does this, and so do metal bars, wood blocks, a gong or a bowl tipped toward the cannon.
- A tube hung upright is a poor target from above. The teardrop only grazes it and then swings wide.
- It strikes at about 4.5 m/s, like a light mallet. Metal and hollow wood carry it best.
Timing
- From the pulse to the strike takes about a tenth of a second at our range: a few hundredths for the tongue to pull in, then the 15 ms stroke and a 75 ms flight. The firmware fires that much early so the strike lands on the beat. Measure it for each target and store it with the target.
- Reloading takes about two and a half seconds after the hit: about a second to reel the teardrop to the muzzle, then the rest to draw it down the bore and cock. So a single cannon plays a note every three seconds or so at most.
Sensing and faults
- The cocked switch is the only proof that it’s safe and ready.
- The spool’s sensor counts the slots in the spool’s flange. It shows the tether going out on a shot and coming in on the rewind, so the ESP32 knows the teardrop actually flew and where it is. If it stops counting while the motor runs, something has stalled: the teardrop is seated and cocking, or something is jammed.
| State | What happens | Leaves when |
|---|---|---|
| Ready | Cocked, teardrop seated, brake on, motor off | A cue arrives |
| Fire | Brake off, then the catch pulses | The spool starts counting |
| Flight | Spool free | The strike time comes, and the brake goes on |
| Rewind | Brake off, motor winds | The count nears home |
| Cock | Motor keeps winding | The switch reads cocked, then the motor stops and the brake goes on |
A cue that arrives outside Ready is ignored; it doesn’t queue shots. Every fault stops the motor, leaves the catch off, puts the brake on and holds. Once the fault clears, it tries one slow rewind and cock. If that fails, it stays in fault until the power is turned off and on. It never fires from a fault.
| Fault | How it shows | Likely cause |
|---|---|---|
| Tangle | The count stops during Rewind while it’s still far from home | The tether caught on the target or the frame |
| No latch | Cocking runs past its time limit without the switch | Tongue stuck, collar slipped on the rod, teardrop not seated |
| Misfire | After the pulse, the spool never counts | The tongue didn’t pull in |
| Teardrop lost | The count goes far past normal, or the rewind spins with no load | The tether broke or the knot slipped |
Since elements only listen, a fault shows on the element itself, on its status light, for a technician to read.
Notes
- This is a first design, drawn but not yet built. Expect one round of fitting.
- The motion in the 3D model is simulated from the physics, with guesses for the shot’s speed (4 m/s from the piston) and how much the teardrop bounces. A test build will give the real figures.
- Costs in the parts list are rough estimates for budgeting, not checked prices. They add up the version we started with.
- The firmware isn’t written yet. It will listen for Control, the one broadcast signal every element hears.
References
- Robot that swings and climbs like Spider-Man (Hackaday.io). A pen-spring launcher fires a tethered grapple on Kevlar thread, a servo pushes the trigger, and a geared winch reels it in. The closest precedent for the cannon.
- Printable spring trigger (MakerWorld, Bri). A compact spring trigger mechanism for props, using a pen spring.
- Solenoid-driven projectile launcher board (Tindie, Questwise Ventures). A solenoid and spring launcher, reset by hand.