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

    M584 doesn't work with axis drives

    Scheduled Pinned Locked Moved
    Beta Firmware
    3
    9
    288
    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.
    • CarlosRundefined
      CarlosR
      last edited by

      Hi all,

      We are getting an error at M584. Our command is:

      M584 X40.0 Y41.0:42.0 Z43.0 U44.0 V45.0 ; axis drive mapping
      

      39d59a87-0ca6-4a63-b91a-bc0b95a38f9f-image.png

      But this is working, and extruder drives are declared correctly

      M584 E20.0:21.0:22.0; extruders drive mapping
      

      Out firmware version is 3.4beta3. Each extruder uses a 1LC board, and the axis use 1XD board.

      Thanks in advance

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

        @carlosr is each board being correctly identified? i.e. if you send M122 B40, is the correct information displayed?
        Could you post the above output from one of the 1XD?

        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

        CarlosRundefined 1 Reply Last reply Reply Quote 0
        • CarlosRundefined
          CarlosR @jay_s_uk
          last edited by

          @jay_s_uk Yes, it seems to be correctly connected

          0e05279b-46da-4d56-92a1-effca9018081-image.png

          jay_s_ukundefined 1 Reply Last reply Reply Quote 1
          • jay_s_ukundefined
            jay_s_uk @CarlosR
            last edited by

            @carlosr and one last question, I'm assuming the M584 in your config is taking place after a delay has been inserted? e.g. G4 S2 as instructed here

            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

            CarlosRundefined 1 Reply Last reply Reply Quote 1
            • CarlosRundefined
              CarlosR @jay_s_uk
              last edited by

              @jay_s_uk Yes, we have a "G4 S3" that waits for boards to start before running the M584

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

                @carlosr ok, not much else I can add here. Please post your config.g for completeness anyway

                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

                CarlosRundefined 1 Reply Last reply Reply Quote 0
                • CarlosRundefined
                  CarlosR @jay_s_uk
                  last edited by

                  @jay_s_uk

                  Our config.g it is very messy and complex, don't think it would help you to understand the problem.

                  My feeling is that it is related to the 1XD board...

                  Just a point, it worked properly before upgrading to 4.3beta3.

                  CarlosRundefined 1 Reply Last reply Reply Quote 0
                  • CarlosRundefined
                    CarlosR @CarlosR
                    last edited by

                    @dc42

                    Any ideas on this?

                    It worked properly on the 3.4beta2+ you shared with @Marcossf, we just upgraded to 3.4beta3 to fix the temperature sensor issues, but now the M584 doesn't work.

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

                      @carlosr do the following commands work:

                      M584 X40.0
                      M569 P40.0

                      Also, please can you construct a simple config.g file that reproduces the problem.

                      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

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