Homing Axes - Timeout (insufficient axes homed)

ShadowRam

I have a larger COREXY setup.

Sometimes it takes a while for the axis to home.
I've noticed, if my printer isn't already close to the home positions, there's some kind of timeout function that triggers and the homing fails.

Where can I find the command to increase or disable this timer?

Thanks,

A Former User

I don't think there is a timeout for homing but rather a predefined amount of travel to reach the limit switch.

look at your homeall.g file

ShadowRam

G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-305 Y305 F1200 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-305 ; home X axis
G1 S1 Y305 ; home Y axis
G1 X5 Y-5 F6000 ; go back a few mm
G1 S1 X-305 F300 ; move slowly to X axis endstop once more (second pass)
G1 S1 Y305 ; then move slowly to Y axis endstop

Are you saying I need to increase the 305 value to a larger distance?

A Former User

yes most likely

ShadowRam

That makes sense,

Thanks for pointing that out,

Cheers,

A Former User

G1 S1 X-305 Y305 F1200 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-305            ; home X axis
G1 S1 Y305             ; home Y axis

i'm no corexy expert, but seems like you should only need the first or two last lines of that section? probably the last two (but add the F1200 parameter , otherwise it would use F6000 from the Z move before it)

deckingman

@bearer said in Homing Axes - Timeout (insufficient axes homed):

G1 S1 X-305 Y305 F1200 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-305            ; home X axis
G1 S1 Y305             ; home Y axis
i'm no corexy expert, but seems like you should only need the first or two last lines of that section? probably the last two (but add the F1200 parameter , otherwise it would use F6000 from the Z move before it)

No, what the OP has is correct. The first line moves diagonally towards both end stops until one or other triggers. But we don't know which one will trigger first, so then we home both X and Y individually, although in practice only one axis will move because the other is already at it's stop.

Edit. We could do away with the diagonal move but it just speeds things up a bit.

A Former User

ah, its just to make it faster then. figured one of the three lines wouldn't do anything, as such it seemed a little redundant.

deckingman

@shadowram As has been pointed out, the travel distances need to be set to at least what you have for your axes maxima. This will then allow homing for the worse case scenario where a gantry starts off as far away from an end stop as is possible,