Announcement

Collapse
No announcement yet.

Prepare, Control missing after install of SKR Mini E3 V1.2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Prepare, Control missing after install of SKR Mini E3 V1.2

    am a newbie with a 3 months old Ender 3 Pro, my first one. I purchased, installed and loaded a new SKR Mini E3 V1.2 mobo. The LCD panel lit up as usual without problems. I selected 'print from card' which showed the micro sd card had 2 files, FIRMWARE and test, as I recall. Then I put the sd card into a micro-sd to SD card adapter, which I hoped to use, and plugged it into the card slot but it didn't work. I fiddled with it a little, then removed the adapter and discarded it. I then removed the card and copied it onto my PC for safekeeping. I also added 2 short, simple .gecode files to check out the printer. I put it back into the printer and turned it on. The panel came on listing several entries but Prepare, Control and Print from Card were missing. I opened and scrolled each item, even clicking on 'Initiate EEPROM' but without success. I plugged and re-plugged the sd card, restarted the printer several times with no luck. Put the sd card back into the PC and both original files plus the 2 .gcode files I added were still there. This exhausts my meager knowledge of things to do and I surely hope someone can help me out! Thank you!

    #2
    You were able to install the board and load the firmware (I'm assuming home all from the menu works as it should and everything heats as it should from the menu) and I would start here again. Reflash/reload the firmware, then with a different sd card try loading just the .gcode file from your slicer and print (make sure the sd card is formatted correctly i.e. fat/fat32 and make sure if you set up your own slicer that the gcode flavors are the same i.e. reprap firmware on machine reprap flavor from the slicer or marlin in machine marlin in slicer...just to be sure) then see what happens. If this happens again I'd be looking at the firmware I used or I'd be writing/finding a different one. Happy printing.

    Comment


      #3
      Thank you MadeBye!Yes, the bed and extruder heats and the axis controls function. As to reflash/reload, does reload mean to restart the printer with the sd card in place? I have never done a flash procedure, and quite frankly, one of the main reasons for going to the SKR board was that it already had a bootloader installed and I wouldn't have to flash Marlin!. Obviously I have some confusion about flashing and bootloader, just part of the many areas I have to gain education in. I will definitely format another sd card (I use an SD card formatter)and a .gecode file and try that. In addition, I realize I have to face the obvious and make a diligent research of YT vids again and ultimately find one that I can confidently learn about flashing, knowing that it is inevitable!! Also, your reminder to make sure Cura and Marlin are in sync, to the best of my knowledge, is well said. As I recall, this new SKR board has Marlin 2.0 so a contingency plan will be to update Marlin to perhaps 4.5. This post is probably disorganized but you have helped and I am sincerely appreciative. Please don't let my apparent ignorance drive you away!

      Comment


        #4
        Flashing the firmware again is what I was talking about. The bootloader is something you only have to do once then you can flash firmware as many times as you need to. Usually firmware flashing/updating is as simple as having the firmware you want to use on the sd card (firmware only) named correctly (ie firmware.bin) then insert the microsd card and turn the machine on. According to bigtree's github - Note: The filename must be renamed to "firmware.bin" before coping this file to the motherboard onboard TF (MicroSD) card. Then, We will copy this file to the TF (MicroSD) card of the motherboard, and then reset the motherboard, so that the firmware is burned into the motherboard, the red led D10 will always blink in the burning, After the burning is completed, D10 stop blink, and the file name in the TF card (MicroSD) will change from 'firmware.bin' to 'FIRMWARE.CUR'. If you need the firmware again the bigtree github is here https://github.com/bigtreetech/BIGTR.../firmware/V2.0 and I would download a new copy direct from them. The Led at D10 will let you know if you're flashing firmware and the .CUR name change would indicate a successful firmware flash. Happy flashing then printing.

        Comment


          #5
          Thanks again! I appreciate your efforts to explain things as simply as possible--even so, a noob like me will sometimes not fully understand! So--I went to the Github site you hilighted and downloaded "Update V2.0 Firmware.bin"--I didn't unzip; was I supposed to? I copied it to a freshly formatted sd card, and when I opened the card to check, it shows "firmware" and type-bin file. Put it into the 3d printer--long wait-- the panel displays "Info, Motion, Temp, Configuration, About printer, Initiate Media, Media released. If Configuration is selected and you scroll to Advanced settings, Initiate EEPROM appears. I clicked on Initiate Media and initiate EEPROM but nothing happened. The led panel never showed "'firmware.bin' or 'FIRMWARE.CUR". I opened each of the menu topics and nowhere does it show anything like .gecode files or print from files or prepare or control. I forgot to open up the printer control box so I didn't get to see the D10 led. I tried to follow your guide otherwise precisely, but sometimes what came up didn't reflect what you said should--I have tried to reproduce my steps and the results. I just pray that you can see key things(s) that led to my failure.

          Comment


            #6
            Put the firmware on the sd, with machine off put in sd, watch the LED a D10 then turn the machine on, the red led D10 will flash during the burning/flashing (If you can't see the led at d10 then you don't know if it is working, look at the led), after the burning/flashing is completed D10 will stop flashing, then the update is complete. Wait 30 sec-1 min to be sure.
            Turn the machine off then remove the micro sd and insert it into your computer then check to see if the name changed (This is a backup way to be sure it worked, the LED at D10 is the thing to watch and this is a double check).
            I can't understand where you got the need to initiate eeprom from as I haven't seen anything about this on the bigtree github. Honestly, I know more about skr boards than I ever wanted to now. I'm just trying to get you to square one so you can start to troubleshoot. There could be other things going on but If you need the firmware/board working properly. Where are you getting the gcode files that your trying to print?
            Once you've done the firmware procedure above you're done. Next then load an stl into your slicer of choice, adjust your settings or use an ender 3 profile, slice, put the newly sliced .gcode on a freshly formatted microsd, insert into the ender 3/skr board and turn it on. You shouldn't have to initiate the sd if its installed when you turn the machine on and this would let you know if you got the microsd formatted incorrectly (if it doesn't show the .gcode on the ender lcd then you have a formatting or microsd card issue). I hope this gets you somewhere.

            Comment


              #7
              I downloaded the BIGTREETECH-SKR-mini-E3/firmware/V2.0/firmware.bin file from github, and copied it to a freshly formatted sd card. The file was already named 'firmware.bin'. Inserted it into printer and turned it on--the red led was on constantly, not blinking, and the other led--labeled 'status-- never came on. The led panel remained blue but otherwise blank. No menu, no nothing. I get my .gcode files from Thingiverse. As to my clicking on EEPROM, I was simply trying to get something to work. Afterward, I put the sd card back into my PC and, nope, the name had not changed! I take it from your comment that you are not a fan of skr boards so maybe I made a mistake by buying oneI Your instructions were perfectly clear and easy to follow. I can only assume that the board is faulty unless I STILL managed to screw up somewhere! So, I guess I'll either get another one or go back to the Creality board. You have certainly done your part for which I am very grateful!

              Comment


                #8
                Sorry about not liking the skr boards, I don't have any need or reason to learn them as I don't see myself ever buying one (don't know about quality control either). I use duet3d wifi boards on my big printer, and I like octoprint alot so I run octopi with klipper firmware on my printers with 8 bit boards. My first guess was that you had a bad firmware flash and thats what reflashing was going to help me confirm. There is the sdcard formatting but if your using sd card formatter or being sure your formatted FAT your ok, and if you can see .gcode files on the printer display as you had at one point then your ok. If your status led never starts flashing then the current firmware isn't looking to the sd card and isn't performing the flash on boot I would have to say bad board. The only other thing I would try to do is disconnect all connections except the main power and the display from the board and try the firmware one last time (Just in case you have something wiring incorrectly during the swap). If it were me I would double check the wiring then if its all correct id be sending that board back for a replacement.

                Comment


                  #9
                  I knew nothing about 3d printing (still don't!) but the idea has always fascinated me. I opted for a cheap printer to 'learn' on, being fully aware of the some-very-good and some-very-bad Chinese reputation. Simply printing became boring and the urge to try new things arose, so I got the cheap SKR board. I never intended the printer to be anything other than a toy, to explore with and pass time. It's clear my lack of knowledge is a formidable barrier and perhaps 'above my pay grade' unless I adopt a more intensive approach to self-advance but time is rather limiting (I'm 82). Having to lean on others to circumvent a basic process understanding is akin to kissing your sister, nice, but leads nowhere. All in all, the experience has been informative and enjoyable. I'm going to reinstall the Creative board and probably concentrate on improving the quality of the prints--or maybe not!. Finding kind souls like yourself, on these fora who are willing to endure what must be mind-boggling frustration is rare. Your patience and the admirable ability to explain clearly has meant a great deal to me and for which I will always be thankful. "If you dig it, do it; if you really dig it, do it again."

                  Comment

                  Working...
                  X