So yesterday, I quite literally dusted off my Snapmaker A350 with the intentions of delving back into 3D printing/engraving after over a year now that I finally have a motivation and a good place to use it again. I had it working back before I stopped using it, however I struggled with bed adhesion (which is part of the reason I gave up.) However, I can’t even get that far anymore.
Here is my process and the resulting problem:
I load the filament using the menu
I calibrate the bed, and set the Z offset
I launch Luban, load my .stl file (benchy) generate the G code and load it to the Workspace
I successfully connect to the snapmaker via wifi (using the same wifi network as my PC)
I set the work origin to the center of the bed and run the boundary (which is unusually large for what I’m trying to print)
then, I successfully send (and receive) the file to the device via Wifi, check my settings and hit print.
here, the problem starts. It appears to run the auto calibration again for some reason, then moves the print head all the way to the bottom-left hand corner of the bed, and then just sits there. If I try and cancel the job, the touchscreen freezes for a few minutes. It doesn’t matter if I export the file via wifi or via USB drive, the same result happens.
I am at my wits end and am really frustrated. I’ve gone over the instructions, and have been searching all over Youtube and Google for a solution. I have tried powering the snapmaker on and off, using several different types of print files, updating Luban to the most recent version, doublechecking my axis cables are connected properly, making sure Luban settings are set to A350, and as I mentioned before, printing the file via Wifi and USB drive.
What am I doing wrong? I’ve been out of this hobby for so long, I can hardly remember anything. It’s probably something really dumb I’m overlooking.
Looking at the unit from the front (meaning the same side as which the toolhead is mounted on the x-axis) the head should go all the way to the left and the bed move to the back so that the head is at the left (EDIT: I mistakenly put right in my original posting) front corner. If it’s not then there is a problem with how your cables are plugged in. (or possibly but very rarely a problem with the splitter.)
You shouldn’t need to set a work origin or run a boundary on a 3d print. Also doesn’t make sense that you’re doing this before you’ve sent the file to the SM. I personally don’t like to run any of the functions from within Luban - too many ways where the connection can be interrupted or fail. I always run directly from the SM. Also that way all of your settings should be set before creating the g-code.
I second what @sdj544 just said (with a caveat that “left” and “right” are slippery terms here).
Also, it’s normal for the print head to sit at the front corner of the bed (the one at 0,0 on the grid) for a few minutes as the system brings head and bed up to temperature. If this is what it’s doing, you should be able to tell from what’s on the touchscreen, though.
@MDG the steps that you are showing, are exactly what is supposed to happen. On the last step that you list, the printer is heating up both the heated bed and the hot end. It can take a while for the heated bed to get up to temperature, and you should be able to see the temperature of each increase until they reach the set temperature. Once both the heated bed and hot end have reached temperature, the 3D Printer Module will purge some filament and then move the head to begin printing.
Since you didn’t know how this works, I suggest that you watch a few videos on how 3D printers work. And by a few, I mean no less than 6 and more like a dozen or so. Also, make sure that you are running the latest version of the firmware, and the latest version of Luban. If you don’t do do this, I can guarantee you that you will fail, and that you will probably never use your Snapmaker again.
You Snapmaker is a tool, just like a drill press, a lathe, a table saw, or an end mill. You wouldn’t use any of them w/o knowing exactly how to use them, would you?
Maybe I was not clear - both the bed and the hot end were up to temperature. I waited about 20 minutes after that and nothing happened. It also purged the extra filament. My firmware is up to date. And if you read my post more closely, I you would see that I already said that Luban was up to date.
The problem is IT HANGS AND IS NOT CONTINUING TO THE JOB DESPITE BEING UP TO TEMPERATURE. I would appreciate a little less condescension in your tone, as I in fact do know how this works.
Your eyes are a tool, you wouldn’t gloss over a post and miss details just to talk to me like I’m 5 years old, would you?
Thanks. Unfortunately the problem is that the job never begins, even about 20 minutes after the bed and hot end are fully up to temperature.
I have already ensured that the cables are plugged in correctly - would the calibration phase not also fail if these were set up incorrectly?
You’re right about the boundary part, I had that mixed up with the laser module step. I only did this because I was getting desperate and running out of ideas.
@mdg I’m all for continuing this flame war for amusement’s sake, but I did originally interpret your somewhat ambiguous original post more in line with William’s interpretation. There are a couple things you say that are mutually exclusive and cannot happen. Even after your clarification posts something seems wrong and I can’t figure out what.
Is it hanging after being at temperature repeatable? Could you post a picture? I’ve never heard of that happening on this forum previously, so you might be in uncharted waters here.
Could you upload the gcode file (as a zip file) or post a link to it hosted somewhere? Maybe there’s a clue in there.
So, two things I would try (and maybe you already have):
use the Luban console (over serial if possible) to send a few gcode commands to the printer - things like move the head, extrude filament, etc - and see if it works
paste gcode generated by the teachingtech pages directly into the Luban console - same as 1) only it will perform a complete print
…but yeah, sounds like the touchscreen isn’t starting the job correctly. Maybe downgrade the firmware.
Back to topic. @MDG have you had any luck yet? I rarely update my firmware for a reason, Snapmaker has a history of botching it. I would do as @edf suggested and downgrade the firmware. Let us know results so we can help you further.
I’ve encountered this condition several times.
However, it was not with Snapmaker 2.0, but with ANYCUBIC MEGAZERO2.O…
The USB memory seemed to be broken, and the contents of the G-Code spit out by Cura were corrupted, and only a small portion of the G-Code was garbled, so it stayed stopped.
After I found out the reason, I discarded the memory card and it hasn’t happened again.
The forum is made up of a lot of people with good intentions.
Let’s be friendly and think of others when posting.
