DivingDuck

This isn't surprising. PC is not resistant to bases, aromatic and halogenated hydrocarbons as well as ketones and esters. Prolonged exposure to hot water can cause stress cracking (as you already experienced). In combination with dishwasher detergents whereas alkaline compounds (bases) are an essential part of, this isn't a really a good choice. ABS is maybe the better choice for this DIY and you can gain the temperature range with annealing a bit further. As well doable at home. Shrinking during the annealing process needs to be compensate in addition and is part related. You need to make some test parts for annealing.

Nicely written explanation. We need a bell for new articles in the support area 🙂

Use Cura showing and directing you to the correct place where the configuration folder live. That way there is absolutely no confusion about this question (and this is why the entry exists in the menu). It it mentioned in the second post in this thread. Some remarks: 1. Cura: -->Help -->Show Configuration Folder 2. Each Cura version have its own configuration folder (... 4.13, 5.0, 5.1, 5.2 ...) 3. Everything in %appdata% is for usual Windows user not visible as this is an hidden folder structure. You maybe need to change configuration of your Explorer / file manager to see them. (For Explorer see one post above your post for the ) BTW: %APPDATA%\cura\5.1 works fine in case you had installed this version and not delete the configuration files during an update / uninstall of Cura. %APPDATA%\cura works as well to find all existing configurations, but again: use Cura to show you the way to your "journey".

It looks like you possibly change the code page of the file to something different to utf8. This can happen if you use a normal text editor and then save the file as text file. or add a character ("¤") in your profile. Maybe with copy and past from an other file or html file Use instead a coding editor like notepad++, vs code or something similar. For the latter one and most possible issue find and delete this wrongly inserted character in the profile. Position 37 should be a good indicator where this character is located in the mentioned file.

As @MariMakes already told, the file you had attached is corrupt. The stl file inside the .3mf file is corrupt. No chance to do anything. A suggestion is to attach a newly created project file once more for upload and add in addition the stl file. There are as well missing some important information, like Cura version, operating system and material used. The part seems to be small. Depending on the material used it is maybe worthwhile to play with flow rate, temperature, fan speed and retraction length / -speed in addition.

+1 good catch. Spaces in file and path names are often a problem. This is why I always add surrounding quotation marks for path and file names in the batch example.

Here is a good description for commonly errors with stl files: https://facfox.com/docs/kb/the-most-common-stl-file-errors-you-will-meet-in-3d-printing-process Sketchup is known to export problematic stl files. Sketchup doesn't enforce for solid parts (at least the older versions). You can find a lot of requests here in the forum about this topic.

Check if the STL export produce a defect file. Install the plugin Mesh Tools from marketplace and check your stl file.

There seems to be no redirections for former link addresses. I found a new location, but this isn't as elegant as before: https://support.makerbot.com/s/topic/0TO5b000000Q4utGAC/ultimaker-cura

@chizlerstone, you can't update the firmware with Pronterface. Why don't you update the firmware with a SD card, as this is usually the way to do this? https://jgaurorawiki.com/a5s/firmware

The best way to overcome these problems is to create a folder that includes all files needed including the .stl file and a little batch file for running the slicer engine. Looking on your errors there are missing: ultimaker2_extruder_0.def.json, in addition you need: ultimaker.def.json, fdmextruder.def.json Here is an litte example, extract the folder Test to your Desktop and run batch file SliceUM2.bat in cmd window: Test.zip

This happen because the Cura installation folder change with every new Cura version. Select "user defined" instead of "Cura", click on folder and select the new location of Cura. In my case it is: "c:\Program Files\Ultimaker Cura 5.2.1\Ultimaker-Cura.exe" In your case it is: "c:\Program Files\Ultimaker Cura 5.1.1\Ultimaker-Cura.exe"

Usually for existing profiles from Ultimaker this isn't a huge problem as they at least do some checks of those profiles / configurations and correct general settings if they need to be changed. For own configurations and profiles you need to do that yourself. Only major setting changes like version and id management will be adjusted during migration. But you can't really be sure as no one else than you know what's in your configurations and what needs to be adjusted. Let me say it that way, if you do it as an service business and you want support printer configurations over lifetime than you better calculate a decent amount of support time and cost for those kind of activities. Regarding saved projects, they are in general not broken as they was build with an correct working configuration matching a Cura version. With an new version of Cura you have at least the chance to import the project. The big question is, will a well tuned project print with a new Cura version as good as with the old version? My answer is: it depends, in most cases not. A project file is good as long you stay in the same environment. Changing the software or firmware version will change the game.

@ripptech, had you seen this: https://support.ultimaker.com/hc/en-us/articles/360011889579 It looks like your OS isn't any longer supported.

Clean in this case means renaming the configuration folder from cura to cura-x. When you start Cura after renaming it won't find any previous configurations and installed plugins and create a new one without any old stuff like plugins and old configurations. The idea behind is to identify if the start problem came from a plugin or an old configuration. If the test wasn't successful you simply delete this newly created folder and rename the old folder back to cura. So you don't loose any setups from old releases. In case Cura will start correctly you know that there is a problem with old configurations or used plugins and you can try to evaluate further.

I just installed 5.2.1 for testing, runs fine for me., but this won't help you. Had you tried to run it "clean" w/o an existing configuration folder? Maybe worth a test. Rename (not delete, as you will loose your old configurations) the cura data folder to like "... \AppData \ Roaming \ cura-x" and start Cura.

Only an suggestion, try to start it without AV. I had a crash where my installed debugger came up during the first time I start Cura and recognize that Windows generate a lot of telemetry and anti-malware system traffic during the first start. This seems to block some resources Cura needs for the first run to setup everything. There was an additional problem with Sidebar Gui 4.4.0. After I did install the latest development version from @fieldOfView the problems with crashes gone away.

Beside the good tips from @gr5 there are 3 resources to gather further information on how printer definitions and profiles work: https://github.com/Ultimaker/Cura/wiki/Adding-new-machine-profiles-to-Cura https://github.com/Ultimaker/Cura/wiki/Profiles-&-Settings and looking into existing definitions and profiles either in program and data directories of Cura or the definition files at Github (https://github.com/Ultimaker/Cura/tree/main/resources and https://github.com/Ultimaker/fdm_materials) The problem with making your own profiles and definition is, that you need to review and update them yourself frequently when new Cura releases come up. Usually this isn't a route that I would suggest users with off the shelf printers especially when there are existing profiles supported from Ultimaker, printer manufacturer or the community here.

@GregValiant, Good catch. I had overseen that lower case y. My firmware have no problem with lower case but other firmware may have and for good measure it is always good practice to us uppercase letters. Edit: Forgot to mention I use both methods if things go wrong. @obewan's method is the last one I use if every goes wrong ( print error or filament shortage when I'm not there, power loss and cold print bed etc). This is then mostly the only solution to rescue a print somehow.

This is bad. Back on track with the paused print isn't really possible. You need do it manually as new print. The gcode file is a text file. Use a tool like Notepad++, Visual Studio Code etc. for editing. What you can do is split the gcode file at the height you did measure (look for G0 ... Zxxxx.xxx where xxx.xx is the print height), then add the start code and alter it to do heating, purging a bit of filament out of the nozzle and manual homing. Before you start the print you need purge a bit filament out of the nozzle in the air. Homing X and Y shouldn't be a problem because your print head is above the print (or you need to move the head to an position where it do not interfere with the existing print). For Z you need to move the head somewhere to a position where you can freely move the head to 0 e.g in the back of the print head. Don't forget to reset the E step counter before you continue the print ( to 0 if you print with relative extrusion or to Exxxx if you print with absolute extrusion) like G92 E0 or G92 Exxxx.xxxxx where xxxx.xxxxx is the value to extrude from. Something like this: ; Manual edited code... ; e.g. Print stops at LAYER:2119 at Z249.935 ; Search for Z249.935 ; see line 5692869 to 5692878: ; line 5692869: G0 F600 X156.533 Y178.621 Z249.935 ; line 5692870: G0 F7200 X160.478 Y181.304 ; line 5692871: G1 F3000 E3704.29793 ; line 5692872: G0 F7200 X160.588 Y181.539 ; line 5692873: TIME_ELAPSED:413513.366218 ; line 5692874: LAYER:2119 ; line 5692875: G1 F3000 E3701.29793 ; line 5692876: TYPE:WALL-INNER ; line 5692877: MESH:SS_Cinderella Castle Disney .3mf ; line 5692878: G1 F3000 E3704.29793 ; ;FLAVOR:Marlin ;TIME:417622 ;Filament used: 205.143m ;Layer height: 0.15 ;MINX:2.669 ;MINY:70.295 ;MINZ:0.36 ;MAXX:347.334 ;MAXY:279.078 ;MAXZ:339.225 ;Generated with Cura_SteamEngine main M140 S65 M105 M190 S65 M104 S225 M105 M109 S225 M82 ;absolute extrusion mode M201 X500.00 Y500.00 Z100.00 E5000.00 ;Setup machine max acceleration M203 X500.00 Y500.00 Z10.00 E50.00 ;Setup machine max feedrate M204 P500.00 R1000.00 T500.00 ;Setup Print/Retract/Travel acceleration M205 X8.00 Y8.00 Z0.40 E5.00 ;Setup Jerk M220 S100 ;Reset Feedrate M221 S100 ;Reset Flowrate G92 E0 ;Reset Extruder ;G28 ;Home ;G29 ;Automatic Leveling G28 X Y ;First home Axis in x and y G1 X5.00 y295.00 ;then go to back of print bed (you need to set a value that match with your ;bed dimensions and where the print head do not crash into the model) G28 Z ;Now home z G1 Z252.935 ;move the head a bit higher as the print was (e.g. Z252.935 if the print broke at 249.935mm) G1 X5.00 Y5.00 ;move the head to a start position outside the print (e.g. G1 X50 Y100). G1 E20 ; extrude 20mm filament to be sure to have filament ready. You need to remove that. ;G1 Z2.0 F3000 ;Move Z Axis up ;G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position ;G1 X10.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line ;G1 X10.4 Y200.0 Z0.28 F5000.0 ;Move to side a little ;G1 X10.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line ;G92 E0 ;Reset Extruder ;G1 Z2.0 F3000 ;Move Z Axis up G92 E3701.29793 ; Preperation, set E step counter to last known absolute value (wherever ;it was when the print failed at layer xxx) G1 X160.588 Y181.539 ; Preperation, set x,y to last known position G1 Z249.935mm ; Preperation, set z to last known position ; now delete all lines in a copy of the original file from line 1 to line 5692873 and insert this ; new start code at line 1 newStartCodeTemplate.gcode

The actual plugin (version 1.2.1) should work well with Cura 5.x. Maybe your plugin need a update?

Er druckt Schokolade im Vasemode. Da funktioniert der Vorschlag nicht. Probiere es mal aus 🙂

Extensions -> Post Processing -> Modify G-Code -> Pause at height

Schau dir mal Minimum Layer Time und Minimum Layer Speed unter Cooling an. Mit diesen Parametern kannst du dies in Grenzen beeinflussen. Was diese beiden Parameter genau machen, wird im Plugin Cura Settings Guide gut beschrieben.

Versuches es mal mit der manuellen Einstellung der Nahtposition über XY Koordinaten.