-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Hide the BED Icon #2943
Comments
That's good to know, thank you for the information. |
Where you have disabled the HB? Just in Marlin config.h or also in TFT firmware (config.ini)? Heated Bed Support |
I disabled the heated bed in the marlin config. h and TFT firmware. But even then It is flashing from the heated bed and chamber in the display status screen |
This issue has been automatically marked as stale because it has had no activity for the last 60 days. It will be closed in 7 days if no further activity occurs. Thank you for your contribution. |
Good Morning Team,
Already, I do the heated_bed: 0 is disabled
in touch screen display. status screen is enabled but the chamber and bed
icon is showing alternatively. If the status screen is disabled in chamber
Icon only shown.
Regards & Thanks
Keerthana T
…On Thu, Jul 11, 2024 at 6:00 PM Zonalimitatore ***@***.***> wrote:
Where you have disabled the HB? Just in Marlin config.h or also in TFT
firmware (config.ini)?
Heated Bed Support Options: [disable: 0, enable: 1]
heated_bed:0
—
Reply to this email directly, view it on GitHub
<#2943 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5AL5PYMFFKZKVW4LUHFQ4DZLZ3H3AVCNFSM6AAAAABJZMFAIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRSHAYTCOJQGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
I will join this postulate. |
Since I am using a chamber and not using a bed, I have disabled the bed temperature. Additionally, I need to remove or hide the bed icon from the BIGTREETECH TFT50 V3 display.
I am using Marlin software on the mainboard.
The text was updated successfully, but these errors were encountered: