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

    Z probe 0 not found after upgrading to Firmware v3.2 from v3.1.1

    Scheduled Pinned Locked Moved
    General Discussion
    4
    9
    450
    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.
    • jsn0327undefined
      jsn0327
      last edited by

      I upgraded to firmware 3.2 from 3.1.1 today and now my printer will not home the Z axis. Before the upgrade, everything worked fine. I'm sure that it is a configuration issue; as I had to change a lot of my configuration syntax when updating from firmware version 2 to 3. I don't understand why the config formatting has to change between firmware versions to the point that it breaks things?

      I am using a BL Touch as my z probe. The error that I am receiving is below. I will upload my config.g, homez.g, and homeall.g for your review. I ran the M98 P"config.g" command in terminal, as was suggested by another post with this error. The printer returned that there is in an invalid P parameter in my config, but it does not say which line that invalid parameter is on. Please let me know if you need any additional information. I appreciate your help!

      Errors:
      1/12/2021, 5:32:07 PM Error: in file macro line 9: G30: Z probe 0 not found
      Error: Homing failed
      1/12/2021, 5:32:07 PM Error: in file macro line 15: G30: Z probe 0 not found
      Error: Missing Z probe pin name(s)
      Error: in file macro line 17: G30: Z probe 0 not found
      1/12/2021, 5:32:06 PM G28
      Error: Missing Z probe pin name(s)

      config.g
      homez.g
      homeall.g

      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        M558 P9 F300            ; speed up homing probe
        G30                     ; home Z by probing the bed
        M558 P9 F120            ; slow down homing probe for second pass
        G30                     ; home Z by probing the bed
        

        Remove the P9 from the M558 commands in your homeall

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator @jsn0327
          last edited by

          @jsn0327 said in Z probe 0 not found after upgrading to Firmware v3.2 from v3.1.1:

          Errors:
          1/12/2021, 5:32:07 PM Error: in file macro line 9: G30: Z probe 0 not found
          Error: Homing failed
          1/12/2021, 5:32:07 PM Error: in file macro line 15: G30: Z probe 0 not found
          Error: Missing Z probe pin name(s)
          Error: in file macro line 17: G30: Z probe 0 not found
          1/12/2021, 5:32:06 PM G28
          Error: Missing Z probe pin name(s)

          Is that from you running M98 P"config.g" or from trying to home?

          Z-Bot CoreXY Build | Thingiverse Profile

          jsn0327undefined 1 Reply Last reply Reply Quote 0
          • jsn0327undefined
            jsn0327 @Phaedrux
            last edited by

            @Phaedrux The errors are from trying to home all and home z.

            1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator
              last edited by Phaedrux

              In that case I am sure the P9 is the problem. Reboot the printer after you remove the P9 and try homing again.

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • jsn0327undefined
                jsn0327
                last edited by

                @Phaedrux said in Z probe 0 not found after upgrading to Firmware v3.2 from v3.1.1:

                M98 P"config.g"

                That fixed it! Thanks a lot! Was that a change from v3.1.1 to 3.2?

                Also, I am still receiving the following error. It doesn't seem to affect anything because OctoPrint just ignores it, but can you tell from my config.g what is wrong? Is there a way to output the line number that the error is referencing?

                Recv: WiFi module is idle
                Recv: HTTP is enabled on port 80
                Recv: FTP is disabled
                Recv: TELNET is disabled
                Recv: Error: Invalid use of P parameter

                Phaedruxundefined 1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator @jsn0327
                  last edited by Phaedrux

                  @jsn0327 said in Z probe 0 not found after upgrading to Firmware v3.2 from v3.1.1:

                  Recv: Error: Invalid use of P parameter

                  Hmm. I wonder which P parameter it means... I can't see anything obvious from your config at a glance.

                  You could try adding some echos to the config.g at various places before any commands with P parameters. M117 with numbers to try and identify where it's happening would probably echo when you use M98 P"config.g"

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • Vetiundefined
                    Veti
                    last edited by

                    M350 X128 Y128 Z128 E16 I0 ; configure microstepping without interpolation

                    this puts unnecessary load on the cpu.
                    unless you have a specific reason, its better to go with x16 and interpolation.

                    1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk
                      last edited by

                      @Phaedrux @jsn0327
                      This line gives the invalid use of P parameter error

                      M574 Z1 S2 P"zstop"
                      

                      Remove that line

                      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

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