Creality 4.2.7 screen "Clicking" on Marlin 2.0.7.2 [BUG] (bug summary) #21408
Comments
|
Please download |
|
compiled the bugfix, same issue. clicking display still. |
|
Video of printer running bug fix 2.0.x still clicking |
|
I have exactly the same issue with the BugFix 2.0 Branch (as of today 28 Mar 21). I just flashed from Creality stock to the Marlin 2.0 bugfix branch. I have a Ender 3 (Non Pro) and the 4.2.2 board. This pressing/clicking happens on any menu for me. (never had it before the flash). Its unusable. https://youtu.be/831YTv_S9Ls |
This comment was marked as spam.
This comment was marked as spam.
|
I just took the config files from the Hotfix branch for the Ender 3 (standard) for 4.2.2, I added several missing probe related values to and compiled against Marlin 2.0.7.2 (as 4.2.2 doesn't exist for this release) and flashed. I can report that the same clicking still exists on 2.0.7.2 (if its of note I do have a BLTouch 3.1 with the single cable connection to the 4.2.2 board and the ZStop disconnected). An observation > this only seems to happen largely when the printer is 'doing something', when its on but stationary this is happening less frequently (but is still happening). |
|
Okay - I have just compiled and flashed Marlin 2.0.6.1 to my Ender3 (standard) with the Creality 4.2.2 board and I can confirm the clicking/selecting problem has gone completely and normal functionality has returned. (I used the Ender3 Pro 1.5) config files and modified the name and a few BLTouch related settings for my configuration. (the config doesn't exist currently for my setup for that version (2.0.6)) Observations:
|
This comment was marked as spam.
This comment was marked as spam.
|
There are a rash of issue emerging that are related to build platform version please try latest bugfix known to have the issue Make sure this is under the [common_stm32f1] section not the [common_stm32] section |
I don't know if it's related to #21429 As 2.0.7.2 didn't have the platform change in it for stm32f1, and he reported the same issues. It was still @ 6.1 Worth a shot though. Also, might be better to see if he can narrow the window between 2.0.6.1 and 2.0.7.2 by stepping forward a release and see if it still exists and then backwards a few weeks and so forth. |
|
Any news about this? this bug is still there and i can confirm that this happen also on Ender 5 with silent board 4.2.7 and last bugfix relase.....any hint or solution? |
|
Duplicate of #21204 |
|
@thisiskeithb How is this a duplicate, the symptoms are very different to that of#21204? |
issue seems different and also Ender 5 is affected. |
I can confirm that the problem is related to build plate heating up i will test 2.0.6.1 as soon as i can, trying to know what change was made to put ender 4.2.7 on this bug |
It cant be because I like the OP have this issue as soon as the machine is turned on, without even heating the bed. |
Im afraid this did not fix it. I just took the lates BugFix branch and made the changes you suggested, the problem still remained. I reverted back to 2.0.6.1 and all is well.. |
If you can find the very first date that the issue appears, that should give a very strong clue to the problem. How do we quickly find that date? By repeatedly testing Marlin from the date half-way between the time we know the bug is absent and the time we know the bug is present. Those dates are now months apart. But after only 4 or 5 tests, those dates will be only days apart. GitHub helpfully provides the ability to download Marlin at any point in time from the "Commits" tab above. |
|
no news about this? very annoying problem, I have to disconnect the display every time I print |
Possibly the recent move of some of the STMF1 to the new STM32 hal would resolve this for you. Just have to hang inthere until a experimental environment in PIO is set up by a dev for the creality series. #21488 If your savvy you could probably test build for your creality on the stm32 platform with a few changes and test |
|
I am having same issue here. It randomly clicks. Like pressing the wheel.
Every single one of them now present the same problem. I don't know much, but I'll make a hardware check, cleaning and reinsert everything. Couldn't be firmware. That's very annoying. I'll try to print with the screen cable off as suggested by @SpaceXM |
|
I'm having the same issue that people are describing. Once the bed is heating it starts "clicking" (sometimes even scrolling) and gets amplified in frequency when the nozzle is also heating. @thisiskeithb the issue you marked this is a duplicate of is not the same. Can you undo it so this issue can be looked at? |
#21204 covers random screen clicks due to lack of proper grounding/EMI in the LCD cable. We don't need multiple issues open for the same thing. |
|
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. |
and others
Did you test the latest
bugfix-2.0.xcode?No, but I will test it now!
Bug Description
Downloaded Marlin 2.0.7.2 from 2.0.x repo, downloaded the matching configuration example for Ender 3 pro 4.2.7 board.
Compiled no errors and flashed. when bed is heating up the screen constantly "clicks" like the button is pressed and makes an audible click from the speaker making printer screen useless while bed is heating.
Bug Timeline
Stock creality is Marlin 2.0.1 according to website i updated to newest 2.0.7.2 and it does it now.
Expected behavior
firmware to flash and bed to heat normally without effecting screen/input button
Actual behavior
constant clicking on the "button" used to control printer and screen selecting and deselecting whatever menu entry it is on.
Steps to Reproduce
compile 2.0.7.2 marlin with matching examples for ender 3 pro creality 4.2.7.
flash it
heat up bed
screen should click the currently selected option over and over again.
Version of Marlin Firmware
2.0.7.2
Printer model
Ender 3 pro
Electronics
4.2.7 board
Add-ons
No response
Your Slicer
Cura
Host Software
SD Card (headless)
Video of issue:
https://youtu.be/3oZkyZr-ntc
The text was updated successfully, but these errors were encountered: