This past week, team F has been gathering information to improve the current AEV design. Two top priorities for the team at this moment are aerodynamics and weight distribution. The code for the AEV is currently being developed at a satisfactory pace, so focusing on the efficiency of the design has occupied much of the lab time. These two priorities have been specifically chosen due to their degree of effect on the AEV performance. It was discovered that, with the addition of the new propellers, changes needed to be made to adapt to the speed in favor of ease of travel around the track. Since giving the design report presentation last Friday, the team has been taking Chris’ questions and advice into account for further testing and modification of the system. Providing quantitative evidence to support the claims of improved speed due to the new propellers and “diamond shaped” design is one goal that the team is moving towards producing in the near future. Anticipating the extra weight of the R2D2 apparatus is the driving factor for weight distribution of the individual AEV model. Without the R2D2, the AEV is observed to be bottom heavy, leaning outwards when making turns on the track. Therefore, moving the weight closer to the center/side of the AEV that faces the inside of the track is a modification that the team has implemented on the design. The team has also begun to make decisions on 3-D designs and materials that could potentially improve the AEV’s track performance. After taking notes and discussing the progress of other groups seen during the presentation lab day, Team F is hoping to develop a model of the AEV on Solidworks to give another perspective of the model, and allow the team to get a better picture of new potential designs and modifications.
Posts
Week 12
In the final week of lab, Team F will attempt to successfully put their AEV to its final test. The team will be allowed two runs to showcase the vehicle on the classroom track and exemplify that it successfully completes the Mission Concept Review as stated in the lab documentation. They will be scored on the vehicle’s ability to begin at the starting block, come to a complete stop prior to the gate, remain stationary until the gate is lowered, continue on until coming to a gentle stop while attaching to the R2D2 unit, and making its way back to the starting position while stopping at the gate once more. Upon completion of this task, Team F will determine whether they require another run in an attempt to better improve their overall score for the assignment, being that the better of the two runs will be the score awarded to the team. Potential errors that could occur during the run that would result in loss of points include the vehicle not traveling far enough to trigger the gate or not traveling far enough to attach to the R2D2, crashing into the gate or the R2D2, and failing to return the R2D2 to the starting position after attachment. Not only does the vehicle have to meet the above stated requirements, it must also produce a low energy to mass ratio, being that one of the main objectives in this lab exercise was making an energy efficient vehicle. The team will be ready to test their final AEV upon entering into Week 12 as PT4 begins. They will have the entire lab week to perfect their design and program, though the majority of this semester-long project was completed in labs prior. It is imperative that the team completes the above stated tasks in a timely manner so that the AEV can be a successfully completed project and that the Mission Concept Review can be adequately addressed as stated.
Week 10
In Lab 10: Performance Test 3: Energy Optimization, Team F will complete a number of tasks so that they may determine which combinations of codes and physical designs will provide the most energy efficient option for the vehicle itself. The code must still complete the tasks as stated in the Mission Concept Review. Minor variations to both the software code and the vehicle design will be made throughout the lab setting so that multiple configurations may be analyzed. The team will first test the code that has been tweaked and varied in the previous lab week with the agreed upon vehicle design. The data from a run will then be analyzed and interpreted on a level involving energy. Upon completing these tasks, a different code will be tested based on the results from the first run. For example, if the previously tested code provides for an analysis that indicates the use of large amounts of energy, the team will work to reduce that energy usage in whatever ways possible, including reducing the weight of the AEV, using larger propellers, going slower around the track, etc. These testing and altering processes will be repeated until the team has settled on a code and design combination that provides for the most energy efficient AEV. It is imperative that the team complete these tasks as stated so that the mission concept review can be properly completed. It is stated in the MCR that the energy source is limited on the remote planet. Because of this, the team must focus on dwindling down the energy usage so that the most efficient AEV can be constructed.
Week 9
In Lab 09: Performance Test 2: Code, Team F will focus on the software component of the project. After having decided upon the team’s design, based off of Lab 08, the vehicle will then be utilized in order to test various coding methods. To do so, the team will develop criteria that they value in regards to the code performance. Such criteria include consistency, versatility, and efficiency. This will allow for a concept scoring matrix to be implemented and referred to in the decisions regarding changes in the team’s code. Should time permit, the team will test three separate code solutions, through a minimum of two programs will be analyzed in this lab period. Both codes must have the ability to complete the entire track layout, a criterion stated in the given mission concept review. Upon the analysis of each code, successful completion of the mission objectives will be evaluated through comparison of the previously performed concept scorings. It is important that the team effectively complete the aforementioned tasks so that they may begin to finalize the code that will serve as Team F’s program.
Week 8
During Lab 8: Performance Test 1 – Design, Team F will will now be responsible for delegating items to be completed and work together to complete a set of objectives. The team will develop two differing AEV designs to be tested in lab. The purpose of this task is to determine which AEV design is superior, in regards to energy usage and completion of the mission concept review. Because of this, the code will not be altered in any way so that the team may focus on the analysis of the design. In lab, the team will construct the first AEV according to the previously decided upon design. Upon doing so, this model will be tested and observations will be made in order to formulate and compose a scoring matrix, allowing the team to analyze the design on a quantitative level. After this is complete, the same processes will be carried out, though this time with the second AEV design. After completing the concept scoring for the second design, the results of each scoring will be compared and contrasted in order to determine the AEV that exhibited the highest performance. With this information, the team will begin to develop a model that represents the agreed upon AEV. It is important that the team complete the above mentioned tasks so that they may begin to develop a plan for the final AEV design and can start to test the improved AEV with varying codes in upcoming labs.
Week 12
Weekly Goals
- Finalize the code that will be used for testing
- Finalize the vehicle design that will be used for testing
- Test on the track as many times as possible, ensuring consistency in performance
- Perform a near perfect presentation and receive an excellent score for the run
Weekly Schedule
Task | Teammate(s) | Start Date | Due Date | Time Needed |
Test multiple times | All | 4/7/17 | 4/7/17 | unlimited |
Make necessary code changes | Derek | 4/7/17 | 4/7/17 | .25hrs |
Make necessary design changes | Olivia, Lauren, Sam | 4/7/17 | 4/7/17 | .25hrs |
Analyze Energy Data | All | 4/7/17 | 4/7/17 | .15hrs |
Test again, multiple times | All | 4/7/17 | 4/7/17 | unlimited |
Perform Final Test | All | 4/7/17 | 4/12/17 | .15 hrs |
Week 10
Weekly Goals
- Test initial code with pre-existing design
- Analyze data from run and determine areas of improvement
- Alter code in ways seen fit
- Alter design in ways seen fit
- Test again and analyze new data to be compared and contrasted to pre-existing data
- Repeat process until most efficient vehicle is constructed
- Determine which design and code combination will be utilized as the team’s final AEV
Weekly Schedule
Task | Teammate(s) | Start Date | Due Date | Time Needed |
Test pre-existing AEV | All | 3/31/17 | 3/31/17 | .10hrs |
Analyze performance | All | 3/31/17 | 3/31/17 | .10hrs |
Rewrite code | Derek | 3/31/17 | 3/31/17 | .25hrs |
Redesign AEV | Olivia, Lauren, Sam | 3/31/17 | 3/31/17 | .25hrs |
Test and analyze | All | 3/31/17 | 3/31/17 | .25hrs |
Compare and contrast | All | 3/31/17 | 3/31/17 | .10hrs |
Repeat if necessary | All | 3/31/17 | 3/31/17 | unlimited |
Begin next PR | All | 3/31/17 | 4/6/17 | unlimited |
Week 9
Weekly Goals
- Develop two working programs to be implemented in the code testing
- Evaluate both programs with a scoring matrix based on previously determined criteria
- Based on these matrices, determine which program is most efficient
- Decide upon a code to utilize in the remainder of the project
Weekly Schedule
Task | Teammate(s) | Start Date | Due Date | Time Needed |
Formulate scoring matrix | All | 3/21/17 | 3/23/17 | .25hrs |
Program #1 | Derek and Olivia | 3/23/17 | 3/23/17 | .25hrs |
Program #2 | Lauren and Sam | 3/23/17 | 3/23/17 | .25hrs |
Test Program #1 | All | 3/23/17 | 3/23/17 | .10hrs |
Evaluate using matrix | All | 3/23/17 | 3/23/17 | .10hrs |
Test Program #2 | All | 3/23/17 | 3/23/17 | .10hrs |
Evaluate using matrix | All | 3/23/17 | 3/23/17 | .10hrs |
Compare data and make decision | All | 3/23/17 | 3/23/17 | .25hrs |
Begin next PR | All | 3/24/17 | 3/30/17 | unlimited |
Week 8
Weekly Goals
- Prepare two potential AEV designs to be tested and evaluated
- Test these designs and determine which vehicle outperforms the other
- Conclude which AEV design will be utilized for the remainder of the project
- Agree upon what assignments will and won’t be completed over break
Weekly Schedule
Task | Teammate(s) | Start Date | Due Date | Time Needed |
Formulate scoring matrix | All | 3/6/17 | 3/6/17 | .25hrs |
Design sketches | All | 3/6/17 | 3/6/17 | .5hrs |
Assemble Design #1 | Lauren (time permitting) | 3/6/17 | 3/9/17 | .25hrs |
Test Design #1 | All | 3/9/17 | 3/9/17 | .10hrs |
Evaluate using matrix | All | 3/9/17 | 3/9/17 | .10hrs |
Assemble Design #2 | All | 3/9/17 | 3/9/17 | .25hrs |
Test Design #2 | All | 3/9/17 | 3/9/17 | .10hrs |
Evaluate using matrix | All | 3/9/17 | 3/9/17 | .10hrs |
Compare data and make decision | All | 3/9/17 | 3/9/17 | .25hrs |
Begin next PR and PDR | All | 3/10/17 | 3/23/17 | unlimited |
Video
Stay tuned for more videos as Team F continues to work on the AEV throughout the semester!