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

    G30 S-1 Crash After Probe Sequence

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    2
    5
    601
    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.
    • scottieknowsundefined
      scottieknows
      last edited by

      Has anyone seen a machine crash following a successful probe sequence?

      G1 X400 Y400 Z5 ; move to middle of bed
      M401 ; deploy BLTouch
      G30 S-1 ; Probe point

      Following the G30 S-1 the machine drives back to X0 Y0, but ignores the end stops and collides into the hard stops.

      Any info on what I may be doing wrong?

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

        Do you have that sequence coded in a macro file? The reason I ask is that I don't think it's that sequence that is causing the crash, it's whatever follows it.

        The M401 command is not needed unless you are either using pre 1.19 firmware or you want the probe to remain deployed after the G30 command.

        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
        • scottieknowsundefined
          scottieknows
          last edited by

          No macro. We are manually moving axes to those positions. When I try to perform just the G30 S-1 the probe does not deploy which is why I added the M401. There shouldn't be anything after the G30 S-1 as we are sending it through the touch screen.

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

            Which firmware version are you using, and what do you have in your retractprobe.g file?

            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
            • scottieknowsundefined
              scottieknows
              last edited by

              Firmware version 1.19.2

              retractprobe.g
              M564 S0 ; don't apply limits
              G1 Z40 F10000 ; raise head
              G1 X-59 Y66 Z35 ; move over the post
              G1 Z7 F500 ; push probe down on post
              G1 Z35 F10000 ; raise head again
              G1 X0 Y0 ; move to somewhere sensible
              M564 S1 ; apply limits again

              This is where the problem is. I need to update this script to what I had in my previous script prior to updating to 1.19 from 1.18

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