Progress Report 2

Week 2

Situation:

In Lab 01, Team H was introduced to the Arduino coding program.  Using the propellers supplied in the AEV kit, motors, Arduino, and AEV motor mount, we were able to program two propellers to start, stop, slow down, and speed up both independently and in unison.  Only one code was needed per team, however, all our group members programed their own code to ensure everyone on the team could use the Arduino program.  We did this so all members of the team could help with the code and keep up with all aspects of the project.

Results and Analysis:

Using the Arduino program in lab, our team learned how to begin programming the AEV.  We also learned how to setup the Arduino and plug all the cables into their correct places.  The goal of this lab was to successfully code and run a given set of instructions using the arduino coding program.  The group was successful in running the given code, and also managed to move onto the second part, where we were able to code the imperial march song from Star Wars.  The group noted that much resistance occurred at the start of the program.  At low power, the propellers did not start spinning at all. (Appendix A: Arduino code: line 1) This means that the code will need to be manipulated to accommodate for this resistance.  Other takeaways from this lab is that applying a break command to the motors will not instantaneously stop the AEV.  It will stop the motors from spinning, however if the AEV has momentum going in one direction, the vehicle will not stop right away after a break command. (Appendix A: Arduino code: line 3) Some potential sources of error in this lab was that it was difficult at points to tell if the motors were running properly with the code because of the resistance and also because many steps were happening rapidly.  Despite this, the group feels confident in their abilities with the Arduino program.  Team H can test the motors at higher speeds, where the propellers can move right away, overcoming the initial resistance; in order to make sure they are running properly. Overall, Team H feels that having the AEV made before the lab would have improved their results for the lab.

Takeaways:

1).  AEV – Must accommodate for resistance in propellers in AEV coding.

2).  AEV –  Brake function will not instantaneously brake AEV, just motors

3).  General –  Group works well when we are all on the same page and working towards a like goal

Week 3

Situation:

Looking ahead, Team H will look at how to set up the AEV.  This is important because we will be able to assemble the machine and be able to find an appropriate design for it.  The team will accomplish this by using the basic set-up provided on Carmen.  Then, if necessary they will adjust where they feel necessary to help with the design.  Team H will also be testing the reflectance sensors in order to make sure they function properly. The importance of this; is that the sensors will count marks from which the team can use to calculate the distance travelled on the track.

 

Weekly Goals:

            –Begin construction of AEV

-Begin brainstorming design tweaks outside of instructions for optimal performance

-Become familiar with the external sensor hardware components

-Become familiar with troubleshooting techniques

-Program function calls for using external sensor hardware components

 

Weekly Schedule:

Task Members Start Due Date Approx. Time
Lab 2 All 25-Jan 25-Jan  1 1/2 hours
Organize progress report, discuss lab, and expectations All 26-Jan 26-Jan 1 hour
progress report week 2 All 26-Jan 1-Feb 4 hours

 

Appendix A:

Arduino Code:

Senario 1

celerate(1,0,15,2.5);                // Accelerate motor 1, from 0% to 15% power, over 2.5 seconds

goFor(1);                                 // Runs the last command (motor 1 at 15% power) for 1 second

brake(1);                                  // Brakes motor 1

celerate(2,0,27,4);                   // Accelerate motor 2, from 0% to 27% power, over 4 seconds

goFor(2.7);                              // Runs the last command (motor 2 at 27% power) for 2.7 seconds

celerate(2,27,15,1);                 // Decelerate motor 2, from 27% to 15% power, over 1 second

brake(2);                                  // Brakes motor 2

reverse(2);                               // Reverses the polarity of motor 2

celerate(4,0,31,2);                   // Accelerate all motors, from 0% to 31% power, over 2 seconds

motorSpeed(4,35);                  // Sets all motors to 35% power

goFor(1);                                 // Runs last command for 1 sec ( all motors at 35%)

brake(2);                                  // Brakes motor 2

goFor(3);                                 // Runs motor 1 at 35% for 3 seconds while motor 2 is broke

brake(4);                                  // Brakes all motors

goFor(1);                                 // Runs the last command for 1 second

reverse(1)                                // Reverses the polarity of motor 1

celerate(1,0,19,2);                   // Accelerate motor 1, from 0% to 19% power, over 2 seconds

motorSpeed(2,35);                  // Sets motor 2 power to 35%

goFor(2);                                 // Runs the 2 commands above (motor 1 power at 19%, and motor

2 power at 35%) simultaneously, for 2 seconds

motorSpeed(4,19);                  // Runs all motors at a constant 19% power

goFor(2);                                 // Runs the last command (all motors at 19%) for 2seconds

celerate(4,19,0,3);                   // Decelerate all motors from 19% power to 0% power in 3 secs

brake(4);                                  // Brakes all motors

Meeting Notes:

Date: 1/19/2017

Time: 8:00 pm-9:00 pm

Members Present: Josh Anson, Nate Heister, Jesse Noble, & Bret Ricklic

Topics Discussed: Progress Report 2

Objective:

Today’s main focus was to divide up portions of the “Lab 2 Progress Report” to be completed and to also establish a pre-due date of Tuesday night. This notion was set in order give the team ample time to evaluate each other’s work and to ensure all requirements of the rubric are discussed in the report.

To Do/Action Items:

“Backwards Looking Summary” (Situation, Results, Analysis) – Nate

– “Forwards Looking Summary” (Situation, Weekly Goals, Weekly Schedule) -Jesse

– “Appendices” (Team Meeting Notes, Arduino Code) – Bret

– “Formatting and Submission”, “Report Questions”, and “Take-Aways (part of “Backwards Looking Summary”) – Josh

Decisions:

The group decided to hold weekly meetings at 8:00-9:00 pm at Thompson library. This is subject to change depending on workload for the week.

-The group decided to come prepared to Lab 3 by completing the reading assignment and quiz on time. This will help ensure that class work is constructive.

Reflections:

Group H feels we completed Lab 2 very efficiently and believe with the same preparation, communication, and teamwork, Lab 3, will have a similar outcome.