Servos Jerky Movement

I am on the final stages of configuring the Scout, but my servos are moving really fast. I am passing this command to ssc 32 that’s supposed to move it in 5 seconds, but it moves them within a half second.
#00P1580#01P1520#02P1410#03P1390#04P1500#05P1380#16P1500#17P1440#18P1470#19P1500#20P1500#21P1390T05000

This command is from a terminal, so I know the command going to ssc 32 is right. Everything else works in the command but just moves the servos really fast and jerks the robot. If someone can point me in the right direction, that will be appreciated.

Will a single servo will move as desired when it is sent a command?

If I rmember correctly, after the first command is sent, the servos will move at full speed, but after the first command is sent any new commands following should respond to the time setting. have you tried sending the command a second time during the same session? I’m refering to the entire line as one command, there needs to be a carriage return then resend the entire line again.

The T command is not recognized when it’s sent as the first command. This is because until the servo is initialized the controller does not know where the servo is positioned. The proper way to do this is to send a command to turn the servo on. #0 P1500 , then you can use the T command, #0 P2000 T2500 . If this is not it, the only thing that would cause this is if you have a power supply issue. Here is a good test.

Start up LynxTerm then power up the SSC-32. The green LED should be lit up. Send #0 P1500 and note the green LED is now out and blinking with every received character. If the green LED is now on again, it means the SSC-32 has reset and it no longer has a reference for moving the servo based on time. If this is what is happening you must provide us with more detailed information on how the bot is wired for power.

Thanks to Robot Dude, I figured out my Problem. My bot wasn’t close enough to the default position, so when I send the default position to the ssc32, it lost connection to my micro controller. I had to reset my micro controller after that first communication and then, after that SSC32 worked perfectly. Of course, I need to make changes, making Scout as close as possible to default position.

it also seems you have “T” followed by a “0” then “5000” (T05000) :confused:

......00#21P1390T05000

i thought it should just be “T5000”

I tested this when I answered the first time, but didn’t mention it. The SSC-32 ignores leading zeros. So T5000 is the same as T05000. :unamused:

Ooo new information. ok. makes sense. :neutral_face: