-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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
[BUG] M504 interferes with ST7565 SPI LCD and causes it to clear on BTT v1.4 #18133
Comments
Seems the defined A0 line is taken low during the execution of M504... Tested with: #define DOGLCD_A0 P0_16 and with default setting: #define DOGLCD_A0 P1_22 |
Issuing the command (set LCD contrast) M250 C200 brings the display back... When issuing the M504 command...and read back M250 contrast value, it is modified.... After reset: M250 After M504: M504 After M501: echo:; LCD Contrast: |
@richardklingler still an issue? |
This is still happening with 2.0.6 bugfix... |
@richardklingler — Enable |
Does it also happen with |
This is what M43 returns: M43 |
Interesting is that M504 changes the contrast value which gets returned by M250: M250 |
This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days. |
So no comment on this? |
Your configs updated to current bugfix for testing. |
Current bugfix this still happens
|
Found it... preparing PR |
If you take a look at the above PR it fixes the contrast corruption for the "M250 M504 M250" test. |
Is now part of marlin. |
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. |
Bug Description
Sending the command M504 causes a ST7565 SPI LCD first to smear on the left side, then on the second M504 command it is cleared...
My Configurations
configuration.zip
Steps to Reproduce
Expected behavior: [No influence on LCD]
Actual behavior: [First M504 command sent]
Actual behavior: [First M504 second sent]
The text was updated successfully, but these errors were encountered: