forum.cncdrive.com

today i hit home all.
while z had already homed and y was homing i changed focus on screen to vcarve program
homing on the x axis didnt happen.
i have been able to replicate this.
bug?
using 029 on that machine

I have similar problem today. I have X and A as slave axis.
I hit HomeAll. While gantry goes to the homing switches, I am click on the "CLOSE" button for close gcode.
Homing happen, but after this A gantry is not moves. On jog only X moves, looks like A axis was unslaved.
After restart UCCNC homing was success.
Using 2033 ver

OK, but while the gantry is homing the file close button does not do anything, because if there is an IsMoving condition then the buttons not doing anything, they just executing a return when you pressing it while moving, so pressing that button should make no effect on the homing process at all.
And the homing happens in a backgroundworker thread, so whatever happens in the GUI thread that backgroundworker thread is independent and should still keep working and going.

With the gantry you say the axes remained unslaved, is there dual home switches configured for that axis?
I will check how is it exactly handled when the axis with dual home switches are homed, maybe there is an error there about if the axis is stopped while homing and when it is unslaved to square the gantry, I suspect there must be something there if the motors remained unslaved.
And just to make sure: You using the standard home all button code and not a macro with your own code which do an unslaving function call?

And could you please post your profile to let us test this with your settings?

Hello Balazs!
Yes, this is dual home switches configured for that axis and I am use standard refall home button #113
It's looks like after homing A axis unslaved, but if I am next time click on the refall button, both axis moves to homing switch again and homing complete. After that slave axis is not moves again. Only program restart solve this issue.
My customers reported that this issue any time and may be without any action with GUI.
Profile file they send later and I will post it.
Thank you!

Hello Balazs!
The profile attached.

Thanks Andrew, my collegue said he will debug this in the afternoon.

Hi Andrew,

My collegue has finished testings this, the homing with your profile file to see if the axes remains unslaved, but they always keep slaved whatever we do.
What we've tried so far is to Home all and after checked the step/dir signals of both axes to see if they still move together.
We've jog-ed them after homed all and also we've tried to do MDI and g-code execution, but we do not see the issue.

I would like to ask for some more informations from you, because maybe you doing something differently than we did?!
So, if you could describe me the exact step-by-step procedure of what you doing to reproduce the problem would be probably helpful.
And also please confirm that the controller is UC400ETH? We've tested now with a UC400ETH, but wanted to make sure you also using that.

Hello Balazs!
Yes, controller is UC400ETH.
My customer said that this problem appears periodically and in different situations.
Let's see if this will happen again and it may be clear in which situation.