Close



Results 1 to 2 of 2
  1. #1

    Problem implementing G34 to Dual Z Axiz alignment

    Thank you in advance if you are able to help me out sorting this strange issue,


    Once i run G34 or Z auto-align from Motion Menu my left Z motor reads fine at left center of my heated bed but for some reason my second Z axis reads at front center of my heated bed, moving the Y axis all the way back.
    It wont even run the entire X to the opposite direction it just stops at center and moves the Y all the way back.
    I have recently upgraded my CR10 to a double Axis, this printer has been modified with a skr 1.4 32 bit board and BLtouch but has been working flawlessly.
    My marlin version is 2.1.1 and i have installed my second Z in the E1 driver port with a TMC2208 , so i have 5 of these in total in X,Y,Z, E0 and (E1, now second Z axis) In configuration.h i have enabled the stepper motor driver type for the Z2:#define Z2_DRIVER_TYPE TMC2208
    And in configuration_adv.h i have,Set same current for both Z and Z2 axis
    and uncommented: #define Z_STEPPER_AUTO_ALIGN
    ***
    The next is not in Marlin Version 2.1.1 since it relies in Z2_DRIVER_TYPE TMC2208 to know a second Z motor/driver is installed.
    #define NumZ_stepper_drivers 2
    ***
    The following parameters have been uncommented and commented back in order to provoke a different interaction, so far with no avail, its not recognizing changes in any of the following:
    //#define Z_STEPPER_ALIGN_XY { { 27, 107 }, { 229.5, 107 } } (the coordinates have been changed several times, i only get an error in the compilation if the values overshoot the bed size.)and
    //#define Z_STEPPERS_ORIENTATION 0
    * 2 Steppers: (0) (1)


    I have been experiencing with these to no avail, still having the problem (it seems the system is choosing between option 0 and 1 and running the 1 from (0) and the 1 from option (1)
    I fell lost.Please let me know if you have experience fixing this issue or have any idea of what may be causing it.

  2. #2
    It seems this was a Marlin´s Version related Bug, I just ported all my configurations to Marlin 2.1.2.4 with the bug fixes patch and it seems to be working correctly.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •