Star Wars Darth Vader

Friday, December 2, 2016

Boe-Bot - 12/2/16

This is going to be one of the final days work can be done on the boe-bot. After math ended I stayed after for a little bit and went to the lab where I went to begin to begin working on the boe-bot, unfortunately neither Carlos or Joel could make it today so I was working alone. I kept in touch with both of my group members to keep tabs on the presentation status. But anyways, I broke out the boe-bot and pulled up the code and went to work. First I thought that it may not be the code at all and maybe something different. Maybe the QTIs were not wired correctly and so I labeled them all and made sure that they were correctly plugged in how the instructions called for.


After I did that I reinstalled my code and it still gave the exact same results as it did before. So I started to think that it may be the servos. So I brought the instruction book out and looked up how to correctly set the servos. I found out how to and I executed the instructions step by step. I learned while I was setting them that they were not correctly set so I was really excited when I went to test again because I thought that was the problem. It preformed better but it couldn't correctly follow the line. I thought immediately that the problem was my code.


So I changed it back to the basics without my alterations. It started to do some very weird things. Like the first time Carlos, Joel and I got it to move it was just spazzing. It was getting scary because soon I had to leave to catch a bus. But I was determined so I went back to work. I completely altered the sensor readings. The result was good. But the Bot wouldn't go straight. So I switched the Servo powers for all of the sensor readings and FINALLY. It followed a line. And it performed amazing. I tested it a few times and then packed up because I had to leave. Here are the two tests. The 90 degree turn, at the end the sensor got stuck on a bundle of tape that's why I had to grab it quickly. I'm very proud of my progress today. I was sad that Carlos or Joel could not attend. But I sent them these very videos and told them of my progress.


Thursday, December 1, 2016

Boe-Bot - 12/1/16

In the beginning of this lab we got back to work on the QTI code. The best part of the day was that I was really starting to understand how this code worked. While I was messing around with it I told Carlos and Joel that because of how close the exam is that they should get started on gathering the information of the project and constructing the presentation while I work on getting the line following robot into working order. Again the group was very busy today and no videos were shared. But my new understanding of the code allowed me to get just a little bit closer to getting it right. Carlos and Joel went and started working on the presentation while I worked on the code. That was our roles for today. I was having problems with the Boe-bot not going the right direction. I even got as far as having it follow a line but not being able to take a right curve or turn. This was my code before I threw in the towel for the day. I was not able to get the code right. Which scares me because according to our WBS and Gantt we were supposed to be finalizing the testing and beginning the presentation. But I'm sure everything will work out.


Tuesday, November 29, 2016

Boe-Bot - 11/29/16

Today there was a lot more frustration then picture taking. So there wont be much to show for today. The whole day consisted of finishing the coding of the QTI sensors... Which we didn't finish. We followed the instructions on writing the code but it just didn't seem to want to work. Joel, Carlos and I altered the code dozens of times, changing the amount of power going into the servos. But nothing would give positive results. We ended up having to call it a day. Unfortunately the end date is coming quickly and we are not having that much to show for it. Here is a picture of how the code was looking.


Monday, November 28, 2016

Boe-Bot - 11/28/16

Today is not an official class day but after a very long break we happened to put ourselves behind schedule which worried Carlos and I. Joel, However, was not able to make it to the meeting. The main objective of the day was getting the Boe-bot to make any movement at all. So we plugged it into the computer and downloaded a code script that Carlos typed up onto the Boe-bot. This is a picture of us downloading the code.



Fortunately we were able to get the boe-bot to move, unfortunately this is what it did...


With some minor adjustments to the code we were able to make it go into circles. The original problem was the amount of power Carlos gave to the servos in the PULSOUT.


This is the most progress that Carlos and I got on the coding of our Boe-Bot today. But before we left I wanted to finish wiring the QTI sensors. When I finished that we packed up and ended the day.







Tuesday, November 22, 2016

Boe-Bot - 11/22/16

When we arrived to class Carlos explained to us that he read a lot on how to program the robot. This was great news because I really had no clue if I was going to be able to Find out how to program. But as we were in class Carlos was explaining everything in detail and it started making more and more sense. Joel and I watched as he showed how it was done. The program that is used for coding looks like this.


The goal of the day was to complete wiring and assembling the Boe-Bot. We also started to install the Qti sensors (Line following sensors). It was a relatively easy install. However, I'm curious to see how the coding is going to work.

Thursday, November 17, 2016

Boe-Bot - 11/17/16

When Carlos, Joel, and I arrived to Lab today we got cracking on the project. After we finalized the Problem Statement and confirmed it with Mrs. Vestal we received our Boe-Bot Kit. My first thought about the kit was that it was very confusing. Before we opened the kit we established our roles. Carlos seemed more into programming the actual bot, Joel was going to work on the design of the Boe-Bot, while I work on assembling the bot. The focus today was the assembly of the bot. We were also faced with the task of wiring the servos of the bot as well. The body was assembled and most of the wiring was finished. Although no one had a clue how to program or work the bot, it was coming together. At this point in time we were ahead of time according to our WBS, and Gantt chart. It is going to be very interesting to discover how this contraption is going to work. Today we also decided that we will be using a line follower kit on our Boe-Bot. The line follower is the best choice due to the concept of our problem statement.

Tuesday, November 15, 2016

Boe-Bot - 11/15/16

Day 4

Today went much differently than expected. We arrived into class and we were faced with the task to finish our Problem Statement. We thought it was going to be much easier with the input that we received from Mrs. Vestal. So we went to work. First we made slight adjustments to the body of the problem statement. Just minor working errors and different kinds of sentence structure errors. Then we wrote our Vision, because we were missing that after finishing our first draft. We thought it was very nice but were very much proved wrong by Mrs. Vestal. We made more errors then we did before! After trial and error we finally developed a problem statement that was finally worthy. Oh look at the time. It was the end of class by the time we finished the problem statement. But that is okay! we are still ahead of schedule! Ill post a picture of the final Problem Statement soon. But that was Day 4 of the Boe-Bot project!