Servo Examination

By Kevin Huynh, Project Manager / Computer Systems and Software

The purpose of this servo examination was to discern the reason for the servos malfunctioning. During the servo testing, it was discovered that three Power HD 1501MG servos were broken and the broken servos were closer to the feet of the robot, suggesting that the load was wearing out the servo by shear stress. We took apart the servos to figure out why the servos were actually breaking. Four servos were taken apart to examine the servo gears and shaft, three of the servos were the nonresponsive Power HD 1501MG servos mentioned in the servo functionality testing and one was a functional Power HD 1501MG servo as a base to compare the broken servos to. There seemed to be nothing physically wrong with the servos.

ServoGears

Next, we examined the circuit board on the other side of the servo. Two of the three broken servos had burned circuit boards, the third servo appeared to have no damage at all.

BurnedServo

Servo Examination Conclusion:
Since there seemed to be nothing wrong with the gears or shafts of the servo, it is unlikely that the servos were directly damaged by carrying the weight of ROFI. Since the circuit boards were burned, it is likely that the servos drew too much current and overheated. This is likely the result of the servos stalling, but continuing to draw a large amount of current in an attempt to reach the position specified by the programming. The constant draw of current eventually overheated the servo and burned the circuit board. We will be looking into ways to prevent the servos from drawing too much current from the LiPo batteries even if the servos stall, starting with a foldback current limiter.

Spiderbot: Chop Suey Returns

By Matthew Clegg, Computer & Control Systems

Chop Suey has returned! David Gonsalez, a member of the Hexapod team from the previous semester, has loaned us the hexapod prototype he built. Having access to an already built prototype will save time and money because we will not have to devote resources to make one. It will also allow me to visualize how the servos will be working to move the legs and body, depending on which type of walk, or gait, the Spiderbot will use.

We scouted the area where Spiderbot will be required to move through and took measurements of obstacles. After previewing the terrain, it seems that Spiderbot may have to switch between two different types of gaits in order to overcome obstacles and move with good speed. The two gaits in consideration are the tripod gait, which will allow for a greater speed on level surfaces, and the wave gait, which is slower but will allow for more stability over uneven terrain.

Further explanation of these gaits can be found in the blog of the previous semester’s Hexapod project.

Sprinkler_Top

The length of some of these obstacles will also affect the distance that the legs of Spiderbot will have to sweep.  This will be determined in part by the length of the legs. The photo above indicates that the maximum width of the obstacles from a top view (both sprinkler heads and branches) measured to 2.5 inches, which is the leg sweep that will be required of Spiderbot.

In accordance with the previous semester’s design choices, we have also decided to use the Arduino Mega ADK, as well as the Adafruit 16-Channel 12-bit PWM/Servo Driver in Spiderbot’s design. The Mega ADK will allow for fewer complications when interfacing with an Android smartphone because of the dedicated usb port placed on the board. The Mega ADK will not be able to support the number of servos we will be using (a total of 20 servos!), which is why we will be using servo drivers. The use of the drivers will also free up processing power from the Arduino ADK. These components are shown below:

 

ArduinoADKFront450px

Image from: http://arduino.cc/en/uploads/Main/ArduinoADKFront450px.jpg


adafruit-16-channel-i2c-servo-controller-1_1

Image from: http://www.robotshop.com/media/catalog/product/cache/1/image/800×800/
9df78eab33525d08d6e5fb8d27136e95/a/d/adafruit-16-channel-i2c-servo-controller-1_1.jpg

The next thing in store for Spiderbot: trade-off studies of servo motors for leg operation of Spiderbot and familiarization with everything Chop Suey has to offer to better our design.

Servo Functionality Test

By Elaine Doan, Systems and Test Engineering

Servo Functionality Testing
The objectives of this test were to verify that ROFI’s servos were working correctly. There are two servos that the CSULB Biped group is concerned with: the Towerpro MG996R servo and the Power HD 1501MG servo. These two servos were used in both ROFI and ROFIA, with ROFI having a combination of both servos and ROFIA using exclusively Power HD 1501MG servos.

Servo Test Materials
1. Arduino MEGA 2560
2. Towerpro MG996R and Power HD 1501MG on ROFI
3. UBEC-5A-HV DC-DC regulator

Servo Wiring Procedure
1. Connect the red wire to the positive terminal of the UBEC and the brown wire to the negative terminal of the UBEC DC-DC regulator. Do not connect either the red wire or the brown wire of the servo to the Arduino, there is a possibility that the servo will draw a lot of current and destroy the Arduino.
2. Connect the orange wire to an Arduino output pin. The orange wire is the control signal terminal of the servo and will allow you to control the servo with the Arduino.

 

Testing Code
The following code will command a servo on Arduino PIN 8 to rotate 60° clockwise within two seconds, then rotate 60° counterclockwise within two seconds. This process is repeated until the Arduino is turned off. The servo is assumed to have been centered before the test, but can be centered by using myservo.write(90).

#include <SPI.h>
#include <Servo.h>            // Include servo library

Servo myservo;               // create servo object to control a servo

void setup()
{
 myservo.attach(32);           // attaches servo on pin 8 to servo object
}

void loop()
{
 myservo.write(1);             // Move servo to 1 degree angle
 delay(2000);                  // Delay 2 seconds
 myservo.write(120);           // Move servo to 120 degree angle
 delay(2000);                  // Delay 2 seconds
}

Servo Test Conclusions:
Three of the twelve servos on ROFI were found to be completely non-responsive. All of the nonresponsive  servos were Power HD 1501MG servos and tended to be close to the feet of the robot, suggesting that the load was responsible for breaking the servos. Following this is a diagram and table detailing the results of the servo test.

 

ROFI

Servo#           Servo Type                       Result
    1                      Towerpro MG996RC        Functional, rotates 90°
    2                      Power HD 1501MG           Functional, rotates 120°
    3                      Towerpro MG996R           Functional, rotates 90°
    4                      Power HD 1501MG           Nonresponsive
    5                      Towerpro MG996R           Functional, rotates 90°
    6                      Towerpro MG996R           Functional, rotates 90°
    7                      Towerpro MG996R           Functional, rotates 90°
    8                      Towerpro MG996R           Functional, rotates 90°
    9                      Towerpro MG996R           Functional, rotates 90°
    10                    Power HD 1501MG           Nonresponsive
    11                    Power HD 1501MG           Nonresponsive
    12                    Towerpro MG996R           Functional, rotates 90°

Demonstration Video
http://youtu.be/hO09e36LdrU

Datasheets available at:
Power HD 1501 MG: http://www.pololu.com/file/0J729/HD-1501MG.pdf
TowerPro MG996R: http://www.towerpro.com.tw/driver/drivers/Towerpro%20servo%20spec.pdf

Spiderbot – Life & Times (Vol. 2)

Spiderbot_Logo_smaller

By Kristine Abatay, Project Manager

main()
{
printf(“hello, world!”);
}

It is a new semester at Robot Company and with it, a new Spiderbot!

 Our mission: construct a six-legged robot that will match the speed of the Robot Company’s rover project, operate safely, and have the capability of maneuvering a route in a natural setting.

 This robot will have a spider-like appearance and walk, but with six legs instead of eight, all the while being controlled wirelessly using an application for Arxterra, designed for Android smart phones. Spiderbot will achieve a speed of 0.2003 m/s on a flat surface – the calculated speed using specifications from components of the rover project last semester.

Click here to see the calculation used to determine the speed requirement  

The natural setting that Spiderbot will be able to maneuver is located on the East Wing of the CSULB campus as shown by the following map:

Map

 Our group surveyed the area and created a route for Spiderbot to complete as indicated in the picture above and the total length measured to roughly 42 m. This is the same path that will be used to test both the Rover and the Hexapod projects. A quick run through of the route can be found in the following link:

The pictures below are some of the obstacles encountered while surveying the Spiderbot route. A sprinkler head with a height of roughly 4 inches and a branch with a width of 2.5 inches were the most notable obstacles. These measurements will dictate the overall body design of our Spiderbot. In addition to these design requirements, our Spiderbot will function properly while following the health and safety policy of the engineering department of CSULB (found here: http://www.csulb.edu/colleges/coe/views/safety_and_environment/safety_policy.shtml).

SONY DSC

Our date of completion is set for May 12, 2014 so stay tuned for future updates as we progress in our construction of Spiderbot!

Riverside Robot Expo 2013

Riverside Robot expo was awesome this year. Ran into some familiar faces and reconnected with some other maker groups. Vocademy is opening a Riverside Makerspace space in the area and we can’t wait to see what they start to offer. Thank you the the Riverside Robotics Society for putting this on.

20131102_155536 20131102_114401 20131102_110419

Northern California Maker Faire Tour!

We had a blast at all the Faires. It was Santa Rosa’s first shot at it and the people where great! East Bay Maker Faire was as expected from the people who bring you the larger Bay Area Maker Faire. We couldn’t leave our booths for either event! All in all a good trip. We met a lot of interesting makers and enthusiasts! See you next year!

20131019_085830 20131019_101422 20131020_092105

Rosco and Pathfinder Arduino Code Versions Available

Arxterra has released the current beta versions of Arduino code for our telerobotics plaform. The Rosco Code utilizes and Arduino uno and android OS 3.0 and higher. For those of you with Android phones OS 2.3 and higher we suggest you take a look at the pathfinder Arduino code, which can be used in conjunction with and Arduino mega ADK. We haven’t had the chance to work with the USB host shield but it should be simple for all you makers our there. Any takers?

Code is available at www.github.com/arxterra

Robotics Society of Southern California

Home

Pathfinder Rover was exploring the most recent meeting for the Robotics Society of Southern California. There were also interesting presentations on autonomous robots (Leaf Project) and Lego NXT Sensor Interfacing. Meetings are free and every second Saturday of the month.

For more info go to http://rssc.org/node/1.

OC Interactive Meetup

Arxterra was on hand at the OC Interactive Group giving a presentation on Arduino Flash Based Control! Of course Rosco was on hand for a quick demo! Thanks to our own Jeff Gomes for setting everything up.

More info on OC Interactive can be found at:

http://www.meetup.com/Orange-County-MultiMedia-Association/

Arduino Enthusiast Meeting

Rosco and Pathfinder were on display at the monthly LA Arduino Enthusiast Meeting. Great turnout and interesting people from all backgrounds. If you’re in the area and love Arduino, a great meeting to check out! People of all ages and backgrounds!

Two Roscos and a Pathfinder

Two Roscos and a Pathfinder

Dancing Follower Robots

For more information on LA Arduino Enthusiasts go to: http://www.meetup.com/LA-Arduino/