Nevermind, figured it out.
The SSC turns itself off shortly after I turn it and the robot arm on. It dies regardless of whether I turn on the microcontroller or the arm first or if I turn them on at the same time. It turns itself off more quickly when I have it connected to a computer - at least that’s what I assume it’s doing, because I don’t hear any of the servos and the LED turns off.
Please note, the LED on the SSC-32 is not a power indicator. It does turn on when you first power up, but will then blink as the SSC-32 receives serial data. So it could easily be that no valid data is being sent to the SSC-32.
There are several threads up on the forums that help you debug serial communication issues, such as: viewtopic.php?f=2&t=4702
If you still have problems, please provide additional information, like how is the SSC-32 wired, what jumpers are installed and/or provide a picture(s) showing your setup, What are you trying to communicate to the SSC-32 with? Is the computer or microcontroller configured to send out the data to the SSC-32 at the correct baud rate…
Kurt
There is also no sound from the servos. Like, when both are turned on, the arm may jerk a little bit, then there is no sound and no response. It is the basic arm being controlled with a computer. Neither the graphic style program nor would the tester program create a response. The jumper between the two power cord leads is removed per instructions but all the others have been left alone. The arm was working for about 20 minutes before this too, then we tried it with Flowarm software and it would refuse to respond to either software.
I will try what you have posted tomorrow as I don’t have the arm at home.
