The flight was to arrive in Kuala Lumpur at around 13:00 and we would depart for Bali at 21:50. Arriving at 13:00, we should have been able to arrive in the city via Grab between 14:30 – 15:00, but it took at least an hour at the immigration line so we didn’t get to the city until after 16:00. This would leave us around 5 hours in Kuala Lumpur, which is not great, but not terrible.

We had only eaten breakfast, so by this time, we were starving. So we went to Lot 10. Everything looks super good, but in actually only tasted okay. I thought it’d be on par with my trip to Singapore.

Next, we visited a nearby street market. The market reminded me a lot of Singapore – similar food options (bak kut teh, chili crab, stingray, etc.), which makes sense since Singapore used to be a part of Malaysia.

Our next destination was the iconic Petronas Twin Towers, but all of a sudden out of nowhere, it started pouring with thunder and lightning. At first the thunder was a few kilometers away judging but how long it took to hear the sound, but not long after it was right on top of us.

We got on a Grab to head over there, but the sudden rainstorm brought traffic to a complete stop and it was barely moving. After being in the car for 30 mins and having gone less than a kilometer, the driver advised that we head to the airport directly as there wouldn’t be enough time to hit up the twin towers and make our flight. We reluctantly agreed.

During the car ride, I chatted with the driver about living in Kuala Lumpur. The driver was Cantonese in enthnicity but was born and raised in Kuala Lumpur, which I didn’t expect at all. I had forgotten about how stuck we were in traffic while chatting with the driver (at one point the driver took a bathroom break and left the keys in the ignition).

Eventually, I looked on Google Maps, and saw there was no way we’d make it to the airport by car. We decided to get dropped off at the metro station in the pouring rain and we’d take public transit the rest of the way. Check it out in Mike’s video (the raining part starts at ~5:10).

That was pretty much our trip to Kuala Lumpur. After a big delay at the airport and the freak rainstorm, we really only had 3 hours in the city to do stuff, which was too bad. See the rest of the photos here.

Im Juni 2011, bin ich schon nach Amsterdam gegangen, aber dies mal reiste ich nach dem Ende des Roboter-Wettbewerbs mit ein Paar Freunden von dem UBC Thunderbots.  Wir reisten aus Eindhoven nach Amsterdem mit dem Zug, und am etwa 11 Uhr kamen an.  Weil ich hier einmal gegangen bin, erinnere ich sich ein Paar Orte wie Sehenswürdigkeiten und Restaurants wo ich gegessen hatte.

Es passiert einfach so, dass gleichzeitig mein Freund aus Hongkong nach Amsterdam gereist hatte, so traf ich mich mit ihm. Ich hatte nicht in 3 Jahren ihm gesehen, so es ziemlich cool war ihn zu sehen.  Ich konnte den Anschluss mit ihm finden.

Weil der Roboter-Wettbewerb gerade beendet war, hatten viele Mitbewerber danach nach Amsterdam gereist, und so manchmal sahen wir sie.  Es war ein bisschen seltsam sie zu sehen, weil normalerweise ich nur in dem Wettbewerb sie sehe.

Letzte mal war das Rijksmuseum noch nicht geöffnet.  Obwohl es jetzt geöffnet war, besuchte ich nicht weil, Kunstmuseen für mich zu langweilig sind.

Wie eine Person aus Amsterdam, fuhren wir Fahrräder herum der Stadt. Die orange Farbe passte sehr gut. Weil einer unserer Freunde krank war, konnten wir nicht so viel Fahrräder fahren.

Wir fuhren auch mit dem Boot auf die Amstel und hatten die Kanäle gesehen. Viele Leute wohnen anscheinend in Häuser auf dem Fluss!

Abends, gehen wir zum Rotlichtviertel. Meine Freunde trollten mir über Dinge dass im Rotlichtviertel passiert. Ich sagte dass, “wenn ihr später mich nicht seht, werdet ihr wissen wo ich bin”. Das Rotlichtviertel war wie Leute sagten: viele Prostituierte, Marihuana, und Sex-Shows.

Der nächste Tag war der letzte Tag unserer Reise. Wir fuhren zum Flughafen und flogen nach Vancouver zurück. Während des Flugs, vermisste ich sofort Europa. Ich liebte das Reisen in Europa und hoffentlich in der Zukunft, werde ich noch einer Gelegenheit nach Europa zu reisen haben.  Für die nächsten Tage, dachte ich über Europa die ganze Zeit, und ich wollte zurückfahren.  Auch jetzt, dachte ich an meine Erfahrungen zurück und es war eine der besten Erfahrungen meines Lebens.

Fotoalben: hier

We had spent a whole year upgrading everything.  I designed a new ball kicking system that was more durable, more maintenance free, and more powerful than the year before.  The other mechanical systems were more robust as well.  The electrical system also had a huge upgrade.  Burning and smoking electrical boards were a thing of the past!  We have never had a design this robust – ever!

What is RoboCup?

For those who don’t know what RoboCup is, RoboCup is an international robotics competition aimed to further robotics research.  Their long-term goal is to have robots beat the World Cup Soccer team winners by 2050. There are various leagues within RoboCup, such as in robotic soccer (where we participate), home care, rescue, simulation, etc.  Our team, the UBC Thunderbots, compete in the small-size soccer league, which is probably has the fastest game play of all the different leagues.  The robots are generally cylinders with a diameter of about 18 cm and a height of 15 cm.  They can move at around 4 m/s and kick a golf ball at 8 m/s.

One of the other leagues, the Standard Platform League competes with standardized robots for all teams and the key difference between each is the software that is written for the robots.

Another league, the mid-size league in RoboCup Soccer competes with robots that are about a 1/3 of the size of a person. The game isn’t as quick as the small-size league game and they play with a real soccer ball instead of a golf ball. During the competition, it gathered quite the crowd too.

Preparing for the Games

Most teams arrived at the venue when it opened to get to work right away. Everybody wanted their robots in tip-top shape. Our team did the same. Even though our robots were ready mechanically and electrically, the key game changer was seeing which team had better artificial intelligence for their robots. Whenever got time to test on the field, we took advantage of it to make sure our AI was working well too.

Round Robin

In the round robin stage, each team gets four games against other teams in their bracket. Each bracket is made up of five teams and the skill level is spread out based on the rankings of the previous year.

We lost our first two games against a team called KIKS from the Toyota National College of Technology in Japan, and a team called STOx’s from the Universidad Santo Tomás in Colombia. In both of those games, we were simply outplayed because the other team had better software than we did. At the end of the game against the Japanese team, I spoke a bit of my horrible Japanese to them and they were super surprised and impressed that I knew a bit of Japanese!

Because our robots were finished not long before the competition began, the software team did not get a chance to test the code that was written, and so we found out the problems during the competition. Our robots were never able to drive up to a ball and take possession of it. The robots somehow always missed the ball. When the robot had the ball, it didn’t know what to do with it. It sat there holding onto the ball doing nothing. This was so frustrating for our team and even more so for the software team who wished they had more time to test.

We won our next two games against two lower tier teams. One is called RoboFEI, from the Centro Universitário da FEI in Brazil, and a team called RFC Cambridge from Harvard and MIT. It’s nice to be able to say that we beat a team from these two ivy league schools. Looks good when we look for sponsors too!

Lucky Loser Round

Because we had a 2-2 record during the group stage, we played a fifth game, the so-called Lucky Loser Round, to see if we could qualify for the quarter finals. Our match up was against a team called ODENS from the Osaka Electro-Communication University in Japan.  The game was so close that there was a dispute about the rules and whether what our team did was legitimate. Because our robots were not able to move up to a ball and shoot it at the net during the shootout, the referee introduced a workaround that the other team disputed.

Our referee’s native tongue was Portuguese, we spoke English, and the other team spoke Japanese. I didn’t know enough Japanese to translate. Eventually, members from other teams like the Thai and Chinese team came to help with the dispute. During the discussion that took about an hour, I heard people speak English, Japanese, Portuguese, Thai, Japanese, and Mandarin all at the same time. It seemed like nobody had the full picture of what was happening and how to resolve it.

The dispute was resolved when both teams agreed to a specific workaround that made it possible for our robots to do shootouts.  The game ended with a shootout and we lost on the very last shot of the shootout unfortunately. We almost made it to 8th place.  Still, achieving 9th place out of 22 teams was the best that the team has ever done before.

The Competition Ends

Skuba, from Kasetsart University in Thailand, had won the competition for four years in a row since 2009, but this year they had a surprising finish that was not even the top 4.  The second place team, ZJUNlict from Zhejiang University in China had beat them early in the quarterfinals.  ZJUNlict’s strongest opponent this year was CMDragons, from Carnegie Mellon University in USA.  In the final round, they were tied for the entire game and the game went to shootouts where CMDragons lost by one goal.  ZJUNlict had made first place in the RoboCup 2013 in the Small Size League.

As the competition came to a close, we said goodbye to the people on other teams that we met and as a parting gift from the German team ER-Force, they gave us a German flag with the names of all their team members signed onto it, with the message, “for our amazing friends, the Thunderbots, from team ER-Force”.

I realized now that the competition is over, I probably wouldn’t be going to competitions in the future because I’ve graduated from university. It made me feel a little bit sad that I couldn’t compete anymore, but at least I can still help out the team wherever they need it.

Link to photo album here

This gave us a lot of opportunities to find out what was wrong with our robots before the real competition began. We found out that are mechanical and electrical systems were quite robust, while our software system was the weakest link of the three.

In the downtime, we were taken on a tour of the nearby Eichbaum Brewery. The tour was quite difficult to follow because it was pretty much all in German. Even though I had learned some German, it was still quite difficult for me to follow.

I had been to Mannheim before and both times I went to Mannheim before this time, I had a very negative experience. The first time, I got food poisoning (I still remember which restaurant it was), and the second time, my friends and I waited at the Mannheim train station for 4 hours for a train to Berlin with a scheduled departure time of 12am.

Having had lived in Germany before meant I recognized a lot of brands like food chains, department stores, cell phone companies, etc. Because of that, my teammates often asked me different things about Germany such as how German phone plans worked and how to sign up for a plan. I explained it to them and even asked the cashier at the supermarket who didn’t speak English about phone plans.

On another day, we were also taken on a tour to the nearby city of Heidelberg. I had also been here before and vaguely knew my way around. We hiked up to the castle again, but we were there in the evening so the inside of the castle was closed by the time we arrived, so we just went as high as we could.

After spending a few days in Mannheim, all three of the teams organized transportation together to Eindhoven, where the real competition would begin. The workshop allowed us to see what our robots were capable of and what we could improve on early, so that we would be better prepared for the real thing.

Link to photo album here

As I sat on the plane, my mind began to wander. I had this weird fear that something might go wrong like I would get mugged or something or maybe there was some fundamental mistake in my trip planning.  I was reminded of the time my wallet was stolen in Brussels and I certainly didn’t want anything like that to happen again.  And then I thought about how much fun I had when I lived in Stuttgart.  I have very fond memories of my experience in Germany.  I then felt a slight rush of emotion and almost reliving some of my experiences in my head.  Then I figured I just had to be confident with my trip preparations and let myself have fun on this trip.  After all, not many people get an opportunity like this.

Since it was late September, we weren’t expecting any snow.  It wasn’t even cold for that matter.  We all met up on campus in the morning and off we went.  From there, it was about a 2.5 hour drive.  I would have stopped in Squamish to go to Tim Horton’s if I had known to take that exit.  We arrived at the UBC Whistler Lodge at around 11.  The lodge had a pool table and an arcade machine!  They didn’t have Tetris on the arcade machine though.  If they did, that would have been super awesome.

The lobby also featured nice First Nations artwork over top of the fireplace.

We spent about an hour and a bit with presentations from each of the sub teams (mechanical, electrical, and software) so everyone could get a little bit of an orientation about what everyone else was working on on the team.  This was helpful in that each sub team would not be working alone on their components anymore.  This promoted the very important idea of multi-disciplinary teamwork.

After the exploring, we decided to walk around to check out the scenery.

We spent the rest of the day socializing with one another and it helped us all get to know each other a little better.  It’s definitely better to know one’s teammates better in order to help team chemistry.  It definitely helped the team get a lot closer.

People took part in a variety of activities: Big 2, drunken poker, Apples to Apples, just chatting, among other things.  Pretty sure everyone had a good time.

We stayed for a day and a night at the lodge.  Before we left, we took a nice stroll in the Whistler Village. It was nice since there was not a lot of people during the off-season.

On the drive back, we stopped at some viewpoints to appreciate the scenery.

Some of the mountains still even had snow on them!

Once we left Whistler, the drive back became a lot more boring. I guess I was just in a hurry to head home then. I figured that was a long enough break (even though I only had less than a month of school), so I probably should take care of my actual priorities again…

More photos here

Flying to Mexico City

When we got to Dallas Airport, we had a stopover of few hours, so we decided to have some Texan steak – or at least as Texan as we tried to get without leaving the airport.  We ended up at TGI Fridays.  It was the first steak that I’ve had in a long time, and I definitely could use another one.  The steak even came with “Jack Daniel’s Sauce”, which made it that much better.

After eating, we met up with two others on the team who had flown from San Jose and Toronto.  After a four hour flight to Dallas, and other few hours of stopover there, we had to fly for another two and a half hours to get to Mexico City.

As my friend said, “it’s like China happened”.  The Benito Juárez International Airport was probably the most disorganized airport I’ve ever seen.  It’s as if every single flight landed at the same time.  The lineup to grow through customs took at least forty-five minutes.  During this whole time, everyone was tired and wanted get their sleep.  A lot of the people on the team hadn’t slept the night before (rather than sleep 2 or 3 hours to wake up early for the flight right?).  While in this lineup, we saw a couple of other RoboCup teams landing as well (Skuba, MRL, among others).  After finally getting through customs and a security check, we got a ride to our hostel via transportation that we organized with the hostel prior to our departure.

Hostel Mundo Joven Catedral

The hostel we stayed had very nice staff that really cared about making its guests feel safe there.  It’s a common feeling among travelers to think that Mexico City is definitely not one of the safer places to travel to.  To combat that, the hostel had its own security guards, security cameras, and they even called legitimate taxi’s for its guests.  They even told us which direction to walk when leaving the hostel to avoid going to the shadier parts of town.  Furthermore, it was situated in the historic center of Mexico City, within walking distance of the Metropolitan Cathedral of the Assumption of Mary of Mexico City and the Plaza de la Constitución.  From some of the rooms at the hostel, there was a nice view of the cathedral.

Work Day

We spent the next day working on the robots to make sure none of the mechanical parts had been affected during the flight from Vancouver.  We had packed all the robots in a regular suitcase with packing foam all around it to protect it.  Looking over the mechanical parts, everything was in order.  The main things we had to fix were tightening screws, adjusting the wiring etc.  The software team had very little to do because they’ve written all the code they could, and just needed robots to test with.  The electrical team on the other hand, toiled tirelessly to troubleshoot all the boards and make sure they were all functioning properly.

RoboCup Begins!

We arrived at the competition venue, the World Trade Center at 8 AM to find a slew of other teams patiently waiting to register.  After probably an hour long wait, we all finally moved in and set up our work places.  When we looked at the field the robots would be playing on, we noticed that the organizers hadn’t yet set up the cameras yet (required for the robots to “see” where they’re going).  This meant that no teams could test.  Teams that were ready could only wait until the organizers got those set up.  Because of this delay, the games had to be delayed as well.  This gave us more time to get the robots ready.  For the next little while, we were the first team to arrive and the last team to leave everyday.  The electrical team needed all the time they could get to finish everything.

Because we had already finished most our maintenance work the day before, there wasn’t a whole lot we could do.  The electrical team had to continue working on their stuff to get as many robots ready as possible.  For the next day and a half, we let the electrical team do their work and we’d help them along the way by replacing parts that were broken (encoders and such).  Otherwise, there wasn’t much we could help with.

Food for the next Week

When we got hungry during the competition, we did a little bit of exploration to find food.  Eventually, all the teams wound up at the same shopping mall for food.  There was a supermarket downstairs to buy water and a food court upstairs with a variety of foods.  We went to this mall pretty much everyday for as long as we were at the World Trade Center.  One day we’d try Mexican food, other days we’d try plain-old hamburgers and other days we’d try even Chinese food (at least the white person’s interpretation of it).  It wasn’t really healthy for us, but we figured it was only for a week.

For dinner, most teams ended up ordering pizza from the nearby Domino’s.  We ate it so much that everybody got sick of having pizza.  Sometimes, we’d have dinner with other teams at our hostel restaurant so we could get to know them a little bit better.  After all, the competition is more about mutual learning and robotics advancement rather than about winning.

Let the Games Begin

Because our team wasn’t that ready to begin with, we had to forfeit our first game against the Immortals from Iran.  By the time we got three robots up and running, we played against the RoboJackets from Georgia Tech.  They only fielded five robots out of the total six.  For most of the game, both teams played pretty evenly, despite their two-robot advantage.  All was going well until one of the opponent’s robots chipped the ball that hit the top of one of our robots, bounced off and rolled into the goal.  In that particular situation, the referee had called an “indirect free kick”, meaning the shot, even if it went in the net, would not count.  But unfortunately, that rule was not applicable because it hit off of another robot.  It was an unlucky goal for us, and we definitely could not score a goal to tie up the game.  We ended up losing one-nil.  For the next few days, we kept complaining about that goal.

In our third game, we played against RoboFEI from Brazil.  There were so many good scoring chances in this game from both our teams that made this game so intense.  Even though we were only watching machines play, everybody cheered them on.  We had four robots on the field this game and they all worked like a charm.  The mechanical system, electrical system, and the artificial intelligence worked so well together.  It was a great feeling for everyone on our team – to see our design work.  After almost a year of hard work, this was it.  We saw our robots move, intercept balls, shoot on the goal, etc.  A lot of the robot shortcomings from the North American Open were also dealt with, such as the problem of the break beam sensors not working, and the robot not moving accurately on the field.  When we scored, we cheered so loud that every single person in the room could hear us (there were probably about 1000 people in that room).  We all got an immense feeling of satisfaction in seeing our working robots score their first goal.  A few minutes later, the other team scored a goal.  It didn’t matter to us, we were still high in the clouds in terms of our mood.  The game ended 1-1.  Despite the tie game, everyone on the team was so happy in seeing our robots work, it didn’t matter what the result was.

This was a great morale boost for the team because for our forth and last game, we played against BRocks from Turkey.  This time, we had our full fleet of robots.  We played our first six on six game.  Yet again, we saw our robots work.  Nothing broke down during the game and everything just worked.  It was quite rare for us to just put our robots on the field and have nothing go wrong.  At one point, our robot shot the ball into the opposing robot and a piece fell off of it.  We knew our design worked when stuff like this happens.  This game was less intense for us than our previous game, but we did end up winning.  That put our record at 1 win, 1 tie, and 2 losses – a total of 4 points.  Unfortunately, this wasn’t enough for us to advance to the next round of the competition and as a result we finished 13th out of 20 teams in the league.  Not so bad for having zero working robots when we got to Mexico.

After the official games, we played a couple friendly games with other teams.  The first game we played was against the Mannheim Tigers.  The game was going well, until we found problems where some of the screws on the robot weren’t tightened sufficiently.  As a result, things well off the robot when we played.  It was quite embarrassing to see.  At least it was only  something minor like putting in a screw, and not something major like a design problem.  In our second friendly game, this time against ER-Force from Erlangen, we found some electrical parts frying randomly on the board, which wasn’t good either.  Out of six working robots, we now had three – still a net gain I guess.

After we were done playing, we watched the other teams play for first place.  From watching their games, it was clear that they played on a way higher level than we did.  Everything that their robots did were way better than ours.  Shooting was faster, chipping went further, robots moved faster, kicks were more accurate, etc.  Everything about their robots was just better.  There is definitely a lot we could learn from these teams.  The final winner of this year’s competition ended up being Skuba from Thailand, who beat ZJUNLict from China.  Both teams analyzed each others strategies for days, but only one team could come out on top.  And now for the fourth year in a row, Skuba remains the undefeated winner of the competition.

Other Leagues in RoboCup

During our idle time, we walked around the other rooms to see how the other teams were working.  RoboCup has many different competitions under its name, while our Small Size League competition is only one small part of it.  Leagues range from soccer robots, rescue, simulation, to even home care robotics.  In the home care robotics league, the competition involved a robotic navigating through a mock house to perform certain chores such as picking up objects to hand to people, speaking and hearing instructions, etc.  It was an admittedly difficult task to do for these robots, but many teams were quite successful at it.

Accidents Happen

Just like in the North American Open, there was yet again another accident involving batteries.  Except this time, nobody noticed and the whole battery lit up in flames.  Somebody just yelled “fire, fire!” and started trying to pat it down with something.  Knowing that I was too far away to do anything, I just took out my camera and snapped a picture of the whole thing.  Eventually, someone just poured lots of water over it to put our the fire.  In retrospect, that might not have been a good idea since water in an electrical fire is not really a good thing.  Nobody got hurt though, which is good.  Afterward, the organizers didn’t let us charge batteries nearby our work space anymore.

Some Design Shortcomings

Knowing that our ball kicker would be able to withstand impacts of the ball, what we had forgotten to analyze was how well the kicker would hold up if it hit a object fixed to the ground.  We found out the hard way at the competition after a few games when we discovered that our robot kicker head was bent out of shape.  We also had a lot of turf buildup inside the robot that was enough to slow down the wheel during the game.  This turf had to be cleaned out after every match.

For the kicking mechanism, the robot uses a solenoid/plunger mechanism.  Activating the coil would cause the plunger inside the core to move quickly to hit the ball.  A rubber band secured to the end of it would allow the plunger to return to its initial position.  The problem with this setup was that the rubber band would easily break and had to be replaced after every game.  When we took out the rubber band, we could always see cut marks along it.  In another instance, a chipper solenoid on a robot almost popped out.  It’s not really clear why this happened at all, but it could have been a screw that was not very tight to begin with.

RoboCup Closing

To close the competition, there was a soccer game where humans played against the middle size league robots.  It was pretty funny to see the robots struggle to take the ball away from people who could handle the ball way better.  At the same time, the humans were really scared of the robots since if a human ever got hit by the kicker head from the robot, it would break bones.  The robot goalie however, proved quite competent in blocking shots – better than the human goal from what I saw.  Or maybe the human goalie wasn’t trying very hard.  I’m not sure who won the game since I didn’t watch the whole thing, but it was still really interesting to see.

Afterward, all the teams packed up their things and waited for the closing banquet.  At the closing banquet, they served a standard meal for everyone.  It was a really good chance for teams to celebrate their achievements and finally relax a little bit after the competition.  Everyone deserved a rest after all of that.

First Real Tour of Mexico – Teotihuacan

After the competitions ended, most teams stayed an extra day or two to see the sights in Mexico City.  The organizers of the Small Size League were nice enough to organize a tour for everyone the day after the competition ended.  Most of the SSL teams went with us to the Aztec pyramids in Teotihuacan.  The tour first showed us how their predecessors used different plants and minerals to make tools such as knives and sewing thread.  That part was interesting at first, but I think what a lot of us really wanted to see were the pyramids.  Afterward, the tour guide led us to the gift shop.  For some reason, most of the people were so interested there, it took about an hour for everyone to finish so that we could move on with the tour.  After the gift shop, we finally made it to the pyramids.

After walking up and down the pyramids, we had lunch and went back to Mexico City to see the Basilica of Our Lady of Guadalupe.  This was one of the most visited Catholic shrines in the world.  But because I had already visited so many churchs and cathedrals from my tour around Europe, this part of the tour was less interesting for me.

Historic City Center

The team would fly back to Vancouver on the day after visiting the pyramids.  But before leaving, we made sure to visit the Metropolitan Cathedral of the Assumption of Mary of Mexico City and the Plaza de la Constitución.  In the plaza, hung a giant flag of Mexico.  This is where the city center used to be, at least during the 19th century.

Going Home

After 10 days in Mexico, we all longed to go home.  It had been a long week – full of stress, adrenaline pumping excitement and overall a good experience.  But after all that, we were ready to go.  We flew out in the afternoon from Mexico City.  Apparently, at around the same time that we were at the airport in Mexico City, three cops had been shot to death.  While we were there though, we didn’t hear anything of it.  We safely arrived in Dallas for a brief stopover and arrived back in Vancouver at about 8:30 PM, just in time to go home, wash up and go to bed.

More photos here

Beginning of the Competition

On the first day of the competition, there was a work day for all the teams to use to get their robots ready again after a long flight to Canada.  As the current mechanical team lead for the Thunderbots, I too had to get our own robots ready to play.  The mechanical systems had already been completed some weeks ago, but unfortunately, even now, the electrical board testing and firmware coding still had not been completed yet and some parts that we needed were still not in.  For the next day and a half, the team was scrambling to get everything finished in preparation for the first game on Sunday.  Because, the only critical tasks remaining were the electrical testing and coding, only the electrical team had the know-how to tackle those tasks.  The mechanical and software teams could only wait for results.  As the electrical team worked, everybody else on the team became more and more stressed.  We all kept wondering whether the team would have working robots for the first game.  We were all helpless in this situation.  The electrical team worked throughout the day and night trying to finish.  Some of the other team members stayed in anticipation while others went home to rest hoping for results in the morning.

Throughout this work day, the Chinese team continued testing their robots on the field.  They seemed like the most ready team.  The German team however, had lots of work to do as well.  Their flight to London from Germany was delayed and as a result, they missed their flight from London to Vancouver.  They arrived in Vancouver on Saturday night.  They  had even less time than we did to get their robots working.  When each team set up their work space, they each made sure to put up their mascots.  For the Chinese team, they had a panda plush of about 1.5 ft tall and the Germans had a full size German flag.

Game Days

On the game day, I woke at up 5:30 AM and arrived bright and early on campus at 8 AM.  When I arrived, the electrical team was still at it and seemingly not even close to finishing.  This led to a change in the team’s strategy to the competition.  We would try to repair the electrical boards from last year’s robots.  These old boards had a different size than the new ones and had different mounting holes, but luckily, somebody on the team had the great idea of including mounting holes for these old boards for this year’s robots.  Otherwise, we would have had a really hard time hacking that together.  Given only the few hours we had to hack this set up together, the mech team and I worked as fast as we could to finish.  We each probably ran up and down the stairs at the UBC Engineering Design Center about 20 times that day looking for tools and delivering robots.

The first game was supposed to be at 9:30 AM, but my team certainly was not ready.  It seemed like the other teams weren’t completely ready either, so the game was postponed until the afternoon.  The Thunderbots was supposed to play the first game, but due to our lack of readiness, China and Germany played each other instead.  When it became our turn we play, we managed to get three robots out of six on the field.  None of these robots had a working break beam sensor (the sensor on the robot that is designed to detect ball possession).  Without break beams, the robots did not know they could kick the ball, since it would never know if it had ball possession.  The robots did not have a controller that worked well either (the controller determines how much voltage to apply to each of the motors such that the robot can move smoothly from A to B).  A controller that didn’t work well meant the robots drove about on the field seemingly confused.  “Derp” is probably the best word to describe it.  Despite the shortcomings of these three robots, they played their best against ZJUNLIct from China and the Thunderbots were defeated 10-0.

On the following few days, the mech team tried to help the electrical team the best they could with tasks such as building extra connectors.  We also tried to get the old break beam sensors working again.  It was something that had to be on the robot if it were to ever kick the ball properly.  After toiling for a few hours, we managed to get two out of three of them working.  We probably could have gotten more if we knew more about the electrical design.  There was little to go on in terms of the wiring schematic and spare parts.  It was also hard to troubleshoot since ambient lighting largely affected the sensor.  If it worked upstairs in our work space, it wouldn’t work downstairs on the playing field.  It took us a while to figure that out.

In our second game, we played against ER-Force from Deutschland.  For this game, we still only had three robots, but this time they were a little bit better equipped.  Even then, the robots still had trouble kicking because the lights being used on the field emitted too much infrared light, which obstructed the break beam sensors.  It was very frustrating to see the robots not knowing when to kick even though they were handling the ball perfectly. But somehow, we still managed to score a goal.  In the end we lost the game 6 to 1.

In the final game between China’s ZJUNLict and Germany’s ER-Force, the Chinese team was victorious.  Both teams had a full fleet of robots to play six on six.  A modest crowd of spectators also watched the whole game being played and in general people were quite impressed at this engineering feat.

Team Social

To allow the teams to better know one another, there was a social event planned by the organizers of the North American Open.  There, I met a lot of the members of the German and Chinese teams.  It was nice that that I could talk to each team in their native languages.  Although my German wasn’t that good to keep up a conversation for a long time, it was enough to get the Germans wondering how I knew it at all.  The last thing they’d expect is for a Chinese guy to start speaking German to them.  My Mandarin was at a level that I could talk to people in it, but there were still some occasions where I didn’t understand what they said.  It was probably because of me not having a lot of practice with Mandarin (I speak Cantonese normally) and them having an accent from their region that I didn’t recognize.

Press Conference

The organizers made sure to invite as much of the press as they could.  More publicity meant that the team could potentially get more money in sponsorship.  More money means better robots.  The administrative members of the team were in the spotlight and talked to most of the people from the press, while the technical members of the team continued to do their work.  The team leads from mech, software and electrical also had a brief interview with the 24 Hours Vancouver newspaper.  The team was also featured in the Ubbyssey here and on MacLean’s magazine here.

The Chinese team also put on a show for the press by putting all 12 of their robots on the field so they could they play against themselves six on six.  The performance went quite smoothly as there were not random break downs and the press were very impressed.

Engineering Failures

As with these student projects, an accident was bound to happen.  This one was with a battery.  There was have been a defective battery that the Chinese team unknowingly brought and when they charged it, the battery started puffing up – not a good sign for a battery.  One of our team members was quick to notice and instantly dunked it in soap water and disposed of it.

For our team, we had problems where the solenoid kicker would get stuck after being used repetitively.  Heat from the power dissipation in the solenoid windings would heat up the whole assembly and cause the solenoid housing to permanently deform.  The solenoid was produced out of stacked layers of poly-carbonate sheets.  This stacking of layers allowed each layer to deform individually.  To fix this problem, we printed out new housings made of ABS plastic.  By having one solid solenoid housing, it was more difficult for it to deform.

The German team had some problems with the turf getting dug out of the carpet and getting everywhere inside the problem and also with their robot shells not staying on properly.  The turf inside the robot meant that gears could get stuck intermittently and could also get in the way of other mechanical components.  Their solution solution for now was to clean it all out every game.  During games, the shells of the robot would pop out randomly whenever there was an intense impact with a ball or another robot.

Getting Ready for Mexico

On the Friday before all three teams left for Mexico City, everybody had to pack up all of their things.  The German and Chinese teams could pack everything easily since they had packed everything once before when they had to fly to Vancouver.  For us, our tools were scattered all over the place.  It took us about 4 hours to find all tools to pack into the the luggage containers.  The approach to packing was that we would pack any tool that was ours and was already lying out on the table.  This is because if we took it out of the tool closet, it meant that the team used it for something.  Naturally all of the hex keys, screw drivers and the like were packed.  All spare parts were packed.  Every tool that we had sitting around was packed.  Even electrical equipment like a power supply and an oscilloscope was packed.  We had everything we needed for RoboCup 2012 in Mexico City.  Even though not everything was done in time for this competition, everybody was confident that things would be better in the competition in Mexico.

More photos here

Team Formation

I think this is where a lot of students struggle when things go wrong.  It’s always possible to get a teammate that is hard to work with.  While it is no fault of either person, the two personalities (either in values, cultural background, style of working, way of thinking, etc.) are different enough to cause disagreements.  At times, the disagreements can become so heated that the team’s progress in the project is hindered.

I realized that there were communication issues among each other in the group, which delayed progress in the early stages of the project.  These issues came about in the form of misunderstandings of what people said during team meetings.  I found myself in the position where I was expressing my own interpretation of what people said in the hopes that everyone would reach a common understanding.  As the project went on, family issues prevented one member from continuing this project further.  In a way, this eased our communication problems since communication between three people was a lot easier than between four people, based on what I experienced in the project.  Afterward, our team became a lot more efficient and progressed at a faster rate than before.

One of the things that the mechanical engineering curriculum at UBC teaches is team dynamics.  After learning a lot of theory as to how to work best with teams, doing projects with other people puts that knowledge to the test.  Some people don’t really manage working with others and feel set in their ways.  Differences among people exist and I realize that adjustments in the way I work with them is required in order to promote a healthy functioning group.

Project Scope

In retrospect, I would have advocated reducing the project scope since; I feel that the hours we put in were beyond what the course asked for.  I estimate that each member put in over 300 hours on the project.  Since a large part of this course is about design justification, time is very realistic constraint that can limit project scope.  At the same time, there are other courses to worry about.  By spending extra time on 45X, less time is available for other courses.

In the beginning of the project, I couldn’t predict well how long things would take.  Therefore, time for “messing up” or “unforeseen consequences” should be budgeted for.  Many people say things like “I can finish this in about 2 hours”, but in reality, it will take him two days.

Documentation

Very often I found myself referring to old dossier documents to find out information that I needed to know. For example, if I forgot how much something cost, I looked back on the dossier to find out.  If I forgot one of the project requirements, back to the dossier I looked.  At times, it is a bit of a pain to write some sections of the dossier since I couldn’t make sense of the some of the wording.  To deal with it, I had to ask the project supervisor during team meetings.

Project Logistics

I booked as much machine shop time as we could ahead of time knowing that we would need it.  The team would have liked to send in parts for the waterjet or have the technicians work on them, but we were way too late for that.  With a simpler project scope, we could have designed our parts faster and could have been further ahead in those manufacturing lineups to decrease the lead time.  My teammates and I spent quite a bit of time in the machine shop to get as much as we could ready for the design review.  At the same time, I had to look at when ordered parts arrived such that things would arrive in time so that we had everything prepared while building the prototype.

Time Management

While doing 45X, I was also working on New Venture Design and Thunderbots at the same time, which also took up a lot of my time.  As with design projects, they take up the most time relative to other courses.  For me, I had to juggle these three for the entire year.  This gave me a lot of stress at times, but it taught me to be more productive.  For example, on the way home, I would be responding to e-mails that I received during the day so I would have more time to work on the project when I got home.  Since my commute to campus is 1.5 hours just to get to campus (one direction), I had to learn how to make use of this time.

Project Management

I took up the role of “project manager” in the beginning of the project and this role showed me a lot of the logistics that had to be considered in a project.  Very often I found myself asking for progress on certain tasks and pushing teammates to finish faster.  Different issues often came to my head that I had to find an answer for such as “are our parts going to arrive in time for machining” or “do we need to have another meeting with the client”.

For Future 45X Students

Don’t wait until the last minute to do something.  There is always something that needs to be done in this course from beginning to end.  Mech students like to aim high, which is good, but 99% of the time there is not enough time to accomplish the “perfect” design that they always aim for.  This leads to a lot of sleepless nights or worse, a prototype that isn’t ready to be handed in.  Be ready to bite the bullet and make compromises like cutting features to make work less for the team and to meet deadlines.  No design will be “perfect” at the end of the course and this fact, however brutal it may be, must be accepted.

1.0 Motors

The chosen motors are:

• Finger grasping – Cytron IG32E-264K at a cost of USD $57.03 from RobotShop
• Finger sliding – Cytron MO-SPG-30E-20K at a cost of USD $22.58 from RobotShop

Both motors meet the torque speed requirements for this project.

1.1 Finger Grasping Actuation

From the initial budget, the budget set for actuators was set at $325.  The torque requirement needed for gripping was also calculated and each finger would require 4 Nm at its output to lift a 4 kg object using only the fingertips.  The evaluation criteria states that the device grasp as fast as possible and that the client would have the highest satisfaction if the device cost was less than $700.

Looking on several websites that sold motors, the following DC motor was chosen: Cytron IG32E-264K at a cost of USD $57.03 from RobotShop.  The specifications are as follows:

At 12 V with gearing included, the stall torque would be 20.7 Nm (without consideration of mechanical efficiency).  A motor with a high stall torque is also beneficial because it lowers the gear ratio required, which leads to the use of less space for gearing.  The motor also comes with its gearing, which contributes to its high torque.  Given the high stall torque of this motor addition gear reduction is not required.  During grasping, the motor will be exerting high torque at low speeds and therefore, the motor will be operating near the stall torque.  The torque here is more than sufficient even with mechanical efficiency losses accounted for.

For finger actuation before grasping occurs, there is a low load and therefore the motor will be operating closer to the no load speed.  The no load speed with gear reduction is 27.7 rpm (without consideration of mechanical efficiency).  Split among three output shafts, the speed would be 9.21 rpm.  Even with the load of the fingers accounted for, this is still acceptable. based on requirements and evaluation criteria.

While the torque is a lot higher than required, this motor was only more expensive than a motor of one size smaller by less than three dollars.  The electrical characteristics were also identical.  With a higher motor torque, the grasper would be comfortable in lifting objects even heavier than 4 kg, which is another benefit based on the evaluation criteria.

1.2 Finger Sliding Actuation

The motor required here does not require a large torque since motion in this degree of freedom is not expected to handle heavy loads.  This motor only requires enough torque to overcome the friction of the finger on the power screw that it is mounted on.  Therefore, a low-cost motor (relative to the grasping motor) will suffice.  The DC motor of choice is the Cytron MO-SPG-30E-20K at a cost of USD $22.58 from RobotShop.

The specifications are as follows:

The consistency of the stated specifications do not match the previous motor because the information that was provided by the manufacturer was not consistent.

An initial estimate of two 200 g fingers sliding on a 1/2” diameter power screw with a steel-steel sliding interface (friction coefficient of 0.8) shows that only 20 mNm of torque is required.  Therefore, this motor meets the requirement.  The power screw also has 13 threads per inch, and at the rated 185 rpm, the power screw would slide linearly at 6 mm/s.

1.3 Motor Type

DC and servo motors are motors that are suitable for the project.  An investigation between DC and servo motors showed that many manufacturers of motors did not provide the necessary specifications for choosing a servo motor in terms of the values of the no load, stall torque, and stall current.  While servos generate a lot of torque relative to their size when compared to DC motors, it is not feasible to use a servo motor because of the unknowns in the specifications.  It is possible to buy several servos and test them, but this is costly and time consuming.  At this stage in the project, the team is not able to commit the time to investigate further.

Comparison of the cost of the grasping motor relative to motors from Maxon Motor, a supplier of motors for UBC Thunderbots, shows that the price of a motor of the same power output costs approximately the same amount.  However, a fundamental difference is that the motor from Maxon does not include a gearbox, while the chosen motor for this project does.

2.0 Microcontroller

The microcontroller of choice is the Arduino Diecimila.  The primary motivator for using this board is because the UBC Thunderbots team already has this board and is currently unused.  The Thunderbots team has generously provided the board for use on this project.

The MCU will allow the turning the motors on and off, changing motor direction, changing motor speed, and reading encoder feedback.

3.0 Voltage Regulation for Encoders

Since the power supply is likely going to be run at 12 V, the encoders will require voltage regulation down to 5 V (the operating voltage of the encoder for the motors).  The chosen voltage regulator is the MC78L05A at a cost of USD from Digikey.  According to the typical application diagram of the datasheet, two capacitors will also be required (0.33 μF and 0.1 μF).  The cost of these are less than $1.

The voltage regulator will be wired up in this way as the datasheet shows:

The input will be from the 12 V source, and the output will be to the encoders.

4.0 Motor Driver

To control the motors, an H-Bridge is to be used.  However, due to the different current flows for each motor, one motor driver will require a high current capacity while the other one will not.  The high current capacity motor driver consists of a driving circuit using two half-bridges.  The low current capacity motor driver is made up of 1 IC.

4.1 Finger Grasping Motor Driver

To design the H-Bridge for controlling the motor, an L6205 motor driver will be used.  Each of them costs USD $11.36 from Digikey and can withstand a continuous current of 2.8 A and a peak current of 5.8 A and can be interfaced with the microcontroller with PWM inputs.  The driver can also be run in a parallel mode to double the current ratings by using both of its full bridges together.  The datasheet provides an application circuit as follows:

Output pins from the Arduino can turn the motor on and off through the enable pins.  Direction is controlled by adjusting the voltage polarity between IN1 and IN2.

There are also two output pins for current sensing.  By using it to measure the current draw, the microcontroller program can determine what the torque is through the use of the motor curves provided in the motor specifications.

4.2 Finger Sliding Motor Driver

The motor driver of choice is the L293D and each one costs $2.50 from Digikey.  Bidirectional control of a DC motor can be achieved by adapting the application circuit from the datasheet:

The 1A and 2A pins determine the direction of the motor or the motor deceleration.  A truth table is provided in the datasheet.

5.0 Power Supply

To power the grasper, a power supply plugged into the wall will be used.  It is expected that the future robot will have a power source of its own which will power the hand as well.  Therefore, for the purposes of testing the grasper for this project only a wall power supply will be required.

Looking at the maximum electrical power consumption of the two motors, the total comes to ~65 W (12 V * 5 A + 12 V * 0.41 A).  The other components also consume power and so the final power consumption will be higher.  To compensate, a 12 V power supply with a maximum wattage and current of 84 W and 7 A was selected.  The part number is CENB1090 and each costs USD $70.48 from Digikey.

6.0 Power Supply Connector

The power supply chosen has one port that uses a Molex Mini-Fit Jr. Receptacle.  Therefore, a proper receptacle must be used so that proper wire routing can power all the circuitry.  This also means that the future robot will also require a matching plug for this receptacle.

7.0 Fuses

Fuses will also be used as a redundant mechanism to stop the motor in case the current draw is too high.  The primary method of stopping the motor is through the current sense pins on the motor driver.