Recent Changes - Search:

TEAMS Academy Wiki

Explore TEAMS!
for visiting sophomores & juniors

Robotics

EnvBioTech

Bat Design

Assistive Tech


Students


Instructors

TEAMS Forum

TEAMS Calendar

TEAMS Web Site

Wiki Info

edit Student.SideBar

TrongsWallFollowing

Trong's Wall Following

Summary, Problems, and Debugging

For lab 5, I was responsible for providing a code that follows walls using distance sensors. With these distance sensors, which are external sensors, I am able to tell how far I am from a wall without using the Create’s demo for wall following. To begin, I made a flow chart that would plan out the code that the Create will be following. I did this because I didn’t have a flowchart on the last lab report, and it cost me dearly in terms of getting a good grade. Since I have a flowchart, I have a more structured idea of how to go about completing my code. After completing my flowchart, I first tried to break the code into smaller parts in order to place together when I finished all of the different pieces. This was a smart and good step for me because I am starting with a logic to go by. Some of my problems included small technical problems such as spelling problems within the code. Another problem was when I was soldering the wires to make them longer. I did not solder the wires well enough and it caused the sensors to not work at all. Some debugging tools I used included using the cricket display. By using the cricket display, I was able to see how far the Create traveled as it is running its code. This was an efficient and productive way of debugging because it is exact and I don’t have to keep track of anything. Another way of debugging that I tried was by using the LEDs to tell me what stage the Create was in or what part of the code it is performing

Lessons Learned

Some things I learned included soldering. When soldering, I should be more careful and make sure that I use the wire holders to hold the wires for me when I solder. When I was soldering, I had others hold the wires for me and I later learned that it was a hazard to the person that was holding the wires and it could have caused harm to both me and my assistant. Another lesson was to mind what things I am typing when writing my code. Often at times, I would type in code and misspell words that would make the code not make sense. So by proofreading after writing code, I am able to track down little mistakes that would harm my progress.

Trong's Wall Following Picture Δ

Trong's Wall Following Code Δ

Trong's Wall Following Flowchart Δ

Back to Trong

Edit - History - Print - Recent Changes - Search
Page last modified on January 21, 2008, at 11:43 AM