Hello,

today I did the steps from tommy`s link.
At the end i played around with the P and FF1.
After arount 50 different tests, slowly the hard errors dissapeared and at the end i found the best working configuration with P=15 and FF1 =1

So I configured this parameter on all 3 Axes and it works.
Only one last problem is the speed for "Go To Home"
Is ther a info where i can find the different settings for all moves?
Jogging Speed is OK and i can change ist via the GUI.
Homing Speed is also OK, but "Go Home" is far to fast.

Best regards
Jens 

Here is my config (with working Linear-Encoders​ & Closed Loop Stepper)
 
 ​​​​​​

So, just to side track a little....

Where would you stick the control? Assume the machine is open, cause its a wood machine.

Would you put an arm on the machine frame, our would you put it on the stand? I feel like cause the stand is optional/variable, mounting it to the machine is better. off to the right side (viewed from the front) vertical 15" capacitive touch. with a little printed housing for a clusters of physical buttons and e stop.

Thoughts?

 

ln -s /usr/lib/linuxcnc/modules/maxkins.so /usr/lib/linuxcnc/modules/matrixkins.so
# ll /usr/lib/linuxcnc/modules/ma*
-rw-r--r-- 1 root root 15240 окт 23 01:43 /usr/lib/linuxcnc/modules/maj3.so
-rw-r--r-- 1 root root 15680 окт 23 01:43 /usr/lib/linuxcnc/modules/match8.so
-rw-r--r-- 1 root root 14800 окт 23 01:43 /usr/lib/linuxcnc/modules/matrix_kb.so
lrwxrwxrwx 1 root root 36 ноя 20 22:52 /usr/lib/linuxcnc/modules/matrixkins.so -> /usr/lib/linuxcnc/modules/maxkins.so
-rw-r--r-- 1 root root 15512 окт 23 01:43 /usr/lib/linuxcnc/modules/max31855.so
-rw-r--r-- 1 root root 14704 окт 23 01:43 /usr/lib/linuxcnc/modules/maxkins.so

Start = abort,
=============
Debug file information:
Note: Using POSIX realtime
4.hal:16: /usr/bin/rtapi_app exited without becoming ready
4.hal:16: insmod for matrixkins failed, returned -1
1358
Stopping realtime threads
Unloading hal components
maxkins: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
<commandline>:0: unloadrt failed

ЧЯДНТ? What I Do Wrong?

Grazie per la risposta,
Si, si tratta della funziona Hal. Ho letto come impostarla, ma sono in difficoltà nell'imdividuare i piedini della parallela. Pensavo di usare il p. 12 come ingressa di M8, il piedino 3 come segnale di PAUSE, e il piedino 13 come segnale di RESUME. Sono segnali TTL in uscita da un integrato cd 4017.
Un saluto 

SOLVED  -
 matrixkins is a standard technique for correcting the curvature of the portal in the LinuxCNC 2.10 kernel (and above). The issue of mutual correction of XYZ coordinates is resolved by specifying correction coefficients. However, this component is provided for single-engine machines, i.e. XYZ schemes. To use this software correction, changes must be made to the ini machine configuration files. Hal file does not require correction. MAN does not give these examples, см. github.com/LinuxCNC/linuxcnc/blob/master...ents/matrixkins.comp . However, in the ini file 
instead of -
KINEMATICS = trivkins coordinates=XYZ
set -
KINEMATICS=matrixkins
then explicitly specify non-zero correction factors, for example -
halcmd setp matrixkins.C_yx -0.00252427184466  

You will find the coefficient values and the transformation matrix in MAN.
The halcmd setp matrixkins.C_yx correction command -0.00252427184466 can be executed in the terminal (not while the machine is moving!), i.e. the parameter can be changed on the fly.

In case you have a multi-engine XXYZ configuration, etc., you need to change the source code of the matrixkins component ( github.com/LinuxCNC/linuxcnc/blob/master...ents/matrixkins.comp ), similar to  www.forum.linuxcnc.org/38-general-linuxc...xyyz?start=20#338894

+ sudo halcompile --install matrixkins.comp


 

For real-time kernel5.4.254 or 5.4.290, there is only version 2.9.4. Apparently, this patch isn’t there?

As planned, I installed 2.9.4 with both 254 and 290 cores. The test result is bad - excellent jitter (less than 1000), but the same sensor response error (when performing G38.5, the sensor moves, the response stops, stops and flies out error The sensor was activated during working movement - but in the g-code program there are no commands of the form G1-G3 at all!). 
In addition, a completely new mistake for me is misalignment of axes (joints)! First, Joint0 (this is the first X motor), then Joint3 (the first Y motor) - XXYYZ circuit.

Good morning everyone.
I need to replace an old Siemens CNC.
I'd like to try Linux CNC, but the machine is a boring machine with a Z-axis that can be controlled manually or via CNC.
Let me explain. The Z-axis performs normal axis reference and moves in jog+ and jog- directions, with the position controlled by an optical scale.
However, the operator can press a mechanical selector, which allows the axis to be moved with a mechanical handwheel and, when desired, re-engage the axis in the CNC.
Clearly, the current CNC disables the axis drive when the mechanical handwheel is selected.
The axis on the current CNC goes into park mode, meaning the commanded position follows the feedback position, and when the mechanical handwheel is disengaged, the CNC does not enter a following error.
With Linux CNC, I could disable the drive and move the axis with the mechanical handwheel, but as soon as I disable the handwheel and enable the drive again, the CNC displays the following error because the commanded position doesn't follow the feedback position.

Is there a way to mimic the behavior of the Siemens CNC?

Thanks for support

Fantastic!

"zstd: error 70 : Write error : cannot write block : No space left on device"
Boot device too small most likely.

A fresh install is never wrong.
You should be able to use a swedish I mean german version.
You seem to have missed a step where it says it will dismount the cd-rom and restart or something like that. A guess.
Install all in one large partition, or at least 100 Mb in the boot partition if you are required to have one.

This seem to be the proper sequence to remove raspi-firmware, you'll need to do that after a new install.

You guys rock. Thank you so much for pointing that out. I was editing hal with libre office instead of text editor. Added the line about offset mode and now the servos are quiet and don't move or jump when enabled.