General fixes and improvements to CR-10 SE, Ender-3 V3 KE, Ender-3 S1 Plus, & small fix for Ender-3 V3 SE

[cochcoder]

This PR is working towards fixing all the errors/bugs in the profiles that I added to Orca Slicer.

TODO:

• Fix incorrect line width (mentioned by exploitfate in Add Ender-3 V3 SE .2, .6, .8 and fix small Ender-3 Pro bug #4653)
• Fix incorrect line width for CR-10 SE
• Fix CR-10 SE G-code error (by @bkonosky)
• Add changes to CR-10 SE from @bkonosky in CR-10 SE Config #4966
• Fix incorrect build plate model sizing GCODE Error, Creality CR10 SE profile #4786
• Fix the incorrect bed size for the Ender-3 S1 Plus 0.8 nozzle type
• Make build plate model for Ender-3 S1 Plus more accurate
• Fix low default acceleration in CR-10 SE profile (mentioned here)
• Fix CR-10 SE build area
• minor Ender-3 V3 KE improvements (as mentioned by @Orel-A)

Closes #4786

[bistory]

Yep, never rename an existing file or you will break compatibility ;-)
That's what happened with one of your previous commits.
I know it's tempting to rename files and uniformize names but refrain from doing that. I made the same mistakes ;-)

[cochcoder]

I am having this strange issue where even though I changed the start G-Code and line width to be correct, they don't apply when I build the program, any help with this would be greatly appreciated!

[Orel-A]

There is a bug when settings 0% on retract amount before wipe. It will treat it like we set 52% amount before wipe.
On BambuStudio the bug isn't present.

[cochcoder]

@cochcoder Thank you very much. There are some conflicts, could you take a look?

Done!

[SoftFever]

Looks good
Thank you!

[lmutt]

I notice now that with the latest OrcaSlicer 2.1.0-beta, my Ender 3 V3 KE (stock, no root) do bed mesh calibration at the start of every print... This is the intended new default?

I print offline (copying gcode file to a USB flash drive and put in on the KE), and at the stock KE display/touchscreen interface, at the start of each print there is a checkbox "Calibrate". With this new behavior in OrcaSlicer 2.1.0-beta, I think that this make the user experience a bit weird, because unchecking that "Calibrate" checkbox, the machine still will do the bed mesh (by Orca starting gcode)... And if I check that checkbox, the printer will do the calibration twice (first by machine internal routines then by Orca starting gcode).

Is that right or am I not understanding the concept of this?

[cochcoder]

@Orel-A Do you also experience this? (Just checking in case of different firmware versions). Does the same happen if you upload a copy to the printer over wifi?

[numToStr]

@cochcoder

I have the same setup as @lmutt and can confirm the same experience/behaviour as explained above on every print with v2.1.0-beta . Although I usually upload gcode and start printing via the web interface.

I knew something was different from 2.0.0 but being a newbie i didn't know this is an unexpected behaviour.

[cochcoder]

@numToStr Thanks for conforming this isn't a single device issue. I'll get on it! Just to confirm, does removing bed_calibrate from your start gcode fix this issue, while still having the option for a bed mesh to be made?

[Orel-A]

If you tick the Calibrate checkbox while selecting the file uploaded via Orca on the screen of the printer, of course it'll do calibration twice. Just don't tick the Calibrate button on the printer. I don't see it as an issue. Unless you have a method to detect in the start gcode if the printer was already homed and skip the procedure.

[cochcoder]

If you tick the Calibrate checkbox while selecting the file uploaded via Orca on the screen of the printer, of course it'll do calibration twice. Just don't tick the Calibrate button on the printer. I don't see it as an issue. Unless you have a method to detect in the start gcode if the printer was already homed and skip the procedure.

What would happen if the printer doesn't calibrate at all? Wouldn't work as normal without the bed mesh?

[Orel-A]

Are you asking what would happen if the user doesn't tick Calibrate and doesn't have the bed mesh gcode line that we've recently added? It'll load the previous bed mesh, which could mean an old 5x5 bed mesh.

Typically the user does this when he calibrates the printer for the first time, but he can go to the screen settings and there in Equipment Self-Check he has 2 options, Z-Offset calibration and Auto-Level calibration. If he selects both, the printer will do the z-offset first and proceeds to do Auto-Level correctly. However of he chooses to only do Auto-Level calibration, this won't heat the bed to 60C and will create problems on the next print run. Another problem is that a bed mesh heated to 60C isn't that accurate for 80C when printing Petg since the bed will warp differently... So a mix of various problems.

[cochcoder]

Ok, I'll leave as it is

[maxzera]

What should be the values for these parameters in the CR-10 SE?

[cochcoder]

What should be the values for these parameters in the CR-10 SE?

It'll give a brief description of where to measure when you hover over the values. If anyone finds a dramatically different value for the stock hot end on these printers, let me know ;)

[Orel-A]

@cochcoder
Hi, you accidentally changed the default line width to 0.45mm instead of the internal solid infill.
The bridge flow ratio of 0.95 is causing issues with PETG. Since the material likes to contract under cooling and finally lines snap as there is no enough material to hold the bridge. This happens on both eSun and PolyMaker. On PolyMaker specifically, to make a successful bridge one needs to enable Thick Bridges however. There is no apparent downside to this change on PLA.

Please make the following changes:

"line_width": "0.42"
"internal_solid_infill_line_width": "0.45"
"bridge_flow": "1"
"elefant_foot_compensation": "0.05"
"xy_hole_compensation": "0.025"
"outer_wall_acceleration": "4000"

EDIT: The change filament gcode should be M600 instead of PAUSE.

[cochcoder]

@cochcoder

Hi, you accidentally changed the default line width to 0.45mm instead of the internal solid infill.

The bridge flow ratio of 0.95 is causing issues with PETG. Since the material likes to contract under cooling and finally lines snap as there is no enough material to hold the bridge. This happens on both eSun and PolyMaker. On PolyMaker specifically, to make a successful bridge one needs to enable Thick Bridges however. There is no apparent downside to this change on PLA.

Please make the following changes:

"line_width": "0.42"

"internal_solid_infill_line_width": "0.45"

"bridge_flow": "1"

"elefant_foot_compensation": "0.05"

"xy_hole_compensation": "0.025"

"outer_wall_acceleration": "4000"

EDIT: The change filament gcode should be M600 instead of PAUSE.

This is in regards to the Ender-3 V3 KE, right?

[Orel-A]

This is in regards to the Ender-3 V3 KE, right?

Right.

[cochcoder]

When you enable thick bridges, how much is the quality affected? If there is a significant difference, then I think it should remain disabled.

[Orel-A]

I was more concerned that with eSun PETG the bridges were failing. Fortunately the bridge flow increase solves the issue for this filament.

[Orel-A]

Ah, I think I confused you. When I wrote "no apparent downside to this change on PLA" I didn't mean the thick bridge feature, I meant the bridge flow increase to 1 ratio.

[cochcoder]

Ah, I think I confused you. When I wrote "no apparent downside to this change on PLA" I didn't mean the thick bridge feature, I meant the bridge flow increase to 1 ratio.

That would be it :)

Thank you for finding this changes, I've add them to #5743