Throughout the week, we had opportunities to start to test the AEV on a more consistent basis. This is because we now have three class periods to work on the AEV per week. With this being said, through the class periods in which we tested, we essentially wanted to try and get the timing aspect of the AEV under control. We wanted to simply get this accomplished because our design is still currently being created via the 3D printer, so we were just testing with our basic design. Despite that fact that there are going to be some differences in aerodynamics, air resistance, and weight between the two designs, we just needed to create a baseline for the timing aspect, so we used the basic design. Along with the timing aspect, we just took time to fine tune the code for the AEV just in case some things didn’t work as expected, and as expected the code did need to be tuned. Overall, this week was used as a trial and error week in order to get the overall objective completed.
For the first trial after uploading the situation code into the Arduino, the AEV moved a few inches away from the starting point with a very low speed. The same thing happened for the second trial. The problem was solved by increasing the power output of the motors. The AEV moved forward right away in the third trial with a suitable speed and it stopped a few inches away from the gate. The movement of the AEV was fairly balanced and stable, it did not lean to either side nor did it sway. However, after stopping near the gate, the AEV moved back and forth for 2 times which was not supposed to happen. After moving back and forth, the AEV moved forward to the right direction but it did not stop at the right spot. These performance issues were addressed and the sample codes provided have the fixes.
The two codes we used were focused around efficiency of the code itself. They involved testing whether a precise measurement of distance was more efficient than a measurement of time. Sample code one was focused around the distance while 2 was focused on time. Also the measurement of distance included some decelerations to handle better around the curves, and those were being tested as well for their power efficiency.
| Task | Teammate(s) | Start Date | End Date | Time Expected |
| Complete the Progress Report | All | 3/24/17 | 3/31/17 | 2 hours |
| Work on PDR | All | 3/24/17 | 3/27/17 | 6 hours |
| Complete the Code for Performance Test 2 | Shane | 3/24/17 | 3/27/17 | 2 hours |
| Complete the Test Performance 2 | All | 3/20/17 | 3/24/17 | 2 hours |
Team meeting notes
Date: 22 – March – 2017
Time: 5:00 pm (Face to Face)
Members Present: All
Topics Discussed: Test Performance 1 and Preliminary Design Report
_________________________________________________________
Objective: To ensure the group is on track with the due dates and to discuss which assignments should be prioritized. This meeting also discussed on how to complete the test performance in the given time.
_________________________________________________________
To do/Action Items:
-Complete the task that needs to be submitted while testing the AEV.
-Figure out what needs to be improved for the AEV code and basic design.
_________________________________________________________
Decisions: The team needs to distribute the work where two members were in charged with the AEV testing performance and the other two members worked on the documents that need to be submitted.
_________________________________________________________
Reflections: The team needs to distribute the work among the teammates evenly so that the task could be done in the given time with excellent quality. Distributing the tasks also helped the team to utilize the time in class.