1 / 10

Innovative Robotics Team Project - Lessons Learned and Future Development

A detailed account of a team's successful robotics project, discussing sensor and design choices, roles played, challenges faced, and future improvements. Lessons learned include resource management and the importance of effective teamwork.

qiana
Download Presentation

Innovative Robotics Team Project - Lessons Learned and Future Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Unknown Kyri David Andy Sami Cheryl the dog

  2. Teamwork • We discussed all the problems we came up against. • We came to solutions amicably. • We divided the tasks between us, in order to work to each of our individual strengths.

  3. Roles played • Kyri • Programming • Building • David • Programming • Building • Andy • Presentation • Building • Sami • Presentation • Building • Cheryl • Mascot

  4. Why we chose our Sensors • Light Sensors • Easy to use • Reliable • Would pick up the masking tape on the dark carpet • Touch Sensor • To detect the taller cans • Easier to use than a light sensor for detecting obstacles • Motors • Necessary • Needed to move the robot itself

  5. Why we chose our Design • Why we opted for the design: • Stability/Reliability • Seemed most suited to our needs • Tracks vs Wheels • Lower centre of gravity • More suited to the rough surface of the carpet • Slower (slow and steady wins the race) • Programming • Have robot run. • Light sensors pick up change in light. Robot then reverses and turns accordingly. • Touch sensor on front. Picks up taller can, and ram turns to correct direction.

  6. Final Sensors vs Chosen Sensors • We initially asked for: • 3 light sensors • 4 motors • 2 touch sensors (possibly) • We got: • 2 light sensors (we won the coin toss…) • 4 motors • 1 touch sensor • Differed because: • Availability • Changes to our initial ideas

  7. Experimental Methodology • We used a simple track to test out our initial ideas. • Once we had developed our programs somewhat, we designed a much more challenging course to see how our robot fared in a number of different situations. • Initially we made our track to test if the light sensors could detect the masking tape. • Once that had been achieved, we added cans to the track to see if our robot could achieve objectives 2 and 3.

  8. Lessons Learnt • There are always limitations to a good idea. • Resource management. • Teamwork can cause conflict. • (don’t stay up to ridiculous hours of the morning so you’re too tired to write the presentation…)

  9. Problems • We underestimated the weight of the bean cans. • So we had to redesign the structure of the robot to make it stronger. • (which did actually improve it…) • Problems connecting the bumper to the chassis. • So we had to be all inventive and stuffffff and think about how to connect it. • The mechanism we used to knock the cans out of the way obstructed the touch sensor. • So we moved it forward so that it wasn’t obstructed anymore….

  10. Future Development • If we had more time we would: • Use more sensors. • Use the newest RCX block available. • This would allow more sensor inputs. • We’d use IF functions more effectively. • (we’d also go to bed early….*snore*…im sure that as you’re reading this at least one of us is trying not to yawn).

More Related