Skip to content
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

TFT32 - After update to V3.0.6 no Heat Bed is showing up #483

Closed
BenediktS opened this issue Nov 22, 2020 · 6 comments
Closed

TFT32 - After update to V3.0.6 no Heat Bed is showing up #483

BenediktS opened this issue Nov 22, 2020 · 6 comments

Comments

@BenediktS
Copy link

I just updated my "MKS TFT32_L V3.0" to the firmware version v3.0.6 .
After the update the heating bed is not showing up anymore.

It is not showing up in the pre heat screen nor in the printing screen.
In my configuration file this are the hotbed lines:

cfg_custom_bed_flag: 1 # Please choose 1:Enable bed 0:Disable bed
cfg_max_hotbed_temperature: 150 # The max target temp of heated bed

Did i miss something?

@mks-viva
Copy link
Collaborator

Hi! You can check your baudrate settings in your config file.

@BenediktS
Copy link
Author

BenediktS commented Nov 25, 2020

I checked it.
It is the same baudrate that is configured on the marlin board.

I could see the sprayer temperature and can use it.
I can also print without problems.
I could only not see the hotbed.

Is the sprayer temperature using a different communication then the hotbed?

@mks-viva
Copy link
Collaborator

Marlin firmware have config hotbed?

@BenediktS
Copy link
Author

I have to update the firmware i will get back to you. I think i can test it next weekend.

@mks-viva
Copy link
Collaborator

Waiting for your good news

@mks-viva
Copy link
Collaborator

mks-viva commented Jan 6, 2021

Hi! I will close this issues temporarily.

@mks-viva mks-viva closed this as completed Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants