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

    deployprobe.g for Euclid not running

    Scheduled Pinned Locked Moved Solved
    Tuning and tweaking
    5
    23
    1.2k
    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.
    • fcwiltundefined
      fcwilt @Adamfilip
      last edited by

      @adamfilip

      If you have two steppers for the Y axis why do they not appear in your M584 commands?

      Normally it would look like this (based on the comments):

      M584 X0 Y1:4 Z2 E3

      Thanks.

      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

      Adamfilipundefined 1 Reply Last reply Reply Quote 0
      • Adamfilipundefined
        Adamfilip @fcwilt
        last edited by

        @fcwilt actually I use too, its changed to only a signal Y.
        sorry some old notes still linger

        1 Reply Last reply Reply Quote 1
        • Adamfilipundefined
          Adamfilip @jay_s_uk
          last edited by

          @jay_s_uk yeah its weird.

          I restarted the machine. did home all.
          ran the macro and nothing.
          not even the first echo statement showed up in console

          Adamfilipundefined fcwiltundefined 2 Replies Last reply Reply Quote 0
          • Adamfilipundefined
            Adamfilip @Adamfilip
            last edited by

            @adamfilip

            I copied the entire deployprobe.g code into a macro and it runs on its own

            so it seems like the deployprobe.g itself isnt being run when asked with
            M401 P1 ;Deployprobe

            fcwiltundefined oliofundefined 2 Replies Last reply Reply Quote 0
            • fcwiltundefined
              fcwilt @Adamfilip
              last edited by

              @adamfilip

              Just to provide another point of view.

              I no longer home things as needed because I found I did not like homing taking place unexpectedly because I had tried to do something that required the printer to be homed, like mount the probe.

              So now I just check that the printer is homed and abort if it is not.

              I have a Euclid on one of my printers but I don't use the deploy/retract feature that is part of the firmware. I call my routines to mount/unmount the probe as needed. I have found that for normal operations I can keep the probe mounted except during actual printing. Any operation that needs the probe, such as setting the Z=0 Datum, mounts the probe and leaves it mounted. In the print start code just before actual printing begins the probe is unmounted.

              Just food for thought.

              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
              • fcwiltundefined
                fcwilt @Adamfilip
                last edited by

                @adamfilip said in deployprobe.g for Euclid not running:

                so it seems like the deployprobe.g itself isnt being run when asked with
                M401 P1 ;Deployprobe

                Doesn't the firmware track the state of the probe and only run the deploy/retract routines when it thinks it needs to?

                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
                • oliofundefined
                  oliof @Adamfilip
                  last edited by

                  @adamfilip If the euclid is your only probe, drop the P1 and only run M401. Alternately, try P0 because your probe definition assignes ID 0.

                  <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                  Adamfilipundefined 1 Reply Last reply Reply Quote 1
                  • Adamfilipundefined
                    Adamfilip @oliof
                    last edited by

                    @oliof Thank you both M401 and M401 P0 worked!

                    Adamfilipundefined 1 Reply Last reply Reply Quote 1
                    • Adamfilipundefined
                      Adamfilip @Adamfilip
                      last edited by

                      @adamfilip only other error im getting in console is

                      Probe Pickup complete
                      Warning: G3000: Command is not supported

                      Adamfilipundefined 1 Reply Last reply Reply Quote 0
                      • Adamfilipundefined
                        Adamfilip @Adamfilip
                        last edited by

                        @adamfilip

                        G90                           ; absolute positioning
                        G0 X150 Y150 G3000            ; move to the center of the bed
                        M400                          ; wait for moves to finish
                        
                        Adamfilipundefined 1 Reply Last reply Reply Quote 0
                        • Adamfilipundefined
                          Adamfilip @Adamfilip
                          last edited by

                          @adamfilip probably just a typo and should be F

                          1 Reply Last reply Reply Quote 2
                          • Phaedruxundefined Phaedrux marked this topic as a question
                          • Phaedruxundefined Phaedrux has marked this topic as solved
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA