Backwards Looking Summary
In the weeks leading up to this week, much was done in the lab to prepare the group for the project ahead. The first lab familiarized the group members with the motors to be used on the AEV, the arduino controller for the motors, and the code used to run the motors. This was an important first step because understanding how to effectively and efficiently operate the AEV will be very important to the success of the group moving forward. The group first had to download the Arduino software onto the computers. With this completed, certain files specific to the AEV project where also downloaded. After familiarizing ourselves with the Arduino language, the group had to write a code to complete a given scenario consisting of functions like accelerating and braking. This code was then uploaded to the Arduino Nano board. The board was connected to two motors, which were mounted to a stand. The code was then ran, and the motors were observed.
In the second week of lab, the group was familiarized with the wheel sensors that track the position of the AEV. The sensors were important to understand because they will help determine how accurately our AEV performs on the track. The group was given another scenario similar to that of week one, and wrote a code to complete the scenario. This code was then uploaded to the Arduino that had been mounted on the sample AEV design that the group had constructed, which included the wheel sensors. The code was then ran, and the resulting functions of the AEV where observed.
The third week of lab consisted of brainstorming AEV concept designs. This was a crucial point, as a good design for the AEV will help it perform as best as possible in the end. The group first learned about creative design thinking and then each individual designed their own AEV concept on orthographic paper. Once each member had a sketch, the group came together and designed a concept AEV as a team.
In the fourth week of lab, the group was familiarized with the design analysis tool in MATLAB. This tool was important to understand how to use, as it will be very useful in the future when studying the results of our research and AEV’s performance tests. The team wrote an Arduino code based off of a given scenario and uploaded the code to the AEV. The AEV was then ran on a test track using the code. The Arduino tracked the performance of the AEV during its run, and the results of the test run were then uploaded from the Arduino to the data analysis tool and analyzed.
In lab one, the propellers turned without too much trouble. However, when the motor was programmed to run at low speeds, such as 5-10% power, the propellers faced a fair bit of resistance and did not turn. The commands used in the code limit the AEV to only accelerating, decelerating, reversing, and completely stopping the motors. They did not allow for the AEV to travel a certain distance before executing the next line of code. This means that the group would have to determine exactly how far the AEV goes using certain strings of code if the code is to be of any use in further testing on an actual track. The group did run into some errors when initially setting up the Arduino program. The COM was initially wrong, as well as the selected board in the program, however, all was worked out using the troubleshooting guide for the lab.
In lab two, the commands used in the lab can severely limit the success of the AEV for the given scenario. First off, the AEV is supposed to be moving in a direction at a constant speed, and instantly reverse the fans. Not only does this cause a bit of work for the fans, but the AEV will use a large amount of power to fully reverse the direction, due to costing an equal amount of power to stop the AEV, and then more power to make it move in the opposite direction. As for the brake function, this merely stops the fans, not the AEV. Therefore, if the brake function is applied, the AEV will continue to coast and will require friction to completely stop. When initially programming the code for this lab, the group did not fully understand the difference between the commands for absolute and relative distances, but through trial and error, the group was able to write the proper code and had a better understand of coding as a result.
In lab three, each team member designed a different concept drawing for the AEV. The following were the concepts:
Design 1
Design 1 is a simple one. The motors should be able to provide enough power to move the vehicle. The minimal materials not only is cost effective, but it also makes the vehicle lighter and easier to move.
Design 2
This vertical design of Design 2 keeps the weight condensed, close to the wheels. This design uses minimal metal materials which will cut down on the weight as well, with the motors facing in opposite directions we should be able to have enough push/pull from the two of them to move our AEV.
Design 3
Design 3 is meant to be small, light, and compact. The arms with the motors are angled up in order to reduce the width of the vehicle as well as drag and potential torque.
Design 4
Design 4 was one based more on style than substance. The design, heavily based on the Star Wars ship Slave I follows a vertical Arduino setup similar to one model seen earlier on this page. Its vertical nature is to set the weight at the base and allow the propellers free range and less mid weight as they are in the middle of the ship without much weight beside themselves.
In lab four, we tested our AEV with a specific code, and used another program to graph the AEVs power vs distance and its power vs time as graphs. Below are said graphs.
Figure 1
Figure 2
Figure 1 (power over distance) explains the correlation of how much power is used as the AEV moves a certain distance. As it is seen, after the first short distance, the AEV lowers in power and this lower power is kept relatively consistent for the rest of the distance travelled. At the very end, we can see how the power completely drops off, but the distance continues for just a short while as the wheel continues to spin without any power. This would be seen as the coasting aspect of the program.
Figure 2 (power over time) shows the speed at which the fans spin as the code is progressed through. Initially, the speed is very high, and the power usage is very high, due to the percent of power usage being around 35%. This goes down to 30 (and stays 30 for much of the time) and eventually drops down to 0 when the motors are braked. There is still a little time however between the brakes occurring and the power turning off, simply due to the rest of the code being processed and ran.
Takeaways from our AEV as a team we have taken away many things from the AEV and in general. One of our biggest takeaways was the fact that we might be able to use our data from the power lab to see if it is more energy efficient and cheaper to coast or to power break and have the AEV travel faster? One of takeaways as a general project would have been time management and planning. As a team when we set out times we were going to meet and planned what we were going to do at those meetings on a more frequent basis led to better understand from the team.
Forwards Looking Plan
Now that the Preliminary Research and Development has all been completed, the group is now looking towards the Advanced Research Development part of the project along with the Grant proposal and Committee Meeting.
The purpose of this Advanced Research and Development is to give the group a deeper understanding of the AEV project as a whole. Each group is asked to choose two of the given advanced research topics. The group has decided to complete testing on the topics of Battery Testing and Track Variance. For battery testing the group is going to try and see whether an immediate input of the desired power or a constant acceleration to reach the power is more energy efficient. As for the track variance, the goal of that testing is going to be seeing if there is a difference between the four different tracks that the AEVs will be running on. If there is a difference the group will try to determine if it is of significance. After the AR&D is finished, the findings will be presented to the class.
The Grant Proposal is an opportunity for the group to present a design that they have created that will help with the project. If the design is voted as one of the best, extra funding will be given to the team. As of now, the goal is to come up with a design. The team is thinking along the lines of a front piece to help with aerodynamics.
The last major point that the group is preparing for is the first committee meeting. The group will split up and present to the rest of the company a summary of what they have done so far. The group will split up based on their assigned team roles. The goal is to have the website completed in time for the meeting and to have a good understanding of what the team has done and found so far.
The schedule for the upcoming weeks is spread out between the different tasks the group needs to complete. First and foremost, the group needs to complete the end of the Screening and Scoring Lab. The group still needs to complete the charts that are required. The group will meet within a couple days to complete this. Lab 05 and 07 will be designated for Advanced Research and Development. The group may have to schedule more time to get together to go over the findings and discuss what will be presented. Lab 06 is the scheduled Grant Proposal and Committee Meeting. The team will have to meet soon and prepare. After the Screening and Scoring lba is finished this will be the main concern as it is only one week away. Whenever the group meets for this they will work on the website and make sure they have a design and a presentation for that design. After the Grant Proposal and Committee Meeting have taken place, the group will shift all focus to the Advanced Research and Development and the presentation that will have to be made for it.
Appendix
Team Meetings
1/18/18
Attendance: All member Present
Topics of discussion: Discussed what we needed to do in SolidWorks for our project, very minimal substantial conversations
1/23/18
Attendance: All members present
Topics of discussion: Started our preliminary research, wen through the steps of the labs, didn’t take much out of the labs but maybe gave us some ideas on how to build/difficulty of building.
1/25/18
Attendance: All members Present
Topics of discussion: Worked on non related orthographic drawings, looked at one of Coles complex pieces from SolidWorks to see the potential complexity of our object.
1/30/18
Attendance: All members present
Topics of discussion: we messed around with all types of different codes, starting basic to working to a more complex code where motors were on and off after a certain time as well as working one motor only and both motors working together in 2 directions. We also completed the in class lab activity.
2/1/18
Attendance: All members present
Topics of Discussion: We briefly went over what was needed to be done for the weekend/next week at the end of class today.
2/5/18
Attendance: All members Present
Topics of Discussion: Worked on completing Progress Report 1
Discussed what we wanted our final design to be after we did the screening and scoring.
Also updated our website for website update 2.
Code Used:
For Lab One:
celerate(1,0,15,2.5);
goFor(1);
brake(1);
celerate(2,0,27,4);
goFor(2.7);
celerate(2,27,15,1);
brake(2);
reverse(2);
celerate(4,0,31,2);
brake(2);
goFor(3);
brake(4);
reverse(1);
celerate(1,0,19,2);
motorSpeed(2,35,);
goFor(2);
motorSpeed(4,19);
goFor(2);
celerate(4,19,0,3);
brake(4);
For Lab Two:
motorSpeed(4,25);
goFor(2);
goToAbsolutePosition(295);
reverse(4);
motorSpeed(4,30);
goFor(1.5);
brake(4);
For Lab Four:
celerate(4,0,25,3);
goFor(1);
motorSpeed(4,20);
goFor(2);
reverse(4);
motorSpeed(4,25);
goFor(2);
brake(4);