<p>I have very strange problem. Motors X and Z are messing up somehow. I mean if I try to home X only, Z moves also. And vice-versa. Y motor homes and moves normally.</p>
<p>Board is stock E3v2 v4.2.2 with TMC2208. <strong>With Marlin everything is OK.</strong></p>
<p>Also, I'm not sure if it's important, but I have compiled firmware 3 times and all 3 are different in size - 20424 bytes first, 20540 bytes second, and 21172 last. All with the same settings -&gt; STM32F103, 28kbit bootloader, com only (USB, CAN disabled).</p>
<p>Heaters seem to work too.</p>
<p><a href="https://drive.google.com/file/d/1goiZtvODy5wEK6wjPuUyLP-nROM1xtKh/view?usp=sharing" rel="nofollow noreferrer">Video</a>
(I'm not sure how to add a video window here)</p>
<p>Here is my config for motors:</p>
<pre><code>[stepper_x]
step_pin: PC2
dir_pin: PB9
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA5
position_endstop: 0
position_max: 225
homing_speed: 50

[stepper_y]
step_pin: PB8
dir_pin: PB7
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA6
position_endstop: 0
position_max: 225
homing_speed: 50

[stepper_z]
step_pin: PB6
dir_pin: PB5
enable_pin: !PC3
microsteps: 16
rotation_distance: 8
endstop_pin: ^PA7
position_endstop: 0.0
position_max: 250
</code></pre>

CC BY-SA 4.0
2021-06-15T07:05:40.533Z
You should probably create an issue about this on the Klipper Github (https://github.com/KevinOConnor/klipper/issues)

Maybe something about the shared enable pins?
The HAL itself for the F103 works fine from my experience.

Make sure your `kinematics:` in the `[printer]` section is set to `cartesian`
towe
CC BY-SA 4.0
2021-06-15T08:48:29.683Z
Don't open a ticket on Github, read the documentation: help requests go to the Discord channel.
FarO
CC BY-SA 4.0
2021-06-15T08:54:59.513Z
Also, check connections: maybe you inverted some cables.
FarO
CC BY-SA 4.0
2021-06-15T12:07:39.667Z
"Make sure your kinematics: in the [printer] section is set to cartesian"

Thanks, that help!
Minkoff
<creality-ender-3><firmware><motor><klipper>
Klipper on Ender 3 v2 wrong signals
Minkoff
# Klipper on Ender 3 v2 wrong signals

(Asked by: username_0 on 2021-06-14)

I have very strange problem. Motors X and Z are messing up somehow. I mean if I try to home X only, Z moves also. And vice-versa. Y motor homes and moves normally.
Board is stock E3v2 v4.2.2 with TMC2208. With Marlin everything is OK.
Also, I'm not sure if it's important, but I have compiled firmware 3 times and all 3 are different in size - 20424 bytes first, 20540 bytes second, and 21172 last. All with the same settings -> STM32F103, 28kbit bootloader, com only (USB, CAN disabled).
Heaters seem to work too.
Video
(I'm not sure how to add a video window here)
Here is my config for motors:
[stepper_x]
step_pin: PC2
dir_pin: PB9
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA5
position_endstop: 0
position_max: 225
homing_speed: 50

[stepper_y]
step_pin: PB8
dir_pin: PB7
enable_pin: !PC3
microsteps: 16
rotation_distance: 40
endstop_pin: ^PA6
position_endstop: 0
position_max: 225
homing_speed: 50

[stepper_z]
step_pin: PB6
dir_pin: PB5
enable_pin: !PC3
microsteps: 16
rotation_distance: 8
endstop_pin: ^PA7
position_endstop: 0.0
position_max: 250

**Tags:** creality-ender-3, firmware, motor, klipper
> **Comments:**
> **username_1**: You should probably create an issue about this on the Klipper Github (https://github.com/KevinOConnor/klipper/issues)  Maybe something about the shared enable pins? The HAL itself for the F103 works fine from my experience.  Make sure your `kinematics:` in the `[printer]` section is set to `cartesian`  
> **username_2**: Don't open a ticket on Github, read the documentation: help requests go to the Discord channel.  
> **username_2**: Also, check connections: maybe you inverted some cables.  
> **username_0**: "Make sure your kinematics: in the [printer] section is set to cartesian"  Thanks, that help!  

---

## 0 answers

