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

Lab4RichardsWimpModeDebugging

Debugging

Debugging is an important part of trying to get your wimp mode to work because there are a lot of loops involved in it, making it very tedious. To debug my code I made good use of the LEDs and also the cricket display. I used the LEDs by turning specific ones on depending on what my robot was doing. For example, when the right bumper was hit, or when the Cr8 was rotating clockwise, the advanced LED would be green. After uploading my code, I would run the program and see if the LEDs lit up how I intended them to. Most of the times that my program didn’t work was because it got stuck in a certain loop; so I had to fix that up in my main.c. With how I used the LEDs, it was easy to find where I messed up in my code. I used the cricket display to debug the distance in my program. When running my program, I would check if the Cr8 stopped after 600mm, and most of the time that was fairly accurate, so I didn’t have to worry much about that. Debugging speeds up your process a lot because when something wrong happens, you know what to fix in your code from what the robot did or didn’t do.

Edit - History - Print - Recent Changes - Search
Page last modified on December 19, 2007, at 08:31 AM