Progress Report 2

Progress Report 2

 

AR&D week 5  Backwards Looking Summary

Situation

During the preliminary research and development, the team was asked to choose two topics to be tested. One of the topics that was chosen was battery testing. The objective of this test was to run multiple tests on the LI-PO battery to determine a relationship between battery voltage versus number of test runs and battery voltage versus distance. Although the battery is rated at 7.4 V fully charged, it varies depending on manufacturing variance and age of battery. Because of this, the battery needs to be tested. Factors that were consistent in each test were the battery mount position, starting point, testing track. The AEV started at 30 inches for each trial

Results and Analysis

In the first part of test, the AEV are ordered to run 6 seconds with a speed of 25 and then reverse the motor direction and run 1 second with the speed of 40. The data recorded in the first running are too deflected so we abandoned them. The voltage of battery decreased about 0.10 voltage after each running, and the distance AEV travelled decreased as the decreasing of the battery voltage. In the second part of test, the AVE was ordered to run 5 second with a speed of 35 and then reversed the motor direction and ran 3 second with the speed of 40. The voltage of the battery decreased about 0.01 volts after each running. The distance AEV travelled decreased as the decreasing of the battery voltage. The testing was continued in week 6, where the analysis was performed on the different battery testing.

Takeaways

We learned from the aev that the battery doesn’t actually differ in voltage significantly throughout each run. We used this information to help in how we are going to run the program for our final design. Because the voltage did not change significantly we decided that we could use power breaking and not make a too drastic drop in the battery.

 

AR&D week 6 Backwards looking summary

Situation

Because we had some delays in the previous lab designing our aev and getting the test data to upload, lab week 6 was used to continue battery testing.. The last lab not enough trials were ran with different codes to get sufficient results and conclusions. This lab was usd to finish those results and have more of a claim to back up our conclusion.

Results and Analysis

After running two different codes more times to give us more data and to understand more how the battery was affected the two  different battery results showed that the batteries were fairly consistent and the voltage only dropped a very small amount. It also showed that our AEV design is efficient and does not provide a lot of stress on the battery. This will help us when the payload is added to the AEV to keep the battery lasting longer and stronger.  

Takeaways

We used this lab to help determine that our aev is energy efficient and does not cause a high stress on the motors or battery. This data will help us when we add more weight because we know that most of our energy can be focused towards moving the payload and not just the actual aev itself.

 

 

AR&D Week 7: Backward Looking Summary

Situation

The other topic that was considered for AR&D was motor configuration. The team chose this topic because different motor configurations help the AEV travel further on less power which helps it be energy efficient. The objective of the test were to collect data on the distance the AEV traveled and analyze the data to choose the configuration. During testing, the starting position and the number of motors stayed the same. Our goal of theses test is to come up with a motor configuration that provide the greatest distance while also conserving power.

Results and Analysis

The first design had two motors horizontally next to each other in the back of the AEV. After testing this configuration with the code the AEV ran an average distance of 177 inches. After reconfiguring the motors so that each motor was slanted outward on the AEV, the average distance ran was 276 inches. The motor change provided almost a 100 inch difference using the same code.

It was concluded that the reason for this drastic change was that now the motors each were creating their own propulsion on each side of the AEV to provide a larger amount of thrust then when being right next to each other and directly behind the AEV. Furthermore pulling the motors out to the side acts as a balancing device for the AEV and allows it to run smoother on the track because the weight is more evenly distributed. Also pulling the motors out to the side allowed each motor to have its own airflow instead of using the same airflow and this helped us gain more thrust and balance because each motor was outflowing the air to the sides to balance the aev in the center.

Takeaway

We learned that the titleted motors provided more speed and balance using the same code and energy. This helped us greatly because we were able to use all the same parts and code, but by just making the motors 45 degrees outward we were able to increase the distance in one run by almost 100 inches. This test allowed us to become set on using the angled motors and now we will use this information in the future to help redesign and evaluate our motors based on the angled motors.

 

 

Forward Looking Summary

Situation:

The objective on the forefront of Group H’s activities in the upcoming weeks is to slightly alter the design of the AEV so that it can run on the required track for the transport of passengers. When trying to run the AEV in lab it was discovered that how the support arm was connected to the base prevented the AEV from traveling down the track. The design will be altered before the team returns to lab from spring break. In week 9, performance test 1 will be completed. Group H will develop a code that makes the AEV travel down the track and stop at a closed gate until it opens. The team intends to use power breaking to help accomplish the test. In week 10, performance test 2 will be completed. The goal of this test is to have the AEV travel through the gate and magnetically attach to a payload. In week 12, Group H will work on having the AEV traverse back to the starting zone with the payload attached. In addition to the lab exercises, the team will also be working on the deliverables that can be found in the table that follows.

Schedule

Table 1: Upcoming Schedule

Task Members Start Date Due Date Time Involved
Performance Test1 ALL March 20
CDR Draft ALL March 23
Performance Test2 ALL March 27
Committee Meeting 2 ALL March 29
Progress Report 3 ALL April 5
Final Oral Presentation Draft ALL April 9
Final Performance Test ALL April 12
Final Oral Presentation ALL April 16
Final Website ALL April 19

 

Appendix

 

Team Meeting Notes #3

Group: H

Location: 18 Avenue Library

Time Started: 1300, FEB 05, 2018

Time Finished: 1430, FEB 05,2018

Attendees: Snigdha Tiwari, Jack Werren, Elijah Baker

*Nan had informed us previously that she would not be able to attend the meeting because she had a meeting with a professor. Nan was informed what work she had been assigned and she completed it.

Topic:

Website Upload 2

Progress Report 1

Upcoming tasks:

Website Update 2 (All group members are responsible for that)

Progress Report 1

To-Do:

  • MCR – all members
  • Progress Reports for each lab
  • Code for all Labs
  • AEV findings supported
  • Decide on advanced R&D topics to test

Notes:

Snigdha was assigned the progress report for lab 04.

Jack was assigned the progress report for lab 01.

Nan was assigned the progress report for lab 02.

Eli was assigned the progress report for lab 05.

All members collaborated on the progress report for lab 03.

Team Meeting Notes #4

Group: H

Location: Torres House

Time Started: 5:00 PM, FEB 12, 2018

Time Finished: 7:30 PM, FEB 12,2018

Attendees: Snigdha Tiwari, Jack Werren, Elijah Baker, Nan Zhang

Topic:

Grant Proposal

Committee Meeting

Upcoming tasks:

Website Update 3 (All group members are responsible for that)

Progress Report 2

To-Do:

  • Progress Reports for each lab
  • Code for all Labs
  • AEV findings supported
  • Decide on advanced R&D topics to test

Notes:

Everyone was assigned a part in the committee meeting:

Snigdha was human resources

Nan was public relations

Jack and Eli were research and development

Team Meeting Notes #5

Group: G

Location: 18 Avenue Library

Time: 5:30, Feb 26, 2018

Attendees: Snigdha Tiwari, Jack Werren, Nan Zhang, Eli Baker

Topic:  

Website Upload 3

R&D Presentation

Upcoming tasks:

Progress Report

Lab 8 Presentations(in-class)

To-Do:

  • Put up Summary for Labs
  • Do AR&D research
  • Finish R&D Presentation
  • Finish Website Update
  • Upload nose cone file for 3D printing

Notes:

Jack – Upload nose cone

 

Code Since Last Progress Report

Code for Battery Test1

 

void myCode()

{

//—————————————————————————————-

// myCode();

//

// This is the tab where the programming of your vehicle operation is done.

// Tab _00_AEV_key_words contains a compiled list of functions/subroutines used for vehicle

// operation.

//

// Note:

// (1) After running your AEV do not turn the AEV off, connect the AEV to a computer, or

//     push the reset button on the Arduino. There is a 13 second processing period. In

//     post processing, data is stored and battery recuperation takes place.

// (2) Time, current, voltage, total marks, position traveled are recorded approximately

//     every 60 milliseconds. This may vary depending on the vehicles operational tasks.

//     It takes approximately 35-40 milliseconds for each recording. Thus when programming,

//     code complexity may not be beneficial.

// (3) Always comment your code. Debugging will be quicker and easier to do and will

//     especially aid the instructional team in helping you.

//—————————————————————————————-

// Program between here——————————————————————-

// Run all motors at a constant speed (25% power) for 6 second.

motorSpeed(4,25);

goFor(6);

 

// Reverse motors.

reverse(4);

// Run all motors at a constant speed of 30% power for 1.5 second.

motorSpeed(4,40);

goFor(1);

// Brake motor one.

brake(4);

// And here——————————————————————————–

} // DO NOT REMOVE. end of void myCode()

 

Code for Battery Test2

 

void myCode()

{

//—————————————————————————————-

// myCode();

//

// This is the tab where the programming of your vehicle operation is done.

// Tab _00_AEV_key_words contains a compiled list of functions/subroutines used for vehicle

// operation.

//

// Note:

// (1) After running your AEV do not turn the AEV off, connect the AEV to a computer, or

//     push the reset button on the Arduino. There is a 13 second processing period. In

//     post processing, data is stored and battery recuperation takes place.

// (2) Time, current, voltage, total marks, position traveled are recorded approximately

//     every 60 milliseconds. This may vary depending on the vehicles operational tasks.

//     It takes approximately 35-40 milliseconds for each recording. Thus when programming,

//     code complexity may not be beneficial.

// (3) Always comment your code. Debugging will be quicker and easier to do and will

//     especially aid the instructional team in helping you.

//—————————————————————————————-

// Program between here——————————————————————-

// Run all motors at a constant speed (25% power) for 6 second.

motorSpeed(4,35);

goFor(5);

 

// Reverse motors.

reverse(4);

// Run all motors at a constant speed of 30% power for 1.5 second.

motorSpeed(4,40);

goFor(3);

// Brake motor one.

brake(4);

// And here——————————————————————————–

} // DO NOT REMOVE. end of void myCode()

 

Code for Motor Configuration Test

 

void myCode()

{

//—————————————————————————————-

// myCode();

//

// This is the tab where the programming of your vehicle operation is done.

// Tab _00_AEV_key_words contains a compiled list of functions/subroutines used for vehicle

// operation.

//

// Note:

// (1) After running your AEV do not turn the AEV off, connect the AEV to a computer, or

//     push the reset button on the Arduino. There is a 13 second processing period. In

//     post processing, data is stored and battery recuperation takes place.

// (2) Time, current, voltage, total marks, position traveled are recorded approximately

//     every 60 milliseconds. This may vary depending on the vehicles operational tasks.

//     It takes approximately 35-40 milliseconds for each recording. Thus when programming,

//     code complexity may not be beneficial.

// (3) Always comment your code. Debugging will be quicker and easier to do and will

//     especially aid the instructional team in helping you.

//—————————————————————————————-

// Program between here——————————————————————-

// Run all motors at a constant speed (25% power) for 6 second.

motorSpeed(4,35);

goFor(5);

 

// Reverse motors.

reverse(4);

// Run all motors at a constant speed of 30% power for 1.5 second.

motorSpeed(4,40);

goFor(3);

// Brake motor one.

brake(4);

// And here——————————————————————————–

} // DO NOT REMOVE. end of void myCode()

 

Figures and Tables

Battery Test
Test Code Distance(in) Voltage1(v) Voltage2(v) Voltage difference(v)
1.1 motorSpeed(4, 25);

goFor(6);

reverse(4);

motorSpeed(4, 40);

goFor(1);

 121 8.51 8.4 0.11
1.2 114 8.4 8.39 0.01
2.1 motorSpeed(4, 35);

goFor(5);

reverse(4);

motorSpeed(4, 40);

goFor(3);

 180 8.39 8.37 0.02
2.2 174 8.37 8.36 0.01

Table 1

 

Motor Configuration
Test Code Distance(in)
Test 2: Non-Slanted Motors 1.1 motorSpeed(4, 35);

goFor(5);

reverse(4);

motorSpeed(4, 40);

goFor(3);

 180
1.2 174
Test 3: Slanted Motors 2.1 motorSpeed(4, 35);

goFor(5);

reverse(4);

motorSpeed(4, 40);

goFor(3);

 278
2.2 274

Table 2

 

Figure 1

Figure 2

Figure 3

 

Figure 4

Figure 5