Just one video today—Ted’s lecture on very basic coding techniques.
Just one video today—Ted’s lecture on very basic coding techniques.
Two videos from today’s lecture:
1) on the switch circuit and code
2) on the colour sensor circuit and code
And some photos to help:
I’ve made a little video to help you plan for the Race to the Wall
Some notes from Ted’s lab:
From the lecture, here’s info on powering your colour sensor
And, finally, some hints on using the breadboard
I’ve posted three videos from the second day of class, click the words to view them. There is one on soldering
another on assembling a circuit to power one motor,
and finally a talk Ted gave in our lab on the circuitry and driver chip needed to power two motors for your robot.
I have also posted a video Ted and I made before the semester started about getting the wheels to turn various directions.
They are raw, but we hope they will help in case you need a refresher or missed something in the first go. The following pictures may help, too.
Welcome to the RoboSumo project, which is undertaken by students of programme DT066 (Engineering common first year) and programme DT009 in the Dublin Institute of Technology. Over the course of this semester, you will work in teams of (usually) three to design and build a robot that will compete in a RoboSumo tournament. The tournament consists of a series of bouts in which two robots at a time compete to push each other off a table (the arena). The tournament rules (together with a small number of additional local rules) impose constraints on the cost, weight, physical dimensions and various other elements of the robot design. It is up to each team to improvise within the specified constraints to produce the most competitive robot they can.
There are 13 teaching weeks in the semester. The provisional schedule for the RoboSumo project is shown below. This schedule is subject to modification and is provided here as a general guide to help you plan your work.
In today’s lecture (2-3pm in room KE3-008, which is the large lecture theatre on the third floor of the main building in Kevin St), I will describe the project objectives, review the provisional schedule and explain how the assessment works.
In today’s lab (3-6pm in various labs on the ground floor of the main building in Kevin St), you have five jobs to do. The first four are very short; the fifth is more challenging.
Each team must have a unique name and team number. Your tutor will assign your team a number from the range allocated to your group, as shown below:
Note: Tutors, please make a list of teams in your group that includes team number, team members! (Team name too, if known)
Your RoboSumo kit will eventually contain the following items:
To set up your blog,
Once everyone on your team has set up their blog, it’s time to proceed to the LED Flash Challenge.
We’re beginning the RoboSumo project with a little competitive puzzle called the LED Flash Challenge. We’re not attaching formal assessment weight to this challenge, but we’ll be keeping a close eye on which teams do well. In this challenge, doing well means two things: getting it working quickly and trying to understand what you’re doing.
In today’s lab (and for some of you part of the next lab) you’ll be working with your team to complete two tasks:
The first task is very prescriptive, which means that we’ll basically tell you exactly what to do, but to complete the second task you’ll need to think for yourselves.
You’ll need a team number to complete this challenge. Your tutor will assign your team a unique number within the range shown below:
This task is relatively straightforward and shouldn’t take you too long to get working. Open the link below in a new tab and follow the instructions as far as the end of Part 1. Once your LED is blinking, come back here. (Note: The LED you receive may be a different colour and/or shape to that shown in the instructions.)
Once your LED is blinking, there are four things you need to understand before moving on:
Once you understand these four things, you have finished this part of the task (the easy part) and it’s time to move on to the LED Flash Challenge.
In this part, you’re going to modify your circuit to create a simple optical transmitter, which transmits a digital message (a sequence of 1s and 0s) as a series of LED flashes. I’ll demonstrate this to you in the lecture.
The message that you’ll transmit will be 2 bytes long (a byte is 8 bits, or 8 ones and zeros) and it will contain your team number (byte 1) followed by a second number calculated by subtracting your team number from 255 (byte 2).
For example, if your team number is 79…
Specifically, you need to do the following:
Let’s consider that example team number 79 again. As explained above, byte 1 is 79 and byte 2 is 176.
To summarise, the complete 20-bit sequence for team 79 would be as follows:
The validator for checking your transmission is a web application which I have posted at the following location:
I will set up an official validation station in KEG-036 where you can record your result once your circuit is working. Other tutors may set up validation stations in the other rooms, but that will depend on available cameras and light levels.
You are welcome to try the validator on your own laptop / PC. In principle, it should work on any modern PC with a webcam and up-to-date browser. However, since video capture is relatively new in HTML, I recommend using the current release of Google Chrome which is what I tested it in.
Your tutor will be able to clarify anything you don’t understand about this.
Click here for Live Tournament ranking (Note: All rankings are provisional and subject to change)
Please review the following information carefully from start to finish.
The tournament will commence at 2pm on Wednesday 26th April 2017 in room KEG-036, which is located in one of the smaller side corridors on the ground floor of the main building in DIT Kevin St. During the initial “sorting” phase of the tournament, two competition arenas (sumo tables) will operate in parallel in the same room.
The exact duration of the tournament will depend on how quickly things progress, but we aim to be completely finished by 5pm. To ensure that the tournament proceeds efficiently, teams must comply with the instructions of the referee(s) without dispute at all times.
Before your robot can compete in any sumo bouts, it must weigh-in to ensure compliance with the competition rules.
Teams should present their robots for the weigh-in at 1:30pm in room KEG-036. Paul Leamy is managing the weigh-in and will run through a checklist with each team. He will also provide Q6a feedback forms for you to complete and return with your robot after the tournament.
From 2:00pm onwards, teams must be continuously present in room KEG-036 and ready to compete immediately whenever summoned to one of the arenas. If a team is not ready when they are called to compete in a bout, their opponent will be granted a walkover in that bout. However, that team remains eligible to compete in subsequent bouts (until they are eliminated from the tournament).
Once your team is eliminated from the competition (or has won!), you must submit your robot for assessment. This is critically important for your final grade. Paul Leamy (or another tutor) will be managing the submission of robots and will run through the following checklist with each team:
Please do not leave without submitting your robot. Doing so may have a catastrophic effect on your grade.
The RoboSumo tournament rules are those of the Robot Challenge “Mini” class, mostly as described in the Robot Challenge rules PDF document. However, those rules make provision for tournament organisers to introduce local rule changes as appropriate.
The following rule variations apply in the DIT RoboSumo tournament:
Important note: Every effort has been made to compose the rules of each bout and the structure of the tournament as a whole in a way that is fair and consistent, but since it is impossible to anticipate every eventuality, the referee(s) must have ultimate discretion to overrule any regulation or introduce a rule change at any time.
The tournament is divided into two main phases – a sorting phase and a knockout phase. Each team must also complete a validation process prior to competing in their first match.
The validation process ensures that each robot complies with the restrictions on size and mass imposed by the Mini class rules. Teams who do not successfully complete the validation process are not eligible to compete in the RoboSumo tournament. Teams who are unable to field a compliant robot may still be asked to compete in one or more exhibition bouts for assessment purposes, but they cannot progress in the tournament.
Following validation (the “weigh-in”), if a team makes any change to their robot which increases its size or mass, they must repeat the validation process prior to competing in a match.
The referees will divide the competing teams into two pools. The initial ranking in each group will be determined primarily by the results of the Race to the Wall challenge. The objective of the sorting phase is to select the top 8 teams from each group. A variation on the so-called bubble sort will be followed for the majority of the sorting phase. However, the referee in charge of each arena may deviate from this pattern at his/her own discretion to resolve any unforeseen ranking issues or anomalies.
In each group, the sorting phase will conclude until the referee is satisfied that he/she has identified which 8 teams should progress to the knockout phase of the tournament.
The 8 top-ranked teams from each group (A1, A2, A3…A8 and B1, B2, B3…B8) will proceed to the knockout phase of the tournament. When a team loses a match in this phase, they are eliminated from the tournament. The referees will decide the number of bouts per match in each stage of the knockout phase.
The matches in this phase of the tournament are as follows:
Inevitably, many teams will face technical issues on the day of the tournament, and it’s impossible to foresee every problem. However, there are certain issues which we see every year:
Finally, remember to get plenty of photos and videos of your robot (and team) in the run up to and during the tournament. Of all the evidence you will provide on your blog, photos and videos are some of the easiest to create, and they can really help to tell the story of your project.
Finally, best of luck to all of you!