Dual motor axis end stop woes -> Bug report

[abraxas]

Using the config tool I found out a Bug that can produce serious damage when homing:

When defining endstops like this (on four 1HCL Ports):

Axis Driver Endstop Type Endstop Port Endstop Location Homing Speeds
X 112.0 Switch 112.io0.in Low end 10/5 mm/s
X 114.0 112.io1.in
Y 111.0 Switch 111.io0.in Low end 10/5 mm/s
Y 113.0 114.io0.in

the tool produces this code:
M574 X1 P"112.io0.in+io1.in" S1 ; configure X axis endstop
M574 Y1 P"111.io0.in+io0.in" S1 ; configure Y axis endstop

That produces a homing sequence moving only one end of the X Axis and one end of the Y Axis. The working code is:

M574 X1 P"112.io0.in+112.io1.in" S1 ; configure X axis endstop
M574 Y1 P"111.io0.in+114.io0.in" S1 ; configure Y axis endstop

I hope that helps someone, best, Felix

[jay_s_uk]

@abraxas one for @chrishamm

[chrishamm]

@abraxas Thanks for pointing it out, I've got a fix ready that avoids stripping the board number of following ports if they diverge. Are you sure that 112.io0.in+io1.in doesn't work for ports io0.in and io1.in on expansion board #112? I could confirm that M574 does require explicit board numbers unlike M950. I've updated the configtool again.