Testing slaved axes under stepconf

I just had a heart stopping moment where I thought that one of the drivers in my G540 had bitten the dust.

I had a basic config running last night, machine (X-Carve) has dual Y axis motors connected to Y and A on the G540. It worked under Linuxcnc but was a bit slow so this morning decided to run some speed tests under stepconf.
Only one Y axis motor moved. I swapped cables and was about to open up the G540 to swap driver boards when I decided to test again using linuxcnc. Both motors move as expected.

It seems that when you do an axis test under stepconf, any slaving configuration is ignored and just the first Y axis entry is used. I did a bit of browsing but couldn't find anything to confirm this.

Has anyone else had a similar experience? Running LinuxCNC 2.7

Geoff

thats possible as stepconf is only meant as a starting point and cannot cover all combinations of axes .
and does not know over changes you have made in the hal file

stepconf is just a starting point , to get you going

That makes sense. A bit of trap for the inexperienced though.

geoffs wrote:

That makes sense. A bit of trap for the inexperienced though.

Yep, caught me out and had me scratching my head for a while. Using exactly the same G540 and two Y axis steppers as you.

Perhaps a bold note in the documentation or even a note in the stepconfig GUI would be a worthwhile addition in the future?

Cheers,
Jason.

How was the second y axis configured using stepconf?

cmorley wrote:

How was the second y axis configured using stepconf?

Take a look at the photo attached. To get everything working as it should the one of the Y axis had to be inverted as did the E stop in at pin 15.

Cheers,
Jason.

Yes The test code only looks for the first pin with the axis name in it.
I'll think about what could be done about that.

Chris M