Lab 09-Performance Test 2: Code
During this week in lab the team was tasked with developing two Arduino codes that would complete the full track as stated in the MCR. The to codes were used by the team to check which would perform more consistently and minimize the amount the energy used. The team spent countless amount of hours tweaking the two codes, but in the end decided that the code that worked best for them. One code the team composed of was short, but used more energy than the other. The other code the team wrote was longer, but saved energy as it has in more waits and stops. The two codes can be found below :
Code 1
Code 2
Weekly Schedule
Team Meeting Notes Week 11
Date: 4/3/2017
Time: 5:00 pm
Members Present: Cat, Emily, Lovell
Topics Discussed: Progress Report Week 11, Portfolio, Codes, Design, Performance Test 3 & 4, CDR
Objective:
The objective of today’s meeting is to discuss that needs to be done this week for Performance Test 3 to prepare for Performance Test 4 and the Progress Report 11. Also the group needs to discuss starting the CDR as well as updating the portfolio
To do/Action Items:
-Discuss and break up parts to Progress Report 11
-Update Portfolio
-Discuss what needs to be done with codes and design this week
-Discuss requirements of Performance Test 3 & 4
-make CDR presentation
-Start thinking of CDR
Decisions:
-The Progress Report will be split evenly and done before class thursday
-The portfolio will be updated before class Friday
-The code with the more efficient data will be used to continue around the track
-CDR presentation made with minimal errors left to further fix
-The CDR was started and parts were assigned
Reflections:
This meeting was a good start to looking ahead to rounding out the rest of this project. It is becoming a stressful time with not having the code always work when going to the gate and not yet making it to R2D2 so those are the immediate goals, then the team will be able to meet again to move forward more with the reports.