#Ender 3 S1 Pro with Sonic Pad updating firmware and connecting

1 messages · Page 1 of 1 (latest)

tough isle
#

Hello, I am trying to connect a Sonic Pad to my Ender 3 S1 Pro and it won't connect. It says klipper is not working properly and can't connect. I assume it is not flashing properly so when I boot up the 3d printer it is not overwriting the firmware. I took a looksie online and they say if your small touch screen is still looking normal the firmware did not overwrite. I tried a few different things to see if a brand new SD card was the issue and swapped to the one that initially came with the printer an 8 GB SD card. When going through the steps on the sonic pad and booting the printer the small screen started the start up creality title screen then froze halfway through. I thought the thing was finally getting somewhere however the pad never connected after waiting a while. After such I tried a few different attempts then I said screw it and wanted to go back. I tried loading the firmware with marlin I found online with the same stuff as my printer and now it won't go back to normal. I need help getting my printer back.

TLDR: Tried changing the firmware for the Sonic Pad. Won't work. Old firmware won't work either. I just want something to work and I hit a deadend.

twin snowBOT
#
AI Help

It seems like you're experiencing difficulties with flashing firmware on your Ender 3 S1 Pro for the Sonic Pad. Here are some steps you can try to resolve the issue:

  1. Make sure you have the correct firmware for your specific printer model. Installing incorrect firmware can cause issues.

  2. Check your connection between the Sonic Pad and your Ender 3 S1 Pro. Ensure the cables are properly connected and not loose.

  3. Try using a different SD card to transfer the firmware files. Sometimes SD cards can be the source of the problem.

  4. If you are having trouble with Klipper, try reinstalling it following the proper instructions for your setup.

  5. Consider reaching out to the manufacturer or their customer support for further guidance on troubleshooting the issue.

If you still encounter difficulties, consider seeking help from online forums or communities dedicated to 3D printing for more specific advice tailored to your situation.

tough isle
#

Hello Mr AI,

#
  1. I'm pretty sure I have the right firmware. I checked the control chip on my board and have a picture to reference. It is an STM32F401RCT6. I do not know the board version but I'm pretty sure this lowers it down to the right firmware which I grabbed from creality's website. https://www.creality.com/pages/download-ender-3-s1-pro

  2. Cables are not the problems in terms of being plugged in. However I could not tell you if they are broken coming brand new from the box.

  3. I have tried two SD cards! I am actually happy I did do something smart. Sadly though it did not work.

  4. I followed the instructions tooth and nail several times. From the manual, from online youtube videos. All aren't working sadly.

  5. I have reached out to the manufacturer. Not sure when I get a response and I thought I would get a more tailored response from a great community like this.

graceful vault
#

i use to run that setup but its been a while. are you making sure you are getting the right firmware for your printer? for the s1 pro there are 2 different versions. one with the STM32F401 and the other with the STM32F103.

tough isle
#

Yeah I'm sure I have the F401. I'm really confused on why the old firmware from creality's website didn't work with rebooting it and the new firmware from the sonic pad didn't just work.

#

Courtesy photo

tough isle
graceful vault
#

not sure why but creality mainboards won't flash firmware with the same name twice in a row. change the name of the .bin file

tough isle
#

Hmm I'll try that. I looked in the manual and it's saying I might need to update my bootloader but I have no idea how to do that. I'm through all the steps except I'm sure I have to name it something specific to actually get it to update when it boots up.

#

I'll try renaming the file.

#

This is a reddit conversation I've found closest to my issue but I have everything in the right ports :/

#

Renamed to klipper.bin testing now.

#

Same error. I believe these are the dots are the ones people refer to in the reddit posts. In which case the printer may have the klipper firmware already in there.

#

I'm gonna try the bootloader

#

No go 😦

short vault
#

what usb port are you plugging into it has to be the top one on the side

#

the rest wouldnt connect on my regular s1

#

@tough isle

tough isle
#

Top one on tbe left side. Labeled as USB1 in the schematics and manual.

#

I tried all the usb ports as well with hope and it didn't work.

short vault
#

also creality firmware doesnt boot on my printer either :/ idk y

#

hmmm

#

re flash with the firmware from the creality pad then restart the pad and printer

#

acutally

#

you have the board i do

#

use the firmware for the regular s1

tough isle
#

What do you mean?

#

Like just ender 3 s1

short vault
#

on the select printer screen

tough isle
#

Not pro

short vault
#

yeah

#

the not pro

tough isle
#

Same chip?

short vault
#

eyah

#

yeah

#

the f401

tough isle
#

Okie doke. I'll try it tomorrow morning though boss I'm heading to bed. Fiance says no more for the day.

short vault
#

lol have a good night happy wife happy life

tough isle
#

Absolutely!

short vault
#

ill be on tomorrow @ me and ill help

twin snowBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

tough isle
#

@short vault I am continuing the journey of the difficult 3D printer.

#

So I tried reflashing. Then restarted the printer and pad. No go. Same error still have dots on the initial small touch pad.

#

Gonna try the different flash method with the S1 not S1 pro

#

Same error. "Error message
Printer is not ready
The klippy host software is attempting to connect.
Please retry in a few moments."

#

Gonna try renaming the .bin file name.

#

Maybe it just didn't rewrite.

#

Same error

tough isle
#

Tried a different cable. It connected instantly. I hate creality and some of the stuff they send sometimes :/

#

?solved