- Posts: 15
- Thank you received: 0
Custom kinematic - TCP compensation Joint following Error
6 years 3 weeks ago #185091
by Xpertmill
Hello Everyone.
We use a custom kinematic (based on maxkins.c) for a university project. The axis we are using is a rotational axis (b-axis), which is mounted on the x-axis and z-axis. The rotation of the b-axis is getting compensated to the TCP position. However if i press the machine-off button in linuxcnc and the b-axis has moved (and got compensated in x and z) I get a joint-0 following error (which is the joint of the x-axis).
Can someone tell us, what we can do that this error does not occur anymore?
Here you can find the kinematic we use (aimiskins.c):
github.com/AIMIS-FYT/AIMIS_PRINTER/tree/master/kins
Kind regards,
Michael
We use a custom kinematic (based on maxkins.c) for a university project. The axis we are using is a rotational axis (b-axis), which is mounted on the x-axis and z-axis. The rotation of the b-axis is getting compensated to the TCP position. However if i press the machine-off button in linuxcnc and the b-axis has moved (and got compensated in x and z) I get a joint-0 following error (which is the joint of the x-axis).
Can someone tell us, what we can do that this error does not occur anymore?
Here you can find the kinematic we use (aimiskins.c):
github.com/AIMIS-FYT/AIMIS_PRINTER/tree/master/kins
Kind regards,
Michael
Please Log in to join the conversation.
- tommylight
-
- Offline
- Administrator
-
Less
More
- Posts: 22010
- Thank you received: 3
6 years 2 weeks ago #185645
by tommylight
Replied by tommylight on topic Custom kinematic - TCP compensation Joint following Error
Can you post the hal and ini files so we can have a look ?
Also some more info on the system would help, like what motor/drives are in use, how is the B axis mounted in relation to X and Z, etc.
Also some more info on the system would help, like what motor/drives are in use, how is the B axis mounted in relation to X and Z, etc.
Please Log in to join the conversation.
Time to create page: 0.066 seconds
