GregValiant

Double dip.

I made up a custom definition file. I have that in there as an override. I also don't like Support Horizontal Expansion defaulting to 0.8 so that's in there as well.

You will need to switch to "Custom" settings and unhide all the settings. "Skirt Height" is under the "Bed Adhesion" settings. Set it to "1". I find it annoying that when the feature was added the default was made "3".

If the printer is capable you can try the post processor "Create Thumbnail". It is under "Extensions - Post Process - Modifiy Gcode" and then "Add a script".

This doesn't look right. If you are going to put this into an accordion it won't pump air. Slashee - I couldn't get it to set flat on the build plate either.

Congratulations. It will now hold more than a capful. 🍺 Loft and Shell are maybe the two trickiest functions to work with when you are trying to make a printable model. A Shell feature needs to be in just in the right place in the feature tree. Lofts from a square to a circle is tough math. I will often break a circle into 4 arcs and add in extremely short lines between the arcs. It still looks like a circle, but Inventor will see 4 sides to the square and match them up with the 4 arcs. That will often eliminate any twists that might develop. For threads I use my own thread form that has a 70° included angle because they don't require support. Flat roots and thread ends are also helpful when printing.

304 naked edges and 4 planar holes. Lofts are always tough because the math of the surface is so complex. In addition, it is easy to get gaps between a loft and another feature. They look merged, but they aren't. This is what AHoeben is talking about. Errors in a model seriously affect a slice. Here is the transition between the lower rectangular shape and the transition loft. Cura was unable to decide if they should be connected or not. This model needs to go back into CAD and be repaired. A couple of fillets at the transition wouldn't hurt. When the loft is constrained to the other parts of the model, then the slice will be performed as you would expect.

You aren't giving much information here. What exactly are you trying to do? What does the model look like? Is there more than one model? If there is more than one model do they "merge" or are they always separate? A project file ("File | Save Project") always helps.

Slashee nailed it. You will need to splice two files together. There is a trick to smooth the process. Just talkin' here... Let's say you want the print to change from normal to spiralize at layer 250. Put a "Pause at Height" at layer 250. Slice the file with the "normal" settings for the base and save the gcode as "something_base.gcode". Switch over to "Spiralize" and touch up your settings. Do not change the layer height (you will learn how to do that in the advanced class). Slice the file and save the gcode as "something_upper.gcode". Open the base file and search for "PauseAtHeight". Delete everything from the line ";script: PauseAtHeight.py" to the end of the "base" file. Open the "upper" file. Search for PauseAtHeight again in the Upper file. Copy everything from the Z return line (similar to "G1 F300 Z15.2") to the end of the file. That line is usually 2 lines below the actual pause line. Paste all of that into the new end of the base file. Do a "save-as". I usually name the file "something_combined.gcode". The base will print, the printer will see the transition code and shuffle over to the start of the spiralize, the extruder location will be set to continue, and Bob's your uncle. ;TYPE:CUSTOM ;added code by post processing ;script: PauseAtHeight.py BASE FILE UP TO THIS POINT UPPER FILE FROM HERE DOWN TO THE END G1 F300 Z15.2 ;>>>>>>>>>This line might seem wrong if Z-hops are enabled. G1 F9000 X106.155 Y105.917 ;>>>>>>This is the XY "return to" G1 F300 Z15.2 ; resume height >>>>>double check this for sure G1 F2100 ; restore extrusion feedrate M82 ; switch back to absolute E values G92 E2271.49422 ;>>>>>>>>>>>>>>>>This sets the E location so the print will continue smoothly. The same trick can be used to change layer heights. If the base is at 0.20 Layer Height and the upper is at 0.10 layer height then the "Pause" in the second file would be at layer 2X whatever it was in the first file. In the example above the pause in the second file would be at layer 500. You must always double check that the extruder location, XY return location, and the Z height are correct.

The same files still work for me in 5.6.0. The "creality_base.def.json" file calls for 4 possible extruders. Extruder 0 is included with Cura and the other three are contained in that zip file. Double check that you have the new "creality_base.def.json" file in the: "C:\Program Files\UltiMaker Cura 5.6.0\share\cura\resources\definitions" folder. Check that the 3 additional extruder files are in the: "C:\Program Files\UltiMaker Cura 5.6.0\share\cura\resources\extruders" folder. When the files are correctly placed you should see this in the Machine Settings in Cura and your Ender 5 Plus should be configurable with up to 4 extruders:

After sitting at room temperature all night my hot end and bed are different by 3°. 175° sounds pretty low but every thermocouple/thermistor thing is different. I can't get a new "minimum temperature" to save in the printer. At power up it always goes back to 170. If I was having a problem I would need to include an M302 in my startup.

I'm getting the same thing on my older Ender 3 Pro. Even if it's a relative move, max height is max height.

If "Ironing" is turned on and the settings are for something like a 0.1 line width at 10% flow then it will look as if the extruder has stopped because it is turning so slowly. That would pretty much effect Top Skins only. If the Hot End Temperature falls below some number (usually around 170° to 175°) the extruder will stop turning to avoid cold extrusions. At the end of "LAYER:0" in the gcode there might be an M104 line that is supposed to change the printer from "Initial Layer Print Temperature" to "Print Temperature". If that line is wrong or is mis-understood by the printer, then the hot end could shut down and extrusion would stop. Other than those two situations: if there is an E parameter in a movement line (G1, 2, 3) in the gcode, the extruder should move to push or pull that much material.

The Sidewinder has been around for a bit and I don't recall any problem like this. The files are in your installation or it wouldn't show up at all. FYI the build plate file is "artillery_swx1.stl" and it's in the "C:\Program Files\UltiMaker Cura 5.6.0\share\cura\resources\meshes" folder. As Slashee says, there isn't anything that is user configurable here. The definition file tells Cura which platform to load and there are a couple of numbers that tell Cura where to put it.

To see if I understand... There are two gcode files. The first file finishes with a partial top layer. The second file is printed. It completes the partial layer left by the first file and continues for 2 more layers. The print finishes with the standard ending gcode. Is that what you are trying to do? When the first print ends - some firmware will automatically disable the stepper motors even without an M84. At that point they lose their location. When the second print starts with no "G28" the steppers don't know where they are. That will cause layer shifts and might be the cause of the nozzle hitting the bed. Have you tried "splicing" the files by copying the second file into the first file? If you use "Pause at Height" at the layer after that partial layer you could cut the pause gcode out and paste it in where you wanted it. You would absolutely need to change the XYZE lines so the print would continue from the correct location of all axes. That is not as difficult as trying to print a second gcode file on top of a print. This would be the pause portion of the gcode. The lines that would/might require changes are in bold. ;TYPE:CUSTOM ;added code by post processing ;script: PauseAtHeight.py ;current layer: 15 M83 ; switch to relative E values for any needed retraction G1 F300 Z5 ; move up a millimeter to get out of the way G1 F9000 X0 Y0 ; park the head G1 F300 Z15 ; too close to bed--move to at least 15mm M104 S205 ; standby temperature M0 ; Do the actual pause M104 S205 ; resume temperature G1 F300 Z4 G1 F9000 X64.325 Y107.595 G1 F300 Z4 ; move back down to resume height G1 F2100 ; restore extrusion feedrate M82 ; switch back to absolute E values G92 E1633.44314 ;LAYER:15

The printer build plate, and it's callout in the definition file, are part of the definition package that was submitted to UltiMaker. What printer are we talking about?

Yes there are several. On Jan 23 @CasperLamboo responded HERE on Github in response to one of the bug reports. It would appear that the problem with "initial_extruder_nr" might have been addressed for 5.7.

If you select one of the included profiles (like "Standard") and when asked select "Discard all changes" you should get settings that work correctly for something basic like a calibration cube.

I have a third end stop switch for the Z (but I don't have ABL). There is no "positive" end stop switch for any axis. That's in the firmware and that's why "relative" moves can be a problem. Some firmware is configured to respond to M211 which is "set or disable software endstops". The firmware should stop a move to something like X1000 but a relative move of X1000 might slip through. That would be ugly and the printer could hurt itself. Congratulations on your system of "Start in the middle and work both ways". It is just like my system of "Randomly stumble in the dark" only different.

I don't see that on my machine. If the firmware is configured that way then that's what it is. I moved the F parameter to the end and it made no difference. Other slicers always put the feedrate at the end. The parameter is in the line for that move and it should be obeyed as an absolute value for the move.

"line 6 will decelerate from 5000mm/min to 1000mm/min over the course of the move," ??? Line 6 should be a move back to X10 at 1000mm/min. There can be no "gradual change over the course of the move" from 5000 to 1000.

You can query the printer for "where are you right now" using M114 but it requires a USB connection that can read the response and then the response would need to be parsed. Parsing a response requires an additional app as Cura doesn't really "communicate" (it's "send" only), and although Pronterface will display a response, it doesn't do any parsing. You can see that all of that goes well beyond what can be done in your Ending G-code. This is a response to M114 from my older Ender 3 Pro. The last three numbers are the "steps" that have been sent to get it to the current XYZ location. X:111.22 Y:111.22 Z:5.20 E:1123.57 Count X:8880 Y:9280 Z:2080

There is a bug in the "initial_extruder_nr" replacement pattern. It always returns "0" rather than the actual tool number. You have it in two places in your startup gcode. Hopefully it will be addressed in Cura 5.7.0. A workaround is to remove the temperature lines from your StartUp Gcode and allow Cura to determine temperatures. It might not be as efficient as a custom one but it should work. This is from the BIBO definition file and has my suggestions. ;M104 T0 165 ; remove ;M104 T1 165 ; remove M109 S{material_print_temperature_layer_0} ; alter G21 ;metric values G90 ;absolute positioning M107 ;start with the fan off G28 X0 Y0 ;move X/Y to min endstops G28 Z0 ;move Z to min endstops G1 Z2.0 F400 ;move the platform down 2mm ;T0 ; remove G92 E0 G28 G1 Y0 F1200 E0 G92 E0 ;T{initial_extruder_nr} ; remove M117 BIBO Printing...

Here is the Monoprice guide pamphlet.

The "Time Lapse" plugin should be available under the "Extensions / Post Processing / Modify Gcode" menu, and then "Add a Script". I did a slight rewrite of the "Time Lapse" script. This one allows you to choose how often to take a picture rather than always being every layer. Unzip and put "TimeLapse_GV.py" into the Configuration Folder ("Help | Show Configuration Folder") and the "scripts" sub-folder. TimeLapse_GV.zip