mirror of
https://github.com/bassamanator/Sovol-SV06-firmware.git
synced 2025-11-08 13:31:16 +00:00
Compare commits
6 Commits
100308b81e
...
master
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
515b423237 | ||
|
|
869bbffeb9 | ||
|
|
9e3ba15aee | ||
|
|
7d9cb1d8fb | ||
|
|
5267b5db80 | ||
|
|
f704ca26aa |
@@ -346,6 +346,13 @@ Edit the relevant file according to your needs.
|
|||||||
| `variable_bed_temp_over` | `0` | `10` (default) | Speeds up print start |
|
| `variable_bed_temp_over` | `0` | `10` (default) | Speeds up print start |
|
||||||
| `variable_bed_temp_not_exact` | `0` | `1` (default) | Speeds up print start |
|
| `variable_bed_temp_not_exact` | `0` | `1` (default) | Speeds up print start |
|
||||||
|
|
||||||
|
### Any differences between this configuration and Sovol's Marlin firmware?
|
||||||
|
|
||||||
|
| Property | Marlin | OSS Klipper Config |
|
||||||
|
| ------------------------- | ------ | ------------------ |
|
||||||
|
| `stepper_z` `run_current` | 0.800 | 0.900 |
|
||||||
|
| `microsteps` | 16 | 128 |
|
||||||
|
|
||||||
### How do I import a configuration bundle into SuperSlicer/PrusaSlicer?
|
### How do I import a configuration bundle into SuperSlicer/PrusaSlicer?
|
||||||
|
|
||||||
Please see this [discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/13).
|
Please see this [discussion](https://github.com/bassamanator/Sovol-SV06-firmware/discussions/13).
|
||||||
|
|||||||
@@ -23,8 +23,6 @@ You have to decide what camp you want to be apart off.
|
|||||||
|
|
||||||
##### Update Klipper repo first
|
##### Update Klipper repo first
|
||||||
|
|
||||||
\*\* _For those coming from the_ ${\small{\textcolor{WildStrawberry}{\texttt{Before You B.egin}}}}$ _section (installing Klipper for the first time), complete_ **only** _this section_. No need to compile the firmware, etc.
|
|
||||||
|
|
||||||
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.
|
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 `Fluidd`, you can do this from `Settings` > `Software Updates`.
|
||||||
@@ -39,6 +37,10 @@ It's always best to update the Klipper repository that lives on the host before
|
|||||||
3. `make menuconfig`
|
3. `make menuconfig`
|
||||||
4. Set things up to look as follows:
|
4. Set things up to look as follows:
|
||||||

|

|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> New option added: `Optimize stepper code for 'step on both edges'`, enable it.
|
||||||
|
|
||||||
5. `make clean`
|
5. `make clean`
|
||||||
- Clears `~/klipper/out/`
|
- Clears `~/klipper/out/`
|
||||||
6. `make`
|
6. `make`
|
||||||
|
|||||||
BIN
misc/images/make-menuconfig-v0.13.0-371-g7a723bdc.png
Normal file
BIN
misc/images/make-menuconfig-v0.13.0-371-g7a723bdc.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 72 KiB |
BIN
misc/klipper-v0.13.0-371-g7a723bdc.bin
Executable file
BIN
misc/klipper-v0.13.0-371-g7a723bdc.bin
Executable file
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -80,7 +80,7 @@ homing_speed: 5
|
|||||||
|
|
||||||
[tmc2209 stepper_z]
|
[tmc2209 stepper_z]
|
||||||
uart_pin: PA15
|
uart_pin: PA15
|
||||||
run_current: 1.000
|
run_current: 0.900
|
||||||
stealthchop_threshold: 0
|
stealthchop_threshold: 0
|
||||||
interpolate: False
|
interpolate: False
|
||||||
sense_resistor: 0.150
|
sense_resistor: 0.150
|
||||||
|
|||||||
Reference in New Issue
Block a user