Cura tried to send my hotend to never never land??

[berrybot3d 0]

Hi Guys,

I have been printing a lot and everything working great until I tried to print two parts in one program with Cura. After the first part completed I expected the move to the next part starting point however this did not happen. Instead my end effector made a rapid move right off my platen. I opened the code to find the move that made my machine do such a heinous, vicious, violent act I just have no idea why it spit out this code? I am hoping someone can give me some clues?

Thanks in advance!!

Happy printing!

Werner Berry

BerryBot3D

https://www.dropbox.com/s/i1xy3eqo2fp22qe/Cura.jpg

 

[ian 32]

mmmm do you have the mode file you tried to print ??

it could be.. sometimes if the model is not really clean, there can be some node points left over... a few meters away from the central 3d model object and then when cura tries to gcode it.. it of course tries its best to cater for all the 3d data.. including the extra spare nodes...

i just wonder is there some crazy 3d model trash hiding, that might have caused your printing problem....

Ian :-)

 

[gr5 2,167]

strange. I like Ian's explanation. But also check all the values in "file" "preferences". Particularly anything in mm.

Also it helps to run the "first run wizard" if you never did - you only have to answer the first question or two - telling it that you have an ultimaker. Or do you not have an ultimaker?

 

[berrybot3d 0]

Thanks Ian and gr5 for the ideas!! I did look very carefully for something perhaps in the model space that could have caused my problem not finding anything. When looking at the toolpath in Repetier I could see the path just went out to space and then back the line looked parallel about ¾” apart. That would be expected with a move that is X4294928.25 Y4294950.48. One other thing is that I have printed each of these two part many times independently without any problem. If you look carefully at the code I showed in the picture you can see that the line 46517 where this rogue move takes place is just after the completion of the first part with a retraction. The next move I would expect would be an XY move without any Z move to the next part position than a Z down to start the next Skirt that you can see in the code. My guess is that only the programmers would ever be able to figure this one out. It is very strange. Fortunately for me I have a magnetically held end effector which just popped off when it hit my column (The BerryBot3D is a delta) and no damage done.

Thanks again Guys,

Happy printing!

Werner

 

[berrybot3d 0]

I am still working on trying to figure out why my code is getting jacked up. I produced another gcode file with four items and sure enough after each part printed the same move to forever is in the code?? Is anyone printing multiple parts with success?

Thanks for the help!

Werner

 

[berrybot3d 0]

I am still working on trying to figure out why my code is getting jacked up. I produced another gcode file with four items and sure enough after each part printed the same move to forever is in the code?? Is anyone printing multiple parts with success?

Thanks for the help!

Werner

 

[gr5 2,167]

It sounds like a cura bug for non-ultimakers. Please run the "first run wizard" under expert menu, and let me know what you fill in for all the values. I will then do the same thing here and then place two simple cubes and slice and see if I get the same problems as you.

 

[Daid 306]

(Back after 2 weeks vacation)

 

Which version are you using? I know one release had this issue when you had dual-extrusion enabled (even in a single extrusion print)

 

[berrybot3d 0]

Hi Guys thanks for the reply’s! Hope you had a great vacation Daid! I am using Cura-13.06.4. Running the wizard = Other, 400,400,410, yes to bed center 0,0,0. I do have Preferences set to Extruder count = 1. Printer head size set to 25,25,25,25,55

Thanks for the help!!

Have a great weekend!

Werner

 

[berrybot3d 0]

Hi Guys, Just to update the latest beta version 13.07 is woiking just fine with this issue. Everything working great!

Thanks again for the help!

Werner