this post was submitted on 01 Aug 2023
7 points (88.9% liked)

3DPrinting

15545 readers
304 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: [email protected] or [email protected]

There are CAD communities available at: [email protected] or [email protected]

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago
MODERATORS
 

SOLVED The serial settings are fine, I just had the wrong display type defined in the firmware. I'm a very paranoid person apparently.

Thanks everyone.

Original post:

I have acted recklessly and now I need help.

I tried to update my Ender 3 Pro with an SKR V1.3 to Marlin 2.1 and I tried to skip some steps.

I couldn't find a v1.3 example in the configurations repo so I used a v1.4 instead because it had the right processor.

I changed some stuff over but didn't give it a thorough look and I didn't change the SERIAL_PORT 1 and 2 settings.

When I tried to load the new firmware from the SD card the screen was blank and it hasn't worked since.

The firmware file changed to a .elf so it maybe installed?

I wonder if I can even load via the SD if I've super messed up it's serial config. I tried some other firmware versions plus BigTreeTech's from 3 years ago but I don't think they're being read.

If I've messed up those serial configs I wonder how I could undo it without the SD card. Help...

P.s. does anyone have a copy of Marlin 2.1 that works with the SKR V1.3 or the config files for that board on the Ender 3 Pro?

Catch you on the flip side 😎 👉👉

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

Thanks for the info. You were right it was the display settings. Look at me getting worried over nothing.