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

    G30 Causing G28 can not be called in homing file error

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    8
    211
    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.
    • JADoglioundefined
      JADoglio
      last edited by

      NOT SURE WHERE TO POST THIS SO I THOUGHT I WOULD START HERE. SORRY IF IT SHOULD BE IN A DIFFERENT CHAT!

      My machine is a Voron 2.4r2.

      Board: Duet 3 Mini 5+ (Mini5plus) with the 2 port expansion board

      Firmware: RepRap Firmware for Duet 3 Mini 5+ 3.4.6 (2023-07-21)

      Duet WiFi Server Version: 1.27

      The Situation

      When I issue a homeall.g command using DWC HomeAll Button. X and Y home as they should while Z homes but issues the error message below. The homing files are attached as is my config.g. As I am using a klicky probe I have written macros to check to see if the probe is attached before the execution of the most moves. During maintenance I seem to frequently leave it attached and that creates issues chasing it down when it gets knocked off.

      The Issue

      When I include G30 in the homing file I get the error message below. When I don't include the G30, Z moves to position to home, but does not home. I assume G30 is calling G28 which is why the firmware complains about it but then ignores it and does the homing anyway. I would like to find a way to make this home without getting the error. Is that possible?

      4/2/2024, 4:08:46 PM M292
      Error: G28 may not be used within a homing file
      Probe already attached
      Attach Probe Successful

      config.g.txt
      HomeAll Incuding X Y Z Files.txt

      Not a huge issue but I suspect there is a simple solution.

      Thanks

      gloomyandyundefined dc42undefined 2 Replies Last reply Reply Quote 0
      • gloomyandyundefined
        gloomyandy @JADoglio
        last edited by

        @JADoglio Are those your actual homing macros? What is producing the output "Attach Probe Successful"? Do you still get that error message if you remove (or comment out) the M291 command from your homez?

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

          @JADoglio please also post your deployprobe.g and retractprobe.g files, if you have those.

          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

          JADoglioundefined 1 Reply Last reply Reply Quote 0
          • JADoglioundefined
            JADoglio @dc42
            last edited by

            @dc42
            David, thanks for the reply. Here is the file you asked for

            retract attach probe.txt

            gloomy,

            The command to test for probe attachment is in the file. When I remove it, I get the same error

            if sensors.probes[0].value[0] == 0 ; if sensor value is 0 do this, 0 = probe attached
            echo "Probe already attached"

            Thanks all

            gloomyandyundefined 1 Reply Last reply Reply Quote 0
            • gloomyandyundefined
              gloomyandy @JADoglio
              last edited by

              @JADoglio What does the code in this file do:
              M98 P"Home if needed.g"

              JADoglioundefined 1 Reply Last reply Reply Quote 0
              • JADoglioundefined
                JADoglio @gloomyandy
                last edited by

                @gloomyandy

                It is a macro that is called at the start of a print. If the machine is already homed, it will not home again even though there is a G28 in the start g code file for the printer.

                if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed ; if homed don't home again
                G28 ; if not, continue homing

                gloomyandyundefined 1 Reply Last reply Reply Quote 0
                • gloomyandyundefined
                  gloomyandy @JADoglio
                  last edited by

                  @JADoglio You are calling that file at the start of your deployprobe.g file, this is probably what is causing that message about G28 as your call to G30 will be triggering a call to deployprobe.g which is calling Home if needed.g which will see that Z is not currently homed and will then try to run M28...

                  This is what you said is in your deployprobe.g file:

                  deployprobe.g in sys folder
                  
                  M98 P"Home if needed.g"
                  
                  if sensors.probes[0].value[0] == 0	; if sensor is value ia 0 do this, 0 = probe attached
                  		echo "Probe already attached"
                  
                  if sensors.probes[0].value[0] == 1000		; if sensor is 1000 do this, 1000 = probe detached
                  
                  	G1 X53 F20000						; X position of klicky dock
                  	G1 Y340 F20000:120						; Y position of klicky dock
                  	G1 Y345 F600
                  	M400
                  	G1 Y175 F12000						; slide out of dock return to bed Y center
                  	G1 X175 F12000 Z10						; slide out of dock return to bed X center
                  	M400								;	wait for moves to finish
                  		
                  if sensors.probes[0].value[0] == 1000	;Check to see if probe is attached 1000 = not attached
                  	G1 X175 Y175 F10000  
                  	abort "Attach probe FAILED!"
                  else	
                  	echo "Attach Probe Successfull"
                  	
                  	
                  
                  JADoglioundefined 1 Reply Last reply Reply Quote 0
                  • JADoglioundefined
                    JADoglio @gloomyandy
                    last edited by

                    @gloomyandy Thanks. That was the source of the issue. I figured out how to get around it. I appreciate the help. Regards, Jim

                    1 Reply Last reply Reply Quote 0
                    • 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