Cura 3d Download

[Billie Kjergaard]

TheMethod series is designed for the high-quality production of tools and end-use parts. Their actively heated build chambers, direct drive, and rigid metal frame make it easy to 3D print a specific range of engineering-grade materials with high repeatability and dimensional accuracy using 1.75 mm filament.

So... I run Cura 5.4 just fine. I have a custom printer that I built myself. Roughly following the pursa mendel format and running with Duet2wifi electronics. When I upgraded to 5.6 and now again when I try 5.7, I get this (this is the calibration cube from the Extensions -> Parts for Calibration menu ... but it happens equally with a part that I made. I used the calibration cube so that nobody needed to ask or examine my own part ... for whatever problems it might have.

Another thing ... even under 5.4, after printing at least once, the interface zooms in some random amount and will no longer zoom out past that amount. I don't know what sets the level of zoom, but it means that I re-run 5.4 a lot to be able to look at the part.

Do you have the Printer Settings plugin loaded? Are any of the Cura setting boxes "red"? I ask because some of the settings like "Max Speed Z" in the Printer Settings might be lower than a setting you have in Cura. Something like that will cause a "won't slice" condition.

I don't see how that plugin could cause CuraEngine to fail... It mostly just toggles the Cura preference to auto-slice. Pausing and unpausing effectively results in restarting the slice, which CuraEngine should be able to do just fine.

I think I get your question about 'pause' ... when it fails, I click pause ... so it changes to 'play' ... when I then click to try slicing again ... which also fails. Here's a new log with the printer plugin disabled.

To be clear, I think the printer plugin is responsible for the zoom problem, but this unable to slice problem continues after I disabled the printer plugin. The log I've dragged in here is just loading it, command it to slice a cube and the printer is disabled before loading cura.

You can try setting up your slice in 5.4 and then creating a "Project File". Open the project in 5.7 and it will carry over the settings from 5.4. You can also export your custom setting profile from 5.4 and import it into 5.7. Going from 5.6 to 5.7 those sorts of things carry over automatically but I don't know how many versions back Cura will go.

One error I know occurs is when the "Max Speed Z" is set to maybe 10mm/sec but the "Z-hop Speed" is set to 20mm/sec. I know that will cause a "won't slice" and there are probably others. Beyond that - just going down through all the settings and looking for ones that are red may net you something.

I added the log plugin. Then I saved a project in 5.4. Loading that project in 5.7 works. Then CTRL-N and loading the 10cube works. But restarting cura and loading 10cube then fails. It just goes on slicing infinitely. I've attached the log.

One additional thing you can try. You haven't mentioned what OS your computer is running but t's been determined that on some Windows systems - right-clicking on the Cura desktop icon and selecting "Run as Administrator" can fix some "won't slice" crashes. (That bug has been worked on and should be fixed in the next release.)

If it was running on FreeBSD, I'd already be using it, but Cura is the only software in my build chain that doesn't run there (so windows is still in use). I'm trying to correct this, but Cura's build chain is somewhat obtuse.

Go to %APPDATA% and rename the entire cura folder so it's forced to generate a completely new config from a blank slate. If you're using a custom printer definition, open Cura, then just quit it and put your definition in the %APPDATA%\cura\5.7 (definitions and variants if necessary, if you have a custom definition then you've already done this) folder it should have created so you can open it again and your printer will be in the list to add.

Anyways, set up your printer. Get a model which won't slice (if you want one from the calibration shapes plugin, then go to the configuration folder you just moved out of the way and they're in plugins\CalibrationShapes\CalibrationShapes\models\) and see if it'll slice. If it doesn't, then either your custom printer definition is causing it or you have bigger problems.

And when I say you can approach it from the other direction: that's starting with what you have now and removing things individually until it works. But I prefer to do it from the ground up in case of things like aforementioned bum configuration file somewhere which you wouldn't get around to removing.

This is why you rename the config directory instead of delete it. All your settings are still going to be around and if nothing in there is a problem, sure you have bigger problems, but you can just rename it back and everything will be just like it was. And doing it this way if something in there is a problem, you'll have everything except that.

I installed Cura 5.7.0 today and when I tried to print the PLA was not sticking to the bed plate. I have an Ender 3 V3 SE and it was working perfectly. Not it will not take any PLA on hte bed plate. I thought it was a settinbg on my printer so I done various bed and nozzle heat settings and also bed levellingh and Z off-set. I finally tried to print with Creality Print (even though I dont like it much) and the PLA was sticking to my bed plate. I thought hte update had something to do with it and I uninstalled 5.7.0 and reinstated 5.6.0 and I am back to printing. I have lost a fair bit of PLA with all of the failed prints from nopt sticking to the bed plate.

If a Creality owner submitted a change to the printer definition file and the ABL settings changed then your first layer height might be too tall and the extrusions aren't getting pressed down like they should.

...not that it necessarily helps here. I can print from Cura 5.7 fine. When a Cura version first runs, it copies the configuration folder from the most recent version. Although my situation may differ in that I use a custom machine definition file, not rely on the one included in Cura.

If it printed fine in 5.6, then install 5.7 if it isn't already (they install side by side fine), then go to the Cura configuration folder (in Cura go to Help > Show Configuration Folder) and then go up one folder so you're in the folder with all the different versions and delete the folder for 5.7.

Copy the printer's definition file from 5.6 - default location in Windows is C:\Program Files\UltiMaker Cura 5.6.0\share\cura\resources\definitions\creality_ender3v3se.def.json then go to the folder for 5.7 (just change the 6 in the folder name to a 7) and paste it over the definition file that came with 5.7.

With the Machine Depth and Width at 220 it might be able to get to a negative "X" location. I can see someone trying to move the purge lines further to the left. The 5.6 definition has the purge lines at X10 and that could interfere with large prints.

People submit pull requests to change printer definitions all the time. UltiMaker can check some things regarding other manufacturers hardware but not all things (unless they bought one of every printer on the planet like Slashee does).

A definition change that includes someone's "personal preferences" is never a good idea because they are forcing that on the rest of the users. Definitions should be generic and simply work. If a user wants to customize it then that's their decision. My own Startup Gcode is...complicated. I doubt it's something that anyone else would want, but it works for me.

Cura always puts Z-hops in as G1 lines even though there is no E parameter. Maybe because they are part of the Retraction settings. Still, without an E parameter it seems that they should be G0 lines. Off the top of my head that's the only instance I can think of where the "guideline" isn't followed.

Also true of the Ender-3 V1 and V2, except I think it's more like 10mm. The V3's plate has the room, but has physical blockers installed to prevent it being moved to those areas. Methinks Creality got sick of people not buying bigger, more expensive printers.

Regardless, the printer is likely to either ignore a command that goes outside the space it knows it has or just go as far left as it can go (0). Given my experiments with Z movements trying (and failing) to settle a discussion about whether it's a problem if a "Move Z Up When Done" script which uses relative positioning which would end up above the actual print height and therefore be bad, the E3V3SE will just to move to its endstop on that axis. In this case that would make it wipe its nose at X0 both times which is probably not great trying to extrude at the same height down something you've already done.

It's not that many. I only managed to kill three printers in five months (none my fault) and then this one has been going for a little under 4 months now. And it's not really that hard: the first one was an Ender-3 V2 Neo. The last three (including this one) were/are Ender-3 V3 SE's.

No it doesn't. As a general rule, at least in my experience, only the first line where it starts a section it moves at a different speed (like a travel, or the print after the travel) has a feed rate value.

Or any coordinate system being specified. Just because it uses absolute coordinates by default doesn't mean it's not nice to throw a G90 in the startup gcode to make it clear. Or fix it if someone manages to mess up their firmware and set it to relative by default.

I uninstalled v5.7.0 and tried 5.6.0 and it is not doing as good as it was. I have done a z reset and it still doesn't print properly. Since 5.7.0 screwed something up, even 5.6.0 isn't making it better. Things I try to print either does not stick to the bed or if it does manage to start to stick, it doesn't last long before it gets caught up in the hot end and just makes a mess.. The top wipe and first strip and top clean work great as it should. The rest is not and miss. I have uninstalled 5.6.0 and reinstalled it and it still happens. I am thinking I have to flash the printer firmware to reset the printer. Nothing went wrong before 5.7.0 was installed on my laptop.

3a8082e126