-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugfix: Correct dir_pin on stepper_z1 and stepper_z2 #489
base: Voron2.4
Are you sure you want to change the base?
Conversation
* Correct dir_pin on stepper_z1 and stepper_z2 Tried moving gantry up using sample config. The front side moved up and the back side moved down. Checked other sample configs and found ! on dir_pin normally look similar between motors z and z2, and motors z1 and z3. Previous commit has ! on dir_pin similar between motors z and z1, and the motor z2 and z3. Swapping the ! on dir_pin on z1 and z2 corrects the issue
I think this is dependent on your motor cables and the startup procedure has you run STEPPER_BUZZ STEPPER on each z motor. |
Admittedly, I was focusing more on which stepper activated and its location during through STEPPER_BUZZ, and not paying too much attention to direction. It's a tad easy to miss which way the stepper moves and get lost on where in the pattern you are, so I jog the axis a 2-3 mm to check directionality after confirming the motors for the axis activate through STEPPER_BUZZ. Also, I doubt my cable motors are an issue, they came with the LDO voron v2.4 stepper motor kit. If the cables for the steppers were the issue, it'd a bit odd to get 2 bad cables in one kit, since both motor cables used for the back steppers would need to be miswired in the same way to produce those results. And if that was the only things I found, then I'd just depin and rewire the connectors, and call it a day. The sign that makes me think it's a misconfiguration in the sample file is how the pattern for dir_pin in the z steppers is different from the configuration files for other boards. For example(s):
Looking at these other configs, there's a clear pattern where Z0 and Z2 spin in one direction, and Z1 and Z3 spin in the opposite direction. This pattern also matches up with the locations of which of the Z_Drive are normal versions and which of them are the mirrored versions. Compared to the current config file for M8P v2.0
Z0 and Z1 spin in the same direction, and Z2 and Z3 spin in the opposite direction. This runs contrary to the pattern found in the other config files, and seems to cause the one half of the gantry to move up while the other half moves down. Correcting the config so Z0 and Z2 spin the same direction and Z1 and Z3 spin the other direction fixes the issue. |
I agree that it makes sense to have a default configuration where all axis at least move in the same direction, when all motors are wired the same. This is the case for all other configs. If it's the wrong direction the user has to invert, but chances are 50% they get it right. |
Tried moving gantry up using sample config. The front side moved up and the back side moved down.
Checked other sample configs and found ! on dir_pin normally look similar between motors z and z2, and motors z1 and z3. Previous commit has ! on dir_pin similar between motors z and z1, and the motor z2 and z3.
Swapping the ! on dir_pin on z1 and z2 corrects the issue