Posts: 13
Threads: 2
Joined: Sep 2020
Reputation:
0
I just experienced this same issue on my unit. It has been printing fine, but suddenly yesterday when I started a print, it drove into the LCD and stopped when the motor stalled. I head the humming upstairs in my house. I quickly ran down and stopped the print. The build plate remained in the vat, so I attempted to lift the plate using the manual commands on the LCD display and it wouldn't move. I power cycled the machine and was able to get it to drive up this time, but it eventually exceeded the upper limit on the Z-axis and stalled out at the top.
I believe this was a slicing issue or file corruption problem. I have not had any issues up to this point and after a re-leveling of my build plate, it is printing other files just fine.
Carverbain, have you tried different files to print? What settings were used in the slicer? Also, important to be sure we know what model Mars you are using, since the settings can vary a lot between the different versions of printers.
Posts: 1
Threads: 0
Joined: Dec 2020
Reputation:
0
Any updates on this? I just got the Mars 2 and am having the exact same issue. My test print worked perfectly, but now I attempt my second and it burys itself in the resin and starts making that loud whrrrrr sound.
Posts: 1
Threads: 0
Joined: Dec 2020
Reputation:
0
I have the same exact issue. I cleaned everything twice, leveled maybe 3 times already but no matter what I do, it always starts humming and pressing against the LCD.
I even formatted a different USB to FAT32 but even then this issue occurs.
Posts: 7
Threads: 1
Joined: Jan 2021
Reputation:
0
I've had the Mars 2 Pro do that once, turned out there was a reeeealy small piece of a support that got loose in the VAT and obstructed the plate from going down fully.
Posts: 1
Threads: 0
Joined: Dec 2021
Reputation:
0
Late to the party on this thread, but just wanted to contribute that when this happened to me, I lubricated the axis. No difference. Then I re-levelled the build plate and re-set the zero and that seemed to fix the problem.