Jump to content
Ultimaker Community of 3D Printing Experts
jeroenm

Cura 2.3/2.3.1 x64 BUG

Recommended Posts

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:

5a3323d865df2_Cura2_3Bug.thumb.png.7470fb5bd25eee6eebc8c4c2927f0e25.png

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

5a3323d865df2_Cura2_3Bug.thumb.png.7470fb5bd25eee6eebc8c4c2927f0e25.png

Share this post


Link to post
Share on other sites

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 by Guest

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

5a33242563335_Curaerror.thumb.PNG.b9f4261bab5226c8ccbb41ed1e5310e1.PNG

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.

5a33242563335_Curaerror.thumb.PNG.b9f4261bab5226c8ccbb41ed1e5310e1.PNG

Share this post


Link to post
Share on other sites

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 by Guest

Share this post


Link to post
Share on other sites

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:

5a3324a4c027c_WP_20161206_19_39_59_Rich(2).thumb.jpg.ef4d246d9d444ccfb26ae209629e6488.jpg

See the print blob in the middle of the print.

This is the screenshot from the last layer of cura:

5a3324a3532c1_Curabug2.3.1x64makermagazine.thumb.PNG.de35d1d92281775d885ea053647b9250.PNG

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.

5a3324a4c027c_WP_20161206_19_39_59_Rich(2).thumb.jpg.ef4d246d9d444ccfb26ae209629e6488.jpg

5a3324a3532c1_Curabug2.3.1x64makermagazine.thumb.PNG.de35d1d92281775d885ea053647b9250.PNG

Edited by Guest

Share this post


Link to post
Share on other sites

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

WP_20161219_18_22_20_Rich.thumb.jpg.996309cafc5f27732ed9a3f3d4af07b5.jpg

Below you can see the Gcode simulation

5a33253bf1bca_CuraError.thumb.PNG.5782f2f47c57906be86751bfaa0cc977.PNG

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:

5a33254146d97_CuraError(Curalayerview).thumb.PNG.5b5977819dd49c64e66718f082cf083a.PNG

The Gcode can be found here:

Gcode

WP_20161219_18_22_20_Rich.thumb.jpg.996309cafc5f27732ed9a3f3d4af07b5.jpg

5a33253bf1bca_CuraError.thumb.PNG.5782f2f47c57906be86751bfaa0cc977.PNG

5a33254146d97_CuraError(Curalayerview).thumb.PNG.5b5977819dd49c64e66718f082cf083a.PNG

Edited by Guest

Share this post


Link to post
Share on other sites

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.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

Terms of Use Privacy Policy