Closed elementfoundry closed 4 years ago
I think it is necessary to activate Stealth Chop for sensorless homing. Regarding your log, i think it is disabled.
Recv: stealthChop false false false false
See also issue #15424
unless I'm missing something it is enabled in Configuration_adv.h
Had the same problem on my SKR E3 Mini V1.2... StealthChop is enabled. No triggering of 'endstops' on hit whatsoever. Any advice would be helpful.
Did you double check the wiring, jumpers and settings?
Diag Pin at the driver has to be connected to the Board.
This one is from TMC2209 V1.2 Bigtreetech
Unused Diag Pins at Bigtreetech Drivers (maybe E and Z) has to be removed! Otherwise you get in trouble with the endstops! I don't know, if there is an issue with Watterott or Fysetc too.
Fysetc V3.0 seems to have same pinning as BTT
This one is from Watterott and the pinning seems to be different.
Connected to the Mainboard here:
And activated the jumpers for X and Y Endstops over the DIAG Pin. The other ones have to be removed.
Disconnect the mechanical endstops:
In Configuration.h
#define X_MIN_ENDSTOP_INVERTING true // Set to true to invert the logic of the endstop.
#define Y_MIN_ENDSTOP_INVERTING true // Set to true to invert the logic of the endstop.
In Configuration_adv.h
#define SENSORLESS_HOMING // StallGuard capable drivers only
Upon further investigation it would appear that Marlin is not putting the tmc2209 drivers into stealthchop mode before moving the axes that require them before homing. Setting stealthchop manually before homing seems to work. So I think the solution to this problem is for marlin to check for stealthchop and enable if necessary before any sensorless homing.
@elementfoundry since 2.0 was just released a few days ago has this changed this issue at all?
@boelle - this was using marlin 2.0
Upon further investigation it would appear that Marlin is not putting the tmc2209 drivers into stealthchop mode before moving the axes that require them before homing. Setting stealthchop manually before homing seems to work. So I think the solution to this problem is for marlin to check for stealthchop and enable if necessary before any sensorless homing.
@elementfoundry How did you come to that conclusion? any way to test the theory?
I'm having a similar issue (https://github.com/MarlinFirmware/Marlin/issues/15848) but in my case sensorless homing always triggers (as soon as it starts) with a threshold value (with my current config 160) but it never does so when I set the number lower than that (159). As far as I can tell I do have stealhchop enabled when it homes:
Driver stepping mode:
M569 S1 X Y Z
M569 S1 T0 E
M569 S1 T1 E
But there may something I'm missing?
I saw your PR (https://github.com/MarlinFirmware/Marlin/pull/16153) and tried flashing that to test if it changed anything for me, but no luck, so I'm afraid mine is unrelated 😞
@uorbe001 : i came to that conclusion due to the line:
* TMC2209 requires STEALTHCHOP enabled for SENSORLESS_HOMING
in configuration_adv.h, the comment from @hammerhead2k2 at the beginning of the thread, and observing behavior on my printer when manually putting the drivers into stealthchop before homing with sensorless homing turned on.
in your case, it sounds like its a sensitivity issue, which was different from what I had written the patch for.
@elementfoundry is the issue still the same with all the updates in the last 9 days?
btw, who can confirm there is an issue? use the same configs as OP and the same hardware if possible
@boelle - still seems to be an issue with 2.0.1 - sensorless homing fails to trigger when set to spreadcycle with tmc2209 drivers
TMC2209 requires Stealthchop for sensorless homing
@elementfoundry is this still a problem? btw use bugfix 2.0.x and not 2.0.1, the first one is updated more than the other
Lack of Activity This issue is being closed due to lack of activity. If you have solved the issue, please let us know how you solved it. If you haven't, please tell us what else you've tried in the meantime, and possibly this issue will be reopened.
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.
Hardware: Bigtreetech SKR 1.3, Bigtreetech 2209 V1.2
I've tried enabling sensorless homing with my setup, but the "endstops" never trigger.
Debug info (this was captured during a G28 home all axis)