Yes your right, no movement at all
Switch sounds normal
OK, now I am totally confused. You want to home but printer does not move at all? Did you ever print something with klipper? What is the problem? If you do not go through the install steps of Klipper, noone can do that for you…
Did you create the printer.cfg on your own or did you download a ready to go printer.cfg?
You might increase your “homing_retract_dist” value to free the endstop switch before it can be triggered again.
This parameter has to be added to your [stepper_x] and / or [stepper_y] respectively.
You can also set this value to 0 to disable the second home.
See:
https://www.klipper3d.org/Config_Reference.html#stepper
It was partially created based on answers creality V2 host server
Let me read up and get back to you
Hi Royce,
Increased HRD
still getting
[ERROR] 2023-01-15 07:28:36,709 [root] [gcode:_respond_raw:467] ++++++++++++++msg:!! {“code”:“key23”, “msg”:“Endstop x still triggered after retract”, “values”: [“x”]}
MCU ‘mcu’ shutdown: Stepper too far in past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.
Here is the most recent klippy log
klippy.log (1).txt (262.8 KB)
All open
screenshot_deleted
Are you running on Creality Sonic Pad ?
yes via remote desktop in the same network
That is a problem. That Klipper version that is used there does not support the complete klippy.log format.
Support is quite difficult this way.
Klippy Sonic pad knows home cordenents but will not sync with printer