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

    BLTouch giving error

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    5
    12
    345
    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.
    • jay_s_ukundefined
      jay_s_uk @terhart
      last edited by

      @terhart post your homez file
      M401 and M402 should just be M401 and M402 with no P0 at the end

      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 0
      • droftartsundefined
        droftarts administrators @terhart
        last edited by

        @terhart @jay_s_uk M401 and M402 should be able to take a P parameter; see https://docs.duet3d.com/User_manual/Reference/Gcodes#m401-deploy-z-probe

        However, this sounds like a bug, and that it is looking for deployprobe0.g, and when it does not find it, it is not switching to deployprobe.g. I've marked this as a bug for @dc42 to check.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        1 Reply Last reply Reply Quote 1
        • terhartundefined
          terhart
          last edited by

          Here is the homez file:
          Thanks a lot for your help.

          ; homez.g
          ; called to home the Z axis
          ;
          ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Apr 17 2021 19:16:17 GMT+0200 (Midden-Europese zomertijd)
          G91 ; relative positioning
          G1 H2 Z5 F6000 ; lift Z relative to current position
          G90 ; absolute positioning
          G1 X15 Y15 F6000 ; go to first probe point
          G30 ; home Z by probing the bed

          ; Uncomment the following lines to lift Z after probing
          ;G91 ; relative positioning
          ;G1 Z5 F100 ; lift Z relative to current position
          ;G90 ; absolute positioning

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

            Did you modify your deploy and retract macros to remove the P0 from the M280 commands?

            Z-Bot CoreXY Build | Thingiverse Profile

            terhartundefined 2 Replies Last reply Reply Quote 0
            • terhartundefined
              terhart @Phaedrux
              last edited by

              @Phaedrux Yes, I did. But unfortunately it didnt solve anything. Error stays.
              Thanks for your help.

              1 Reply Last reply Reply Quote 0
              • terhartundefined
                terhart @Phaedrux
                last edited by

                @Phaedrux Next to my previous remark: This is exact error text that is generated:

                M98 P"0:/macros/BLTouch Retract"
                Error: Bad command: probe

                There is no error on the deploy macro.
                Also, if I initiate the command "M280!P0 S90" or "M280!P0 S10" the BLTouch deploys and retract without an error.
                The error only comes on M402.

                Thanks.

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

                  deployprobe.g and retractprobe.g must be in the sys folder for M401 and M402 to work. They must be named that way too.

                  Z-Bot CoreXY Build | Thingiverse Profile

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

                    @terhart said in BLTouch giving error:

                    M98 P"0:/macros/BLTouch Retract"
                    Error: Bad command: probe

                    We'll need to see the contents of macro file "BLTouch Retract" to diagnose that.

                    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

                    terhartundefined 1 Reply Last reply Reply Quote 0
                    • terhartundefined
                      terhart @dc42
                      last edited by

                      @dc42
                      Hi, thanks for helping me.
                      This is all that is in the BL Touch Retract file:

                      M402

                      If I just enter M402 on the command line, a "probe" error is raised.

                      Best regards,

                      Hans ter Hart

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

                        retractprobe.g deployprobe.g

                        Try placing these files in your sys folder.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        terhartundefined 1 Reply Last reply Reply Quote 0
                        • terhartundefined
                          terhart @Phaedrux
                          last edited by

                          @Phaedrux

                          THANKS!!!! That did it....!! Problem solved! No error anymore.
                          Thanks a lot for your help.

                          Best regards,

                          Hans

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