The single, most Frequently Asked (and answered) Question:
Q) What is your advice to a person who has just started exploring the field of robotics?
A) Start off with DIY tutorials and MOOCS (Massive Open Online Courses). They’re an inexpensive and fun way to learn programming languages. After that, while developing and tinkering, it’s useful to note a few things:
- The cheapest way to get spare parts is to take apart old and unused electronics. (Eg. press-buttons from a broken calculator, motors and RF modules from old RC cars, etc.)
- Proper indentation always helps when debugging code. Commenting at important sections also helps to identify glitches quickly.
- Faulty hardware accounts for over 50% of any problem. Seriously.
- When soldering multiple wires and bunching them together in a single cable, it’s always safer to use heat shrink tubing compared to electrical tape.
- If a python code which uses GPIO pins is not running on a Raspberry Pi, it’s probably because another process which started earlier is using the same pins. Try running ‘sudo killall python’ and then execute the new code.
- ATV’s should have thick tyres because thin wheels tend to cut through sand easily.
- The chassis of a racer or walker should be lightweight and strong.
- Hot glue sticks almost anything. It secures electrical and mechanical connections well, and can also be removed easily without the need for much scraping.
- Autonomous robots tend to skid if their motor’s rpm is high (greater than 250). A good way to prevent this is to incorporate a short reverse command with a small delay of 100 to 1000 milliseconds, depending on weight and speed of the robot.
Didn’t find what you were looking for? Fill up the form and I’ll do my best to clear your doubts.