Q command problem

Hello,

I have some problem with the Q command and visual basic,
the ssc-32 send me the β€œ.” before the movement is completely finished.
Not so much, but if i use it to test the end of a move and if i send another
command, the firt move stop until is finished.
This problem occur especially if the time movement is around 1000 ms.
Not occur at a time of : 3000 ms and much more.

The ssc-32 firmware version is 1.06XE

Thanks you very much

Sorry if my english is not so good :blush:

me personally i havent use the Q command i use a pause in the program = to the time i set on the move seems to work for me and your already ahead of me using VB mabe sombody with a little more knowledge will chime in sorry if this dont help

It may cause confusion, but the ssc-32 does not know the actual position status of the servo. I think it can only tell you if the last command to the servo has been sent. Maybe some one familiar with the chip programming can speak to the timed movement feedback.

The response to the Q command has a resolution of 10uS. Im not certain of the exact rounding done but it could be +/-5 steps so a response of 150 could mean anywhere between 1495 and 1505. +/- 5 is not much as to be honest I’m using it quite a bit at the moment and don’t seem to see the problem you are seeing. I should imagine it would be a lot more visible on slow moves…

As suggested by zoomkat, this is probably due to the fact that the SSC-32 does not know when the servo has finished moving. It returns β€˜.’ when the pulse width it is sending is equal to the target pulse width for the move; but the servo might not have reached the final position yet. This would be most noticable on a fast move with a slow servo. It makes sense that you see it only on faster moves, but not so much on slower moves.