Cura 2.3/2.3.1 x64 BUG

[jeroenm 5]

Hello,

I recently installed Cura 2.3.1 64 bit version and today i started printing some object, but there is a bug in de Gcode. Which cause the print head to go into the model. I had this also with cura 2.3 (see here LINK). Cura 2.3.1 32 bit doesn't have this bug

Gcode simulator:

It was good that I was near my printer otherwise something could have been broken. Now only a 4,5hour model is to waste.

[IRobertI 521]

I'm not quite sure I understand what's happening. Could you point out what it is that's incorrect? Also, do you see the same issue in layer view in cura?

[jeroenm 5]

if you look at the screenshort you can see that the nozzle is inside the model (shown on the right side of the screenshot. Also on the left side the purple line is all over the model.

I can't show it in the cura viewer. Because I now installed the 32bit version which also seems to fix the 64bit version.

Edited November 18, 2016 by Guest

[nallath 1,124]

Without providing us with logging / settings / models you used, there is little we can do about this.

[jeroenm 5]

What would you like to have ?

I only have the Gcode that was generated by Cura with the error.

And the .STL file of the model.

[jeroenm 5]

Yesterday I printed another part made with the 32 bit version and also this one has gone wrong but on the last layer:

So I loaded the model in cura today but now the generated Gcode is good.

Gcode Part 1

Gcode Part 2

[bagel-orb 61]

I don't understand the problem. Could you explain it in the clearest wat you can, please?

What lines of gcode are wrong? What is wrong about that?

[jeroenm 5]

In the first screenshot from the startpost an simulation of de Gcode can be seen (simulator used is from http://gcodesim.dietzm.de/). The Gcode tells the UM2 on the last layer to go down and start printing. Which means that the nozzle is pressed into the already printed part. Which is clearly the supposed to do that.

In the second screenshot on the last layer the Gcode tells the UM2 to start printing in the air on the right side of the already (unfinishend) part.

I have had this problem 4 times with cura 2.3 and 2.3.1. With 3.2 only with the 64bit version and with 2.3.1 32 and 64 bit version.

In dutch:

Ik heb mijn model ingeladen in Cura 2.3.1 64 bits toen gcode laten genereren en die geprint. Bij de laatste laag ging the print kop ineens naar beneden waardoor hij vast kwam te zitten in het model en toen begon hij te bewegen (wat niet ging omdat hij vast zat in het model). Toen ik in de simulator ging kijken zat ik dat hij het zelfde deed, daardoor wist ik dat het niet aan de printer zelf lag.

Twee andere keren had ik soort gelijk probleem maar begon hij in de lucht te printen langs het model. Het gaat niet altijd fout.

De eerste keer had ik dat bij de 64 bits versie van Cura 2.3 toen heb ik de 32 bits versie geïnstalleerd en heb ik het probleem niet meer gezien ook niet na het weer installeren van de 64 bits versie. Toen ik de update 2.3.1 geïnstalleerd had kreeg ik weer het zelfde maar dit keer bij 64 bits en 32 bits versie.

[jeroenm 5]

Today I printed the part again with minor changes to the model. And again a print error. This time it printed some top infill on top of other infill on the same layer.

In the red circled areas you see the green top -1 layer which should not be visible.

The nozzle (the small white circles) is printing again over the purple area.

[peggyb 171]

can you share your stl to see if your problem can be replicated?

Did you check your model (xray) for mistakes?

[jeroenm 5]

The STL can be found here:

STL File

xray didn't show anything as did the layer view in cura.

It seems to be always the last layer.

[peggyb 171]

no problems here, it slices just fine on the default settings of 2.3.1 (Mac)

so it should be something on your pc, graphic drivers perhaps?

[peggyb 171]

[jeroenm 5]

And what does the Gcode simulator show ?

http://gcodesim.dietzm.de/

Because in Cura I also cant find anything. There probably some relation between cura and my windows/drivers.

But I never had this problem with Cur 2.1.2 and earlier it started with 2.3 final.

I also had it with other stl files not only this one.

Edited November 26, 2016 by Guest

[peggyb 171]

simulator does not show anything unusual.

there are some reports about reinstalling Cura and deleting old files in Windows...

Edited November 26, 2016 by Guest

[jeroenm 5]

Still having troubles with Cura 2.3.1.

I installed Cura on my laptop (which never had any cura install) and used the model from the maker magazine test of 2015 the fine_positive_features stl.

I set cura to normal profile and generated the Gcode ans started printing with the following result:

See the print blob in the middle of the print.

This is the screenshot from the last layer of cura:

The green line is not supposed to be there

I also installed 2.1.3 and loaded the same model as above, than generated the Gcode on normal settings and run the simulator. Everything was ok.

Than restarted Cura 2.1.3 and loaded the model again, and again in the simulator it show the same error as above. The same with 2.1.2.

A friend of mine tried it with cura 2.3.0 (on windows 7) without any problems.

Maybe there is some relation with windows 10.

EDIT:

I tried one other Windows 8 PC which I couldn't reproduce the error. And another windows 10 laptop also could not produce the error.

I'm going to reinstall my main windows 10 PC coming weekend to see if it fixes, or that maybe another program causes the bug.

Edited December 7, 2016 by Guest

[jeroenm 5]

Last weekend I reinstalled my windows 10 x64 PC fresh install of cura 2.3.1 after several print the error is back

The blob in the photo below is the result of air printing

Below you can see the Gcode simulation

From this I saw that the it started to print an previous printed model (the blue square with the red crosses).

Is there someone of the Ultimaker Cura team who can help, I now have to check the Gcode every time before printing.

This is the cura layer view of that exact Gcode:

The Gcode can be found here:

Gcode

Edited December 19, 2016 by Guest

[bagel-orb 61]

That is some mighty strange behaviour!

Are you running some post-processing scripts?

Do you eject before you remove the drive on which you have saved the gcode?

You can try Cura 2.4 beta whch was released today: https://ultimaker.com/en/products/cura-software

BTW: The link to the gcode is dead.

[jeroenm 5]

I was rethinking my step when I tested with other PC's and only with my laptop which I tested first I directly saved the file to my SD card and checked the Gcode, than I got the errors. But with all the other PC's I saved the file to the local disk drive and none of them showed any errors.

So that made me suspect the SD card, so I completely formatted my SD card, and so far no issues. Them will tell if the issue is fixed.

[bagel-orb 61]

Sounds promising!