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.31k stars 1.65k forks source link

[BUG] What could cause vertical noise after update? #2078

Closed brunoosti closed 3 years ago

brunoosti commented 3 years ago

What on this firmware (and branches) could cause vertical random noise on the TFT screen? (most noticeable on gray buttons) Like refresh rate or something like it?

I have a sidewinder X1 and upgraded the TFT from as many sources I could find, and all leads to this vertical noise on the screen. Stock TFT firmware shows no interference at all.

Already revised the wires connections inside the printer and disconnected fans with no change to the interference.

discip commented 3 years ago

Did you compile it yourself? Nothing like that here (same machine)! šŸ¤·ā€ā™‚ļø Try the following one: ASW-X1.zip !rename first!

brunoosti commented 3 years ago

The first I got was from digant on thingiverse (excelente work, by the way). Than I tested others, like the one with a dinosaur, and a couple more. Finally I installed a different UI from 3d nexus which didn't show any interference. One thing I noticed in common between the 3d nexus and the stock firmware is that both have the buttons as .bin files while the branches from this are .bmp. Would thar even make any difference? It is like some electromagnetic interference (vertical thin lines dancing along the screen) and the screen seams a bit more "pale", with not so much contrast as it could have.

discip commented 3 years ago

Have you tried the above attached?

brunoosti commented 3 years ago

Just did. Almost no noise, but much better than before. What kind of sorcery is this? Edit: now that I'm printing a piece, the noise is very similar to digant's update. Most visible over the gray buttons. If i remember right I had it worst when PID tuning myself. Than I copied the values from artillery's github page and the noise faded a bit. This is so odd.. I've tried moving the printer to another room to see if some appliance was causing it. But if it changes depending on the firmware, I'm guessing is some configuration on the screen's capability of displaying the UI?

discip commented 3 years ago

Have you changed the mainboard? What else is connected to the TFT? On mine I removed the filament runout sensor.

brunoosti commented 3 years ago

Everything is sock. Also I tested disconnecting the sensor plug. And the board fan. Had to disconnect the reset cable from the TFT to be able to flash new Marlin fw (though digant's tft fw says it is not required to open the printer). But the noise was already there before I did it.

brunoosti commented 3 years ago

Could it have something about grounding the printer? (though it doesn't how in other TFT fw)

brunoosti commented 3 years ago

Realized the interference is there even with the printer disconnected from the power with only USB plugged to the computer. And before finishing installing any TFT fw. With Artillery's stock fw the noise disappears as soon as the UI loads. It looks like it's something related to the screen brightness, but I'm not able to control it at the config.ini file.

discip commented 3 years ago

Could you please post a picture of the backside of the TFT when configured with BTT's firmware?

brunoosti commented 3 years ago

Sure : ) Thank you for your interest in this issue! IMG_20210810_180105 IMG_20210810_180019

brunoosti commented 3 years ago

Video with a lot of interference on: https://photos.app.goo.gl/6DeLjDvYfgxnGG8v9

discip commented 3 years ago

Good afternoon @brunoosti, have you tried removing the filament run out sensor? In the 1st picture the upper left.

brunoosti commented 3 years ago

yep. Removed every single wire possible.

discip commented 3 years ago

@brunoosti Have you tried unscrewing the TFT and the PCB with USB and TF card from the main body? Make sure, that it does not touch the metal body while powering on.

brunoosti commented 3 years ago

Will do that! Read somewhere, about someoneĀ else's other issue, that a plastic washer should be placed between the board and the frame (I think it was about the touching not being properly registered)

brunoosti commented 3 years ago

No difference, as expected. If there is no noise with other TFT fw, the difference is in this one. Or my board (v 1.2). I looks so much as it's some brightness issue. The fw that don't have this setting in the config file also present no noise. This one have it, but the screen can't interpret it.

oldman4U commented 3 years ago

Have you tried to remove ALL cables and connect only 5V and GND like described in the ReadMe?

Have you tried an older fw from this repository?

brunoosti commented 3 years ago

Couldn't find what you refer to in any of the 4 files in the folter readme. Either way, I had the printer disconnected from the wall plug and only USB though the main board and it had the noise. I've tried other instances of the fw, all showing this strange interference.

NO interference: https://github.com/artillery3d/sidewinder-x1-tft-firmware (stock) https://3d-nexus.com/forums/resources/artillery-swx1-marlin-1-1-9-advanced-firmware-and-gui.2/ https://www.thingiverse.com/thing:3856144

With interference: https://www.thingiverse.com/thing:4294049 https://github.com/wgcv/RAWR-TFT-Firmware-Artillery3D https://3dprintbeginner.com/custom-screen-firmware-for-sidewinder-x1-and-genius/

What differentiate those??

oldman4U commented 3 years ago

This ReadMe.

https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware

brunoosti commented 3 years ago

Oh ok! As I don't have the tools to make the proper connector, did something "similar" just now: reinstalled the TFT fw with only the USB connection to the printer (in another words, though the main board). Same interference. Imagine having to open the printer every time to flash the TFT fw, though.

oldman4U commented 3 years ago

This does not help. You have to provide power from another source than the mainboard.

brunoosti commented 3 years ago

Sorry... I understand.. for now this is a dead end for me, as I'd risk frying the TFT without the proper connection.

oldman4U commented 3 years ago

So you need someone else with the same problem doing this test. How many other users do you know with the same problem who could do this test?

brunoosti commented 3 years ago

Not many. A couple follows/likes in one or another posts on thingiverse/facebook/reddit.

oldman4U commented 3 years ago

Given the number of sidewinder sold, there must be hundreds with this issue. Finally all which are upgrading the firmware of the TFT. One has to be willing to do all the tests needed to find the problem or it will not be solved.

brunoosti commented 3 years ago

Maybe It doesn't bother people that much (or they simply don't know where to look for a solution). Right now, at this moment, I'm printing something and the noise is almost unnoticeable (it happens). Go figure... Maybe It is something with my electric grid (the strange thing being it does not affect some other firmware). It's a fact a couldn't find anything similar anywhere online.

oldman4U commented 3 years ago

Software changes over time. Most of the time it improves things. Sometimes a change causes issues but your issue is more likely a hardware issue or a combination of several things.

BTT turned off all serial ports by default which solved issues like interrupted or failed prints in case of a problem with EMI. If a user with such an issue now activates one or several serial ports he will correctly claim that activating the serial port causes issues. But he is wrong. Very likely your problem is something similar and a problem which always existed is "visible" when using the firmware from this repository.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 7 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.