Summary
Throughout Lab 01, which dealt with Arduino programming basics, the team became familiar with the automatic control system hardware components. They went through and identified each part in the kit; marking them off on the “AEV Kit Checklist” when each part was accounted for. This ensured all parts needed for the project were provided and that each team member knew the name and function of each part. This will aid the team in future projects, making it easier to understand the lab readings, and better understand the project. In addition to the inventory check, basic function calls were used to program a set of instructions and upload the code on the Arduino using the sketchbook program. This was done by opening up the sketchbook program, and putting the code under the “01_myCode” tab. The basic function calls utilized included “celerate”, “motorSpeed”, “goFor”, “brake”, and “reverse”. The team split up the work between the group and each member coded a portion of the program before connecting the Arduino to the computer and uploading the final code. This provided experience with basic programming and connection skills that will be used throughout the project to operate and test other controls. The team also mounted the curved propellers firmly to the motors with the dull side away from the motor. This was done to observe how the code worked with the propellers and eventually how it will move the AEV later in the project. Lab 01 left the team members with an understanding of the functions of the sketchbook program and how a program can be uploaded to the Arduino.
Results
An arduino code attempted to test and control the AEV propellor system. One of the motors did not work; this was an internal error that was difficult to resolve. One of the motors responded to the code while the other stopped and started very quickly. The motor must be replaced for the system to work correctly. This lab error was useful as any internal errors that occur will be quickly identified. Lab setup and testing takes a large amount of the lab period and efficient work was required to finish the lab on time. The lab was not completely finished in the period provided and the second optional part of the lab, Scenario 2, was not attempted. Better time management and allocation of lab responsibilities are necessary in future labs. No quantitative results were taken from the lab but many qualitative results were recorded from the system failure.
During the first test, the propellers were unable to run. After an examination of the motor, the propellers were determined to be touching the motor and creating unwanted friction – stopping the propellers from rotate. After testing a second time, it was determined that the friction against the wall was not the problem. The lab group attempted to troubleshoot the problem, checking each connection. With no success, the TA was asked to check over the configuration for any obvious errors made during the setup. An error was not discovered and the group was referred to the GTA office hours. At the office hours, another unsuccessful attempt was made to get the motors to run, the problem was postponed to the next lab period. The group will attempt a third time along with more troubleshooting to resolve the problem.
The commands used to make the AEV function have limitations associated with them. When using the “brake(m)” command the AEV does not stop immediately. The function does not brake the AEV system, but rather cuts the power from the motor. Additionally, the track itself was a restriction as the AEV can only go as far as the track allows. This will need to be taken in consideration when programming the tasks that will need to be completed by the AEV – it cannot be programmed to go a further distance than the track will be capable of carrying it.
The team wasn’t able to finish the first scenario and as a result could not start on the second scenario due to multiple errors. The first significant error was connecting the wrong COM port in the program, which wasted time trying to figure out why the program did not connect to the Arduino. Another error that was made by the team was mounting the propellers too far down the shaft creating friction. The second Scenario was to test out and get familiar with more sketchbook commands, including running both motors at the same time with different acceleration.
The team had trouble getting started during the lab experiment as seen in the errors made. The TA’s were needed often throughout the period to accomplish simple tasks. The lab group as a whole needs to read the laboratory manual thoroughly before the experiment for it to run more smoothly and efficiently in the future.
Team Meeting Notes
Date: 1-22-2017
Time: 8:00-9:15 pm
Members Present: Evan Berry and Alex Savelieff
Topics Discussed: We discussed who should do which projects and parts on the progress report while incorporating and taking in consideration objectives and goals we needed to accomplish outside of the lab report including building the AEV.
Objective: Evenly distribute the work of the progress report along with setting dates they should be completed by.
To do/Action Items: Situation for past week, situation for next week, and weekly goals and schedule.
Decisions: The next meeting date was determined to be on 1/23.
Date: 1-23-2017
Time: 6:30-9:00 pm
Members Present: Evan Berry and Ahmed Negn
Topics Discussed: Possibly setting up a general meeting time every Sunday that all members will attend if progress report is not completely finished.
Objective: Complete all parts of the progress report assigned to Evan and Ahmed. Work together to figure out what should and should not be included on the takeaways and weekly goals.
To do/Action Items: Takeaways, next week schedule, situation.
Decisions: Create two mandatory meetings every week all group members attend. One on wednesdays to plan the progress report completion and one on sunday to create the final copy of the report.
Date: 1-24-2017
Time: 9:30-10:30 am
Members Present: Evan Berry and Alex Savelieff
Topics Discussed: What changes need to be made to the progress report before we can submit it as a final copy.
Objective: Turn in final progress report and print out hard copy
To do/Action Items: Proofread entire report. Correct all errors including incorrect tense and grammar mistakes.
Decisions: The progress report is complete and ready to be turned in
Weekly Schedule
| Task | Teammate(s) | Start Date | Due Date | Time Needed |
| Construct AEV | Alex & Cameron | 1/23/17 | 1/24/17 | 30 mins |
| Install Sensors | Alex & Cameron | 1/24/17 | 1/24/17 | 15 mins |
| Test Sensors | All | 1/24/17 | 1/24/17 | 30 mins |
| Code Program | Evan & Alex | 1/24/17 | 1/24/17 | 15 mins |
| Troubleshoot | All | 1/24/17 | 1/24/17 | 30 mins |
| Start Progress Report | All | 1/24/17 | 2/7/17 | 4 hrs |
| Prepare Next Lab (02b) | All | 1/27/17 | 1/31/17 | 1 hr |