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

Map Z axis to V axis

Scheduled Pinned Locked Moved
My Duet controlled machine
2
4
292
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.
  • undefined
    SebastianM
    last edited by SebastianM 19 Oct 2022, 18:35

    Hello all -

    Issue:
    I am trying to map the Z axis of one of two tools to the V axis (an independent axis operating in the z-direction), however this action appears unsupported. Has anyone found a way around this / or could indicate where I am making an error?

    Background:
    I have built a custom 3D printer which has two independent X-axes for 2 toolheads (each on its own rail). Each x-rail is controlled by independent Z-stepper motors. The setup has 5 axes:
    x-0
    Y-1
    Z-2
    U-3 (powered by stepper driver 6) - parallel to X-axis
    V-4 (powered by stepper driver 7) - parallel to Z-axis

    The Y-axis is shared between both toolheads (the bed moves).

    To move the toolheads independently in the X and Z directions, I've mapped Tool 0 to X0 Y1 Z2 and Tool 2 to X3 Y1 Z4, where axis 3 is the U axis, and axis 4 is the V axis per the duet documentation.

    The issue: In the interface, after selecting Tool 2 and moving the 'x' axis, it moves the U axis as expected. However, when moving the 'z' axis, it moves the Z instead of V axis.

    I've tried changing the mapping of Z with no effect. The documentation states that mapping of the X and Y axes is possible, but does not indicate whether the Z axis can also be remapped.

    Here are the relevant pieces of setup code:
    ; Drives
    M569 P0 s1 ; physical drive 0 goes backwards
    M569 P1 S1 ; physical drive 1 goes backwards
    M569 P2 S1 ; physical drive 2 goes backwards
    M569 P3 S0 ; physical drive 3 goes forwards
    M569 P4 S0 ; physical drive 4 goes forwards
    M569 P5 S1 ; physical drive 5 goes backwards
    M569 P6 S1 ; physical drive 5 goes backwards
    M569 P7 S1 ; physical drive 6 goes backwards
    M584 X0 Y1 Z2 E3:4:5 U6 V7 ; set drive mapping

    M563 P0 D0 H1 F0 X0 Y1 Z2 ; define tool 0
    M563 P2 D2 H2 F2 X3 Y1 Z4 ; define tool 2

    Thank you for your help!

    undefined 1 Reply Last reply 20 Oct 2022, 07:46 Reply Quote 0
    • undefined
      o_lampe @SebastianM
      last edited by o_lampe 20 Oct 2022, 07:46

      @SebastianM said in Map Z axis to V axis:

      M563 P2 D2 H2 F2 X3 Y1 Z4 ; define tool 2

      This should be Z7, not Z4 from my understanding. But then again, it should also be X6....I'm confused

      undefined 1 Reply Last reply 21 Oct 2022, 16:52 Reply Quote 0
      • undefined
        SebastianM @o_lampe
        last edited by 21 Oct 2022, 16:52

        @o_lampe Thanks for the response.

        I initially thought that as well, however, after that didn't work, this is what I found in the documentation which clarified that U is the 3rd and V4th axis.

        M563:
        X, Y The X and Y mapping option is used to create tools on machines with multiple independent X and/or Y carriages. The additional carriages are set up as axes U, V etc. (see M584) and the X mapping option in M563 defines which carriage or carriages are used. Axes are mapped in the order XYZUVWABC, where X=0, Y=1, Z=2, U=3 etc, not by driver number.

        undefined 1 Reply Last reply 22 Oct 2022, 07:01 Reply Quote 0
        • undefined
          o_lampe @SebastianM
          last edited by 22 Oct 2022, 07:01

          @SebastianM
          I remember, I fell in the same trap before. But with RRF3.2, I could only make it work when the driver number matched the letter-numbering you quoted.

          M584 X0 Y1 Z2 U3 V4 E5 ; set drive mapping
          ...
          ; Drives hashPrinter
          ;
          ; X | V
          ;---|---
          ; Y | U
          ;
          M569 P0 S1 ; physical drive 0 goes forwards
          M569 P1 S0 ; physical drive 1 goes forwards
          M569 P2 S1 ; physical drive 2 goes forwards
          M569 P3 S0 ; U axis als 2te x
          M569 P4 S1 ; V axis als 2te Y
          ...
          ; Tools
          ;
          ; 1 | 2
          ;---|---
          ; 0 | 3
          ;
          M563 P0 D0 H1 S"XY" X0 Y1 F0 ; define tool 0 in bottom left corner
          G10 P0 X-0 Y-0 Z0 ; set tool 0 axis offsets
          G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
          M563 P1 D0 H1 S"XV" X0 Y4 F0 ; define tool 1 in top left corner
          G10 P1 X-0 V0 Z0 ; set tool 1 axis offsets
          G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C
          M563 P2 D0 H1 S"UV" X3 Y4 F0 ; define tool 2 in top right corner
          G10 P2 U0 V0 Z0 ; set tool 2 axis offsets
          G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C
          M563 P3 D0 H1 S"UY" X3 Y1 F0 ; define tool 3 in bottom right corner
          G10 P3 U0 Y-0 Z0 ; set tool 3 axis offsets
          G10 P3 R0 S0 ; set initial tool 3 active and standby temperatures to 0C

          So I've put the extrudermotor(s) behind the motion drivers

          1 Reply Last reply Reply Quote 0
          • undefined oribotic referenced this topic 21 Feb 2023, 14:30
          3 out of 4
          • First post
            3/4
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA