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

    Core XY won't home X if near Y endstop

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    9
    563
    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.
    • EricE555undefined
      EricE555
      last edited by

      Voron 2.4 Core XY
      Printer was running fine before I had a crash where the print head collided with a warping part and stopped the printer.
      Now it won't work correctly.
      If I center X and Y axis first, it homes correctly hitting all endstops.
      If I try homeall.g again right after that, it will not move on the home X move and ultimately get confused about where the print head is relative to X; which then messes everything up.

      What diagnostics do I have available to figure this out or does anyone have any ideas what is wrong?

      T3P3Tonyundefined o_lampeundefined 2 Replies Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @EricE555
        last edited by

        @erice555 was the only thing that happened the crash? I can't see how that would have impacted the configuration but to help me understand how the printer homes please post your homeall.g (using the </> to format it for easy viewing).

        What happens if you just send home X after homeall?

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • o_lampeundefined
          o_lampe @EricE555
          last edited by

          @erice555 said in Core XY won't home X if near Y endstop:

          If I try homeall.g again right after that, it will not move on the home X move

          I'm sure the X-endstop is already triggered, you can test it by sending M119 from the console after running homeX.g

          1 Reply Last reply Reply Quote 0
          • EricE555undefined
            EricE555
            last edited by

            So using M119 I can see that X somehow says "at max stop" even after it has moved away from max stop.
            Ideas?

            Here is my homeall.g:
            ; homeall.g
            ; called to home all axes

            G91 ; relative positioning
            G1 Z8 F800 H2 ; lift Z relative to current position

            ; Homing Moves
            G1 H1 X310 F6000 ; move quickly to X axis endstops and stop there (first pass)
            G1 H1 Y310 F6000 ; move quickly to Y axis endstops and stop there (first pass)

            G90 ; back to absolute mode

            ;Homing Z
            G1 X204 Y310 F3600 ;position of Z swtich ;
            G1 H1 Z-200 F360 ; move Z down until the switch triggers ; speed 360
            ; never leave nozzle on endstop in case nozzle is hot = BAD

            ; Z Offset
            G1 Z10
            G1 X195 ; move to the side of endstop pin
            G1 Z0 ; PEI move to 0
            G92 Z.55 ; PEI : reset to actual height

            ; Slow nozzle wipe
            G1 X182 F3600; move TO brass brush
            G1 X145 F200; move through brass brush
            G1 X165 ; move back through brush

            ; Parking Position
            G1 Z10 F6000 ; park it

            EricE555undefined 1 Reply Last reply Reply Quote 0
            • EricE555undefined
              EricE555 @EricE555
              last edited by

              @erice555 I am going to replace the X endstop and see if this is somehow a switch problem.

              T3P3Tonyundefined 1 Reply Last reply Reply Quote 1
              • T3P3Tonyundefined
                T3P3Tony administrators @EricE555
                last edited by

                @erice555 how far do you need to move away to.show that it's not triggered?

                www.duet3d.com

                1 Reply Last reply Reply Quote 0
                • EricE555undefined
                  EricE555
                  last edited by

                  Solved.
                  Or rather, not solved but I know what the issue is. I put in a new endstop switch but in doing so found the wiring between the switch and the mainboard is broken on one wire. Somehow since it worked on one wire of the two, it allowed the switch to trigger when it was triggered but according to the mainboard it acted like it was stuck down. So the only time it would act as normal was right after startup when the endstop had not been fired yet.

                  T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
                  • T3P3Tonyundefined
                    T3P3Tony administrators @EricE555
                    last edited by

                    @erice555 thatt is very strange failure mode, but glad you found the problem. out of interest what sort of homing switch are you using?

                    www.duet3d.com

                    EricE555undefined 1 Reply Last reply Reply Quote 0
                    • EricE555undefined
                      EricE555 @T3P3Tony
                      last edited by

                      @t3p3tony https://www.amazon.com/gp/product/B088W8WMTB/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

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