The group used the basic AEV design in order to test different speeds and try to make the AEV stop at the gate. The speeds that were tested were not optimal, as the AEV would not stop at the gate. One thing that could have been added would’ve be a reverse command to slow the AEV down as it neared the gate instead of letting it run for the full duration, then glide until it came to a stop.
For the first activity, the code was successfully uploaded and the AEV traveled from the starting point to the first stop in the proper direction. During the first trial, the AEV traveled with a power setting of 20% and the AEV moved very slowly on the rail. The low power setting made the AEV stop partway on the rail as the low power motor could not overcome the friction, thus the AEV did not move forward. For the second trial, the power setting was increased to 22.5% and the AEV moved at above optimal speed. Due to error in downloading, the data from the automatic control system could not be obtained for all trials. The group was able to get one trial into the computer at the very end of the lab. Therefore, the data could not be compared to the other trials. The graph showed that the arduino needed extra phases to be able to stop at the gate as the team wanted it to. The code will need to have a minimum of three phases for each stop that the arduino makes. Because of this and only a singular line of code that moved the AEV, as shown below, the team showed the calculations for phase 1 and phase 2 of the AEV.
| Task | Teammate(s) | Start Date | End Date | Time Expected |
| Progress Report 5 | All | 2/17/2017 | 2/24/2017 | 3 hours |
| Choose optimal AEV design | All | 2/17/2017 | 2/17/2017 | 1 hour |
| Update Portfolio | All | 2/17/2017 | 2/24/2017 | 4 hours each |
Team Meeting Notes
Date: 15 – Feb – 2017
Time: 5:00 pm (Face to Face)
Members Present: All
Topics Discussed:
-Lab 05
-What to do for lab report data that was not collected
_________________________________________________________
Objective: Determine what to do for the data that was not able to be collected, and discuss what will be done in Lab 5
_________________________________________________________
To do/Action Items:
-Create a To do list
-Discuss whether to attempt calculations with no power versus time data or not.
_________________________________________________________
Decisions:
– The calculations would not be possible without the graph as no direct amount of power would be able to be seen over the duration of the code. As such the group will quickly gather the data at the beginning of Lab 5 and include the chart as well as calculations in the Lab 6 progress report.
_________________________________________________________
Reflections:
– The team needs to come into lab with a better understanding of how to do everything that is required for each day so that no further mistakes are made that would compromise the ability to complete the progress report for that week.