Skip to the notes
robocupjunior.org.nz

Junior Robotics Notes

an independent NZ guide to classroom robotics

N-05Competitions explained

Robots on stage: dance and theatre projects

Choreography by timing, servos that wave and nod, and how to combine art, music and code into a robot performance.

Not every robotics student wants to chase a ball or follow a line. Robot dance and theatre projects bring in students who love music, costume, storytelling and design, and they often produce the most memorable robots in a school. The engineering is just as real: a performance that is meant to land on the beat needs reliable timing, careful mechanics and a lot of testing.

What an on-stage project involves

A typical performance is a short routine, a few minutes long at most, in which one or more robots move to music or act out a story. Students usually design the robots, build costumes or sets, choose the music and write the program. Many school competitions that include this category also interview the team, so students should be able to explain how their robots work and which parts they made themselves.

As always, specific events publish their own rules on length, size, music and judging. Check the current rules for any event you plan to enter, and treat this note as general background.

Choreography by timing

The simplest approach is a timed script: move forward for two seconds, spin for one, wave an arm for half a second, and so on. It is easy to understand and easy to start with.

# a timed routine, MicroPython style
forward(speed=50); sleep(2000)
spin(speed=40);    sleep(1000)
wave_arm(times=2)
pause(500)

The catch is drift. Motors run slightly differently as the batteries drain, and small timing errors add up. By the end of a song, a purely timed robot can be well out of step with the music.

Ways to keep in sync:

  1. Break the routine into sections that each start on a cue, rather than one long script.
  2. Use a start signal such as a button press, a clap picked up by a microphone, or a radio message from a second board.
  3. Anchor to the clock, not to delays: schedule each move for a time measured from the start, so errors don't accumulate.
  4. Test with fresh and half-flat batteries so you know how much the routine drifts.

Servos: the dancer's joints

Wheels move the robot around the stage, but most of the expression comes from servo motors: small motors that turn to a set angle and hold it. Hobby servos are typically controlled with a timed pulse, and most standard ones move through about 180 degrees. They are ideal for arms, heads, eyelids and flags.

A few practical tips:

  • Power servos from a suitable supply rather than straight from a small board's pins; several servos moving at once can draw more current than the board can provide.
  • Move servos in small steps for smooth motion; jumping straight to an angle looks jerky.
  • Keep costume pieces light. Heavy cardboard wings strain small servos and drain batteries.
Moves scheduled on beats measured from the start, rather than chained delays roll forward wave arms spin and bow 0 s (start cue) each move starts at a set time
Fig. 1: tie each move to a beat measured from the start cue so small errors never pile up.

Bringing art and code together

The best performances usually come from teams that plan the story first and the code second. A useful process:

  1. Storyboard the routine on paper, one box per musical phrase.
  2. List the moves each robot needs, and check each one is mechanically possible.
  3. Build and test moves separately before stitching them together.
  4. Rehearse on the real surface. A robot that turns perfectly on carpet may skid on a smooth stage floor.
  5. Plan for failure. Decide what happens if a robot stalls mid-routine, and keep the show going.

On-stage robotics is also a natural fit for cross-curricular work. Music, visual art, drama and Digital Technologies all meet in a single project, and students who would never call themselves "techy" often end up writing the cleverest timing code in the room.

Using sensors in a performance

Once a routine runs reliably, sensors can make it feel alive. A robot can turn to face a spotlight using two light sensors, react to a clap using a microphone, or stop at the edge of the stage using a downward-facing sensor. Two micro:bits can use radio to signal each other, so one robot's move can trigger another's reply. These touches make a performance look less like a recording and more like the robots are responding to each other.

Each sensor adds risk, though, especially under unfamiliar stage lighting. Keep a fallback: if a sensor reading doesn't arrive within a second or two, the routine should carry on with its timed version rather than freezing.

Recording and reflecting

Film every rehearsal, even on a phone. Watching the footage back is the quickest way to spot a move that is late, an arm that snags a costume or a robot that drifts toward the edge of the stage. Students can annotate the video with timestamps and fix problems one at a time, and the clips double as evidence of the design process if an event or teacher asks to see it.

Sources: Arduino guide to servo motors; Microsoft MakeCode for micro:bit.