Recieved my sonic pad a few days ago. Tried to hook it up to my ender 3 v3 se. Upon starting the sonic pad, it had an old version of firmware so it did not have a v3 option. Tried updating through the pad with no luck, tried updating through usb with no luck, then went nuclear and found instructions for a full refresh. After getting it to update, i was able to take the steps to link the se, but cannot connect. I am using the seriel cable provided. When it goes to connect to the printer, it ends up giving an error that klippy host software is attempting to connect. I believe its one of two issues. An issue with the ubs port/s or user error on my part. Im still in my learning curve so i believe i may be doing the sd card printer firmware update incorrect. Can somebody show me the files that should be written to the printers sd card?
The sonic pad creates the correct firmware to flash to the printer, it is part of the installation routine. I would check delete the printer from the pad, check that your SDcard is correctly formatted and rewrite the firmware as instructed by the sonic pad. Knowing how my printer goes through SDcards I would try a fresh one.
First, id like to say thank you for all of your responses. Ive seen your comments everywhere on this site while troubleshooting different things on the two enders ive owned. Ill try a new sd card tomorrow and see if that changes anything. Just to be clear though, the sonic pad downloaded 4 different files onto the usb. Im supposed to transfer all 4 files to the sd card, correct?
Also, im using FAT32 formatting. Is that also correct?
Hello In_The_Works_Garage,
If I might add, the V3 SE does not like SD cards greater than 8 GB.
The firmware files are generally only a fraction of 1GB, so anything from .5GB to 8GB will be fine.
Cheers.
Thank you. I was just about to go buy one and thats good information to have
Update. I got it working. Im not sure why i had 4 files on the usb drive. I deleted everything, went through the process again from the start, changed the name on the .bin to add âfirmwareâ and reflashed. Now its connected and im starti g the test print.
Just keep hitting it until it works, think my initial install was a bit like that (dodgy SDcard). Fitted a bigtreetch runout sensor to one of my printers, well documented mod. Could I get the printer.cfg file to work without parsing errors? Took me 2 hours to figure it out, even my coding friend couldnât see where it was wrong. Fixed it at random.
Fail warning, i have not looked this up yet. I have a creality runout sensor thsts been on the printer forever. Do i have to do anything to make that keep working? Or is it better to bite the bullet and buy a btt sensor?
Sorry that was me just wittering, I have added it to my Qidi Xplus3, the only reason I did it was because the original sensor, similar to any printer is just a limit switch, failed to notice a filament break after the sensor. The BTT would have caught that failure as it also measures if a filament has stopped and pauses the print. Wouldnât have a clue how to install it on a V3SE so I wouldnât worry about it. Downside is that it is a little harder to load material so I think I might struggle with TPU (floppy wet spaghetti)
The btt is harder to load filament? You have it mounted at the ribbon cable?
No it is on a completely different printer, like I said I was wittering.
Is there any way i can convince you to send me your start stop config for cura? mine is saying
!! {âcodeâ:âkey38â, âmsgâ:âError on âTEMPERATURE_WAITâ: missing MINIMUM or MAXIMUM.â, âvaluesâ: }