From 96c847a66c69be2ef0d6b2d2b2a7be3dc6d8d8c6 Mon Sep 17 00:00:00 2001
From: Bassam Husain <bassam.husain@gmail.com>
Date: Sat, 25 Nov 2023 02:06:48 -0500
Subject: [PATCH] Add screws_tilt_adjust, axis_twist_compensation sections.

---
 misc/compile-how-to.md | 43 ++++++++++++++++++++++++++++++++++++++++++
 printer.cfg            | 27 +++++++++++++++++++++++++-
 2 files changed, 69 insertions(+), 1 deletion(-)
 create mode 100644 misc/compile-how-to.md

diff --git a/misc/compile-how-to.md b/misc/compile-how-to.md
new file mode 100644
index 0000000..33bdf54
--- /dev/null
+++ b/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/`
diff --git a/printer.cfg b/printer.cfg
index bc18f19..c00d3e3 100644
--- a/printer.cfg
+++ b/printer.cfg
@@ -164,6 +164,11 @@ fade_start: 1
 fade_end: 10
 fade_target: 0
 
+[axis_twist_compensation]
+calibrate_start_x: 27 # probe x coor at furthest left
+calibrate_end_x: 272 # probe x coor at furthest right ; (x.position_max - abs(x_offset) - 1)
+calibrate_y: 154
+
 #####################################################################
 #   Fans
 #####################################################################
@@ -175,7 +180,7 @@ pin: PA0
 #   Misc
 #####################################################################
 
-# NOTE Apparently the screen is not Klipper friendly
+# NOTE The screen is not Klipper friendly
 # [display]
 # lcd_type: st7920
 # cs_pin: PB12
@@ -184,6 +189,26 @@ pin: PA0
 # encoder_pins: ^PB14, ^PB10
 # click_pin: ^!PB2
 
+[screws_tilt_adjust]
+screw1_name: front center left base
+screw1: 84, 136
+screw2_name: front left
+screw2: 5, 55
+screw3_name: front right
+screw3: 244, 55
+screw4_name: front center right
+screw4: 164, 136
+screw5_name: back center left
+screw5: 84, 216
+screw6_name: back center right
+screw6: 164, 216
+screw7_name: back left
+screw7: 5, 295
+screw8_name: back right
+screw8: 244, 295
+horizontal_move_z: 10
+screw_thread: CCW-M4
+
 # NOTE The speaker will not work, since the screen doesn't
 # [output_pin beeper]
 # pin: PC6