- Performance Test two is the next step after deciding on a design, the team now works to find the best possible code to run the AEV consistently and efficiently. Because of the inconsistencies faced with coasting, the team decided to look into power-breaking with a slow deceleration rather than coasting. The only difference between codes is the stopping method at the gate, and can be checked in the “Arduino Codes” tab.
Results:
_________________________________________________________________
- Power Breaking – Code A
- Figures 13 & 14 show the results from the four runs are not perfect copies of each other but are at least relatively consistent.
- Coasting – Code B
- Figure 15 shows the inconsistency related with coasting as the same track and code was used on all runs.
- Figure 16 shows that coasting was almost perfectly consistent when looking at the amount of power drawn over time.
Conclusion:
_________________________________________________________________
- Although coasting uses significantly less power than power-breaking the inconsistency related with coasting is far too great to safely complete the MCR. The team has decided to power-break and use more power in the short term for the sake of safety and consistency.