Homing out of range and slams xy endstops

[matt37137]

Hi, finally managed to install klipper after battle with 1.1.5. ender 3 (stock except for ducts). Downloaded printer.cfg from 2018 ender because 1.1.5. is 8-bit, only difference is stepper motors and bootloader.

Success
I was even able to do two cubes with no problem at all. It works quite good, with no changes in cura from marlin.

Problem
Buuut… Every time I try to home it slams the x and y end stop(no probe). If I manually move to 0, then it goes without problem. I changed the home speed to 20, and now it’s not slamming, but I get red triangle in mainsail every time I try homing XYZ and info that it gets out of range. I tried messing with endstop position to even 10 and min position, but it didn’t help. I wanted to add bl-touch, but with this problem I’m afraid of breaking it.

Tested triggers and they work as they should

I’m adding my log right after start and messing with homing.
klippy-4.log (3.5 MB)

I don’t know if it matters, but I was able to flash ender mainboard with this code
avrdude -p atmega1284p -c arduino -b 57600 -P /dev/ttyUSB0 -U out/klipper.elf.hex
but It went after deleting -b 57600

And I didn’t update mainsail and all, because when I did that when installing for the first time I couldn’t get klipper to work.

[Arakon]

Printer.cfg also contains the pin mappings for the endstops, and if they don’t match up with your actual board, they will never be triggered.

[EddyMI3D]

You can check the endstop status with:

https://reprap.org/wiki/G-code#M119:_Get_Endstop_Status

[matt37137]

@Arakon It match’s up.
@EddyMI3D Just like I posted. I checked edstops statuses. They are good. I only got crazy values during homing.

[matt37137]

I installed Bl-Touch and now I can’t even home Z, because printer refuse to go down. All probe testing are going great, but printer is on some level, and can’t go down. On top of that I got crazy values on Z homeing, out of my Z printer max…

[jakep_82]

These “crazy” values are normal. Klipper basically assumes it’s at a position a little beyond your min or max value for the axis (depends on endstop position) so that it can move the full length of the axis during homing. If the endstop is functioning correctly it will stop as soon as it triggers and set the kinematic position for that axis to match the configured position_endstop value.