Summary
The group began the AEV project by exploring the automatic control system hardware components, setting up the AEV software, learning how to program basic function calls in Arduino, learning how to upload and test programs in Arduino, and becoming familiar with various troubleshooting techniques. The purpose of this lab was to introduce the group to the AEV and teach basic programming knowledge needed to program commands.
The group first mounted propellers on two motors. The Arduino Sketchbook program was downloaded to the computer and a scenario was given where the group had to practice programming nineteen various function calls. Some of these calls included accelerating, decelerating, braking, running, and reversing the motors. The group then uploaded the Arduino Sketchbook program to the arduino where it was tested by turning on the switch.
Results and Analysis
As a result of the lab experimentation, important information about the arduino-controlled motor system and the execution of the code was learned. In regards to the motor system, when the command to run the propellers was run at less than 25% power, the propellers would not spin. This is because the electric motors were not given enough power to generate enough force to overcome the resistive frictional force. Another important piece of information learned from the experimentation was that when the brake command is used, the propellers do not immediately stop but instead slow down. This is important to the running of the AEV as a distance for the vehicle to coast after braking the motor is necessary to include when judging the distances the AEV will travel. The last bit of important information from the lab is that a semicolon is needed at the end of every command call due to the syntax of the sketchbook program.
Errors in the experimentation were few and mainly stemmed from a lack of experience and knowledge of the programs the group used. One error made, as referenced above, was due to improper syntax of the sketchbook code. This error was resolved by adding a semicolon to the end of every line of code where a function call was made. Another error was the connection of the battery to the arduino controller and electric motors. A resolution to this error was to unscrew the connector then insert the wire into the slot and fasten the connection with the screw.
As a recommendation for the lab material provided the group felt that the instructions on how to assemble the configuration was a bit confusing and that more descriptive pictures, such as ones that show different angles or views of the configuration, could have been included to improve the efficiency of lab time.
Takeaways
- AEV- The AEV controller was introduced
- AEV – The AEV software and hardware (Sketchbook and Arduino microcontroller) were set up
- AEV – Basic function calls were introduced and tested
- General – It is important to first check the code if a problem arises