Marlin: [bugfix-1.1.x] SanityCheck X_MIN_ENDSTOP_INVERTING

[Ludy87]

Description

I try to activate SENSORLESS_HOMING and get the error.

   SanityCheck.h:1446: error: #error "SENSORLESS_HOMING requires X_MIN_ENDSTOP_INVERTING when homing to X_MIN."

   #error "SENSORLESS_HOMING requires X_MIN_ENDSTOP_INVERTING when homing to X_MIN."

Steps to Reproduce

1. activeate SENSORLESS_HOMING in Configuration_adv.h
2. compiling

Configuration.zip

sorry for my bad English

[psavva]

In your configuration.h file, change

define X_MIN_ENDSTOP_INVERTING false

to

define X_MIN_ENDSTOP_INVERTING true

[thinkyhead]

Yep! We often use #error to tell you what you need to change.

[Ludy87]

When set to true, the ENDSTOP is triggered and is not open!

[marcio-ao]

Do you have the pullup resistors enabled?

[Ludy87]

No, why?

EDIT: Yes, this error is same!

[marcio-ao]

@Ludy87 : I'm just trying to narrow down the problem. If the endstops pullup resistors had not been enabled, it would explain why sensorless homing was not working for you.

[Ludy87]

Real? Before have i update install, no error!

[marcio-ao]

@Ludy87 : I believe you when you say something is wrong, I just don't know what.

[thinkyhead]

@Ludy87 — Try M502 followed by M500 and re-start the machine to see if it helps.

[thinkyhead]

@marcio-ao — The line that was removed setting diag1….
Should it perhaps just have been _changed_ instead?

[marcio-ao]

@thinkyhead : I could have changed it to the following:

st.diag1_active_high(0); // For sensorless homing

However, this is supposed to be the power up default. I suppose people could be having issues if they upgraded their FW and did not cycle the power on their printers.

[thinkyhead]

It's certainly possible for the stepper drivers to maintain voltage —and thus previous state— across reboots. But it sounds like the issue would indicate corrupted state.

[Ludy87]

sorry, it was a short on the board. Apologize a lot!

[github-actions[bot]]

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.