search

bigtreetech / BIGTREETECH-TouchScreenFirmware

support TFT35 V1.0/V1.1/V1.2/V2.0/V3.0, TFT28, TFT24 V1.1, TFT43, TFT50, TFT70
GNU General Public License v3.0
1.32k stars 1.65k forks source link

[Question] TFT70 not sending commands to the printer. #2906

Closed IoakeimSogiakas closed 8 months ago

IoakeimSogiakas commented 8 months ago

Well this is a weird issue. I have a skr v3 with custom firmware on it that if needed I will share (both on bugfix and on stable release). The issue is as follows, the screen works fine in marlin mode and does connect with the board, or at least I think it does, (tft in listening mode). However although it can display all the numbers temp bed size etc, it cannot or rather will not send to the printer any commands. I can send the firmware for both the board and the screen if needed.

digant73 commented 8 months ago

TFT listening mode feature (pressing on the button on the Connection menu) is needed only by few mainboards (e.g. MKS GENL 1) when printing from mainboard's USB port. That was due to the bus shared by mainboard and TFT. When in TFT listening mode, the TFT simply listen on serial line but doesn't send any gcode. For your mainboard you need to always have TFT listening mode disabled

IoakeimSogiakas commented 8 months ago

oh so it is not connecting correctly then... RIght? the board is a skr 3 and it is connected via uart also here are the files

IoakeimSogiakas commented 8 months ago

FM Fles.zip

IoakeimSogiakas commented 8 months ago

"For your mainboard, you need to always have TFT listening mode disabled". How do i do that?

digant73 commented 8 months ago

You reported that you properly see temps etc... displayed on TFT so the baudrate configured on mainboard and TFT seems to be ok. So you only need to disable TFT listening mode pressing on the ON/OFF button on Menu->Settings->Connection menu. The TFT listening mode text displayed on top of the screen must disappear

IoakeimSogiakas commented 8 months ago

thank you that "fixed" it

github-actions[bot] commented 5 months ago

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.