Time and speed commands have no effect

Lynxmotion Electronics & Software
1

Hi,
I have just got the SSC-32, it seems like a good piece of kit. However when I use the time and speed commands they make no difference.

For example, the following commands all move with the same fast speed from the same start point.

#0 P700
#0 P700 S100
#0 P700 T2000

My set up is:
1 Hitec HS-422 on port 0.
6V power supply connected to VL and bridged to the servo rail on the board.
The firmware is: 1-03XE
I am using the Lynx terminal program

I have tried it with different motors on different ports and with mulitple motors attached, all with the same effect.

Thanks

2

That’s not good…
The first should move to the position as fast as posible.
The second should do the same (speed command deliniates the maximum allowed time to move).
The third should take two seconds to move from where it was to the new destination.

Maybe you’re just having troubles timing things.
Try making it a bit more obvious by doing this:

#0 P1000 <cr>
#0 P2000 <cr>
#0 P1000 T10000 <cr>

If you can’t see a big difference between moving to P2000 and moving back to P1000, then you know you have big issues.

3

Sorry, I should have used that example. It doesn’t matter what numbers I use for speed or time, big or small. There is no difference.

I have tried it over large and small rotations as well.

I have also got a second board (bought at the same time, with same firmware) and that has the same issue. This makes me think it is a problem with my set up or something I am doing, but I cannot see what.

Thanks

4

Wow… that is odd.
Have you tried downloading the latest version of the firmware?
1.06E, if memory serves.

Oh… I just noticed…
P700 is outside the range of my servos (5645).
You might be running into troubles because of that.
Try positions like 1000 and 2000, which are within the range of just about every servo.

5

Please provide a more detailed list of what you are doing. If you are just using the LynxTerm then please provide a detailed list of what you are typing so we can help. I’m very certain that it’s just a matter of how you are testing the movements. I suspect that you may not be telling the servo to move to a new location, but it’s difficult to know without more information.

6

The first command you send to a servo, it’ll move as fast as possible. This is because the SSC doesn’t know where the servo is actually positioned at. Anything you send to the SSC after that should be controllable by the time and speed parameters (as long as the SSC-32 is powered the whole time. It’ll lose the servo positions if you turn it off.)

Here’s working code from my test program (Basic Atom Pro coding):


serout p3, i38400, "#2 P1900", 13]

;pause 1000

serout p3, i38400, "#2 P900 T 2000", 13]
7

Thanks guys,
I have got the problem sorted now. I seemed to be continually managing to try and move the servo with T and S on the first move when it cannot. Had missed that detail.

But can now move the servos as I need. Knew it was something stupid I was doing.

Cheers :slight_smile:

8

Wow Romshark, :open_mouth: Good catch. :smiley:

9

Yea, that one had totally flown over my head.
:blush:

:smiley:

10

Thanks. Luckily I’ve been working with the SSC-32 for my BRAT unit. I’ve only known this specific info for about a week or less.