Hardware How to Root & Improve the Creality K1 + recommended mods & upgrades

[TheStonedModder]

Please note that this guide is a WIP. If you have any suggestions on how I can improve it, or notice any errors please don't hesitate to let me know!

IMPORTANT: When updating to new firmwares your gcode_macros.cfg file will be deleted so make constant local backup! Your printer.cfg should be safe, however it is still a good practice to back this up as well.

Hello all! I recently got a new 3d printer to replace my workhorse Ender 3 and figured I could document and share the experience since this is still a relativity new printer, and since a lot of information around it is mixed between different subreddits, and locked member only facebook groups. There is also a public facing guide on Github but I feel like some of it is not worded the best, and some sections could use a bit more detail since it assumes you've dealt with Klipper in the past. This guide is also missing a section for recommended mods & upgrades for newcomers looking to learn more about where they can take this printer.

Spoiler: Why root my printer?

A lot of printers nowadays us an open source firmware called "Klipper" thanks to being able to install it to a Linux(or even windows with WSL) machine to offload the computation tasks from the generally weak onboard SoCs that the printers come with. This alone allows GCODE to process at a much faster pace you would expect over recent years so we can hit much faster printer speeds as well as do other fun things like Input Shaping since using an an external computer generally allows access to GPIO so we can connect an ADXL345 and measure the vibrations

The creality K1 comes with Klipper preinstalled. The the issue is, its their own personal locked down & outdated by over a year fork/version of Klipper that has useful settings locked away or even straight up misconfigured or could be configured more optimally to give faster and better quality prints.

Spoiler: Requirements

The latest official firmware from Creality's website(or anywhere else you can find it assuming its a trusted source) - this is to ensure we are actually able to gain root access since this was added at a later time.

A USB Stick formatted to FAT32 with a 4096 allocation size

Putty - so that we can SSH into our printer

Creality K1 Reset Utility - To prepare the printer for our Klipper Scripts (THIS IS A DIRECT DOWNLOAD)

Spoiler: Step 1: Install the firmware update

Copy the downloaded Firmware IMG file from the requirements spoiler, to the root of your flash drive

Turn off your printer if it is on

Insert the flash drive

Turn the printer back on

Wait for the update pop-up to appear on your touch screen

Press Upgrade and wait for your printer to restart

Once you see the home screen again, you can safely remove your flashdrive and delete the IMG file if you wish to do so

Spoiler: Step 2: Reset your printer to Factory settings using Creality K1 Reset Utility

Before we go ahead and root our printer, we will want to make sure its on its default settings. The easiest way to do that is to use Creality's reset utility and just do it via Websocket

Simply unzip the zip you've downloaded above

open Creality_K1_Reset_Utility.html inside your favorite internet browser,

enter your printer's IP address. If you don't know your IP you can find it easily under the network tab on your Printer's Touch Screen

click the blue reset button

Spoiler: Step 3: Enable Root Access

On your touch screen Navigate to the settings tab, and tap "Root account information"

Scroll through the disclaimer if you wish(who reads these anyway)

check the box

Tap OK and root access show now be enabled. Don't forget this Username and Password as you will need it for the next steps.

Spoiler: Step 3: Connect to the printer over SSH using Putty

Open Putty, and fill out the "Host Name" box with the IP address of your printer, and click "open". If you're not sure what this is, open the Network tab on your Printer's touchscreen. The IP Address will be located there. If you get a warning in Putty just click accept and move onto the next steps. This is normal


Putty should now ask you to Login. Enter the username you found in the previous step into this field. For me it was "root" afterwards it will ask you for a password. You should also have this from the previous step. For me the password was "creality 2023" (NOTE: Its normal to not see your password as you're typing it out, just hit enter after you type it in) Once complete you should see a screen like mine

Spoiler: Step 4: Using the Installation Helper Script

With Klipper being open source, and not being the easiest to install for newcomers to the community. The community has gone ahead and created a fancy helper script that will do all the heavy lifting to assist us along with this install to our K1 Printers. There are similar scripts around with a popular one called KIUAH but this version is specifically taylored to the K1 series as opposed to a general purpose script

Enter this command to download the script to the root folder of our printer

cd && wget --no-check-certificate https://raw.githubusercontent.com/Guilouz/Creality-K1-and-K1-Max/main/Scripts/installer.sh

Spoiler: How to update the script IF NEEDED

You can use the following command to update the helper script if needed.

cd && rm -f installer.sh && wget --no-check-certificate https://raw.githubusercontent.com/Guilouz/Creality-K1-and-K1-Max/main/Scripts/installer.sh

Now run the script, and you should see a screen similar to mine. For more information on everything you can install using this script and what each option does. I recommend checking out the Github entry here

cd && sh ./installer.sh

Spoiler: Getting an error installing packages? Are you getting an error similar to this while trying to install a package? Easy fix simply install Entware to your system and wget-ssl [CODE

Connecting to github.com (20.248.137.48:443)
wget: TLS error from peer (alert code 80): 80
wget: error getting response: Connection reset by peer
Download failed. Exit code: 1
[/CODE]

To install Entware open the Helper Script, type "1" into the input field and validate it with Enter, than type "5" for Entware on the next screen, and validate that option with your Enter Key once more.

Once installed, finally you can install wget-ssl with the following command, and this should fix your errors

opkg install wget-ssl

Spoiler: Step 5: Install Moonaker, NGINX, Fluidd/Mainsail

Now that we have our helper script, we can go ahead and install the basic necessities for accessing our unlocked Klipper.

Following the menus in Putty install the following

Moonraker and NGINX
Fluidd or Mainsail (depends on your preference, just make note of which you install as their ports to access the interface are different. Fluidd uses port 4408 while Mainsail uses port 4409

After you finish installing these packages, you should now be able to access your Web interface by enter your printers IP address and your port from the previous step into your internet browser of choice following the IPORT format

For example to access Fluid I would use 10.0.0.1:4408

Or if I wanted to access Mainsail I would use 10.0.0.1:4409

You're welcome to install and mess with anything else here as well, but I won't be covering them until later on in this guide

Spoiler: Step 6: Installing and setting up KAMP for adaptive purging and bed mesh creation(speed up the start of your prints!)

Go to the configuration page inside your interface of choice. I'm using Fluidd which can be accessed from your IP:4408 if you're using mainsail use IP:4409 instead

Inside this file find the "enable_object_processing" line under File Manager and change it from False to True like so

[file_manager]
queue_gcode_uploads: False
# Set to 'True' if you use KAMP
enable_object_processing: True

Click Save and restart on the top right of the web interface and go back to the configuration files section of the interface, and open up "printer.cfg" now. This is where all your actual printer parameters are stored.

Inside of this file add the following line to enable KAMP

[include KAMP_Settings.cfg]

Click save and restart once again

Now open your "gcode_macro.cfg" file and search for a macro named "gcode_macro START_PRINT" disable "CX_PRINT_LEVELING_CALIBRATION " by commenting it out with a # and add "BED_MESH_CLEAR" & "BED_MESH_CALIBRATE " Underneath the line you just commented out. Afterwards your START_PRINT macro should look similar to mine

[gcode_macro START_PRINT]
variable_prepare: 0
gcode:
  WAIT_TEMP_END
  CLEAR_PAUSE
  {% set g28_extruder_temp = printer.custom_macro.g28_ext_temp %}
  {% set bed_temp = printer.custom_macro.default_bed_temp %}
  {% set extruder_temp = printer.custom_macro.default_extruder_temp %}
  {% if 'BED_TEMP' in params|upper and (params.BED_TEMP|float) %}
    {% set bed_temp = params.BED_TEMP %}
  {% endif %}
  {% if 'EXTRUDER_TEMP' in params|upper and (params.EXTRUDER_TEMP|float) %}
    {% set extruder_temp = params.EXTRUDER_TEMP %}
  {% endif %}
  {% if printer['gcode_macro START_PRINT'].prepare|int == 0 %}
    {action_respond_info("not prepare.\n")}
    PRINT_PREPARE_CLEAR
    CX_ROUGH_G28 EXTRUDER_TEMP={extruder_temp} BED_TEMP={bed_temp}
    CX_NOZZLE_CLEAR
    ACCURATE_G28
    #CX_PRINT_LEVELING_CALIBRATION
    BED_MESH_CLEAR
    BED_MESH_CALIBRATE

Click save and restart again.

Afterwards open your slicer of choice and make sure you enable "Label Objects" otherwise you won't be able to pick and choose specific parts of a print if you're printing multiple items and one fails. this saves you from having to restart the entire print and having to clear your build plate as you can just exclude the failed object and print around it

If you're using Prusaslicer or a Fork of it(I recommend Orca Slicer) I also recommend adding a few more macros to your gcode_macros.cfg file

[gcode_macro DEFINE_OBJECT]
gcode:
  EXCLUDE_OBJECT_DEFINE {rawparams}

[gcode_macro START_CURRENT_OBJECT]
gcode:
  EXCLUDE_OBJECT_START NAME={params.NAME}

[gcode_macro END_CURRENT_OBJECT]
gcode:
  EXCLUDE_OBJECT_END {% if params.NAME %}NAME={params.NAME}{% endif %}

[gcode_macro LIST_OBJECTS]
gcode:
  EXCLUDE_OBJECT_DEFINE

[gcode_macro LIST_EXCLUDED_OBJECTS]
gcode:
  EXCLUDE_OBJECT

[gcode_macro REMOVE_ALL_EXCLUDED]
gcode:
  EXCLUDE_OBJECT RESET=1

Spoiler: Using your printer's built in buzzer/speaker for alerts

If you would still like to use the built in buzzer in the printer to get notifications (like filament runout or thermal runaway)

That open your installation helper script and install The "Buzzer support files" Please note you will also need to install Klipper Gcode shell commands from this same menu before the script will allow you to download the Buzzer support files

After they are installed open your "gcode_macro.cfg" file and add the following to it

[gcode_shell_command beep]
command: aplay /usr/data/beep.mp3
timeout: 2.
verbose: False

[gcode_macro BEEP]
 gcode:
   RUN_SHELL_COMMAND CMD=beep
   RUN_SHELL_COMMAND CMD=beep
   RUN_SHELL_COMMAND CMD=beep

Don't forget to click save and restart. If you want to test this out you can use the "beep" macro on your homescreen, or enter "beep" though the console in the web interface. You can also use this logic to play a beep in any custom macros you make. For example here is an END_PRINT macro that will play a sound once printing is complete. Isn't this simple?!

[gcode_macro END_PRINT]
gcode:
  PRINT_PREPARE_CLEAR
  M220 S100
  M204 S500
  TURN_OFF_HEATERS
  M107 P1
  M107 P2
  END_PRINT_POINT
  BEEP
  WAIT_TEMP_START
  M84

Spoiler: Setting up and improving Input Shaping

Creality only set up their input shaping by default to use the "ei" shaper without an option for the user to select anything else. The issue with this is, even though the built in ADXL is capable of measuring both the X and Y axis resonances but due to creality using the "ei" shaper the resonance test results from the Y axis is also copied to the X axis. Which is not optimal.

Now that we understand what and why we are fixing lets get into how.

Open your gcode_macro.cfg and search for "gcode_macro AUTOTUNE_SHAPERS" once you find it comment/disable the line "variable_autotune_shapers"

Once done it should look something like this

[gcode_macro AUTOTUNE_SHAPERS]
#variable_autotune_shapers: 'ei'
gcode:

Next search for a macro called "gcode_macro INPUTSHAPER" and replace "AXIS=Y" so it just says SHAPER_CALIBRATE. Once done it should look like the "NEW" spoiler below

Spoiler: OLD gcode_macro INPUTSHAPER

[gcode_macro INPUTSHAPER]
gcode:
  SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=0
  SET_FILAMENT_SENSOR SENSOR=filament_sensor_2 ENABLE=0
  G90
  G28
  {% set POSITION_X = printer.configfile.settings['stepper_x'].position_max/2 %}
  {% set POSITION_Y = printer.configfile.settings['stepper_y'].position_max/2 %}
  G1 X{POSITION_X} Y{POSITION_Y} F6000
  G1 Z10 F600
  SHAPER_CALIBRATE AXIS=y
  CXSAVE_CONFIG
  SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=1
  SET_FILAMENT_SENSOR SENSOR=filament_sensor_2 ENABLE=1

Spoiler: NEW gcode_macro INPUTSHAPER

[gcode_macro INPUTSHAPER]
gcode:
  SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=0
  SET_FILAMENT_SENSOR SENSOR=filament_sensor_2 ENABLE=0
  G90
  G28
  {% set POSITION_X = printer.configfile.settings['stepper_x'].position_max/2 %}
  {% set POSITION_Y = printer.configfile.settings['stepper_y'].position_max/2 %}
  G1 X{POSITION_X} Y{POSITION_Y} F6000
  G1 Z10 F600
  SHAPER_CALIBRATE
  CXSAVE_CONFIG
  SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=1
  SET_FILAMENT_SENSOR SENSOR=filament_sensor_2 ENABLE=1

A very small change, but now we should be able to apply the results from both the X and Y measurements instead of just apply the Y measurement to both axis' and you don't even have to do anything different! The calibrate checkbox before each print will automatically detect and use these changes.

If you'd like to be able to run and apply the results of this test manually you can also set it up as a macro that can be clicked from the homescreen by adding the following to your gcode_macro.cfg" file

[gcode_macro INPUT_SHAPER]
description: Measure X and Y axis resonances
gcode:
  G90
  {% if printer.toolhead.homed_axes != "xyz" %}
    G28
  {% endif %}
  SHAPER_CALIBRATE
  {% set y_park = printer.toolhead.axis_maximum.y/2 %}
  {% set x_park = printer.toolhead.axis_maximum.x|float - 10.0 %}
  G1 X{x_park} Y{y_park} F20000
  M84

 

[TheStonedModder]

If anyone has multiple printers with a KlipperScreen attached and wants to control them from a single screen(in my case BigTreePad7) You can easily configure and control them all by adding this to your Klipperscreen.conf file

Now I'm able to control my K1 from the same pad that my Ender 3 uses and vice versa

[main]
default_printer: Creality K1

[printer Ender 3]
# Define the moonraker host/port if different from 127.0.0.1 and 7125
moonraker_host: 192.168.86.27 #your printers IP
# ports 443 and 7130 will use https/wss
moonraker_port: 7125
# Moonraker API key if this is not connecting from a trusted client IP
moonraker_api_key: False

[printer Creality K1]
# Define the moonraker host/port if different from 127.0.0.1 and 7125
moonraker_host: 192.168.86.34 #your printers IP
# ports 443 and 7130 will use https/wss
moonraker_port: 7125
# Moonraker API key if this is not connecting from a trusted client IP
moonraker_api_key: False

 

[TheStonedModder]

Its not much but working on a little tool to help with the filament calibration process. This should help you get through the full Orcaslicer calibration assistant without needing to remember the formulas

Post automatically merged: Oct 28, 2023

Its not much but working on a little tool to help with the filament calibration process. This should help you get through the full Orcaslicer calibration assistant without needing to remember the formulas

IDK why I decided to use python instead of HTML thats just silly. Here is the same program but in HTML so its easier to run

<!DOCTYPE html>
<html>
<head>
  <title>Orca Slicer Assistant</title>
  <style>
    body {
      background-color: #333;
      color: #fff;
      font-family: Arial, sans-serif;
      text-align: center;
    }
    h1 {
      color: #00a2ff;
    }
    h2 {
      color: #00a2ff;
    }
    label {
      display: block;
      margin-top: 10px;
    }
    select, input {
      background-color: #444;
      color: #fff;
      border: none;
      border-bottom: 2px solid #00a2ff;
      padding: 5px;
      font-size: 16px;
    }
    p {
      color: #00a2ff;
    }
    .created-by {
      margin-top: 20px;
    }
    .created-by p {
      color: #888; /* Change the text color for the "Created by" paragraph */
    }
    .created-by a {
      color: #00a2ff; /* Change the text color for the links */
      text-decoration: underline; /* Underline the links */
      margin: 0 5px; /* Add some spacing between links */
    }
  </style>
</head>
<body>
  <h1>Orca Slicer Assistant</h1>
  <h2>Pressure Advance</h2>
  <label for="circle">Select Extruder Type:</label>
  <select id="circle" onchange="calculate()">
    <option value="DDE">DDE</option>
    <option value="Bowden">Bowden</option>
  </select>
  <br>
  <label for="entry1">PA Step (A):</label>
  <input type="text" id="entry1" value="0.002" oninput="calculate()">
  <br>
  <label for="entry2">Measured Height (B):</label>
  <input type="text" id="entry2" value="8" oninput="calculate()">
  <br>
  <p id="result">Output (DDE): ???</p>
  <h2>Flow Rate</h2>
  <label for="flowRate">Flow Ratio:</label>
  <input type="text" id="flowRate" value="1.029" oninput="calculateFlowRate()">
  <br>
  <label for "modifier">Modifier:</label>
  <input type="text" id="modifier" value="-6" oninput="calculateFlowRate()">
  <br>
  <p id="flowRateResult">Result: ???</p>
  <h2>Retraction</h2>
  <label for="start">Start:</label>
  <input type="text" id="start" value="0.0" oninput="calculateRetraction()">
  <br>
  <label for="measuredHeight">Measured Height:</label>
  <input type="text" id="measuredHeight" value="0.0" oninput="calculateRetraction()">
  <br>
  <label for="factor">Factor:</label>
  <input type="text" id="factor" value="0.0" oninput="calculateRetraction()">
  <br>
  <p id="retractionResult">Result: ???</p>
  <div class="created-by">
    <p>Created by @StonedModder</p>
    <a href="https://twitter.com/StonedModder" target="_blank">Twitter</a> |
    <a href="https://github.com/ItsDeidara" target="_blank">Github</a>
  </div>
  <script>
    function calculate() {
      var circle = document.getElementById("circle").value;
      var entry1 = parseFloat(document.getElementById("entry1").value);
      var entry2 = parseFloat(document.getElementById("entry2").value);
      var result = null;
      if (circle === "DDE" || circle === "Bowden") {
        result = entry1 * entry2;
      }
      if (result !== null) {
        document.getElementById("result").textContent = "Output (" + circle + "): " + result.toFixed(3);
      } else {
        document.getElementById("result").textContent = "Invalid input";
      }
    }
    function calculateFlowRate() {
      var flowRate = parseFloat(document.getElementById("flowRate").value);
      var modifier = parseFloat(document.getElementById("modifier").value);
      var result = flowRate * (100 + modifier) / 100;
      document.getElementById("flowRateResult").textContent = "Result: " + result.toFixed(5);
    }
    function calculateRetraction() {
      var start = parseFloat(document.getElementById("start").value);
      var measuredHeight = parseFloat(document.getElementById("measuredHeight").value);
      var factor = parseFloat(document.getElementById("factor").value);
      var result = start + measuredHeight * factor;
      document.getElementById("retractionResult").textContent = "Result: " + result.toFixed(5);
    }
    calculate(); // Calculate initial values
    calculateFlowRate(); // Calculate initial flow rate
    calculateRetraction(); // Calculate initial retraction
  </script>
</body>
</html>

 

[jattie]

I get the following error ar step 6:

Include file '/usr/data/printer_data/config/KAMP_Settings.cfg' does not exist

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted

 

[TheStonedModder]

I get the following error ar step 6:

Include file '/usr/data/printer_data/config/KAMP_Settings.cfg' does not exist

Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.
Printer is halted

Make sure that you install KAMP from the install script

 

[AstroBoB]

Make sure that you install KAMP from the install script

I had the same ... my problem was I wasn't using a capital S for settings ... btw I am a complete noob ... did you also set the value to true in moonraker.conf for KAMP ?

 

[TheStonedModder]

I had the same ... my problem was I wasn't using a capital S for settings ... btw I am a complete noob ... did you also set the value to true in moonraker.conf for KAMP ?

Yes, setting that value in moonraker.conf is so you can update KAMP from the GUI instead of having to use the script each time

It’s not needed but is helpful. The latest version of the GitHub script should do this all automatically however

 

[razenxd]

Hey man,
I'm having some issues with my K1 Max which I just got.
I rooted the machine and installed the recommended scripts, along with the input shaper.
What so I do now?
Autocalibrate the machine, or run manual calibrations via fluid/mainsail?

 

[TheStonedModder]

Hey man,
I'm having some issues with my K1 Max which I just got.
I rooted the machine and installed the recommended scripts, along with the input shaper.
What so I do now?
Autocalibrate the machine, or run manual calibrations via fluid/mainsail?

You can just let auto calibration do its thing before each print now. It will automatically use the fixed input shaper macro when it runs

You can also disable it before each print if you’d like and just run it manually every once in a while and save time. But personally I think it’s best to just have it do its calibration routine before each print

Hopefully that helps ya a bit. If not lemme know and I can reword it

 

[razenxd]

You can just let auto calibration do its thing before each print now. It will automatically use the fixed input shaper macro when it runs

You can also disable it before each print if you’d like and just run it manually every once in a while and save time. But personally I think it’s best to just have it do its calibration routine before each print

Hopefully that helps ya a bit. If not lemme know and I can reword it

Thanks for the reply.
No , you described it perfectly.
I now put a long 7hours print using an orca profile, usually any Slic3r fork was working better for me than any Cura or cura fork on my machines and afaik creality print is a cura fork.
So hopefully this is gonna fix some of my issues. Will know in the morning

Do I need to manually create a mesh or fiddle around manually with something in fluid/mainsail?
Or just autocalibration(I also use it everytime before printing), calibrate Temp/Flow rate/ PA and that's it?

 

[TheStonedModder]

Thanks for the reply.
No , you described it perfectly.
I now put a long 7hours print using an orca profile, usually any Slic3r fork was working better for me than any Cura or cura fork on my machines and afaik creality print is a cura fork.
So hopefully this is gonna fix some of my issues. Will know in the morning

Do I need to manually create a mesh or fiddle around manually with something in fluid/mainsail?
Or just autocalibration(I also use it everytime before printing), calibrate Temp/Flow rate/ PA and that's it?

If you want to speed up your orca slicer filament calibration process (that’s how you improve your quality and get the speed from) I also made this to automatically do the math for each step
https://github.com/ItsDeidara/Orca-Slicer-Assistant

I do all of the orca slicer calibration prints in order, except for the VFA one. Thats kinda useless unless you’re doing stuff to reduce it and want to see the effects (like swapping your belts out for thicker ones)

As for manually changing any configs or making a mesh. The mesh is automatic if you use auto calibration. Doing it manually really is only needed for visualizing your bed level in real time if/when you’re trying to level it .

(I’ve been smoking all day hopefully I didn’t miss anything)

 

[razenxd]

If you want to speed up your orca slicer filament calibration process (that’s how you improve your quality and get the speed from) I also made this to automatically do the math for each step
https://github.com/ItsDeidara/Orca-Slicer-Assistant

I do all of the orca slicer calibration prints in order, except for the VFA one. Thats kinda useless unless you’re doing stuff to reduce it and want to see the effects (like swapping your belts out for thicker ones)

As for manually changing any configs or making a mesh. The mesh is automatic if you use auto calibration. Doing it manually really is only needed for visualizing your bed level in real time if/when you’re trying to level it .

(I’ve been smoking all day hopefully I didn’t miss anything)

Allright that's what I was thinking but I wanted to be sure.
I've never had a printer with klipper before so I wasn't sure how some things are working.
Well looking at my print so far(the 7+ hrs one I mentioned), and through the tree supports it looks a lot better than the prints I did with creality print.
I'm using Guilouz Profiles and only enabled tree supports and changed the infill to lighting.
If things don't go well I will do the orca calibrations.
Btw what is the recomended support threshold?
On my other printers and with prusaslicer i leave it to 0(auto), orcaslicer needs a number(currently 30 and looks like auto tbh).

 

[TheStonedModder]

Allright that's what I was thinking but I wanted to be sure.
I've never had a printer with klipper before so I wasn't sure how some things are working.
Well looking at my print so far(the 7+ hrs one I mentioned), and through the tree supports it looks a lot better than the prints I did with creality print.
I'm using Guilouz Profiles and only enabled tree supports and changed the infill to lighting.
If things don't go well I will do the orca calibrations.
Btw what is the recomended support threshold?
On my other printers and with prusaslicer i leave it to 0(auto), orcaslicer needs a number(currently 30 and looks like auto tbh).

I don't use supports too often tbh. Most of what I print is small enough were I can get away with the bridging.

I usually just enable organic tree supports and leave everything default tho in the rare occasion I do use them

 

[razenxd]

I don't use supports too often tbh. Most of what I print is small enough were I can get away with the bridging.

I usually just enable organic tree supports and leave everything default tho in the rare occasion I do use them

Ah I see.
Well yeah, I think also that the 30 was the default but have to check because I can't recall.
One thing that I don't understand is why the printer is now(now I mean on the whole print time) Z hoping, while on orcaslicer z hop is not checked