Merge branch 'master' into personal

misc/PrusaSlicer_config_bundle-SV06-Both.ini

@@ -1,4 +1,4 @@
-# generated by PrusaSlicer 2.6.1+linux-x64-GTK3 on 2023-11-20 at 02:32:36 UTC
+# generated by PrusaSlicer 2.6.1+linux-x64-GTK3 on 2023-11-23 at 18:53:35 UTC
 
 [print:0.20mm QUALITY SV06 Ellis]
 avoid_crossing_curled_overhangs = 0
@@ -2610,7 +2610,7 @@ retract_restart_extra_toolchange = 0
 retract_speed = 40
 silent_mode = 0
 single_extruder_multi_material = 0
-start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND=[first_layer_temperature[initial_extruder]]\r\nPURGE_LINE\n\n;; If you are passing variables to PRINT_START, comment out above line and uncomment the last 3 lines instead. (I already did this)\n;; Guide: https://github.com/AndrewEllis93/Print-Tuning-Guide/blob/main/articles/passing_slicer_variables.md\n;; Make sure the variable names match (for example if you use "EXTRUDER" instead of "HOTEND")
+start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND=[first_layer_temperature[initial_extruder]]\r\nPURGE_LINE\n\n;; Guide: https://ellis3dp.com/Print-Tuning-Guide/articles/passing_slicer_variables.html#slicer-start-g-code
 template_custom_gcode = 
 thumbnails = 32x32,400x300
 thumbnails_format = PNG
@@ -2691,7 +2691,7 @@ retract_restart_extra_toolchange = 0
 retract_speed = 40
 silent_mode = 0
 single_extruder_multi_material = 0
-start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND=[first_layer_temperature[initial_extruder]]\r\nPURGE_LINE\n\n;; If you are passing variables to PRINT_START, comment out above line and uncomment the last 3 lines instead. (I already did this)\n;; Guide: https://github.com/AndrewEllis93/Print-Tuning-Guide/blob/main/articles/passing_slicer_variables.md\n;; Make sure the variable names match (for example if you use "EXTRUDER" instead of "HOTEND")
+start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND=[first_layer_temperature[initial_extruder]]\r\nPURGE_LINE\n\n;; Guide: https://ellis3dp.com/Print-Tuning-Guide/articles/passing_slicer_variables.html#slicer-start-g-code
 template_custom_gcode = 
 thumbnails = 32x32,400x300
 thumbnails_format = PNG

misc/SuperSlicer_config_bundle-SV06-Both.ini

@@ -1,4 +1,4 @@
-# generated by SuperSlicer 2.4 on 2023-08-23 at 23:28:35 UTC
+# generated by SuperSlicer 2.4 on 2023-11-23 at 19:03:00 UTC
 
 [print:Ellis_Decorative_45_Degree_15mm3]
 allow_empty_layers = 0
@@ -3707,7 +3707,7 @@ retract_speed = 40
 seam_gap = 15%
 silent_mode = 0
 single_extruder_multi_material = 0
-start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND={first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} CHAMBER=[chamber_temperature]\r\nPURGE_LINE\n\n;; If you are passing variables to PRINT_START, comment out above line and uncomment the last 3 lines instead. (I already did this)\n;; Guide: https://github.com/AndrewEllis93/Print-Tuning-Guide/blob/main/articles/passing_slicer_variables.md\n;; Make sure the variable names match (for example if you use "EXTRUDER" instead of "HOTEND")\n
+start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND={first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} CHAMBER=[chamber_temperature]\r\nPURGE_LINE\n\n;; Guide: https://ellis3dp.com/Print-Tuning-Guide/articles/passing_slicer_variables.html#slicer-start-g-code
 start_gcode_manual = 0
 template_custom_gcode = 
 thumbnails = 32x32,400x300
@@ -3832,7 +3832,7 @@ retract_speed = 40
 seam_gap = 15%
 silent_mode = 0
 single_extruder_multi_material = 0
-start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND={first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} CHAMBER=[chamber_temperature]\r\nPURGE_LINE\n\n;; If you are passing variables to PRINT_START, comment out above line and uncomment the last 3 lines instead. (I already did this)\n;; Guide: https://github.com/AndrewEllis93/Print-Tuning-Guide/blob/main/articles/passing_slicer_variables.md\n;; Make sure the variable names match (for example if you use "EXTRUDER" instead of "HOTEND")\n
+start_gcode = M104 S0 ; Stops PS/SS from sending temp waits separately\r\nM140 S0\nM117\r\nPRINT_START BED=[first_layer_bed_temperature] HOTEND={first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} CHAMBER=[chamber_temperature]\r\nPURGE_LINE\n\n;; Guide: https://ellis3dp.com/Print-Tuning-Guide/articles/passing_slicer_variables.html#slicer-start-g-code
 start_gcode_manual = 0
 template_custom_gcode = 
 thumbnails = 32x32,400x300

misc/compile-how-to.md

@@ -0,0 +1,43 @@
+${\small{\textcolor{green}{\texttt{2 minute read}}}}$
+
+#### Do I need to re-flash the motherboard?
+
+You will _almost never_ need to re-flash `klipper.bin`. When this is needed, your dashboard will explicitly tell you that you need to re-flash.
+
+#### Where does Klipper live?
+
+1. On the motherboard.
+2. On the host device (Raspberry Pi, etc.).
+
+🗒️ These 2 versions of klipper can rightly differ.
+
+#### Should I update Klipper, moonraker, etc.?
+
+I always update everything on the host device via the dashboard. I don't want to miss out on improvements, especially those that improve safety. What this means is that on some occasions, there will be breaking changes: you will need to change a few things in your config **before you can print**. I would suggest that if you absolutely have to get something printed immediately and there's an update, perhaps wait till after the print completes to do the update.
+
+Others will argue that 'if it ain't broke, don't fix it'.
+
+You have to decide what camp you want to be apart off.
+
+#### How-To
+
+##### Update Klipper repo first
+
+It's always best to update the Klipper repository that lives on the host before compiling. This ensures that your `klipper.bin` will be as 'fresh' as possible.
+
+- In `Fluidd`, you can do this from `Settings` > `Software Updates`.
+- In `Mainsail`, you can do this from `Machine` > `Update Manager`.
+
+##### Compile `klipper.bin`
+
+🗒️ The `compilation settings` you see in the image below apply only the the `SV06/Plus` boards, but the steps for compilation apply to any board.
+
+1. `ssh` into the Klipper host (i.e., RPi, OrangePi, etc.).
+2. `cd ~/klipper`
+3. `make menuconfig`
+4. Set things up to look as follows:
+   ![make-menuconfig](https://github.com/bassamanator/Sovol-SV06-firmware/assets/61985779/22298d47-2604-4231-ad10-7d6793be7904)
+5. `make clean`
+   - Clears `~/klipper/out/`
+6. `make`
+   - Compiles `klipper.bin` and puts it in `~/klipper/out/`