How to. 2 or more motors on one axis. Gantry

Hello first sorry for my English
When i use 2 Y axis coupled are there some settings for the (Probe Screen V2) (Makros) ? because i think one doesn't turn wright at probing.

thx
other movements are fine

Hello, I did almost the same to have my 2 steppers in the Z axis in linuxcnc 2.9 master version but I am getting the following error, can someone help me? I am also attaching my ini and hal files to this message.

kevin19 wrote:

Hello, I did almost the same to have my 2 steppers in the Z axis in linuxcnc 2.9 master version but I am getting the following error, can someone help me? I am also attaching my ini and hal files to this message.

for a start change this in the ini file

COORDINATES = XYZ to
COORDINATES = XYZZ

Thank you!

Hello

My 3 axis machine have two motors on Y axis. Previously i had single home sensor on Y axis and run both Y motors operated in same time (XYZ). That configuration homing and works fine without any errors. Config is attached (working.hal and ini).

I've installed second home sensor at Y and trying to work them correctly as XYYZ. I've changed HAL and INI as recommended X and Z homing fine but Y axis can not be homed. After hitting Y sensors it's trying to go further and kill home sensors. What's wrong? Config is attached (luma.hal and ini)
I'm running 2.8.1.

is the last word meant to be both?
looks like a syntax error.

rodw wrote:

[KINS]
JOINTS = 4
KINEMATICS = trivkins coordinates=xyyz kinstype=b

is the last word meant to be both?
looks like a syntax error.

"man kins" says kinstype=b is correct setting. However I tried all tree ways:
1. kinstype=BOTH : same behaviour as with b and explained above. Also it is joints instead of axis in GUI.
2. kinstype=b :same as BOTH
3. skip kinstype : same behaviour as with b and BOTH but display axis correctly.

nau wrote:

rodw wrote:

[KINS]
JOINTS = 4
KINEMATICS = trivkins coordinates=xyyz kinstype=b

is the last word meant to be both?
looks like a syntax error.

"man kins" says kinstype=b is correct setting. However I tried all tree ways:
1. kinstype=BOTH : same behaviour as with b and explained above. Also it is joints instead of axis in GUI.
2. kinstype=b :same as BOTH
3. skip kinstype : same behaviour as with b and BOTH but display axis correctly.

Have you confirmed that the sensor is working in with halshow

Clive wrote:

nau wrote:

Have you confirmed that the sensor is working in with halshow

Yes. All sensor change states with halshow. And works perfectly with simply XYZ configuration.