Currently there is a problem with angle division, which is that it is based on floating point numbers. This means that if you for example have a robot that makes similar movements all the time for thousands of cycles, the absolute angle can drift a bit. I will update the implementation to use fixed point (maybe a resolution of 1/1000000 degrees) some time. Having an angle division of 1 does not have this problem since the encoder has fixed point counts.
Is there some reason you limit the positional control of the motor to 0-360 from the panel in the tool? Can I send larger moves from the terminal window? I guess when I have more time to play with this I will be playing with applications for position control with the can bus.
The reason is that the angle wraps around at 360 degrees, and the control loop will use the shortest movement to get there. For example, if the motor is at 10 degrees and you command 350, it will rotate 20 degrees backwards. The intention is that you use separate motion control with small steps to move the angle smoothly. If you have more experience with position control and have some tips on how it should work I can update the implementation when I'm moving things to fixed point.