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

    Duet3 6HC not deploying BL touch for mesh bed leveling

    Scheduled Pinned Locked Moved Solved
    Tuning and tweaking
    5
    79
    3.7k
    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 @autopilot.exe
      last edited by

      @autopilot-exe

      According to the docs M98 requires double quotes around the file name in v3 firmware.

      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

      autopilot.exeundefined 1 Reply Last reply Reply Quote 0
      • autopilot.exeundefined
        autopilot.exe @fcwilt
        last edited by

        @fcwilt the duet doesn't spit out any errors. I typed "m401" and I get a green notification, but nothing moves on the machine. I type "m402", same thing happens.

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

          Can you confirm that your deploy and retract probe macros are in the /sys folder?

          Z-Bot CoreXY Build | Thingiverse Profile

          autopilot.exeundefined 1 Reply Last reply Reply Quote 0
          • autopilot.exeundefined
            autopilot.exe @fcwilt
            last edited by

            @fcwilt in my homeall.g there are quotes around the file names. Home C,X, and Y are all executed correctly. when it gets to home z, the probe still doesn't deploy. I just tried it after removing the M574 command earlier.

            1 Reply Last reply Reply Quote 0
            • autopilot.exeundefined
              autopilot.exe @Phaedrux
              last edited by

              @Phaedrux Screenshot 2021-03-10 105107.jpg

              Can confirm.

              1 Reply Last reply Reply Quote 0
              • fcwiltundefined
                fcwilt @autopilot.exe
                last edited by

                @autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

                @fcwilt the duet doesn't spit out any errors. I typed "m401" and I get a green notification, but nothing moves on the machine. I type "m402", same thing happens.

                Hmm...

                At this point I suppose we should verify the contents of deployprobe.g and retractprobe.g.

                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

                autopilot.exeundefined 1 Reply Last reply Reply Quote 0
                • autopilot.exeundefined
                  autopilot.exe @fcwilt
                  last edited by

                  @fcwilt

                  ; deployprobe.g
                  ; called to deploy a physical Z probe
                  ;
                  ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 06 2021 11:26:03 GMT-0600 (Central Standard Time)
                  M280 P0 S10 ; deploy BLTouch
                  
                  
                  
                  ; retractprobe.g
                  ; called to retract a physical Z probe
                  ;
                  ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 06 2021 11:26:03 GMT-0600 (Central Standard Time)
                  M280 P0 S90 ; retract BLTouch
                  
                  
                  

                  aceb09ad-be7e-493a-b438-a2b1120527a9-image.png

                  1 Reply Last reply Reply Quote 0
                  • fcwiltundefined
                    fcwilt
                    last edited by

                    Thanks.

                    Does the probe run it's self-test routine when you power on the printer?

                    Did you verify that it is connected to the correct input and output pins?

                    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

                    autopilot.exeundefined 1 Reply Last reply Reply Quote 0
                    • autopilot.exeundefined
                      autopilot.exe @fcwilt
                      last edited by

                      @fcwilt the self test is working, I have it wired correctly according to the documentation. (3.3v: nothing, io7.in: white, GND: black and brown soldered together going to a single pin, io7.out: orange, 5 volt: red)

                      fcwiltundefined 1 Reply Last reply Reply Quote 0
                      • fcwiltundefined
                        fcwilt @autopilot.exe
                        last edited by

                        @autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

                        @fcwilt the self test is working, I have it wired correctly according to the documentation. (3.3v: nothing, io7.in: white, GND: black and brown soldered together going to a single pin, io7.out: orange, 5 volt: red)

                        Running out of ideas.

                        I have a Duet 3 setup on my workbench and BLTouch units in inventory.

                        All boards (6HC, 3HC, 1LC) are running 3.2.2.

                        I will get a BLTouch out and connect and configure as you have.

                        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

                        autopilot.exeundefined 1 Reply Last reply Reply Quote 0
                        • autopilot.exeundefined
                          autopilot.exe @fcwilt
                          last edited by

                          @fcwilt A possibility that I just considered: the firmware generator tool that I used as a base is v3.2.3. Could the mismatch be from there? i.e, the RepRapFirmware Configuration tool version not being in line with the firmware version?

                          dc42undefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators @autopilot.exe
                            last edited by

                            @autopilot-exe , what version is your Duet 3 6HC board?

                            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

                            autopilot.exeundefined 1 Reply Last reply Reply Quote 0
                            • Phaedruxundefined
                              Phaedrux Moderator @autopilot.exe
                              last edited by

                              @autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

                              @fcwilt A possibility that I just considered: the firmware generator tool that I used as a base is v3.2.3. Could the mismatch be from there? i.e, the RepRapFirmware Configuration tool version not being in line with the firmware version?

                              In the tool you can select the firmware version you want it to generate a config for. The exact version of the config tool isn't important really.

                              @autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

                              @fcwilt the self test is working, I have it wired correctly according to the documentation. (3.3v: nothing, io7.in: white, GND: black and brown soldered together going to a single pin, io7.out: orange, 5 volt: red)

                              Can you post a photo of the wiring?

                              io7 should be ok unless it's a prototype board.

                              Z-Bot CoreXY Build | Thingiverse Profile

                              autopilot.exeundefined 1 Reply Last reply Reply Quote 0
                              • autopilot.exeundefined
                                autopilot.exe @dc42
                                last edited by

                                @dc42 hey, its labeled as V1.0

                                fcwiltundefined 1 Reply Last reply Reply Quote 0
                                • fcwiltundefined
                                  fcwilt @autopilot.exe
                                  last edited by fcwilt

                                  @autopilot-exe

                                  I installed the most recent version of a BLTouch on my 6HC board (running 3.2.2) at IO7.

                                  I powered it from 3.3 volts.

                                  These were the configuration commands:

                                  M950 S0 C"io7.out"
                                  M558 P9 C"io7.in" H2 F120 T9000 R0.2 A1 S0.01 ; 1 reading

                                  M401 worked. M402 worked. G30 worked.

                                  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

                                  autopilot.exeundefined 1 Reply Last reply Reply Quote 0
                                  • autopilot.exeundefined
                                    autopilot.exe @Phaedrux
                                    last edited by

                                    @Phaedrux BL touch Wiring.jpg

                                    So when I took this photo I panicked after seeing the brown wire. To make sure it was connected I took a meter to it and confirmed continuity from the last extensions to ground on both the black and brown wire. It's ugly but functional.

                                    1 Reply Last reply Reply Quote 0
                                    • autopilot.exeundefined
                                      autopilot.exe @fcwilt
                                      last edited by

                                      @fcwilt no ^ before io.7in since you you are using 3.3v?

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

                                        It would be the yellow wire that carries the servo control signal back to the BLtouch.

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        1 Reply Last reply Reply Quote 0
                                        • fcwiltundefined
                                          fcwilt @autopilot.exe
                                          last edited by

                                          @autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

                                          @fcwilt no ^ before io.7in since you you are using 3.3v?

                                          I didn't even think about if that was needed or not.

                                          I did not have it as you can see.

                                          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

                                          autopilot.exeundefined 1 Reply Last reply Reply Quote 0
                                          • autopilot.exeundefined
                                            autopilot.exe @fcwilt
                                            last edited by

                                            @fcwilt Just tried both ways. Now pin up and pin down work. Mesh bed leveling does not.

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