Lab Performance Test 3

Lab Summary

This week the lab group used their time to test the AEV getting to the first gate, while only making minimal changes to the code. They tested the difference between coasting and braking. The major decision this week was between coasting and braking/reversing. After various tests, observing the accuracy of each and analyzing the EEPROM data the group came to a decision. The group decided to use a minimal amount of braking and reversed power. As the code was constructed the natural friction of the track was used along with a few marks of reverse, to be used as a brake. Using the natural friction of the track saves power consumption, and utilizes a resource that is already present. On a planet where power is a luxury, as outlined in the Mission Concept Review, saving any amount of energy is paramount, and choosing to incorporate the resource of friction at our disposal was an easy decision. The brake used along with the friction makes the code more precise, the main decision to no go with just coasting. The small amount of reversed marks will use more energy, but the completing the Mission Concept Review is the group’s first priority.

Even though one single long coast was the most efficient, the group was concerned with the possible lack of consistency this would yield. Initial tests of just coasting confirmed those assumptions. The group started to change the code significantly after deciding to use the brake. Instead of constantly tinkering with all the numbers of the marks, power, brake time, reverse marks, and reverse power, the group decided to set all things constant except for the marks of the initial forward burst. This would make the code simpler to fix and analyze results of. This also provided a reliable base for the AEV to operate. Once the group stated testing like this the results were easier for the group to analyze in the short amount of times they had between runs. Additionally, this helped the group understand how much a single change in the code can affect the AEV. Getting to the first gate was a major problem until the group decided to be more efficient with their changing of the code. The group is now successfully through the first gate. Progress on the rest of the code needs to be written rather hastily.

Takeaways

From the past couple labs, the group was able to figure out that a brake stop was more consistent in stopping between the gate sensors; the group will be using the brake code for the rest of the semester. Also, after several trials using the brake code – which includes a very powerful stop using a lot of batter power – the group realized that the battery loses power very quickly, meaning that the stop won’t be as powerful in further trials before recharging or replacing. This will be considered in the future code as the battery will have less power to stop quickly when coming back to the gate. Also, the last lab consisted of a redesign with just the magnet and tying back the wires when realizing the magnet was not completely centered to the R2D2.

Schedule

Task Team Member Start Date Due Date Time
Upload progress report Emily 4-5-17 4-9-17 30 min
Lab 10 progress report compile and check, appendix Megan 4-5-17 4-9-17 2 hour
Lab 10 progress report: Situation Emily 4-5-17 4-9-17 1 hour
Lab 10 progress report: Results and Analysis Patrick 4-5-17 4-9-17 1 hour
Lab 10 progress report: Takeaways Justin 4-5-17 4-9-17 1 hour
Lab 10 progress report: Looking forward Justin 4-5-17 4-9-17 1 hour
Oral Presentation: draft PowerPoint Megan 4-5-17 4-6-17 1 hour

Meeting Notes

Date: 28 – March – 2017

Time: Post-Class

Members Present: All

Objective:

Discuss different options in coding and make sure everyone understands what is going on and due dates.

To Do:

  • Discuss different ways to stop at first gate
  • Assigns roles for progress report
  • Go over the rest of the assignments
  • Talk about AEV goals
  • Talk about how the mission wants to be completed

Decisions:

  • Decided that braking should be used
  • Decided that the first gate should be the most consistent part of the code
  • Decided
    • Megan would start PowerPoint and review progress report
    • Patrick would begin final design review
    • Justin would work on getting the magnet on the AEV
    • Emily would organize code and keep up on project portfolio
  • Decided that the AEV would coast into R2-D2
  • Decided that completing the mission successfully should be our priority

Reflections:

  • The lab group feels overwhelmed thinking of all the assignments due soon, but know if they stay on track everything will be completed. The lab group feels as if once the first gate it coded it will get much easier.