Im trying to figure this out without asking too many dump questions… I found this guide to updating the Screen, is this what I have to do?
I guess if that is correct, then I will only need to do is change the speed, which of course I have no idea how to do.
They make is seem hard.
Copy this whole folder as is, and the two files shown to the SD card on the screen and reboot.
You can change the baud rate one the screen itself after the flash or you can edit that ini file before you flash.
Side note, I see they are requiring some things from marlin now and I am not confident we have all of them enabled. Not sure if it matters since we are not printing though…But Marlin mode will work just fine either way.
Marlin is working fine right now, I would really like to keep using the GUI mode.
Also, I really doubt the issue is with the LCD. If it were, why would the board stop all movements?, I would think that even if the LCD froze, the board would keep working.
I am going to have to find a way to use a computer(tight space) and forget about the GUI mode on the SKR.
No, the screen is sending commands one at a time the board only has a small buffer…and in the GUI mode it is also asking for information about position and temps constantly. The GUI side is very complicated, so much so Marlin has been adding code to not let it slow it down. I looked earlier this morning and it seem the most current TFT firmware is asking for 3-4 specific things to be enabled in Marlin that was not asked for before and I am sure we are not using.
Just started to encounter this issue as well. It has happened 2 times total, on 2 different gcode files. I use OS X and cannot connect to the board via USB.
Guys, I’ve been dealing with the same thing on my GTR with a tft35. I noted that in Marlin mode, everything works perfectly, and only in touch mode does it freeze. I also observed other problems, like random “too long extrusion prevented” and also some garbled pop up messages. The garbled messages pointed my sniffer to the serial cable. The stock tft35 comes with a cable that has jst on one side, duponts on the other, yet all BTT boards use jst for the tft, lol. So needless to say those connectors are barely hanging on and easily could be the issue (movement causes vibes that then create issues… no issues when not moving and communicating at same time). I did see an issue on the BTT github where other folks had the same problem, and a better shielded cable/ferrite fixed it.
I have crimpers and jst terms coming in a couple days, and plan to make a good cable with some cat6 stp and ferrite I have laying around. If that doesn’t work I’ll report back here. Of course my point of mentioning this, is if you have issues with random weird behavior/freezing when printing using touch mode, you may want to try a new cable and ferrite.
Thanks for the input. You can watch a thread without replying though.
Figured I would pop in with an update that may help. I finally sorted out printing from tft to my Gtr board, without random issues. Turns out it may have been some interaction with the way my sdcard is configured in Marlin (LCD not onboard), combined with the way the Gtr has its onboard k type thermocouple amp wired and configured, and I was using a hardware spi pt100 amp as well. After commenting out the soft spi pins for the max31855 chip in the Gtr pins file, the tft print started working well (with Marlin using the tft sdcard too).
So on the skr pro, trying to change the marlinfw sdcard (lcd vs onboard) and commenting out the onboard tc amp pins might work to fix problems with printing from touch mode.
Note though… printing from touch mode is not the same as printing Marlin mode with the lcd sd. Touch mode jitters due to using the serial for host printing (tft reads the card and sends gcode over serial). In Marlin mode using sdcard lcd, Marlin directly accesses the tft sd through hardware spi (aux2… so no jittering).
