Design process lab 04
System Analysis 2 & Design Analysis Tool
For Lab 04a – Performance Data Analysis, the group had to analyze the AEV’s performance after it was programmed to move from the starting point to the first stop, before the gate. Calculating and calibrating the performance of an AEV post-run is really crucial in designing the AEV. The AEV’s time, current, voltage and wheel counts had been recorded by the group using EEPROM on the Arduino. The EEPROM data recorded then been downloaded to the MATLAB. The group members had to convert the data to physical parameters and do plotting, to be able to analyze performance and modify any further improvement of the AEV.
For Lab 04b, MATLAB Graphical User Interface (GUI) had been used to download Arduino data, to perform analysis calculations to do plotting. Learning to use this tool is crucial because it could provide an alternative efficient way to do performance analysis on the AEV. The group had to install and run the Design Analysis Tool, import the Arduino data and calculate performance characteristics of the AEV by using this tool.
Results & Analysis
From the graph, the team will be looking to decrease the power usage in moving the AEV. As can be seen, the greatest power is being consumed when the rotation of the propeller is being reversed to help to stop the AEV (Phase 3). The team discussed that one of the possible ways is to first apply the ‘break’ code before reversing the rotation of the propeller. The other possible way would be to not use the reverse method to stop the AEV before the gate. This can be achieved by cutting the power off much earlier and also decrease the power set for both propellers.
The early part of the graph shows the motor begin to make its power to 35 percent and it is tally with the coding. The next part of the graph shows that the AEV makes its way to 4.49m with nearly same
power. When the calculation is made manually, the AEV should have made its way until 4.45m. This shows that the AEV had done the pretty good job as it had coded. It can be seen that the peak of the graph is achieved when the propeller is reversed. As this coding was intent to help stop the AEV, this power consumption should be avoided. Moreover, due to this coding, the AEV shacked when trying to stop. This is not a good thing as it might drop the AEV down the floor. Thus, the team must come up with another way of stopping the AEV before the gate.
