-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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] TFT35 does not preview only 95x95 sketches #2916
Comments
Which one of the five gcode files displays the thumbnail properly for you? |
@rlneumiller Sorry. None of them. I forgot to attach it. there must be 3 resolutions in the file 70x70, 95x80 and 95x95 for the thumbnail to be displayed. |
This looks like an issue with the gcode output of your slicer (assuming that The thumbnail signatures in the gcode files you've provided that contain a single thumbnail are not formatted properly. Here is a corrected version of your 95.gcode that should work. If this doesn't work and you are building your own firmware, set |
@rlneumiller unfortunately, Your corrected file does not display a thumbnail, and my version of Configuration.h does not have a THUMBNAIL_PARSER |
The Marlin default setting for THUMBNAIL_PARSER is THUMBNAIL_PARSER = 0 (which requires 3 thumbnails in the gcode file) |
@rlneumiller I made changes to Marlin #define THUMBNAIL_PARSER 1 And it doesn't work. with the file corrected-95.zip . And I don't understand how changes in Marlin can affect what is displayed on the TFT35 display, because the thumbnail is read before the file is sent to print. |
Apologies. I referenced Marlin in error and lost sight of the fact that this display is essentially a remote control for Marlin. Your desired behavior would require adding functionality to TFT to allow for control of the thumbnail format via a setting within TFT's config.ini. You could still workaround by modification of Configuration.h as described earlier but within the TFT source tree (see below), which would then require rebuilding BIGTREE_TFT35_V3.0_B1.27.x.bin (or whichever bin matches your hardware), and ensuring that your slicer is outputting the proper thumbnail header. Ultimately this issue is more of a feature request than a bug. |
@rlneumiller Thank you for pointing out the course of action. I have reassembled the firmware for the TFT screen. With the THUMBNAIL_PARSER =1 parameter, thumbnails are displayed with a delay, but they did not appear for the corrected-95 file. Therefore, I use the THUMBNAIL_PARSER =2 parameter, in the slicer settings I chose the PNG format and the sketch size 95x95, gcode turns out to be smaller than BTT 70x70, 95x80, 95x95. I will have to choose to display quickly or a smaller file)))
Originally posted by @discip in SoftFever/OrcaSlicer#1894 (comment) This is an obvious loop nesting error. It turns out that each subsequent screen size requires the presence of a thumbnail in Gcode for the previous 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. |
Description
The TFT35 preview sketches with a resolution of 95x95 G-code. When you specify the BTT TT thumbnail format and size 95x95 in OrcaSlicer, they are not displayed. The Cura plugin generates 5 thumbnail resolutions at once. I have experimentally established that the minimum number of image resolutions required to display on the TFT35 B1 V3 screen is 3 pieces: 70x70, 95x80 and 95x95. I have attached all the options in the archive. Only one of them displays a thumbnail on the screen.
gcode.zip
The text was updated successfully, but these errors were encountered: