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

Home Y not reading all lines of code

Scheduled Pinned Locked Moved
Duet Web Control
3
4
182
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
    PRIOR123
    last edited by 20 Jun 2021, 21:12

    Hi All,

    I hope you can help,

    Trying to work out my homing issues. for my Y axis It doesn't seem to be reading the H1 code. It seems to be jumping straight to the move a few mm line. can some help?

    G91 ; relative positioning
    G1 H2 Z-5 F6000 ; lift Z relative to current position
    G1 H1 Y235 F1800 ; move quickly to Y axis endstop and stop there (first pass)
    G1 H2 Y-5 F6000 ; go back a few mm
    G1 H1 Y235 F360 ; move slowly to Y axis endstop once more (second pass)
    G1 H2 Z-5 F6000 ; lower Z again
    G90 ; absolute positioning

    This is my homey.G

    undefined 1 Reply Last reply 20 Jun 2021, 21:16 Reply Quote 0
    • undefined
      jay_s_uk @PRIOR123
      last edited by 20 Jun 2021, 21:16

      @prior123 I suggest checking your endstops are working as intended using M119

      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

      undefined 1 Reply Last reply 20 Jun 2021, 21:20 Reply Quote 0
      • undefined
        PRIOR123 @jay_s_uk
        last edited by 20 Jun 2021, 21:20

        @jay_s_uk said in Home Y not reading all lines of code:

        M119

        Hey, so you were right the Y end stop was properly connected (facepalm) however it that is now fixed but is still giving me the same outcome

        undefined 1 Reply Last reply 20 Jun 2021, 21:52 Reply Quote 0
        • undefined
          fcwilt @PRIOR123
          last edited by 20 Jun 2021, 21:52

          @prior123

          That behavior suggests that the endstop is triggered when it should not be.

          So the first move never happens because a G1 H1 stops when the endstop is triggered.

          The second move happens because it is not a G1 H1 move.

          The third move never happens because a G1 H1 stops when the endstop is triggered.

          Frederick

          Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

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