Welcome to the SeeMeCNC Community

There was an issue with that some, self included, had with Cura generating the massive string at the end of it's g-code causing the printer to want to head towards the deck. I went and removed the output that generates said string from Cura and have the patch for those that would like to use it as well. Unzip the attachment, and use it to replace the profile.py file located in Program Files>Cura 14.01>Cura>util. It appears to be working for my printer, though, I do not have other Rostock's laying around to test it with, so let me know if it does/doesn't fix your issue!

MSURunner wrote:There was an issue with that some, self included, had with Cura generating the massive string at the end of it's g-code causing the printer to want to head towards the deck. I went and removed the output that generates said string from Cura and have the patch for those that would like to use it as well. Unzip the attachment, and use it to replace the profile.py file located in Program Files>Cura 14.01>Cura>util. It appears to be working for my printer, though, I do not have other Rostock's laying around to test it with, so let me know if it does/doesn't fix your issue!

I am running Windows 7 32 bit. When I replace the profile.py file with the one from your patch, Cura no longer opens. When I restore the original profile.py
Cura opens fine but as you indicate, it sticks that massive string at the end of the gcode. If I manually delete the string and place the gcode on a card I get
a read error every time it is read by the firmware. Looks like I cannot use Cura on .091 Repetier and will have to stay with Slic3r or Kisslicer.

Wait, Eagle, when did you get that rank...

Nylocke wrote:Wait, Eagle, when did you get that rank...

Anyone with 1000 or above has that rank. Pretty rank huh?

Eaglezsoar wrote:

Nylocke wrote:Wait, Eagle, when did you get that rank...

Anyone with 1000 or above has that rank. Pretty rank huh?

they should make one for 2k...

I had that same glitch with Cura generated files crashing into the finished print and ruining it. I just edited the "end" gcode to remove it. Mine looks like this now;

I did the same thing. The "park" command doesn't land the hot-end in a particularly good place.

It's because homing the machine goes to the MAX end-stops instead of the min, and because X0,Y0 is in the middle of the print instead of at the very bottom corner.

I had crash issue with Cura also. Edited my end code so G28 did not have any X or Y values.
Just G28
NOT G28 X0 Y0

Then Cura code works fine on my MAX.

bvandiepenbos wrote:I had crash issue with Cura also. Edited my end code so G28 did not have any X or Y values.
Just G28
NOT G28 X0 Y0

Then Cura code works fine on my MAX.

Are you using the latest release candidate for Cura? If you are how do you handle the last line of the GCode that Cura generates? I try to delete it and get a read error.

I don't know about Brian, but I made similar changes to my end code and I've never seen any crazy last line of code on Cura - and I'm on 14.01

Eaglezsoar wrote:Are you using the latest release candidate for Cura?

You mean the closed beta that got shared the other day?

http://forum.seemecnc.com/viewtopic.php ... eta#p30024

http://software.ultimaker.com/Cura_closed_beta/

Jimustanguitar wrote:

Eaglezsoar wrote:Are you using the latest release candidate for Cura?

You mean the closed beta that got shared the other day?

http://forum.seemecnc.com/viewtopic.php ... eta#p30024

http://software.ultimaker.com/Cura_closed_beta/

Yes the Cura 14.02 adds that last line of gook to the end of the generated gcode file.

I am using 13.06

bvandiepenbos wrote:I am using 13.06

13.06 ? I bet you drive a model A ford too! (just picking on you, I do it to em all!)
14.02 does not work for me so I will get an older version.