Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Config Settings for AWD voron 2.4 - coreXY

    Scheduled Pinned Locked Moved
    General Discussion
    6
    12
    682
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • michaelr123undefined
      michaelr123
      last edited by

      Planning an upgrade to my Voron 2.4 with a duet 2 board, quick question on the config for this setup.

      Here's a link to the mod: https://docs.atinyshellscript.com/v2.4/awd/#nema14-bearing-idler-stacks

      This requires 2x X drives and 2x Y drives. I haven't found any exact examples of how this would look in config, my guess it it would look something like this:

      ; Drives
      M569 P10 S1 ; physical drive 10 goes forwards A1
      M569 P12 S1 ; physical drive 12 goes forwards A2

      M569 P11 S1 ; physical drive 11 goes forwards B1
      M569 P13 S1 ; physical drive 13 goes forwards B2

      M569 P0 S1 ; physical drive 0 goes forwards Z1
      M569 P1 S0 ; physical drive 1 goes backwards Z2
      M569 P2 S1 ; physical drive 2 goes forwards Z3
      M569 P3 S0 ; physical drive 3 goes backwards Z4
      M569 P4 S1 ; physical drive 4 goes forwards E0

      M584 X11:12 Y10:13 Z0:1:2:3 E4 ; set drive mapping AABB + 4 z motors + 1 extruder
      M350 X16 Y16 I1 ; turn interpolation off for AB axes

      I know I'll have to patch in 2 more stepper drivers, I already added 2 more for the AB motors in the first place, so no big deal there. Does this look correct?

      Thanks!
      -Michael

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        yes theoretically that's how you would add additional motors to an axis, though I've not seen it used with corexy before.

        Z-Bot CoreXY Build | Thingiverse Profile

        jay_s_ukundefined deckingmanundefined Mr Yodundefined 3 Replies Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @Phaedrux
          last edited by jay_s_uk

          @Phaedrux I can run my vzbot on RRF with 2x X and 2x Y and that's coreXY

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          3Ddrifterundefined 1 Reply Last reply Reply Quote 1
          • Mr Yodundefined
            Mr Yod
            last edited by

            I haven't made an AWD system yet, but I have 3 Z and they are configured like you did (Z1.0:1.1:1.2 on a Duet3), so I'd say it's the same for XY.

            What I don't get is your "wiring":

            M569 P10 S1 ; physical drive 10 goes forwards A1
            M569 P12 S1 ; physical drive 12 goes forwards A2
            
            M569 P11 S1 ; physical drive 11 goes forwards B1
            M569 P13 S1 ; physical drive 13 goes forwards B2
            [...]
            M584 X11:12 Y10:13 Z0:1:2:3 E4 ; set drive mapping AABB + 4 z motors + 1 extruder
            

            With this you are mapping A2B1 and A1B2, maybe it's correct and I just got confused with your comment.

            Besides: you have to synchronize the steppers in AWD configuration (it's hardware, not software), so remember to do that.

            michaelr123undefined 1 Reply Last reply Reply Quote 0
            • michaelr123undefined
              michaelr123 @Mr Yod
              last edited by

              @Mr-Yod

              I'm just patching in stand alone stepper drivers to add extra drives to the duet 2 rather than using expansion boards as I couldn't get a hold of one stateside at this point. You just borrow spare pins for step, dir, enable and create additional drive channels. when I bought my voron kit I got a full klipper setup with standalone stepper chips so I'm just using those because I have them. Requires a bit of wiring but it's not too much work.

              Mr Yodundefined 1 Reply Last reply Reply Quote 0
              • Mr Yodundefined
                Mr Yod @michaelr123
                last edited by Mr Yod

                @michaelr123
                No, what I meant is:
                your As are 10 and 12, while your Bs are 11 and 13, so I assumed A and B are your X and Y, that was in conflict with your M584 where Xs are 11 and 12 while Ys are 10 and 13.
                But that's more a naming problem: maybe you named them based on the side of the printer, so X is A2B1 and Y is A1B2 in a cross configuration.

                As for synchronization: you need to unscrew the pulley's set screws, move a bit the belts and then screw them again (I think, IIRC).

                michaelr123undefined 1 Reply Last reply Reply Quote 1
                • michaelr123undefined
                  michaelr123 @Mr Yod
                  last edited by

                  @Mr-Yod

                  good catch, yeah I need align the naming convention. And yep will do on the hardware synchronization. Thanks for double checking, everything's ordered so I'll start working on this in a week or so.

                  1 Reply Last reply Reply Quote 0
                  • 3Ddrifterundefined
                    3Ddrifter @jay_s_uk
                    last edited by

                    @jay_s_uk I’m building a vzbot with a duet 3 do you have a config file I can have with lc1 tool board?

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk @3Ddrifter
                      last edited by

                      @3Ddrifter I have it without a toolboard using a super8pro but it'll give you a starter for 10. I'll post it once I'm home

                      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                      1 Reply Last reply Reply Quote 1
                      • deckingmanundefined
                        deckingman @Phaedrux
                        last edited by

                        @Phaedrux said in Config Settings for AWD voron 2.4 - coreXY:

                        yes theoretically that's how you would add additional motors to an axis, though I've not seen it used with corexy before.

                        Yes you have. My CoreXYUVAB only split the axes for homing. After homing, the drives were re-mapped such that there were 3 Alpha motors and 3 Beta motors making it a "simple" CoreXY.

                        Ian
                        https://somei3deas.wordpress.com/
                        https://www.youtube.com/@deckingman

                        Phaedruxundefined 1 Reply Last reply Reply Quote 1
                        • Phaedruxundefined
                          Phaedrux Moderator @deckingman
                          last edited by

                          @deckingman said in Config Settings for AWD voron 2.4 - coreXY:

                          @Phaedrux said in Config Settings for AWD voron 2.4 - coreXY:

                          yes theoretically that's how you would add additional motors to an axis, though I've not seen it used with corexy before.

                          Yes you have. My CoreXYUVAB only split the axes for homing. After homing, the drives were re-mapped such that there were 3 Alpha motors and 3 Beta motors making it a "simple" CoreXY.

                          HA! so I have.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          1 Reply Last reply Reply Quote 0
                          • Mr Yodundefined
                            Mr Yod @Phaedrux
                            last edited by

                            @Phaedrux said in Config Settings for AWD voron 2.4 - coreXY:

                            HA! so I have.

                            Look at HevORT, too. 😃

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Unless otherwise noted, all forum content is licensed under CC-BY-SA