Advanced Search

My guess would be that you lost the { at the end ofor possibly the one that terminates that set.

If you still have the good and bad files, then could you attach them? I don't think that I can make the compiler more helpful in it's error messages, but possibly the preprocessor could be.

How good are the clones they sell o AliExpress?

Has anyone tried one of these on a Nena 23 motors.

embeddedtronicsblog.wordpress.com/2020/06/24/tmc2160/

Note that all that I know about kinematics is that it confuses me...

Forward kinematics takes the joint positions and calculates the end effector position. This will always work and will always return exactly one solution.

Inverse kins takes the required end effector position and calculates the joint positions to achieve that. Sometimes there is no solution (because the arm simply can't reach that point). Sometimes there are multiple solutions (in fact there _generaly_ are.
So, the kins has to choose a solution. And sometimes it can lock itself in a corner, where there are solutions for the current position, and for the next position, but it would have to pass through a "wrong" position to get there.
This isn't just robots. I am sure you have been in this position with your own arms.... The difference is that you have a brain and are not blindly following what is basically a relatively simple mathematical equation which has no predictive capability.

So, back to your questiion: Homing happens in joint space, using forward kinematics. So presumably you only see the error after homing is completed, and the system switches to "world mode" and inverse kins.
Maybe your home position (in XYZABC rather than joint angles) simply isn't reachable? (or, doesn't _actually_ correspond to the joints-homed position?)

I see.
Looking at line 2968 makes me think that 'hide pyvcp' was simply not intended to be persistent by the original author:
github.com/LinuxCNC/linuxcnc/commit/6948...6d967654a7R250-R2968