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

    Expectation fault or actual fault

    Scheduled Pinned Locked Moved
    General Discussion
    3
    7
    265
    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.
    • Garfieldundefined
      Garfield
      last edited by

      So I've been setting up a coreXY and pretty much all going swimmingly except the XY gantry behaviour.

      If for example I send a command from the DWC for X of +50 the extruder moves diagonally - surely the Y stepper should also be rotating - I did not ask Y to change so why is it ?

      Consider that these axes have never been homed, I don't have the end switches wired up yet.

      Even so if I ask for +50 X via the DWC dashboard I don't expect to get +50 Y also. Are my expectations correct ? - why is only one of the X Y steppers turning ?

      All steppers are fully functional and rotation tested.

      The printer is defined using M667 K1, it is usind a Duet 3 and RRF 3 RC2.

      droftartsundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators @Garfield
        last edited by

        @Garfield See https://duet3d.dozuki.com/Wiki/Gcode#Section_M667_Select_CoreXY_or_related_mode

        [M667] is deprecated in RRF 2.03 and later. Use M669 instead.

        If the config tool put M667 in, let me know.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        1 Reply Last reply Reply Quote 0
        • Garfieldundefined
          Garfield
          last edited by

          M669 fixed the problem, and confirmed I wasn't going nuts ....

          Much appreciated.

          Some of the stuff kicked out by the configuation tool isn't so good - needs some work I think.

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

            @Garfield said in Expectation fault or actual fault:

            M667 K1

            The configurator gave you M667 K1? M667 S1 would have still worked. M669 K1 is the newer format. Odd that it's a mix of new and old.

            Just tested the configurator and when choosing Duet3 and rrf3 and corexy I got M667 S1 ; select CoreXY mode which is still valid.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • Garfieldundefined
              Garfield
              last edited by

              I changed the S1 to K1 because documentation said that S1 was obsolete - I need to go look where - I think it was in the place where the differences between V2 and V3 are detailed - I'll go see if I can find

              1 Reply Last reply Reply Quote 0
              • Garfieldundefined
                Garfield
                last edited by

                Well my bad I found the location - I read the K1 but failed to spot that 667 had changed to 669 so this is definitely a PICNIC problem

                (Problem In Chair Not In Computer)

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

                  No worries. The configurator should probably be updated to use M669 now anyway.

                  Z-Bot CoreXY Build | Thingiverse Profile

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