MKS-SKIPR
MKS-SKIPR copied to clipboard
Dead Board?
Hi, I have a very annoying issue with this board.
Initially, it worked, copied my printer.cfg across and updated everything and all seemed good until I restarted the board and nothing.
Read through the small amount of info online and found out i shouldn't have updated. As I own a second board for another machine that I bought at the same time with another EMMC module I swapped this in and again everything looked like it was working. I did nothing to the configuration this time and no updates just switched the machine off again and decided to download the latest firmware and flash it to the original EMMC.
After flashing and re-installing the machine just sits there with the LEDs on and does nothing. Switched it off again after a good while and tried the working EMMC module and this time it didn't work and just sat there with the LEDs on doing nothing.
Any help would be appreciated.
The boards were purchased in January so not exactly old and this is the first chance I have had to try them.
This is a software issue with moonraker - when you plug your updated emmc module back into the SKIPR board, it should tell you what has been depreciated - all the information on how to fix it is in the Klipper documentation.
You say the LEDs are on doing nothing - have you tried to open the webbrowser interface and look at the screen, I'm certain he firmware update would not have killed your board, just stopped Klipper reading your printer config.
Source - I did this myself, and it took me a day or so to find the right information to fix it.
I had the same problem and the only way to turn on the SKipr is to use this guide: https://github.com/NexGen-3D-Printing/MKS-SKIPR-SETUP But now I have an MCU error.
Using the latest build off their github allows me to update everything to most recent versions unlike the version preloaded on my board that threw MCU connection errors after updating, you will have to add wpa_supplicant repository yourself however if you wish to use WIFI, i tried the version @zadnezz32 mentioned and no matter what i did had MCU connection errors because it would not connect to the serial port dictated in printer.cfg