RE: Core One screen flickering / black screen
My new screen and ribbon cable have arrived, however for the last 4 days the screen has been behaving fine. I’ll test the new screen but will probably leave it in the box until the original packs up. Not really sure what to make of it, some days it works, others it won’t
RE:
I am beginning to suspect my issue has something to do with the USB Drive. The printer seems to consistently boot ok (screen working) without the USB Drive inserted but is hit or miss with the drive inserted. Have tried another 32 GB SanDisk Drive in addition to the one provided by Prusa and they behave more or less the same. Once booted I can plug either drive in and it reads the drive and prints ok. Curious if those with replacement screens and cables continue to have the issue or if that solves it.
Planning to continue my chat with support tomorrow as their initial suggestion (reseating the ribbon cables to and inside the screen assembly) didn't seem to do anything.
RE:
I had the same issue. The first few days after finishing the kit assembly everything worked fine, then the screen turned black and began to flicker (white/grey to black). After restarting the printer the main menu occurred for a time range from 10 seconds to 3 minutes (very randomly). This problem never occurred on boot screen, that showed allways fine. For me the screen turned black with or without a USB drive, so I think it has nothing to do with the drive. The solution for me was to reduce the refresh rate of the display (settings > hardware > refresh rate). I hope this was the final solution.
RE: Core One screen flickering / black screen
I have the same issue. Suddenly happen after 3 weeks that the bootloader is displayed fine, but after the second progress bar is at around 50% the screen goes black and do not flicker. I just printing with prusa link and pushing blind on the display. That means the touch is working perfektly. When the print is done, I will try to remove the USB stick to check if this is also here a solution. EMI filter I will also try. Set refreshrate to low is also an option I will try. Let see before contacting the support. Looks like they also do not know what is happening here.
RE: Core One screen flickering / black screen
No chance to test anything. The display worked after the print (and a reset). To be on the safe side I switched to low refresh rate.
RE: Core One screen flickering / black screen
Have the screen flickering issue as well. First saw it after upgrading to 6.3.3 but I did that after only a few hours of use. I was able to get through the menu and set the refresh rate to low, which has solved the issue for now. I also made sure the cables were plugged in properly on the back of the LCD. I also suspect it may be related to the included flash drive, but have not tested it thoroughly.
RE: Core One screen flickering / black screen
I had the same issue of a black screen. Multiple hard reboots at the power supply were required to sometimes get a screen. Following the tutorial of reconnecting the goldish cables seems to have worked for me. Thank you internet stranger!
RE: Core One screen flickering / black screen
I had the same problem. I plugged the power cable into a different socket, and the issue has been gone ever since. Originally, I had the printer in a different room, and when I moved it to another room, the problems suddenly started. I suspect it had something to do with grounding or the power outlet in my case.
RE:
I have the same issue with the CORE One (bought two weeks ago, pre-assembled, firmware 6.3.3). After turning on the printer, the bootloader screen shows up, but after that it goes dark. I checked the wires on the display, they were correctly connected. If I power off and power on the printer multiple times, sometimes the menu appears, sometimes it doesn't. Prusa Connect still works even with a blank screen.
I will now try to set the screen refresh rate to low.
RE:
I have the same issue suddenly since this week.
Core One assembled end of April - running fine ever since. Was away for a week now and as I turned on the machine the first time again -> Display black after initial loading screen. After a reboot cycle the display usually comes back up, though.
I contacted Prusa Support and they told me to reseat the goldish cable or set the refresh rate of the display to "low".
First, I disassembled the display unit, removed the goldish cable, cleaned the contacts with IPA and reseated it very carefully - but the issue persists. Now I've set the refresh rate to "low" and I'm curious if this solves the problem - so far it seems to work.
Big question mark in my head: Why worked the display without any issues for 2 months but suddenly it struggles with the high refresh rate? This makes no sense to me - and I see that this issue is now popping up more and more (here and reddit) - is there something slowly dying in our xLCDs?!
RE: Core One screen flickering / black screen
for me isent the printer... isent display but some elettrical interference... now i try add EMI filter.. all work whit high refresh rate....
I will monitor the situation for a few days and let you know.
What EMI filter did you use? Some kind of plug or a ferrit-core?I think of trying two ferrit cores at both ends of the power cable for testing.
Those are easy to get for a few cents.
RE: Core One screen flickering / black screen
I would be interested as well
RE: Core One screen flickering / black screen
I pugged the printer into a power socket that is directly connected to the electrical cabinet of my house and has a separate circuit breaker. I also pugged the power cable into an Eve Energy switchable socket that is connected to by smart home (via HomeKit). I think the smart home switcher makes some filtering, and the separate power circuit also helps to avoid excessive noise on the power line. Many cheap power supplies of a lot of devices and often LED lamps have surprisingly bad noise filtering and bringing back noise from the devices to the power lines.
Also, I think the flat cable for the display should be shielded in some way; maybe there is some noise from the power line inducted into the cable, disturbing the display while getting commands. I don't know how this display works, but usually they have a small controller with RAM and get commands via SPI, I2C or by 4- or 8-bit parallel lines. All these protocols have no protection for bad signals (no differential signal lines) and can be easily disturbed, especially if the copper lines or cables are long. Maybe the CoreOne power supply needs a better noise filtering with more caps for more different frequencies, but I don't know the internals of the hardware. I just bought a pre-assembled CoreOne 🙂
But plugging the CoreOne into a separate socket away from other devices definitely helps with this issue.
RE: Core One screen flickering / black screen
That guy with that imgur video fixed it.
I disassembled the display, unplugged the flatflex cable from the panel to the PCB, cleaned it with Q-Tip and IPA, and reassembled it.
That brought my screen back, jumped right into the menu, just to be safe, and set to "low refresh rate". I guess the affected LCDs were just assembled poorly or contaminated, degrading the signal between the LCD controller on the PCB and the LCD module itself. With higher refresh rate (higher signal frequencies) the probability of errors increases.
I think this is and was never an issue with the cable between the main board and the LCD board or the ground wire.
RE: Core One screen flickering / black screen
My replacement screen has failed within a week of receiving it. Bringing to think the problem is not the screen itself. Can’t seem to start a web chat today so I will take it up with support via email. Getting a bit fed up with the printer now.
RE:
I assembled the kit and couldn't get it to display on the first boot. I couldn't see the screen even if I wanted to lower the refresh rate.
I removed the door, detached the LCD unit from the metal parts, and realized that it would display if I tapped on the plastic in a free state.
Then I skipped the first step and moved the knob based on the menu list at https://help.prusa3d.com/article/lcd-menu-core-one_829752
(don't touch the LCD!), moved the cursor to Display Refresh Speed, and pressed the knob to set the refresh rate to LOW (pressing the knob switches between HIGH-LOW).
RE: Core One screen flickering / black screen
We have the same display problem, Core One (Kit) worked great for one week, then we updated to firmware 6.3.3, short time after display fails startet, got worse and today the printer is useless because the display is black and stays that way after boot loader.
Changed power outlet, reconnected all cables as mentioned in the posts but missed changing refresh rate. I tried it "blind" but can't say if i hit the right menu point because the screen keeps black with occasional flickering.
- Interestingly, the bootloader shows up reliably on every startup, switching on the printer or pressing reset. So there is a functioning cable connection
- There is definitely a degradation going on, first there were only outtakes, then it got worse, then after bootloader i could see the firmware version, now only the bootloader message. As is gets hotter in germany, maybe this is a thermal issue?
We will contact support...
RE: Core One screen flickering / black screen
I did the same and that fixed it. I took a few attempts to navigate correctly but everything seems to work fine for now. Thank you very much!
RE: Core One screen flickering / black screen
How to change the refresh rate to low - "blind mode".
- reboot the printer, wait until the internal lights turn on
- press center, bottom third of the display (where the "settings" icon is)
- turn the knob few full turns to the right (to get to the bottom option, the menu doesn't wrap to top)
- 2 clicks left-> press -> 4 clicks right -> press
- profit
Note: don't wait more than cca 10 seconds in between the steps or the printer returns to the main screen
RE: Core One screen flickering / black screen
Can confirm, changing the display refresh rate to low did fix the flickering, blanking issue.
I did not notice difference in responsiveness, so I'm going to keep it this way.