MarlinFirmware / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
https://marlinfw.org
GNU General Public License v3.0
16.3k stars 19.25k forks source link

[BUG] Double z mode with asymmetric Z-axis step #24929

Closed amxsa closed 2 years ago

amxsa commented 2 years ago

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

[BUG] Double z mode with asymmetric Z-axis step

MKS GEN_L V2.1 ,Z2_SERIAL_TX_PIN and Z2_SERIAL_RX_PIN not define ?

#define X_DRIVER_TYPE  TMC2209
#define Y_DRIVER_TYPE  TMC2209
#define Z_DRIVER_TYPE  TMC2209
#define Z2_DRIVER_TYPE TMC2209
#define E0_DRIVER_TYPE TMC2209

Bug Timeline

No response

Expected behavior

Double z mode, Z axis step symmetry

Actual behavior

Double z mode with asymmetric Z-axis step

Steps to Reproduce

No response

Version of Marlin Firmware

marlin 2.1.1

Printer model

MKS GEN_L V2.1

Electronics

No response

Add-ons

No response

Bed Leveling

No response

Your Slicer

No response

Host Software

No response

Don't forget to include

Additional information & file uploads

Configuration.zip

amxsa commented 2 years ago

ae8df9de8170edca47f68b7cdc38eaff

In fact, the Z-axis is in uart mode, but the program prompts a TMC connection error

ellensp commented 2 years ago

This Issue Queue is for Marlin bug reports and development-related issues, and we prefer not to handle user-support questions here. (As noted on this page.) For best results getting help with configuration and troubleshooting, please use the following resources:

After seeking help from the community, if the consensus points to a bug in Marlin, then you should post a bug report.

ellensp commented 2 years ago

The uarts pins should auto allocated from the unused E, this is a bug... The TMC error is probably a bad stepper driver.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.