Backward Summary:
Situation:
This group was tasked with creating an Advanced Energy Vehicle to transport people from one end of the city to the other end of the city on a monorail track. The first week was getting familiar with the code needed to get the Arduino to function properly. The Arduino is a programmable device, which is used to run the motors on the AEV. Next, the group put the AEV on a stationary track and performed some simple tasks for the AEV propellers, like getting them to spin forward for 20 seconds at 30% power and then switching them to spin in reverse. This was very important to get down, because, the wheels are free to move, so unless a device like the servo motor is used to directly stop the wheels, it will have to be calculated exactly how far the different motor settings will propel the vehicle.
All four group members came up with their own unique concept for the AEV creation. The designs each had different pros and cons. The differences were due to things such as weight, cost to build, balance, and style. The main objective of the team, was to build a vehicle that can be efficient on energy, but still produce enough power to make the travel time as short as possible. The central idea, was to obtain this by minimizing the parts used and streamlining the design.
The Arduino code was then tested to see how different power settings effected the distance traveled. This was done using a data analysis tool in MATLAB, which can read the data collected on the Arduino and plot the information on an easy to read graph. Code with different power percentages would be compiled onto the Arduino, and the AEV would be run on a monorail track. After each run, the information collected by the Arduino would be loaded onto a computer and opened in the analysis tool. This provided the team with a way to accurately measure the distance traveled and power used by the AEV. The Arduino tracks the revolutions of the wheel using reflectance sensors (figure 8). It was very helpful to get a visual of how much time it took to travel certain distances, at specific power levels. This portion of the lab was also very helpful in furthering the teams understanding of the Arduino code and how exactly it will affect the AEV performance.
Once all sketches had been collected, a concept screening and scoring was performed (figure 6 and 7) to determine which AEV sketches to continue with. This was done by ranking features of the AEV that the team thought were most important. Then each design was rated on a 1-5 scale, with a 5 being the best score. After analyzing the designs based on stability, maintenance, durability, and safety, group A chose Chris’s design and Sean’s design because they were determined to be more energy efficient due to better stability and more aerodynamics designs compared to the others. This will allow the team to focus more energy and time on only two AEVs, instead of everyone working on their own.
Results and Analysis:
After being introduced to the AEV project, Group A started to brainstorm and gather design ideas. Throughout the first few weeks of lab, the engineers had put in the efforts of tackling down the basics of the Arduino board and learning the language of coding. While this a crucial step of the AEV development, the team of engineers also wondered where the placement of the motors should be. What would be affected if the motor is placed at an angle instead of flat on the body? By resolving this, the engineers tested it on a practice track to see that the results affect the air flow when placed flat on the body. The angled placement creates a drag with the air when moving at a faster speed. When moving, the engineers want the vehicle to move as fast, safely, and efficiently as possible, that is where the flat placement of the motors have an impact. Then comes the factor of stopping the vehicle when the motor stops. From the PrgrmBasics code, the movement of the motors running through each code worked flawlessly, however, when putting it on the body of the vehicle, the engineers noticed that the movement of braking and reversing the motor will be the hardest task due to momentum and inertia created from the forward movement. They came up with a result of 3d printing a third wheel and using the servo to help stop the vehicle quickly. While doing so, this will create a more effective way to stop at a certain point when using the goToRelativePosition and goToAbsolutePosition functions. As the engineers become comfortable on how the movement of the vehicle will take effect, they can easily figure out how to calculate when to start stopping or adding more power to the motors when needed. This was done in the first three labs of the project. An example of the analysis tool used to access the data collected by the Arduino can be seen in Figure 5. In the last lab, the engineers were to create the concept screening and matrix to judge the group members design (figures 6 & 7). This part is also crucial because it determines whose design is the most effective and cheapest all in one chart. All of these can be assessed through the appendix showing each figure.
Takeaways:
Lab one helped the team understand how the code worked, and how it had to be written, to get the AEV to perform properly. The team noted that it would be a good idea to have the code written before lab time, maximizing testing time in the lab. Thee second lab introduced the reflectance sensors, this taught the team how the AEV’s movement would be tracked. Understanding how this worked, it was concluded that the distance had a possibility of being precisely controlled. The Data Analysis lab was extremely beneficial, providing the team with data that would hard to measure any other way. According to the concept screening result, both AEV that had be chosen as the best candidate had some similarity. The T shape was used in both AEV sketch, thus resulting in a better stability and durability of the vehicle. Both AEV also has two propellers that resulting in better power outcome. In conclusion, The Engineering Design Process is a useful tool to generate new ideas in every team member and comparing each other ideas by designing and sketch the concept of the AEV. The concept screening and concept scoring were used to decide which individual has the best sketch and will be used as the primary design throughout going forward.
Forward Summary:
Situation:
The group will now be transitioning from preliminary research to advanced research. This is different moving forward from the previous labs as the team will now be choosing their own research topics to guide their study in finding ways to make the AEV design more efficient. The group decided on the following topics to research in the AR&D phase of the project: Materials testing, Motor configuration/quantity and if time permits, battery testing. Material testing seems important to test first because of the effect the group believed it could have on AEV efficiency. Lighter materials will be tested on the track by using the sample AEV built from different provided materials to see if the different materials have any effect on the efficiency of the AEV, and if different materials should be utilized for the body. Motor Configuration/ quantity was also deemed important to determine how the motors can affect the efficiency of the AEV. The motors could be used to either push or pull; they also could be placed in different parts of the AEV to see how the efficiency is affected. The quantity of motors could also affect efficiency if the weight of adding a motor outweighs the thrust it provides. This will be tested by changing the number of motors and the orientation of the propellers on an AEV, running it on the track, and analyzing power consumption during the runs.
Following the AR&D phase the group will use the results collected during that phase to better understand what can improve the efficiency of the AEV. The team will now proceed into a phase of testing a final design and developing the code that the AEV will utilize to run.
Upcoming Goals:
Team A is still deciding what materials will be used for the base of the AEV. In R&D lab, team A will be testing several materials that would possibly have the best outcome, and there are several application tools being used to help the team make the decision during the process of the lab. Tools pertaining crucial information for the lab is MATLAB’s Data Analysis Tool. Redesigning the AEV will be a necessary step, since the group work is an iterative process; there will be always review, feedback, and new ideas to refine and better the AEV. Team A is also waiting for the approval of the Grant Proposal, and if the team will be granted for extra funding, the team will be using the funding to create a Servo mount, using the 3-D printer. The group planned to create the AEV with high stability, efficiency, and low cost. To meet the end goal, the group agreed to meet at least once every week and to meet with either the TA or the Professor frequently to get advice on improving the design. In addition, the group will be discussing how motor configuration/quantity will affect the movement of the AEV and see how placement will affect the distance when applying the code for it to run. From there the group will decide based off the experiment from the lab.
Upcoming Schedule:
AR&D Schedule
| Task | Start | Finish | Due Date | Est Time | Chris | Will | Sean | Hadi |
| Material Testing | 2/9/18 | 2/9/18 | 2/16/18 | 1 hr | 1 hr | 1 hr | 1 hr | 1 hr |
| Motor Testing | 2/16/18 | 2/16/18 | 2/16/18 | 1 hr | 1 hr | 1 hr | 1 hr | 1 hr |
| Analyze and implement research to designs | 2/16/18 | 3/9/18 | 3/9/18 | 4 hr | 1 hr | 1 hr | 1 hr | 1 hr |
Subtask:
Chris & Will: Research & Development
Sean: Human Resource
Hadi: Public Relation
Appendix A:
Meeting notes:
Meeting #1
Date: 27-Jan-2018
Time: 5:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Post Lab 1
Objectives:
The main focus of the meeting was to get a good understanding of what was required for the AEV project. The group wanted to just touch base with each other in person and get to know everyone for the project. As discussed during the meeting, the website will be set up and tasks will be given out to whomever who wants to complete a task.
To do/Action Items:
-Work on website design
-Find who will complete each section
Decisions:
-The group decided that, Will would create the skeleton of the website, Chris and Hadi will work on the Executive Summary, and Sean will work on the MCR summary.
Reflections:
-The group needed to get more familiar with how the website functions and is set up. Group A will continue with construction in between labs.
Meeting #2
Date: 03-Feb-2018
Time: 12:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Post Lab 2
Objectives:
To get an understanding of the Arduino Code, assemble the AEV prototype, and figure out what needs to be updated for the website.
To do/Action Items:
-Run through functions for Arduino Code
-Assemble prototype AEV
-Update Website
Decisions:
-Chris and Hadi will assemble AEV
-Sean will work with William on Arduino Code
-Whole team with collaborate on the website
Reflections:
-At first it was a little difficult to get the Arduino running since we first tried to download the software with a mac. After switching computers, it went a lot smoother. The AEV was assembled as much as the group could during class, but majority was done outside out class. Now the group must start brainstorming on what our teams unique AEV design will be.
Meeting #3
Date: 06-Feb-2018
Time: 3:30 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Post Lab 3&5
Objectives:
The focus of today is to get all the concept drawings finalized and formatted properly. In order to finish lab 5, the group needed to complete the concept screening. In order to know what exactly needs to go into the progress report, the group assigned tasks to each one of the team members. Also adding any additional information to the website.
To do/Action Items:
-Finish Sketches
-Perform Concept Screening
-Update website
-Assign tasks to finish Progress report
Decisions:
-Hadi will work on section 5 for the progress report, and create the template in Excel
-Chris will work on submitting all the documentation of our sketches and progress photos
-William will work on the Arduino Code part of the report
-Sean will complete section 2 for the progress report and cover note taking.
Reflections:
While confused on what to do for the progress report, the group had the drawings done and finalized. As a group we will keep better records of each step of the AEV construction process, which will cause it to be much easier in creating future reports.
Appendix B:
Arduino Codes:
PrgrmBasics
// Accelerate motor one from 15% power in 2.5 seconds.
celerate(1,0,15,2.5);
// Constant speed of 15% power for 1 sec.
goFor(1);
// Brake motor
brake(1);
//Accelerating motor two from start to 27% in 4 seconds
celerate(2,0,27,4);
// motor 2 at a constant speed of 27% for 2.7 seconds
goFor(2.7);
//decelerating from 27% to 15% in 1 sec.
celerate(2,27,15,1);
//brake motor 2
brake(2);
//reverse motor 2
reverse(2);
//accelerate all motors from start to 31% in 2 sec.
celerate(4,0,31,2);
//run all motors at 31% in 1 sec.
motorSpeed(4,35);
goFor(1);
// brake motor 2 but keep motor one at constant speed of 35%
brake(2);
motorSpeed(1,35);
goFor(3);
// brake all motors for 1 sec.
brake(4);
goFor(1);
// reverse motor 1
reverse(1);
// accelerate motor 1 from 0 to 19% over 2 sec.
celerate(1,0,19,2);
//run motor 2 at 35% while motor 1 at 19% for 2 sec.
motorSpeed(2,35);
motorSpeed(1,19);
goFor(2);
//run both motors constant speed 19% for 2 seconds.
motorSpeed(4,19);
goFor(2);
//Decelarate both motors to 0% in 3 seconds.
celerate(4,19,0,3);
//brake all motors.
brake(4);
ExternalSensorsOutside
//run all motors at constant speed 25% power for 2 sec
motorSpeed(4,25);
goFor(2);
//all motors constant speed of 20% power using goToAbsolutePosition 12 ft from starting point
MotorSpeed(4,20);
GoToAbsolutePosition(295);
//reverse all motors
reverse(4);
//all motors in reverse at constant power 30% for 1.5 sec
motorSpeed(4,30);
goFor(1.5);
//brake all motors
brake(4);
//accelerate all motors from start to 25% power for 3 secs
celerate(4,0,25,3);
//continue all motors at 25% power for 1 sec
motorSpeed(4,25);
goFor(1);
//all motors go for 20% power for 2 secs
motorSpeed(4,20);
goFor(2);
//reverse all motors
reverse(4);
//in reverse all motors at 25% power for 2 secs
motorSpeed(4,25);
goFor(2);
//brake all motors
brake(4);
Appendix C: Figures and Tables
This design was made to address two of the major concerns with the design of the AEV which includes the weight and its aerodynamics. This design is lightweight, as it uses minimal parts. It utilizes one motor instead of two in hopes that despite having less motors the lighter weight would compensate for less thrust. This design will also have all the weight concentrated in the center which will result in less tilting in the vehicle which would in turn make it more efficient. Due to the center of weight being concentrated in a thin plane there is little surface facing into the air as it moves which would make the design more efficient due to less drag slowing the AEV down.
Figure 1: Chris Wagner AEV prototype
The body is very light weight and cost efficient. It will cut down on the cost of production, because this design utilizes very few parts. However, with two motors each driving a large propeller, there will be plenty of power supplied to the vehicle. Finally, it is well balanced, with the motors place on opposite ends to maximize stability.
Figure 2: Sean Mclaughlin AEV prototype
The main idea of the whole concept is to use the materials at least as possible, to reduce the cost. Also, the weight of the AEV is in the mid-range weight, rather than lightweight, so it will result in much more stable and safe vehicle.
Figure 3: Hadi Saputra AEV prototype
The design came to mind for the reasons of material cost, weight, and balance. The effectiveness of this design can create a fast and balance travel from point to point created by the two motors driving the propellers at maximum power in the back. As everything is concentrated in the middle of the T-shape plane, it will create a balance fixture for the magnets to sit and not tip over.
Figure 4: William Nguyen AEV prototype
Figure 5: Data Analysis 30% Power
Figure 6: Concept Screening Matrix
Figure 7: Concept Scoring Matrix
Figure 8: Reflectance sensors on AEV