[BUG] (shorFysetc S6 TFT81050 С экрана в меню настроек вы не можете увеличить чувствительность без датчика, только уменьшить. t description)

[Roman-ru]

Configuration.h.zip
Configuration_adv.zip

Bug Description

My Configurations

Required: Please include a ZIP file containing your Configuration.h and Configuration_adv.h files.

Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

Additional Information

• Provide pictures or links to videos that clearly demonstrate the issue.
• See How Can I Contribute for additional guidelines.

[boelle]

Please add som description in english, follow the template

[sjasonsmith]

Google translate translates the title as this:

(shorFysetc S6 TFT81050 From the screen in the settings menu, you cannot increase the sensitivity without a sensor, only decrease it. t description)

It is a duplicate of this one which was already closed due to missing information
#18497

@Roman-ru, it sounds like there might actually be an issue here. Thank you for providing configuration files. We still need more information to know if this is a bug.

1. Please edit the title to be in English
2. Update the description to fill in:
   • Steps to Reproduce
   • Expected Behavior
   • Actual Behavior

It is ok if you use Google Translate to provide English descriptions. Please let us know if you do this, though, since it can occasionally change the meaning of things for you.

[Roman-ru]

https://cloud.mail.ru/stock/m97ncBhrYeH7J4wYSoXhwAgm
I made a video, maybe it'll help.

[Roman-ru]

I'm an ordinary PC user, and I don't know English, so it's hard for me to understand what's needed. In advanced settings - sensorless Homing there are buttons - and q, so, when you press - the value decreases, everything is fine, but when you click on the q except for the sound of pressing nothing happens the value does not increase.

[sjasonsmith]

Please test the change in this pull request. I believe it will fix your problem, but I do not have the hardware to test it.
#18554

[sjasonsmith]

Closing, since @Roman-ru confirmed on a PR comment that the problem is now fixed.

[github-actions]

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.