search

bigtreetech / BIGTREETECH-SKR-mini-E3

BIGTREETECH SKR-mini-E3 motherboard is a ultra-quiet, low-power, high-quality 3D printing machine control board. It is launched by the 3D printing team of Shenzhen BIGTREE technology co., LTD. This board is specially tailored for Ender 3 printer, perfectly replacing the original Ender3 printer motherboard.
2.02k stars 1.98k forks source link

Blank blue LCD screen on stock LCD #224

Open lassespilling opened 4 years ago

lassespilling commented 4 years ago

I have two boards that were working but now show blue blank screen on stock Ender 3 LCD screen. Board one: Went blank after flashing new firmware. (using firmware.bin from Github), this board seems to flash and renames to firmware.cur succesfully.

Board two: Went blank after just turning power on and off without even flashing or doing anything. Tried to flash after LCD went blank (using firmware.bin from Github), but this board won't rename to firmware.cur so i do not think it is flashing at all.

Steps to reproduce

  1. Downloaded Firmware.bin from BIGTREETECH-SKR-mini-E3 github
  2. Put firmware.bin on card
  3. put card into skr mini e3
  4. turn off and on power

Expected behavior Board powers on and LCD should work

Actual behavior Board powers on, LCD shows blank blue.

I now have two boards i cannot use.

h3soy2m commented 4 years ago

last firmware update show this ""missing bmp files"", that why i use some old file, and it work.

Can you share the old file please.

getz97 commented 4 years ago

this one :11 sept. https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/tree/cb2430ca5b8bf1a50b0058f41b0c0c98fb114ff5

Anybid commented 4 years ago

Ok, I just had this problem, tried tried to flash the firmware, specifically the firmware_bltouch.bin. turned the printer off, inserted SD card, firmware.bin renamed to firmware.cur (finally pulled the card out after waiting 10 minutes). Blue screen, completely blank.

Got a new SD card, tried again, no good, still blank. This time, didn't rename the file.

copied the firmware.bin that came on the SD card. Inserted, nothing. Didn't rename the file. when I looked closer, I noticed that my file was named, FIRMWARE.bin. All caps name, lowercase extension. Made extension all caps, inserted. Flashed back to original firmware that came with the board.

So, that solved my restore problem. making sure the file was FIRMWARE.BIN.

Tried the process again, on the new SD card. Same thing, blank screen. Then I restored back to the original.

Then I noticed that the firmware.bin and firmware_bltouch.bin that I downloaded from github, via right-click, save as was only 82KB. While the firmware that came with the board was 209KB. This didn't seem right, so I went back to github and instead of downloading via right click, I clicked on the firmware_blthouch.bin. This loaded a page that said the file ws 226KB, with a download button. Clicked download. Verified that the file was indeed 226KB when downloaded. Renamed it to FIRMWARE.BIN, inserted into SD Slot, turned on printer. 15 seconds later, the screen loads and says I'm on the newer version of Marlin (2.0.6, I think).

So, I am a bit of a dumbass, but in case it might help others, make sure your downloaded file is 200+KB in size, and not 82KB. And renaming to all caps fixed my restore, so I didn't even try the new firmware.bin file lowercase, I just made it all uppercase.

Thank you so much, blhamon!!!! Your are no dumpass but a genius, this was exactly my problem too, and you showed me the solution.

Ansari-Tech commented 4 years ago

I'm also having this issue.

I have nothing connected to the board except power and LCD.

When I upload the firmware.bin (confirmed to be 220kb) to the SD and boot the board up, the status LED flickers for a few seconds indicating that it's flashing, and then goes off. the LCD remains blank.

My FIRMWARE.bin does get changed to FIRMWARE.cur, so I know that it's flashing, but the LCD remains blank and both octopi/pc continue to not see the board whatsoever, as though it's not plugged in at all.

It was working fine for several months, I didn't change anything. I powered up the printer after not using it for a few months and this is the issue I'm having.

JoeDaddy7105 commented 3 years ago

Then I noticed that the firmware.bin and firmware_bltouch.bin that I downloaded from github, via right-click, save as was only 82KB. While the firmware that came with the board was 209KB. This didn't seem right, so I went back to github and instead of downloading via right click, I clicked on the firmware_blthouch.bin. This loaded a page that said the file ws 226KB, with a download button. Clicked download. Verified that the file was indeed 226KB when downloaded. Renamed it to FIRMWARE.BIN, inserted into SD Slot, turned on printer. 15 seconds later, the screen loads and says I'm on the newer version of Marlin (2.0.6, I think).

So, I am a bit of a dumbass, but in case it might help others, make sure your downloaded file is 200+KB in size, and not 82KB. And renaming to all caps fixed my restore, so I didn't even try the new firmware.bin file lowercase, I just made it all uppercase.

You are my hero! I was doing the exact same thing with downloading the bin files with right click save as from Github and getting ~90KB files and thought I had bricked my SKR mini E3 V2.0 since the screen was stuck on the blank screen no matter what I did and I had wiped the original SD card so I didn't have the old firmware to fall back on. Then I saw this and downloaded from Github by clicking the file and using all caps filename and it worked like a charm with the 2.0.7.2 version.

limestone-xyz commented 3 years ago

I've got the exact same problem right now. Printed flawlessly for 6 months and today tried to calibrate again - just for good measure. After some initial test octo print lost the connection and the lcd turned solid blue.

Tried everything mentioned in here, but nothing worked for me unfortunately.

Are there any new insights?

Thanks!

SonnyJim commented 3 years ago

What I did was contacted BTT support, who made me run through quite a few troubleshooting steps. Once it was clear the board was dead they sent me a new one. The board that died was about 7 months old iirc.

On Tue, 17 Nov 2020, 03:58 Gertsch, notifications@github.com wrote:

I've got the exact same problem right now. Printed flawlessly for 6 months and today tried to calibrate again - just for good measure. After some initial test octo print lost the connection and the lcd turned solid blue.

Tried everything mentioned in here, but nothing worked for me unfortunately.

Are there any new insights?

Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/issues/224#issuecomment-728190863, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA6HTFFIWMSMHHNBDGKYZ3SQFK3RANCNFSM4ML5QSNQ .

limestone-xyz commented 3 years ago

As the BTT support didn't get back to me I purchased a SKR mini E3 V2.0 in the meantime. Worked fine from the beginning and did all the calibration. Did some printing and then again the same issue like with the 1.3 board. LCD went black (this time the TFT35) and octoprint lost connection. Wasn't even printing at that moment. Firmware does not get flashed, so I've got two bricked boards now and have no idea what could be causing the problem.

I'm a little stuck right now. Any help is greatly appreciated :)

tchilton commented 3 years ago

I have the solution to this problem from reading between the lines on this page.

The key is the file size.

If you go to the firmware.bin on the github page and right-click, save, you save a file of around 95K, this is simply the HTML of the next page, hence why it does not work as this is not firmware !!

To correctly get the firmware file, you must click on firmware.bin, which takes you to the download page, then click on "View raw file" and it will save the firmware.bin to your machine, this file will be around 224K.

You can also check the files by opening them in notepad. The firmware file will appear as a binary file (unreadable), whereas the 95K one will appear as simple HTML. You will see a line <!DOCTYPE HTML> in the start of the file. Just make sure you don't save the file if you open it in notepad as it would corrupt it.

You can also check the card is programming by looking at the two LED's. The status LED will flash when its programming the firmware.

Correctly downloading and programming resulted in a working machine again.

limestone-xyz commented 3 years ago

I found the cause of my problem at least, and have heard form others with the same experience. Two of my SKR mini E3 V2.0 were bricked by an electrostatic discharge of myself. I just found out because I heard a clicking sound doing some calibration prints and wanting to remove filament residue, but not even touching anything - I just came near. This board then had the exact same issue like the ones before.

So if anyone has the same issue with the board as I had (blank screen, no serial connection/octoprint, can't read MC with STLink), it quite possibly came from an ESD and bricked the MCU/electronics. So be sure to:

tchilton commented 3 years ago

The other thing to watch out for is manually moving the table too fast. When you move the table, you turn the motors into generators (dynomo's) and the resulting voltage (reverse EMF) can be far too large for the logic board and therefore permanently damage it.

It would be good if SKR had put some clamping networks on the board to protect against this obvious problem, particularly given the need to manually move the bed to perform bed levelling and the risk of the bed moving quickly when turning over the printer to change the logic board.

Don't forget that this only has to happen once to spoil your day, so please be careful !!.

GDRPrint commented 3 years ago

Just had this happen after 3 weeks of excellent printing. The 8 bit board worked fine before the upgrade. I have the original screen. Have tried uploading the original BTT firmware, no luck. Thank you for all the posts, have ordered a new board from Amazon, will wait for any results from BTT and post. Ender 3 Pro printed daily, no issues and very good prints with the basic upgrades like glass bed, springs, extruder.

gknapp commented 3 years ago

What you said here makes sense. I was changing my filament, usually I don't bother with the 'change filament' option in Marlin, I just disable steppers, heat the hotend, hold the extruder clip open and pull the filament out myself.

This time I used the menu option to change filament. I did the same procedure, waited for the hotend to heat, pinched the extruder clip and began to pull the filament out. As I did, the extruder stepper motor began to assist. As the filament was coming out of the boden tube I noticed my BTT TFT 3.5 V3 flashed, then a second or so later, went off completely.

From there on, it would not power up. I think as the filament cleared the hotend and became easier to withdraw my assistance has overloaded the board.

I switched out the screen for the original, it just turns on, glows blue but is blank. I've tried placing a firmware.bin on an SD card, the board doesn't appear to read the card as the file is not renamed firmware.cur.

The other thing to watch out for is manually moving the table too fast. When you move the table, you turn the motors into generators (dynomo's) and the resulting voltage (reverse EMF) can be far too large for the logic board and therefore permanently damage it.

It would be good if SKR had put some clamping networks on the board to protect against this obvious problem, particularly given the need to manually move the bed to perform bed levelling and the risk of the bed moving quickly when turning over the printer to change the logic board.

Don't forget that this only has to happen once to spoil your day, so please be careful !!.

MetalMinotaur commented 3 years ago

Hi everyone,

I'll just leave this here, to see if it might help anyone. I also had the issue of the stock LCD of my Ender 3 not working with two different SKR mini e3 v2 boards. Turns out this might be an easy fix in the firmware. After experimenting a bit, I found that not setting the BEEPER_PIN when building Marlin suddenly makes the stock LCD work.

I just changed this part in "Marlin\src\pins\stm32f1\pins_BTT_SKR_MINI_E3_common.h" 

#if HAS_WIRED_LCD

  #if ENABLED(CR10_STOCKDISPLAY)

    #define BEEPER_PIN                      PB5
    #define BTN_ENC                       EXP1_9

to

#if HAS_WIRED_LCD

  #if ENABLED(CR10_STOCKDISPLAY)

    #define BEEPER_PIN                      -1 // PB5
    #define BTN_ENC                       EXP1_9

You'll lose the annoying beeps but you get a working stock display in return. Not a bad deal I guess.

Credit for the hint in the right direction goes to this reddit post - seems like Klipper has the same issue with this board: https://www.reddit.com/r/klippers/comments/msgi7z/ender_3_pro_display_problems_on_skr_mini_e3_v20/

Let me know if this worked for you.

srvoets commented 2 years ago

Hi everyone,

I'll just leave this here, to see if it might help anyone. I also had the issue of the stock LCD of my Ender 3 not working with two different SKR mini e3 v2 boards. Turns out this might be an easy fix in the firmware. After experimenting a bit, I found that not setting the BEEPER_PIN when building Marlin suddenly makes the stock LCD work.

I just changed this part in "Marlin\src\pins\stm32f1\pins_BTT_SKR_MINI_E3_common.h"

#if HAS_WIRED_LCD

  #if ENABLED(CR10_STOCKDISPLAY)

    #define BEEPER_PIN                      PB5
    #define BTN_ENC                       EXP1_9

to

#if HAS_WIRED_LCD

  #if ENABLED(CR10_STOCKDISPLAY)

    #define BEEPER_PIN                      -1 // PB5
    #define BTN_ENC                       EXP1_9

You'll lose the annoying beeps but you get a working stock display in return. Not a bad deal I guess.

Credit for the hint in the right direction goes to this reddit post - seems like Klipper has the same issue with this board: https://www.reddit.com/r/klippers/comments/msgi7z/ender_3_pro_display_problems_on_skr_mini_e3_v20/

Let me know if this worked for you.

I am experiencing this issue, and unfortunately, this did not resolve it.

iD0NTknowWHATimD0ING commented 2 years ago

I have two boards that were working but now show blue blank screen on stock Ender 3 LCD screen. Board one: Went blank after flashing new firmware. (using firmware.bin from Github), this board seems to flash and renames to firmware.cur succesfully.

Board two: Went blank after just turning power on and off without even flashing or doing anything. Tried to flash after LCD went blank (using firmware.bin from Github), but this board won't rename to firmware.cur so i do not think it is flashing at all.

Steps to reproduce

  1. Downloaded Firmware.bin from BIGTREETECH-SKR-mini-E3 github
  2. Put firmware.bin on card
  3. put card into skr mini e3
  4. turn off and on power

Expected behavior Board powers on and LCD should work

Actual behavior Board powers on, LCD shows blank blue.

I now have two boards i cannot use.

This is what worked for me. https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/blob/master/firmware/V2.0/firmware-bltouch.bin

Click on "view raw". Make sure you rename the file to "FIRMWARE".

I tried to name it "firmware.bin", that is what gave me the blue screen. I also tried "firmware" and it didnt work. It must be all caps "FIRMWARE" with no ".bin".

I hope this helps someone. I know, I gave up even trying for a few weeks.

NxtGenCowboy commented 1 year ago

So far I have tried all the methods listed above, same blue LCD... is there any other method to fixing this issue?