NXT Robot FinalNicholas Sergio Noah

                                                                                                     In Action Final

        Our process first starts with three spins. One going clockwise at an average pace moving off of one wheel, the next going counter clockwise at an average pace off of two wheels, then the third goes at an accelerated pace going counter clockwise off of two wheels. Our robot then travels for a few seconds then starts to create 4 squares of equal length. Once the robot had completed that task the robot then starts to create a figure eight. After that our robot then starts to create a square and once it completed that square it would then make a square eight inches larger in its perimeter for the next square and so on. Once the robot was done with all of those task, it came to a stop in which it would play our choice of music (which was the jeopardy theme song). From then on out the robot had to complete its last task which was to have a working bump sensor. Once the song was over the robot started to roam around looking for something to hit and eventually it had ran into our teach Mr. Schrader’s shoe in which it hit the shoe then went in reverse, turned around and eventually came to a stop ending our program.

                                                                                                 What Went Wrong

        During our trial of creating a program, not too many things had gone wrong. In fact it seems as if there was only three or so problems leading up to and during the final. Our main problem was keeping the both straight. Originally in our programing we had placed both of the outputs to be working at a capacity of 75%. Once we tested it out it seemed as if the bot consistently curved to the right. In routines, like our shapes, we had fixed it to be the straightest it could be and it wouldn’t deviate to a noticeable amount; however when it was on the path to go straight for long times, we just had to let it do its thing. Another problem we had seen was when we programmed our bot to play our jeopardy song one of the notes would sound like a horrendous screech. What we did to fix that was we adjusted the frequency. We had no luck with that, so then we changed the volume level and it seemed to go away and produce a quality tone. Our final and last problem was just getting together on a schedule to meet up and work on the bot all at one out of class, so what we did was split sections of coding and the website between the three of us for equal work.

 

                                                                                                 What Went Right

 

        I’d say most of everything had gone right. The things that had gone wrong were so minimal compared to what was expected. We worked well as a group, we excelled at creating a good and properly working routine that met all the requirements for the final, and most of all we had fun while doing so making the class and project all that much more enjoyable.

                                                               Process of making the program

       Lots of the program was trial and error. Once we had finished the task. It seemed as if it wouldn’t keep straight so we would alter the numbers to produce the straightest line we could.

 

Our lego robot in action