Advanced Search

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

Cześć.
Jak udało Ci się wyświetlić paski obciążenia servo w Probe Basic? Czy zrezygnowałeś z nich? Ja również używam tej karty od Dmitry'ego i jestem ciekaw, jak to rozwiązałeś.

Hi,I am currently developing control software for a 3-axis robotic arm using LinuxCNC together with a Mesa 7i96S motion controller. Everything has worked well so far, until I ran into issues related to the Denavit-Hartenberg (DH) parameters defined in the HAL file.As a base, I used the Puma560 example, which worked correctly with the default DH parameters. However, after replacing them with my own DH values, I started encountering problems. Specifically, I’m unsure how to properly handle fixed theta values within LinuxCNC’s DH parameter structure, since there seems to be no direct way to set them.I have created a precise mechanical model of the robot and derived the necessary DH parameters accordingly. Despite this, I consistently receive an "Inverse Kinematics Failed" error whenever I attempt to run the "Home All" sequence for the joints.I’ve attached both the DH parameter values and a visual representation of the robot. The actual robot has 5 axes, but for the purposes of this project, I am controlling only 3 of them using stepper motors to keep the setup simple. I would be very grateful for any advice or guidance on how to resolve this issue.Best regards,
Lex 

in the lower left corner you has the 2 check boxes ... check both and do the restart solution and activate solution ... 

everything should be written in the local memory ... but maybe you will probably need the initCmds file 

do not forget to activate DC .. because it is not active from default .. just SM synchro

if you are lazy, just use the console   to generate right configuration ... double click on the .exe ... then "c -i" enter .. then drag and drop your full master config export...