
abrown

I have a Revolution Six that I have used for one of my robotics classes the past two years. Last year, Six worked fine. This year, for some reason, it is burning out lever servo motors. I have gone through 5 already this year on the same robot. The burnouts occur on different ports, and happen at different times. I asked my students what they were doing when the motors stopped working and they said that they were just using some of the built-in movement scripts.
These burnouts are becoming quite expensive to handle. Has anyone experienced this situation before? If so, what can be done to rectify the situation? Any help would be greatly appreciated. Thanks.
With the 6 powered off, make sure all of the servos can move their full range of motion by hand (some may be stiff, but all should move, without the wires stretching or catching).
Alan
Al B
Richard R - I fully understand you about kids and their ways. Thanks for your insight.
Ensure your class is using the latest ARC with the latest Six project. The latest six project can be loaded from either the EZ-Cloud AppStore or within ARC.
If the robots are used often, 2 years of servo motor use is an acceptable amount of wear and tear. Which means they may be ready for replacement, as they're tiring out. Those little tiny motors in the servo mechanisms work very hard
First step is to ensure the Fast Walk is not used as per the documentation in the project. While the Fast Walk may be visually appealing, the six robot is not a toy and therefore the Fast Walk is unnecessary for educational activities.
Thanks for the helpful pointers. Hopefully this will eliminate the unusually high loss of servos.
The software alone will not prevent the Fast Walk - the software combined with using the latest project is the way.
If your students have saved previous projects, they will have to update to the latest project and overwrite their saved projects.
The Fast Walk has been known to decrease life expectancy of servos, which is why it has been removed from the six project in july.
Updates to projects and ARC software are important to benefit from the advancements made to the product. Product advancements also mean new features and usage improvements, such as this scenario. Without updating the software and projects on a regular basis, you will not be able to enjoy the benefits of advancements.
I don't recall seeing that in the release notes of any release, and I do read them all. Perhaps when you change the sample projects you could also publish release notes. I use a modified version of the Six project, and didn't know that removing fast walk was important. In fact, I have fast walk built into the buttons on my custom Android Wear control project, so I have a bit of work to do to remove it. Luckily I guess, I don't use that feature often as I have not had a problem.
(If you did publish it, and I missed it, I apologize in advance).
Alan