-
-
Notifications
You must be signed in to change notification settings - Fork 19.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensorless homing with TMC 2130 not working when homing all axes at once #9471
Labels
Comments
//#define QUICK_HOME make sure QUICK_HOME is disabled |
Thanks a lot! I would never have found that one. Works perfect! |
See if adding this to the very end of #if ENABLED(SENSORLESS_HOMING)
safe_delay(500); // Short delay needed to settle
#endif |
thinkyhead
added a commit
that referenced
this issue
Feb 19, 2018
thinkyhead
added a commit
that referenced
this issue
Feb 19, 2018
AnHardt
added a commit
to AnHardt/Marlin
that referenced
this issue
Mar 29, 2018
This is a remainder of an unsucsessfull try to fix sensorless quickhoming (MarlinFirmware#9471). A positive effect was never confirmed. Half a second is not short. If this would be a fix for anything, the same fix would be nedded in delta-homing.
AnHardt
added a commit
to AnHardt/Marlin
that referenced
this issue
Mar 29, 2018
This is a remainder of an unsucsessfull try to fix sensorless quickhoming (MarlinFirmware#9471). A positive effect was never confirmed. Half a second is not short. If this would be a fix for anything, the same fix would be nedded in delta-homing.
This was referenced Mar 29, 2018
thinkyhead
added a commit
that referenced
this issue
Sep 22, 2018
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi
Description:
I have some issues using sensorless homing feature of Fysetc 2130. SPI - resistor is soldered out, CF4 and CFG5 are properly soldered. When Homing via GCODE "G28 X", X homes successfully by sensorless homing and detects the end of the axis. Same for "G28 Y". However, if I say "G28" or "G28 XY", both axes are raming into the end without detecting anything.
Expected behaviour:
Proper detection of sensorless X and Y endstops
Actual behaviour:
"G28 X" and "G28 Y" working fine with sensorless homing but "G28 XY" and "G28" do not (ramming without detection)
Steps to reproduce:
Configuration.zip
Thanks in advance
The text was updated successfully, but these errors were encountered: