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

    Adding the P parameter to M584 causes hidden axis not to home

    Scheduled Pinned Locked Moved
    Firmware installation
    2
    3
    207
    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.
    • kazolarundefined
      kazolar
      last edited by

      I defined my axis as follows
      M584 Y0.5:0.0 U0.4:0.1 X0.2 V0.3 W2.2 A1.2 E1.0:1.1:2.0:2.1 Z3.2:3.1:4.2:4.1 B3.1 C4.2 D4.1 'A0.0 'B0.1
      If I add P7 to hide the axis I don't want to see in the UI BCDab, then the homing for those axis doesn't work. I.e my homez.g script looks like this

      M584 Z3.2 B3.1 C4.2 D4.1
      G91
      G1 Z6 B6 C6 D6 F450 H2
      G1 Z-500 B-500 C-500 D-500 F450 H1
      G1 Z5 B5 C5 D5 F450 H2
      G1 Z-10 B-10 C-10 D-10 F100 H1
      G1 Z0.2 B0.2 C0.2 D0.2
      M584 Z3.2:3.1:4.2:4.1
      M671 X708:708:-95:-95 Y615:0:0:615 S5
      G92 Z-1.3 B-1.3 C-1.3 D-1.3
      G90

      if I had P7 in the initial M584 in config.g, then the homing doesn't move the BCD axis, if I don't use the hide parameter, everything homes properly.
      I'm on latest 3.4 firmware

      dc42undefined 1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @kazolar
        last edited by

        @kazolar you need to un-hide an axis in order to command it to move, for example to home it. You can un-hide it in the homing file before homing it and then hide it again at the end.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        kazolarundefined 1 Reply Last reply Reply Quote 0
        • kazolarundefined
          kazolar @dc42
          last edited by

          @dc42 I figured out I don't need to define individual axis anyway, just combine the end stops. No need for extra axis -- would be good if M119 would report the state of each end stop pin in the combined M574 definition. No good way to be sure you have the right end stop configured with the right stepper.

          I did this
          M584 Y0.5:0.0 U0.4:0.1 X0.2 V0.3 W2.2 A1.2 E1.0:1.1:2.0:2.1 Z3.2:3.1:4.2:4.1
          M574 Y1 S1 P"io3.in+io1.in"
          M574 U2 S1 P"io6.in+io4.in"
          M574 X1 S1 P"io8.in"
          M574 V2 S1 P"io2.in"
          M574 W2 S1 P"2.io0.in"
          M574 A1 S1 P"1.io0.in"
          M574 Z1 S1 P"3.io0.in+3.io1.in+4.io5.in+4.io4.in"

          that works fine and no extra axis definitions.

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