OBJECTIVE
- To study the controller operation of arduino and servo motor.
- To describe the input and output controller for quadruped robot.
METHODOLOGY
- Search type of servo motor suitable to be use for quadruped robot.
- Search type of arduino suitable to be use with WiFi module to use for quadruped robot.
- Consult supervisor for advice on choosing components use to develop quadruped robot.
- Define the input and output controller of the quadruped robot.
RESULT
This is the result that obtain after a few research for my project. The arduino that will be use is a NodeMCU Lua ESP8266 WiFi. The reason to choose this type of arduino because its an arduino built with WiFi module.
NodeMCU Lua ESP8266
The servo motor that use is TowerPro 90SG 9gm 180degree micro servo motor because it is smaller compare to other type of servos since the quadruped robot will be develop small in size. The other reason it is cheaper. The material is plastic because the robot body is made up 3D printed model thus it is not heavy.
TowerPro micro servo SG90 9gm 180degree
The input and output controller for this project is stated in the table below.
INPUT
CONTROLLER
|
OUTPUT
CONTROLLER
|
Wi-Fi Switch
|
Servo
motors (12)
|
BLYNK smartphone application controller
|
BLYNK
smartphone application display
|
ANALYSIS/DISCUSSION
The input and output controller is set with the help of my supervisor. The ON and OFF switch is connected to the robot itself so the power can be save when not in use. The BLYNK application will send a signal to the NodeMCU since it is built with WiFi module to turn ON the robot to operate. The NodeMCU will command the servo motors to rotate or moving the legs of the quadruped robot. Then, for each servos that operates will give a display to the BLYNK application.
CONCLUSION
In conclusion, this week objective cannot be achieve without the help of my supervisor and a few advice from him. The components choose is based on discussion with my supervisor. Thus this conclude that the objective for this week is achieve successfully.
No comments:
Post a Comment