Page 1 of 1

Signed position not speed

Posted: Sun Feb 21, 2021 3:37 am
by woko1754
I just found a big misleading information in the roboclaw user manual. In commands 65, 66 and 67 at first I interpreted in the way, that the speed has to be negative to get to a negative position. But my code didn't work for negative positions. Then after sniffing the Motion Studio, I found out, that the position-parameter has to be negative to get to a negative position (as it obviously should be).

Now my code is working as expected :D !

Maybe this applies for other comm ands too.

Re: Signed position not speed

Posted: Wed Feb 24, 2021 11:39 am
by Basicmicro Support
I think your wording is incorrect. It may be a mistake or misunderstanding. Misleading has different connotations.

Positions arguments are 32bit values. You can think of them as signed or unsigned values, your choice. But they must be 32bit value.