My print is wayyyy too tall

[SoylentGeek]

Basic Information:

Printer Model: Tevo volcano
MCU / Printerboard: MKS Gen_L v2.1
Host / SBC Pi4
klippy.log attached
klippy.zip (997.2 KB)

Describe your issue:

Hi,
I am setting this machine up from scratch.

I have NO details on the parts as it was given to me as-is

I think I have most of it running well.

My first print was a benchy.

X and Y seem pretty good in terms of dimentions

However, this is the tallest Benchy I have ever see.

It’s double or almost tripple the height of a normal benchy.

What did I get wrong?

(If you wouldn’t mind sanity checking my other settings, that would be great too)

D

…

[EddyMI3D]

Could be helpful to know how much too tall exactly.

You may check on the z-axes:

rotation_distance 
microsteps

in comparison to the used hardware/the settings on the board.

@SoylentGeek

(If you wouldn’t mind sanity checking my other settings, that would be great too)

Most of them you can do on the hardware:

https://www.klipper3d.org/Config_checks.html

[SoylentGeek]

So,
Here is a picture of the benchy next to a proper benchy.

You can see that it’s just the height that is out of wack.

Something I noticed, the layers are very loose, it will just crumble in my hands.

So, it must be something about how it’s stepping I suspect.

[EddyMI3D]

@SoylentGeek

So, it must be something about how it’s stepping I suspect.

I do too.

For you run the steppers in stand-alone-mode, you should check the microstep settings of the z-axes.
Also the thread pitch of the z-axes.

[Sineos]

Also see Z axis travel adjust - #10 by Sineos

[SoylentGeek]

Just wanted to close the loop and let you all know that it’s working fine now.

I was looking at some other configs and noticed that some specified the TMC driver type and added a section for it. (See below)

Why did adding the tmc2208 section make a difference?

My X and Y are closed loop steppers so on the MB they don’t have driver modules (they are pass throughs since there is a driver board on the motor itself in this case)

Should I add a tmc2208 driver section for X and Y as well or do closed loop steppers not need this?

[stepper_z]
step_pin: PL3
dir_pin: PL1
enable_pin: !PK0
microsteps: 16

For TMC2208 at 1/16 microsteps with 400 steps/mm

Don’t use a calibrated value, use the theorical value only otherwise

the TMC2208 may stop working while printing

rotation_distance = <full_steps_per_rotation> * / <steps_per_mm>

rotation_distance = 200 * 16 / 400

rotation_distance: 8
endstop_pin: probe:z_virtual_endstop
position_max: 300
homing_speed: 8

[tmc2208 stepper_z]
uart_pin: PK3
tx_pin: PL7
run_current: 0.800

[EddyMI3D]

@SoylentGeek

Why did adding the tmc2208 section make a difference?

Obviously the jumpers for the stand-alone settings of the driver are different.

BTW:

When copy&paste code snippets, please use the Preformatted Text feature of the forum editor to make it look more smooth.

[Sineos]

Defining an UART interface for a standalone or externally controlled driver seems very wrong.

• Make sure to jumper your board for stand-alone drivers, e.g. see Drivers_A4988 · makerbase-mks/MKS-GEN_L Wiki · GitHub
• Make sure you set step_pulse_duration to the needs of your external driver