Progress Report 1

Andrew Reade

Jean-Pierre DeDeaux

Caden Pfendler

Aaron Foster

Progress Report 1

 

Backward Looking Summary

 

Situation

 

Something we recently completed is successfully testing our AEV on the track. We did this to find out whether we should continue forward with the project or go back and fix malfunctions. We were able to complete this testing with no errors and everything went smoothly. We were able to complete this by all contributing into the creation of this AEV. From the actual building of the AEV down to the coding that allows the AEV to run.

 

Results and Analysis

 

We were able to successfully test our AEV on the track, however the analysis tool in MATLAB did not work after we run our trials on the track. We went back and ran more trials in order to try and solve the problem, but we found no solution within the lab time. The AEV did move on the track, the AEV traveled back a few feet, and then the motors changed direction, and spun to move the AEV a few feet forward. The AEV seemed to start slow, and then gradually gained speed during the movements. The motors had to overcome the static friction of the AEV. The AEV, designed with capacity and space in mind, is a heavy design with the LiPo and arduino fastened. This would lead to a larger static friction and  more friction on the wheels. Based on the results from running the AEV, it will travel rather slow until it can overcome the static friction and start accelerating. At our table, we ran the AEV, and on the sectioned track the AEV ran well and when it was blocked from moving, it still ran and gave promise to a smooth and methodical run.

 

Tables and Figures

 

We were no able to collect any data from or trial runs of the AEV due to the fact that the analysis tool was not working at the time of the lab.

 

  1. The main design feature is that it is wide and a big design. The motivation for this is to be able to carry as many passengers comfortable as possible. No specific techniques were used to design this AEV, we just wanted something that was able to complete the task effectively. The design also has dual propellers on each motor, which are canted at 90 degrees effectively making it a four blade design. As a group, we chose this based on our theory that a four blade motor is more effective than a two blade design.

 

  1. This AEV design cost is $151,660. The arduino costs $100,000, which is roughly ⅓ of the cost of this design. Overall, the design is rather expensive, but a manageable price for the service it would provide.

Takeaways

 

In Exercise one, we set up our software for the AEV, as well as learned how to program the Arduino and correctly upload the instructions. In Exercise two, we became familiar with using reflectance sensors on the AEV, as well as using functions that relied upon the sensors, such as using them to measure distance. In Exercise three, we learned creative design techniques and used them to create an orthographic concept design for our AEV. In Exercise four, we learned how to use the design analysis tool in MATLAB, as well as how to upload performance data from the AEV and read it with the analysis tool. Unfortunately, due to complications with MATLAB and the AEV, we were unable to get a table from exercise four, and this delay rendered us unable to complete exercise five.

 

Forward Looking Summary

 

Situation

 

Our next task is to Figure out an ideal design to apply to our AEV to make it more unique will also making it more aerodynamic. Our AEV is larger than the regular AEV, so although making it more aerodynamic will not create a significant difference, it will still help. We plan on completing this task by meeting with each other and testing different designs which we feel will be most beneficial.

Our primary goals within the coming weeks are to develop a unique design for the AEV, one that is stable and capable of carrying the required load on the track; complete our Advanced R&D topics (motor and propeller configuration); and prepare a suitable grant proposal. In addition, the code for the Arduino should be clear, concise, and accomplish the task presented to us.

 

Upcoming Schedule

 

Andrew Reade

  • Main programmer
  • Figure out if the code needs any changing to optimize it for our AEV
  • Test different percentages to run at to see if it can be controlled through that or just the counter on the wheel
  • Figure out how to integrate the servo for a braking system

 

Jean-Pierre DeDeaux

  • Design analysis
  • Compile design analysis tool in order to trial various concepts
  • Run through design types to achieve the group’s optimal AEV design

 

Caden Pfendler

  • Coding analysis
  • Solve our data recorder problem
  • Run AEV simulation to collect data in order to evaluate the design success of failure

 

Aaron Foster

  • Main Designer
  • Find place that the servo could be placed to create a braking system
  • Head over the design analysis and AEV simulation
  • Composite all results from testing and create AEV that will be optimized for testing and future runs
  • Design AEV in Solidworks for a more streamlined and highly more accurate  design contrasting from the kit of parts given.

 

In lab we will test the placement of motors and propellers and test where the optimal placements are. We will test whether a two blade design is more appropriate than a single blade design. Also, to test whether the smaller, more squared blades are better than the longer and rounded blades. These can be tested in both the single and double blade design. We cannot test this, but if having four total blades is better, then a blade design with more than four could be designed, and then we can also test the angle at which the blades are set. Testing the motors will be solely on placement and whether two motors is better for propulsion. This will be done on the same design, but motor placement and efficiency may change between designs, so we can consult other groups to have a more accurate representation of motor placement.

Moving forward, the concepts for our AEV need to be finalized to create and compile concrete data to move forward with our design. Learning what makes an AEV design better than another would greatly simplify the troubles of creating the final AEV.

In the code, we need to figure out how to control the AEV on the track and be able to accurately program the AEV in order to efficiently run the track and be able to stop in the proper spots and deviler the passengers safely and in the correct places.

 

Appendix

 

Team Meetings

 

Meeting #1

Date:1/10/2018

Time:1:30 in lab

Members Present:All

Topics Discussed:

  • Introduced ourselves to become familiar with  the team.
  • Exchanged phone numbers.
  • Started making plan for how we will work on the AEV project for the semester.

 

Meeting #2

Date:1/17/2018

Time:12:45 in lab

Members Present:Andrew Reade, Jean-Pierre DeDeaux, Caden Pfendler

Topics Discussed:

  • Introduced ourselves to to newest team member.
  • Began working on Preliminary R&D
  • Finished work and code on exercises one and two.

 

Meeting #3

Date:1/24/2018

Time:12:45 in lab

Members Present:All

Topics Discussed:

  • Resumed work on Preliminary R&D
  • Completed Website Update 1 before class, and ensured it was completed.
  • Asked Aaron to draw the final concept for our AEV and assemble it.

 

Meeting #4

Date:1/31/2018

Time:12:45 in lab

Members Present:All

Topics Discussed:

  • Finished work on Preliminary R&D.
  • Agreed on a final design for the AEV.

 

Arduino Code

 

  • PrgmBasics
    • // Run motor one at a constant speed (23% power) for 2.5 second.
    • motorSpeed(1,23);
    • goFor(2.5);
    • //Accelerate motor one from 0 to 15% power in 2.5 seconds.
    • celerate(1,0,15,2.5);
    • //Run at constant speed for one second.
    • goFor(1);
    • // Brake motor one.
    • brake(1);
    • //Accelerate motor two from zero to 27% power in 4 seconds
    • celerate(2,0,27,4);

 

 

  • ExternalSensorsOutside
    • //Runs both motors at 25% speed for 2 seconds.
    • motorSpeed(4,25);
    • goFor(2);
    • //Runs motors at 20% unitl vehicle has travelled 12 feet,
    • //then stops and reverses the motors, runs them at 30%
    • //for 1.5 seconds, then brakes all the motors.
    • motorSpeed(4,20);
    • goToAbsolutePosition(296);
    • brake(4);
    • reverse(4);
    • motorSpeed(4, 30);
    • goFor(1.5);
    • brake(4);

 

  • CSS1
    • //Accelerates all motors to 25% power in 3 seconds.
    • celerate(4,25,3);
    • //Sets all motors to 25% power for 1 second, then at
    • //20% for 2 seconds, then reverses the motors.
    • motorSpeed(4,25);
    • goFor(1);
    • motorSpeed(4,20);
    • goFor(2);
    • reverse(4);
    • //Runs all motors at 25% for 2 seconds, then brakes all motors.
    • motorSpeed(4,25);
    • goFor(2);
    • brake(4);