Repetier 2.0 A axis homing

FlyNuga

when i homing a axis gives an error message

Repetier

Does your A axis have end stops? What happened? Did it start moving, where did it stop ... What is in the console?
If you have safe homing enabled (default) you need to reverse enough to untrigger end stop or homing will be failed.

FlyNuga

yes there are end stops, writes Warning: Endstop for axis A did not untrigger for retest!

Repetier

You probably have not defined a retest distance so end stop does not untrigger or distance was too low. With safe homing enabled (default) this causes exactly that error.

FlyNuga

#define DOOR_PIN -1

#define DOOR_PULLUP -1

#define DOOR_INVERTING 1

#define ENDSTOP_X_BACK_MOVE 2

#define ENDSTOP_Y_BACK_MOVE 2

#define ENDSTOP_Z_BACK_MOVE 2

#define ENDSTOP_A_BACK_MOVE 4

#define ENDSTOP_X_RETEST_REDUCTION_FACTOR 2

#define ENDSTOP_Y_RETEST_REDUCTION_FACTOR 2

#define ENDSTOP_Z_RETEST_REDUCTION_FACTOR 2

#define ENDSTOP_A_RETEST_REDUCTION_FACTOR 2

#define ENDSTOP_X_BACK_ON_HOME 0.5

#define ENDSTOP_Y_BACK_ON_HOME 0.5

#define ENDSTOP_Z_BACK_ON_HOME 0

#define ENDSTOP_A_BACK_ON_HOME 0

#define ALWAYS_CHECK_ENDSTOPS 0

#define MOVE_X_WHEN_HOMED 0

#define MOVE_Y_WHEN_HOMED 0

#define MOVE_Z_WHEN_HOMED 0

#define MOVE_A_WHEN_HOMED 0

FlyNuga

error occurred when parking for the first time, but after restarting the end stop works correctly

Repetier

When it already fails after first move than the A axis length is set too low. As a test run from close end stop (like probably your second try) and once move to far most distance. Check A axis min/max value.

BTW: Why do you have A axis? Is it a dual X axis setup?

FlyNuga

минимальное значение оси A - 0, максимальное значение - 500 actual maximum position of A-axis 400mm, первая парковка происходит без повторного тестирования

FlyNuga

no, this is not a setup with two X, this is not a printer

Repetier

So what are all your A axis settings and what does console look like when you do a failed home compared to working A home? Need more information to see what is wrong.

FlyNuga

First home

Repetier

Message says first move triggered end stop then it went back
#define ENDSTOP_A_BACK_MOVE 4
expected end stop to untrigger, but that did not happen.
Send M111 S70 before homing and it should show end stop changes in console as well.
Normally 4mm is enough to untigger - maybe you need pull up resistor because end stop is otherwise undefined in behaviour and does not untrigger immediately?

FlyNuga

08:31:31.508 : endstops hit: x_min:H y_min:L z_min:H a_min:H

08:31:31.585 : Warning:Endstop for axis A did not untrigger for retest!

08:31:31.614 : X:0.00 Y:0.00 Z:0.000 E:0.0000 A:0.00

08:31:31.618 : X:0.00 Y:0.00 Z:0.000 E:0.0000 A:0.00

08:31:31.622 : endstops hit: x_min:H y_min:L z_min:H a_min:L

08:31:31.663 : endstops hit: x_min:H y_min:L z_min:H a_min:H

08:31:31.778 : endstops hit: x_min:H y_min:L z_min:H a_min:L

08:31:31.782 : endstops hit: x_min:H y_min:L z_min:H a_min:L

08:31:31.786 : endstops hit: x_min:H y_min:L z_min:H a_min:L

08:31:31.790 : endstops hit: x_min:H y_min:L z_min:H a_min:L

08:31:31.798 : endstops hit: x_min:H y_min:L z_min:H a_min:H

08:31:31.802 : endstops hit: x_min:H y_min:L z_min:H a_min:H

Repetier

You see end stop untriggers 30ms after the message appears. So as a first try increasing #define ENDSTOP_A_BACK_MOVE 4
to 20 and timing should match. I think this is definable in eeprom and will not delete eeprom values on simple upload. So maybe eeprom is already not containing what you think. Anyhow from the log I assume end stop is just a bit slow.

On the other side I see it changing L/H constantly after homing and question arises why it changes signal so quickly. Maybe 4mm is just not enough and you are on the edge of on/off at that position. Depends on switch type.