Mini-Sumo Rules
Overview
Two autonomous robots are place in a ring. The robots try to avoid falling out of or being pushed out of the ring. The first robot that touches outside the ring loses the round. The first robot to win two rounds wins the match.
Mini-Sumo Robots
Autonomous Sumo robots are self-propelled and self-controlled, without tethers. After positioning and starting the robot, no remote control, power, positioning, or other help can be provided. The robot must care for itself until the round ends.
Mass
Mini-Sumo robots may have a mass of up to 500 grams. A scale will be used to measure the mass of each robot and if the scale reads 500 grams or less, the robot will be eligible for competition. Devices such as helium filled balloons cannot be used to lighten a robot.
At the start of each round, Mini-Sumo robots must not exceed 10cm in width or depth. There is no height limit and as soon as movement is allowed in a round the robot may twist, fall, or expand without size limits. Harmlessness
At all times, robot behavior must be non-offensive, non-destructive, and non-harmful to humans, robots, and the facilities. This is an immutable principle, even if the behavior is unintentional or not by design.
During inspection (and at any time during the event), the judges may require safety changes or other modifications to meet the harmlessness requirement. Harmful robots are either not allowed to compete at all or are later disqualified if potential harmful issues are proven or revealed in battle.
During the contest, the judge must determine if a robot’s failure was due to its own lack of durability. Failures due to exposed wires or unsecured or flimsy parts shall be the responsibility of the robot with such weaknesses.
At all times, Sumo Robots must not:
- Emit smoke or fire
- Leak, stain, or soil
- Disperse powder, grit, or grime
- Spray, throw, or use projectiles
- Jam, shock, or electromagnetically interfere
- Snare, entangle, or employ nets/rope
- Scratch, gouge, or scrape
However, as for the last point, naturally some damage occurs from
scoops, changes in starting orientation, and from the battles
themselves. This is expected and acceptable to any reasonable extent.
No flying
Sumo Robots must not fly or generate lift to isolate themselves from the ring surface.
The "no-fly" rule isn't intended to prevent a robot from having a
floating portion (such as a camera, sensor, flag, or distraction) nor to prevent jumping or other interesting behavior. The robot qualifies as long as a major portion of the robot is generally available to be pushed out by the opponent robot.
Suction, Magnets and Sticky Wheels
Use of Suction, Magnets and/or Sticky wheels as a way to increase traction is not permitted in LVBots Mini-Sumo tournaments. To determine whether a robot’s wheels are too sticky the robot will be placed on a piece of paper and lifted up. If the paper lifts with the robot the wheels are too sticky.
The Ring
The ring is a large flat disc made of a smooth rigid material such as wood aluminum or steel. The top surface is painted black except for a white border which is approximately 2.54cm (1 inch) wide. Two starting lines in the middle are brown. The ring will be approximately 77cm in diameter.
The Contest
Our Mini-Sumo tournament will be conducted as a double-elimination tournament. All robots will be inspected to verify that they comply with the stated rules.
A Match
Matches are conducted in the ring and consist of several rounds. The first robot to win two rounds wins the match.
Placement
The better ranked robot or the robot which won the previous round is placed first on its side of the ring. The lesser ranked or the robot that lost the previous round is placed second. Once a robot is placed it can not be moved or rotated. Each robot must be placed behind its respective starting line in the ring.
Robots must have a method of being started. Typically this is done by pressing a button but can be implemented in any other way that meets the requirements. Both contestants will start their robots when the referee says 'Go' and then move away from the ring. During the round, people and objects must be kept away from the ring to avoid disturbing the robots or altering the outcome. Robots should remain motionless for at least 5 seconds after being started.
No Start
During the 5 second countdown at the start of a match, if a contestant notices that their robot has failed to start its countdown, the contestant may alert the referee and halt the countdown.
False Start
If a robot begins moving before the 5 second period is over, the robot has committed a false start and the match will be re-started. Two false starts by the same robot results in a loss of the round for that robot.
Out
A robot loses the round when any portion of the robot touches outside of the ring.
If any piece of the robot, no matter how small or even if detached, touches outside of the ring, the robot is considered out. For example, if a nut drops off a robot within the ring, the robot doesn't immediately lose. However, if the nut is then pushed out or rolls out, the robot loses.
If a robot lands outside the ring atop a whisker, scoop or any portion of the opponent robot, the opponent robot is out. This is consistent with the policy that the robot that touches outside first is out, even if the second robot subsequently touches outside the ring.
Starting to fall or breaking the plane of the ring isn't considered out.
Some portion of the robot must actually touch outside the ring.
Contestant Stoppage
After a round has started, either contestant can stop the round and loses that round.
Referee Stoppage
At the referee's discretion, the referee may restart a round if:
- 3 minutes have expired
- No progress has been made for some period of time
- The robots are entangled or otherwise deadlocked.
The referee may choose to end a round and choose the winnner if:
- Smoke, fire, damage or any other violation has occurred.
- No progress is likely to be made even if the round is restarted.

2012-02-09
Emily: RGB LED Halloween CostumeAdd yourself here!
2012-01-26
6:00-6:10 Robot help - ask questions about anything6:10-6:20 Introductions & group matters
6:20-6:30 Kevin - Zumo prototype and QuadBot
6:30-6:50 Kevin - I2C
6:50-7:00 Nathan - Quick intro to 3D scanning with Davidscanner (free version).
At ~7pm we will adjourn to a nearby bar or restaurant for general discussion.
2012-01-05
Neil and Michael: Navigation project with TReX JrEric and Mark: Big Traxx
Kevin: 5m LED strip synchronized with music
Ryan/Paul: General organizational discussion for LVBots
At ~8pm we will adjourn to a nearby bar or restaurant for general discussion.
2011-10-27
Show and tell: everyoneVintage electronics: Eric
Dual VNH5019 Motor Shield RyanTM
2011-10-13
David: New servo control library for the WixelNathan: Hackerspace Status Update
2011-09-29
Kyle S: Heathkit HERO jr. Robot from 1984, educational robot. it has a few problems.
Nathan: ST L6384E H-Bridge MOSFET driver troubleshooting.
David: AVR Studio 5 demo, featuring the Pololu USB AVR Programmer
RyanTM: New arduino shield
2011-09-15
2011-09-01
Dave: 2-way wireless communication with PICAXE using Wixels
Brian: RGB led strip demo
RyanTM: exciting new motor driver
Kevin: IMU board (gyro+compass+accelerometer) demo
2011-08-18
Paul G: reflectance sensor demo (requested by Paul I)
Dave/Paul/Kevin: Try to wirelessly program a PICAXE - should be much easier since they just use RX, TX, and GND.
2011-08-04
Paul I: Line follower
Dave: Request a demo of how to wirelessly connect a Parallax Sumobot with a serial interface to a computer using Wixels. I have the Sumobot and will purchase the Wixels.
2011-07-21
Paul I: HexapodDiscuss contest ideas.
Dave: Flea and Ant fighting robots (live demo), Boy Scout Electronics Merit Badge Kit (before and after assembly) and a FingerTech motor controller demo.
Andy H: DSO QUAD pocket oscilloscope
Kevin: Tank chassis sumo battle
Paul G: new shiftbrite LED modules
2011-07-07
David: Programming the ATmega2560 with ICSPRyanTM fun small-robot drive: link
2011-06-23
Kevin: more tracked chassis examples using new tracksNathan: Sailboat motor regeneration bench demo
2011-06-09
Kevin: 3d gyro
RyanTM: Wixel Shield for Arduino
David: Programming the Wixel on Linux and maybe a Mac
Someone: new current sensors
2011-05-26
Kevin: building a tank chassis with Tamiya plates and Pololu wheels & treads
Nathan: Regenerative Motor Control Demo (Untested!!)
2011-05-12
RyanTM: new Satellite LED modules (003, 004)
Ben: 25D gearmotors
Ben: tank treads and bolts
Ben: m3pi POV LEDs
Jan: USB microscope
2011-04-28
Kevin: Wixel i2c interface demos - wireless compass and barometer
RyanTM: m3pi (a board for mounting an mbed on a 3pi)
Mark: ?
2011-04-14
Kevin: Wixel wireless tilt mouse and joystick
Paul: new robot arm from Dagu, several new metal gearmotors
2011-03-31
David/Kevin/Paul: new Wixel apps
2011-03-17
David: Deskpet Robot Body from Shapeways
David/others: Wixel
2011-03-03
Paul: Scorbot-ER III robot arm (dropped off by Eric O)
Nathan: Even more regenerative electric motor stuff (batteries included).
2011-02-17
Nathan: Regenerative electric sailboat motor part IIKevin: wireless robot with Rover-5 tank chassis, wixel, and Arduino SVP
David/JanH: wixel bootloading software
RyanTM: AutoHotKey demo (easy way to control servos and other things with a keyboard or joystick)
RyanTM: CHR-UM6 Orientation Sensor
Fang/Paul: torque meter
2011-02-03
Nathan: Regenerative electric sailboat motorRyan: Wirelessly controlled 3pi Robot
Ben: 25mm-diameter encoder motors
2011-01-20
Kevin/Ryan: 3d compass / accelerometerDavid/Kevin: wireless serial port
Paul: absolute encoder
Travis: mbed-based robot ?
Kevin: wireless router robot
Henry: XMOS
2011-01-06
Ryan: barometric pressure sensorByon: removing email addresses
Byon: email requesting help with Sahara West Library robotics program (see Yahoo Group)
David & Kevin: wireless serial port demo
2010-12-16
Henry: XMOSHenry: Windows CE touchscreen computer
Aaron (visitor): demoing his REVO 1 robot
JanH: update on Pololu AVR library support for OSX
RyanM: Relative humidity sensor.
Byon: Minimal progress on the encoder bot chassis
2010-12-02
David: mbed robot racing videoRyan: Demo of computer cable for Agilent meters
Paul: Demo of Octobrite DEFILIPPI driving 24 LEDs
Jan H: Preview of support for Pololu AVR Programmer
Kevin: Demo of 20x4 Character LCD with LED backlight