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

Can't move X axis after successful home (Core XY)

Scheduled Pinned Locked Moved Solved
Tuning and tweaking
4
8
638
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
    JonDaniel
    last edited by 11 Mar 2019, 12:50

    I've been searching these forums for a while and can't find anyone else mentioning an issue like this. I have a Tronxy X5S and have just finished wiring up my Duet Maestro.

    I can home all axis successfully, and can manually move the Y and Z axis, however the X axis won't respond to manual move commands after homing. The odd time that it does, i get a horrible noise from the machine, as if the belt is jumping teeth or something.

    Admittedly i may have gone beyond my skills with this project, but any help would be immensely helpful!

    I've attached my config file for reference.

    0_1552308527032_config.g

    undefined 1 Reply Last reply 11 Mar 2019, 13:04 Reply Quote 0
    • undefined
      deckingman @JonDaniel
      last edited by 11 Mar 2019, 13:04

      @jondaniel What firmware version are you using? I note that you have M667 S1 in your config.g but this is deprecated in firmware 2.03 and later. So, if you are using a later firmware, use M669 K1 instead of M667 S1. See release notes here https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md

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

      undefined 1 Reply Last reply 11 Mar 2019, 14:03 Reply Quote 1
      • undefined
        JonDaniel @deckingman
        last edited by 11 Mar 2019, 14:03

        @deckingman Thanks for the quick reply! I'll check my firmware (update if necessary) and change that M667 code tonight and report back.

        1 Reply Last reply Reply Quote 0
        • undefined
          Veti
          last edited by 11 Mar 2019, 15:38

          you might have x going in the opposite direction.
          after it hits the endstop it might try going further but it cant since it already hit the endstop.

          undefined 1 Reply Last reply 11 Mar 2019, 15:51 Reply Quote 1
          • undefined
            Phaedrux Moderator @Veti
            last edited by 11 Mar 2019, 15:51

            @veti said in Can't move X axis after successful home (Core XY):

            you might have x going in the opposite direction.
            after it hits the endstop it might try going further but it cant since it already hit the endstop.

            That'd be my guess too.

            https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter
            Check your movement section against the guide here. Particularly the commissioning section to verify motor direction.

            Commissioning
            During commissioning, you can test the X and Y motors independently by using the S2 modifier on the G1 command, like this:

            G91 ; relative mode
            G1 S2 X10 ; move the X motor forward 10mm
            G1 S2 X-10 ; move the X motor back 10mm
            G1 S2 Y10 ; move the Y motor forward 10mm
            G1 S2 Y-10 ; move the Y motor back 10mm
            G90 ; back to absolute mode

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • undefined
              JonDaniel
              last edited by 11 Mar 2019, 16:43

              Thanks, i'll try that after i've checked firmware. I figured the motor direction wasn't an issue because the y axis moves properly. Wouldn't that mean that both the x and y motors are spinning correctly since they're both used for both axis?

              1 Reply Last reply Reply Quote 0
              • undefined
                Phaedrux Moderator
                last edited by 11 Mar 2019, 17:04

                Well the only reason it might be homing in the right direction is that the homing file is telling it to move backwards....

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 1
                • undefined
                  JonDaniel
                  last edited by JonDaniel 3 Nov 2019, 22:05 11 Mar 2019, 22:05

                  Thanks everyone that gave me direction on this one. I'm running firmware 2.02RC5(RTOS) (2018-11-28b1).

                  Turns out you were right @ phaedrux. I had my motors AND my endstops backwards, making it appear as though everything was playing nice. I flipped the motors and home code around and it's moving as expected now!

                  I really appreciate the help!

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