Group C – Teressa Pell, Madeline Shaffer, Joe Spinazze, Danny Tomaszewski Progress Report Lab 1
Instructor: Dr. Kecskemety, GTA: Isabel Fernandez 1/27/2017
Lab 1
Situation:
In lab 1, sketchbook was used to write a code that could spin the propellers of the AEV. The group set up the AEV software, using basic function calls. Some of these calls were celerate, motorSpeed, goFor, brake, and reverse. An AEV battery was assembled to the Arduino and connected the motors. The main art of the first lab was the development and the learning of the Sketchbook and the Arduino software. Two programs was written to make the AEV perform as is described in scenarios 1 and 2. The program was uploaded to the Arduino and run.
These processes were completed in order to teach the students the proper procedures for assembly of the AEV. The programming and the scenario problems were completed in order to become familiar with the programming and the language used. The proper procedure of uploading the code was realized, and the goal was to learn it for Lab 2. The procedure was completed with the full use of the team in assembly. Half of the group worked on the programming for Scenario 1, while the other half of the group worked on the programming for Scenario 2.
Results and Analysis:
Scenario 1 proved difficult to test due to time constraints and an incorrect download of files. The program was written, but not tested with the motors and propellers. Although Scenario 1 had its complications, Scenario 2 was completed and tested with the motors and propellers. The program ran effectively, going through each command and stopping at the end.
Focusing on the program commands used, all five commands were utilized. “Celerate” was used to accelerate the motors, “motorSpeed” was used to set the motor speed, “goFor” ran the motors for a set time, “brake” stopped the motors, but not the vehicle attached, and “reverse” reversed the polarity of the motors. All five commands were written into Scenario 1, but Scenario 2 did not require the use of the “reverse” command. By practicing these different commands, their importance was understood and will transfer to the full AEV on the track project later in the year.
The results when observing the resistance of the motors to rotate the propellers at slow speeds in scenario one were not able to be observed as scenario one was not able to be run due to the malfunctioning of technology. However, it is predicted that the motors would experience some resistance to rotate the propellers at low speeds. Another experimental limitation would be that the brake command does not immediately stop the AEV. It will take some time in order to completely stop the weight of the AEV as well as stop the propellers from moving. This will limit the success of the AEV because a potentially unpredictable distance will need to be factored into stopping the AEV as it approaches certain points. During the lab, both scenarios were compiled, but the program for Scenario 1 did not upload to the AEV. This prevented the program from being tested. One too many “sketchbook” files were downloaded from Carmen, which complicated the compile procedure. With help from the teaching assistants, the file was corrected but time ran out afterward. As for Scenario 2, the program correctly compiled and ran successfully. This scenario consisted of various set speeds throughout the entire program, with a brake at the end. The groups could have had more guidance on connecting the computer to the motors which includes how to save the files properly.
Takeaways:
- The code relevant to the AEV project has been practiced and understood.
- The mechanisms and delays from the motors and propellers are well understood.
- Uses for the new commands such as “goFor(1)” and “celerate(1,0,15,25)” and their effects on the AEV propellers and motors have been observed.
- Learning and understanding these commands will be crucial when coding the future AEV on the track and completing the tasks necessary.
Lab 2
Situation:
This week the group will be meeting to familiarize themselves with the external sensor hardware components. They will also become familiar with troubleshooting techniques. Finally, they will use program function calls for using external sensors with AEV control. By the end of lab 2a, the group will understand the use of the reflectance sensors and will be able to instal it onto the AEV. They will learn the usage and syntax surrounding the Arduino command of reflectanceSensorTest, goToRelativePosition, and goToAbsolutePosition. The lab will give two scenarios which utilize the newly learned commands to turn the AEV motors. After completion of these scenarios, the group will receive one of two commands from the instructional team. The team will either have to “run” around the inside or the outside of the track. In lab 2b, the team will be called up to the wind tunnel. The voltage of the wind tunnel will be set to 7.4V. 10% power will also be administered to the propeller in the wind tunnel. The force of the wind will be measured using the given scale and the process described in the lab manual. By analyzing the data from this experiment, the group will apply their knowledge to the design of the AEV. The efficiency of the propellers will help the group to determine how much power is necessary to reach the desirable speed during the experiment.
Weekly Goals:
- Test scenario 1 code from lab 1
- Test External Sensors in Lab
- Wind Tunnel Testing in Lab
- Find time where entire group can meet
Weekly Schedule:
| Task | Teammates | Start Date | Due Date | Time Needed |
| Test and Finish code | Teressa, Joe | 1/27/2017 | 1/27/2017 | 15 min |
| Wind Tunnel Testing | All | 1/27/2017 | 1/27/2017 | 1.5 hours |
| Test External Sensors | All | 1/27/2017 | 1/27/2017 | 1.5 hrs |
| Update Portfolio | Danny | 1/28/2017 | 2/3/2017 | 2 hrs |
| Team Meeting | All | 1/31/2017 | 2/2/2017 | 1 hr |
| Lab 2 Progress Report | All | 1/29/2017 | 2/3/2017 | 3 hrs |
Appendix A
Scenario 1 –
celerate(1,0,15,25); // 1. Accelerate motor one from start to 15% power in 2.5 seconds.
motorSpeed(1,15); // 2. Run motor one at a constant speed (15% power) for 1 second.
goFor(1); // 3. Brake motor one.
brake(1); // 4. Accelerate motor two from start to 27% power in 4 seconds.
celerate(2,0,27,4);
motorSpeed(2,27); // 5. Run motor two at a constant speed (27% power) for 2.7 seconds.
goFor(2.7);
celerate(2,15,0,1); // 6. Decelerate motor two to 15% power in 1 second.
brake(2); // 7. Brake motor two.
reverse(2); // 8. Reverse the direction of only motor 2.
celerate(4,0,31,2); // 9. Accelerate all motors from start to 31% power in 2 seconds.
motorSpeed(4,35); // 10. Run all motors at a constant speed of 35% power for 1 second.
goFor(1);
brake(2); // 11. Brake motor two but keep motor one running at a constant speed (35% power) for 3 seconds.
motorSpeed(1,35);
goFor(3);
brake(4); // 12. Brake all motors for 1 second.
goFor(1);
reverse(1); // 13. Reverse the direction of motor one.
celerate(1,0,19,2); // 14. Accelerate motor one from start to 19% power over 2 seconds.
motorSpeed(2,35); // 15. Run motor two at 35% power while simultaneously running motor one at 19% power for 2 seconds.
motorSpeed(1,19);
goFor(2);
motorSpeed(2,19); // 16. Run both motors at a constant speed (19% power) for 2 seconds.
goFor(2);
celerate(4,19,0,3); // 17. Decelerate both motors to 0% power in 3 seconds.
brake(4); // 18. Brake all motors.
Scenario 2-
reverse(4) // 1. Reverse all motors.
motorSpeed(4,25) // 2. Power all motors at 25% power for 0.5 second.
goFor(0.5)
brake(4) // 3. Brake all motors for 0.1 seconds.
goFor(0.1)
motorSpeed(4,25) // 4. Repeat steps 2 and 3 at total of 2 times
goFor(0.5)
brake(4)
goFor(0.1)
motorSpeed(4,25)
goFor(0.5)
brake(4)
goFor(0.1)
motorSpeed(4,15) // 5. Power all motors at 15% power for 0.3 second.
goFor(0.3)
brake(4) // 6. Brake all motors for 0.05 seconds.
goFor(0.05)
motorSpeed(4,40) // 7. Power all motors at 40% power for 0.3 second.
goFor(0.3)
motorSpeed(4,25) // 8. Power all motors at 25% power for 0.5 second.
goFor(0.5)
motorSpeed(4,15) // 9. Power all motors at 15% power for 0.3 second.
goFor(0.3)
brake(4) // 10. Brake all motors for 0.05 seconds.
goFor(0.05)
motorSpeed(4,40) // 11. Power all motors at 40% power for 0.3 second.
goFor(0.3)
motorSpeed(4,25) // 12. Power all motors at 25% power for 0.5 second.
goFor(0.5)
brake(4) // 13. Brake all motors for 0.5 seconds.
goFor(0.5)
motorSpeed(4,55) // 14. Power all motors at 55% power for 0.5 second.
goFor(.05)
brake(4) // 15. Brake all motors for 0.1 seconds.
goFor(0.1)
motorSpeed(4,55) // 16. Repeat steps 14 and 15 a total of 2 times
goFor(.05)
brake(4)
goFor(0.1)
motorSpeed(4,55)
goFor(.05)
brake(4)
goFor(0.1)
motorSpeed(4,65) // 17. Power all motors at 65% power for a total of 0.3 second.
goFor(0.3)
brake(4) // 18. Brake all motors for 0.05 seconds.
goFor(0.05)
motorSpeed(4,40) // 19. Power all motors at 40% power for 0.3 second.
goFor(0.3)
motorSpeed(4,20) // 20. Power all motors at 20% power for 0.5 second.
goFor(0.5)
motorSpeed(4,15) // 21. Power all motors at 15% power for 0.3 second.
goFor(0.3)
brake(4) // 22. Brake all motors for 0.05 seconds.
goFor(0.05)
motorSpeed(4,40) // 23. Power all motors at 40% power for 0.3 second.
goFor(0.3)
motorSpeed(4,25) // 24. Power all motors at 25% power for 0.5 second.
goFor(0.5)
brake(4) // 25. Brake all motors.
Appendix B
Date: 01 – Jan – 2017
Time: 4:00 pm (Face-to-Face)
Members Present: Teressa Pell, Madeline Shaffer, Joe Spinazze
Topics Discussed: Lab 1 Progress Report
Objective:
Today’s main focus was on meeting to complete the progress report for lab 1 and discuss our plans for lab 2.
Tasks Completed:
- Format of progress report determined
- Jobs assigned for each section
- Majority of progress report completed
- Lab 2 previewed and planned for
Tasks To Do:
- Update portfolio with new information
- Meet with Danny to complete progress report
- Determine what needs to be completed before lab 2 tomorrow
Timeline:
- 1/20/17 – Lab 1 Completed
- 1/26/17 (4:00 pm) – Progress Report Worked on and lab 2 discussed
- 1/26/17 (8:00 pm) – Meeting planned to finish Progress Report
Decisions:
- Teressa will complete appendix B and takeaways
- Joe will complete situations
- Maddie will insert the code, do the weekly schedule, and weekly goals
- Danny will update the portfolio and complete the results & analysis
Reflections:
- Determine a time the whole group can meet
- Split up the work and do a little bit each day of the week instead of completing the whole assignment as once
Date: 01 – Jan – 2017
Time: 8:00 pm (Face-to-Face)
Members Present: Teressa Pell, Madeline Shaffer, Danny Tomaszewski
Topics Discussed: Lab 1 Progress Report
Objective:
Today’s main focus was on meeting to review, finish up, and turn in the progress report for lab 1.
Tasks Completed:
- Danny completed his assigned part
- Progress report was reviewed and edited
- Progress Report was turned in
Tasks To Do:
- Update portfolio with new information
Timeline:
- 1/20/17 – Lab 1 Completed
- 1/26/17 (4:00 pm) – Progress Report Worked on and lab 2 discussed
- 1/26/17 (8:00 pm) – Meeting to finish Progress Report
- 1/27/17 – Start Lab 2
Decisions:
- Meet tomorrow before lab to complete the pre-lab assignment of building the AEV
- Finish the progress report by the end of the night
- Teressa will turn in the progress report when the team lets her know it’s done
Reflections:
- Stay focused during the time the team spends together in order to get the assignment done in an efficient time