[BUG] TJC display screen artifacts

[vw72]

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

I replace my Voxelab Display with an Ender 3v2 display that is the TJC model. The following artifacts exists

When autohomeing the printer, whether through the menu or through the gcode, it appears that Chinese characters are displayed on the screen. The homing works correctly.

When loading gcode with a preview file embeded, the preview on the display looks like a bunch of lines. I am using 230x180 for the image.

While it appears that the mesh is being used as the z value changes as the print head moves, the letter "Z" no longer flashes as it did with earlier versions.

These artifacts are present regardless of the slicer (Cura, PrusaSlicer, OrcaSlicer).

Printer Model

Voxelab Aquila

Model Type

OG

Your Mainboard

Aquila GD32

Other Mainboard Type

No response

Add-ons that could be involved

TJC display

ProUI?

ProUI

Bed Leveling

UBL - Unified Bed Leveling

Did you include your own configuration files?

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

[vw72]

This is with the October firmware release.

[vw72]

Changing the preview size to 180x180 solves the problem with the display of the preview.

[classicrocker883]

I do believe in the head MRiscoC fork repo something like this was mentioned, but you can also try using 200x200 for gcode preview, because that is what they were set at. but for TJC displays 180x180 might be what they are supposed to be. I will look into this and link the info to it.

When autohomeing the printer, whether through the menu or through the gcode, it appears that Chinese characters are displayed on the screen. The homing works correctly.

this is something I may not be able to figure out right away.

While it appears that the mesh is being used as the z value changes as the print head moves, the letter "Z" no longer flashes as it did with earlier versions.

this should be working for all other displays, I'll have to look into this as well. I mean technically if everything is working normally on the DWIN display, it should for TJC. I have to ask then, for the runout sensor (even if you dont have one installed) does that flash as well? you go into menu Prepare > Filament Management > Filament Settings > Runout Enable. and also if it doesnt flash, change Runout Active to HIGH or LOW

then you should also see one of the lower middle icons flashing.

I mean you do see " - ? - " flashing when it isn't homed?

[classicrocker883]

I almost forgot, that for TJC displays, it may require a certain parameter to be defined in the source code.

but to fix your issues, this should do it https://github.com/mriscoc/Special_Configurations/releases/tag/tjc

this isnt my configurations or anything, but you can use this in the time being.

[vw72]

Making the requested changes to the Runout sensor (setting it active and to HIGH and also setting it to LOW), did not cause any flashing. Before working further on this, let me install the BLT version to make sure that the issue isn't caused by the UBL version not installing properly on the GD32 board. I'll report back.

…

On Thu, Oct 19, 2023 at 11:55 PM Andrew ***@***.***> wrote: I do believe in the head MRiscoC fork repo something like this was mentioned, but you can also try using 200x200 for gcode preview, because that is what they were set at. but for TJC displays 180x180 might be what they are supposed to be. I will look into this and link the info to it. If you are able to When autohomeing the printer, whether through the menu or through the gcode, it appears that Chinese characters are displayed on the screen. The homing works correctly. this is something I may not be able to figure out right away. While it appears that the mesh is being used as the z value changes as the print head moves, the letter "Z" no longer flashes as it did with earlier versions. this should be working for all other displays, I'll have to look into this as well. I mean technically if everything is working normally on the DWIN display, it should for TJC. I have to ask then, for the runout sensor (even if you dont have one installed) does that flash as well? you go into menu Prepare > Filament Management > Filament Settings Runout Enable. and also if it doesnt flash, change Runout Active to *HIGH* or *LOW* then you should also see one of the lower middle icons flashing. — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAKGTRGCT7YWHKG72CS2ZJ3YAH723AVCNFSM6AAAAAA6BSM6YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGA4DANJYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[vw72]

I couldn't try these because there wasn't a GD32 version.

…

On Fri, Oct 20, 2023 at 12:47 AM Andrew ***@***.***> wrote: I almost forgot, that for TJC displays, it may require a certain parameter to be defined in the source code. but to fix your issues, this should do it *https://github.com/mriscoc/Special_Configurations/releases/tag/tjc <https://github.com/mriscoc/Special_Configurations/releases/tag/tjc>* this isnt my configurations or anything, but you can use this in the time being. — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAKGTRDVQM7ADIMPQ67POVLYAIGAVAVCNFSM6AAAAAA6BSM6YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGEZDCMBTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[vw72]

I installed the BLT PROUI version from here https://github.com/classicrocker883/MRiscoCProUI/releases/tag/2.1.3e-2-2-test And while it fixed the scroll direction issue, it did not fix the blinking issue regardless of how the runout sensor was set. In addition, it doesn't retain the BLT mesh after shutting down the printer (so the mesh has to be built each time the printer is used).

…

On Thu, Oct 19, 2023 at 11:55 PM Andrew ***@***.***> wrote: I do believe in the head MRiscoC fork repo something like this was mentioned, but you can also try using 200x200 for gcode preview, because that is what they were set at. but for TJC displays 180x180 might be what they are supposed to be. I will look into this and link the info to it. If you are able to When autohomeing the printer, whether through the menu or through the gcode, it appears that Chinese characters are displayed on the screen. The homing works correctly. this is something I may not be able to figure out right away. While it appears that the mesh is being used as the z value changes as the print head moves, the letter "Z" no longer flashes as it did with earlier versions. this should be working for all other displays, I'll have to look into this as well. I mean technically if everything is working normally on the DWIN display, it should for TJC. I have to ask then, for the runout sensor (even if you dont have one installed) does that flash as well? you go into menu Prepare > Filament Management > Filament Settings Runout Enable. and also if it doesnt flash, change Runout Active to *HIGH* or *LOW* then you should also see one of the lower middle icons flashing. — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAKGTRGCT7YWHKG72CS2ZJ3YAH723AVCNFSM6AAAAAA6BSM6YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGA4DANJYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[vw72]

Using Aquila-TJC_GD32_BLT-ProUI.bin (2.1.3e-2-2-test) Does fix the scrolling problem. But does not fix the display problems. However, even though the Z doesn't flash when printing, the z height displayed at the bottom of the screen does indeed change depending on the mesh at the point the printhead is printing. So the leveling does work. I've attached a screenshot. The chinese characters are still displayed when homing, whether through the menus or in gcode.

…

On Fri, Oct 20, 2023 at 12:47 AM Andrew ***@***.***> wrote: I almost forgot, that for TJC displays, it may require a certain parameter to be defined in the source code. but to fix your issues, this should do it *https://github.com/mriscoc/Special_Configurations/releases/tag/tjc <https://github.com/mriscoc/Special_Configurations/releases/tag/tjc>* this isnt my configurations or anything, but you can use this in the time being. — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAKGTRDVQM7ADIMPQ67POVLYAIGAVAVCNFSM6AAAAAA6BSM6YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGEZDCMBTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[classicrocker883]

sorry I do not see an attached screenshot.

there may not be anything I can do for why random characters show when homing.

actually, it may be because I since replaced the image with something else. but that was with the DWIN_SET, which I'm not sure how to update for TJC_SET. I suppose what I can do is change it so when TJC is enabled it will go back to the stock image as before.

as for why the Z isnt blinking im not sure. but does other things blink? like each axis coordinate when its not homed

X - ? - Y - ? - Z - ? -
X Y Z

[vw72]

Not sure about the picture not coming through. Regardless, with the exception of the screen artifact it does work so it isn’t critical that it’s fixed. As for the DWIN vs TJC SET, I noticed that the TJC_SET doesn’t have nearly as much in it as the DWIN version so this might be specific to it. The X, Y and Z coordinates values do blink prior to leveling, so the board can blink. I imagine, but can’t confirm, that the Z is blinking to show the mesh is being used but what is happening is the background color isn’t changing so it is blinking black to black instead of blue to black. None of these are show stoppers but maybe warrant a note if using the TJC board you won’t see the blinking, but can tell it is active by looking at the x coordinate to see it changing. JoeSent from my iPhoneOn Oct 25, 2023, at 9:52 PM, Andrew ***@***.***> wrote: sorry I do not see an attached screenshot. there may not be anything I can do for why random characters show when homing. actually, it may be because I since replaced the image with something else. but that was with the DWIN_SET, which I'm not sure how to update for TJC_SET. I suppose what I can do is change it so when TJC is enabled it will go back to the stock image as before. as for why the Z isnt blinking im not sure. but does other things blink? like each axis coordinate when its not homed X - ? - Y - ? - Z - ? - X Y Z —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[classicrocker883]

okay I see thanks for the update. if I am able to update the TJC_SET like I did with the DWIN_SET I will and it all should work as normal. for now I should be able to fix the homing image thing, and i'll try to do something about the Z icon blink situation.

[classicrocker883]

at the very least, the icons should be changing like so. can you see the difference?

otherwise it must have to do with whatever icons are in the TJC_SET. you did update the LCD and flash it using tjc_update.zip in the display assets folder?

[vw72]

The image is too small for me to see. :(I did flash the TJC_SET.  I wonder if I pull the icons file from the DWIN_SET and replace the icons in the TJC_SET if that will resolve it?  Regardless all the TJC_SET has is the icon file. JoeSent from my iPhoneOn Oct 26, 2023, at 8:16 AM, Andrew ***@***.***> wrote: at the very least, the icons should be changing like so. can you see the difference? otherwise it must have to do with whatever icons are in the TJC_SET. you did update the LCD and flash it using tjc_update.zip in the display assets folder? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[classicrocker883]

they are different. TJC has just one file in TJC_SET - tjc.tft

DWIN_SET's icon file is 9.ico, and comparatively DACAI's (dacai_update.zip) icon file is 9.zico which I would somehow like to update those icon files but sadly cant find information how. for DWIN its very easy, there is a tool which allows you to split .ico files and extract .jpg images from it. conversely, allows you to combine .jpg into .ico.

so ill have to see how the whole tft files work for TJC. otherwise look out for a new revision to the firmware build. ill post any other fixes pertaining to this LCD type.

[classicrocker883]

https://github.com/classicrocker883/MRiscoCProUI/releases/tag/2.1.3e-2-2

heres a new release, not much I can do for the Z offset flashing, but the homing character artifacts should be fixed

[vw72]

This fixed the homing character problem! Thanks, Joe

…

On Fri, Oct 27, 2023 at 3:31 AM Andrew ***@***.***> wrote: https://github.com/classicrocker883/MRiscoCProUI/releases/tag/2.1.3e-2-2 heres a new release, not much I can do for the Z offset flashing, but the homing character artifacts should be fixed — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAKGTRCBOT7ZIV6ST7PCZFTYBNWPPAVCNFSM6AAAAAA6BSM6YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSGUYTMNBQGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[classicrocker883]

https://github.com/classicrocker883/MRiscoCProUI/wiki/3D-BLTouch

this is how the blinking should look like. maybe there is something about the TJC display that makes the "Select" box not show well. you know when you say are in the Move menu and select an Axis to move, there should be a lighter color background over the values. you can also change the color to maybe a brighter color/shade to show better in the color settings.

[vw72]

I figured out what was causing the chinese characters! Using the December noproui version, it displays the characters, but the proui version does not. I believe this is related to the icons. In the noproui version screens with the chinese characters don't show the icon while in the proui, it does. I think the code in the nonproui is trying to display a non-existent icon. This is with the TJC display, so I don't know if it is applicable to other displays.

[classicrocker883]

its possible that TJC_DISPLAY is enabled/disabled using the -NoPro or -ProUI. ill have to take a look through to see if its within the bounds of the PROUI_EX extra features. another thing is I have since updated the ICON_'s, and some may not actually exist in the LCD's firmware. I do know there is an updated firmware version for TJC displays if you haven't installed yet, you can do so with the "private" folder and "firmware.zlib" file within display_assets. check out the README or Wiki on how to do all that.

another thing is TJC_DISPLAY code could be enabled within the PROUI_EX library, which unfortunately I cannot change anything about.

this makes me wonder if the current MRiscoC version is better in that regard, better for TJC displays. I don't use that because it has a different PROUI_EX library that's not compatible with Maple chips. I mean I could use it with the -NoPro, and possibly with the -ProUI but some options may need to be disabled, and some things may not work correctly.

[classicrocker883]

@vw72 hey just recently Mriscoc put out a fix for the TJC_DISPLAY regarding LCD brightness. can you confirm that setting the LCD brightness value in Control - Advanced settings doesn't work properly? like if you change the value between 1-100, 100 is max, and if you go for 101-200 it resets/loops.

because I have a fix in an update coming up soon.

[vw72]

Was the TJC_Display fix in the test firmware you had me run for the fix for when cancelling the bed mesh? If so, the LCD brightness can scroll up to 40 and works as expected. It does alter the brightness very well upto that point but doesn't scroll beyond.

…

On Fri, Jan 26, 2024 at 7:02 AM Andrew ***@***.***> wrote: @vw72 <https://github.com/vw72> hey just recently Mriscoc put out a fix for the TJC_DISPLAY regarding LCD brightness. can you confirm that setting the LCD brightness value in Control - Advanced settings doesn't work properly? like if you change the value between 1-100, 100 is max, and if you go for 101-200 it resets/loops. because I have a fix in an update coming up soon. — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAKGTRDP5KYL33R7UOWEVOTYQOSMTAVCNFSM6AAAAAA6BSM6YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGAZTKMZVGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[classicrocker883]

Was the TJC_Display fix in the test firmware you had me run for the fix for when cancelling the bed mesh? If so, the LCD brightness can scroll up to 40 and works as expected. It does alter the brightness very well upto that point but doesn't scroll beyond.

yes that was the intention. Mriscoc put out a fix on his repo doing that. I saw the dialog between another user and this was a good fix.

I mean I suppose I can lower pass 6, but they experienced the same kind of odd behavior when it was <255. and also <100.

well I'm glad we were able to bang out these issues

[github-actions]

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.