Notifications
Clear all

Cura slicer crashed my printer  

  RSS
jason.w11
(@jason-w11)
New Member
Cura slicer crashed my printer

Hi there folks, I have been using slic3r Prusa Edition since I got my MK2S 2 months ago. I decided to try Cura, after reading good reviews about the software.

So I loaded up an STL, sliced it, exported the g-code, and loaded it onto the printer. The initial setup went a bit differently than normal (it measured the z calibration points immediately upon loading the g-code, and then started heating up after that).

After the nozzle and bed heated up, the nozzle crashed into the heat bed.

Now, I have never had a problem like this with slic3r. I am wondering if anybody else has had this issue with Cura? What could be causing this issue?

Any help is greatly appreciated.

Thanks,

Jason

Opublikowany : 04/10/2017 10:08 pm
Vojtěch Bubník
(@vojtech-bubnik)
Member Admin
Re: Cura slicer crashed my printer

Which Cura version did you use?

It is important, that yourslicer (Cura, Slic3r, Kisslicer, Simplify3D) generate a specific hader for our MK2 printers, containing commands for the auto bed leveling. All the softwares mentioned allow you to enter the starting G-code sequence.

Opublikowany : 21/10/2017 6:10 pm
Scott
(@scott-24)
New Member
Re: Cura slicer crashed my printer

I just started using Cura earlier this week. Its version 3.0.3 and has a pre-configured printer setting called Prusa i3 Mk2. I've made a few prints with no issues. It pre-heats, then runs a 9-point cal, then extrudes starting at home position, then starts the print...all exactly as PrusaControl and Slic3r.

This thread has a discussion on the topic.

https://shop.prusa3d.com/forum/original-prusa-i3-mk2-f23/cura-print-settings-t999-s90.html

Scott

Scott
MK2S

Opublikowany : 27/10/2017 5:28 am
PieterB
(@pieterb)
Eminent Member
Re: Cura slicer crashed my printer

I made a different start gcode for Cura so it is the same as with slic3r and the Cura team integrated it. So it sounds like version 3.0.3 contains this change.

So update your Cura and try again.

Opublikowany : 29/10/2017 10:48 am
Share: