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

    RRF3 BL Touch setup on Duet WiFi v1.0 + Duex5

    Scheduled Pinned Locked Moved
    General Discussion
    3
    7
    333
    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.
    • abearundefined
      abear
      last edited by

      Hi All,

      I have a "BeastV1" from Cultivate3d (a large DIY cartesian 3D printer), that I am upgrading from a Rumba 8bit board to Duet WiFi (v1.0) and Duex5 boards I have had sitting in the draw (for this very purpose) for 3 years. The main reason for ugrade is to get real "auto-bed levelling" with a separate motor driving each of the 3 z-axis lead screws. And because its fun to tinker.

      I have almost everything setup except the BL Touch.
      (a bit of a hiccup with a dodgy FAN0 pin that sits at 10.3 V no matter what I do, but got past it by using FAN1 instead).

      I have followed BeTrue3D's wiring setup
      https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/
      and most of his config.g setup, with the some exceptions to support Mode 9.

      I have cut the 3.3 V strip on the BL Touch (its genuine but a few years old).

      It runs its self test, no problems and worked flawlessly with the Rumba board.

      X and Y end stops are working as expected, the z end stop is not connected in leu of using the BL Touch (similar to my previous setup with the Rumba).

      My config.g is attached
      config.g

      The probe's deploy and retract just won't do anything. Neither the deploy.g/retract.g scripts from the config gen tool, the PinUp.g/Pin Down.g scripts BeTrue or the M401/M402 commands will have any effect.

      And obviously homing the Z axis just crashes the bed into the nozzle.

      Any help would be greatly appreciated.

      Thanks

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

        try inverting the duex port

        M950 S0 C"!duex.pwm5" ; create servo pin 0 for BLTouch

        your M558 is missing the pin

        M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.

        this is not needed in rrf3

        M308 S0 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin e0temp

        your thermistor setting is incorrect. find the correct beta value in your thermistor documentation.

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

          What do you have in your deploy and retract files?

          Z-Bot CoreXY Build | Thingiverse Profile

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

            https://configtool.reprapfirmware.org/Start

            Going through the config tool you get something like this

            ; Z-Probe
            M950 S0 C"duex.pwm5"                           ; create servo pin 0 for BLTouch
            M558 P9 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to bltouch and the dive height + speeds
            G31 P500 X0 Y0 Z2.5                            ; set Z probe trigger value, offset and trigger height
            M557 X15:215 Y15:195 S20                       ; define mesh grid
            
            ; deployprobe.g
            ; called to deploy a physical Z probe
            ;
            ; generated by RepRapFirmware Configuration Tool v3.2.0 on Wed Dec 30 2020 15:25:52 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.0 on Wed Dec 30 2020 15:26:05 GMT-0600 (Central Standard Time)
            M280 P0 S90 ; retract BLTouch
            

            Also make sure your homeall and homez are using G30 instead of G1 H1 Z

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • abearundefined
              abear
              last edited by abear

              @Phaedrux said in RRF3 BL Touch setup on Duet WiFi v1.0 + Duex5:

              he config tool you g

              Thanks Phaedrux and Veti,

              Phaedrux, you were on the right track. My probe up and down scripts (all of them) referred to the pin number (i.e. 7) instead of the port number defined by the M950 command (i.e. 0).
              A problem caused by mashing together the defaults from the RRF3 config tool and the BeTrue3D how to article which used RRF2 (or earlier).
              My BLTouch working config.g and probe up and down scripts are attached (with my comments included) for anyone else that may need to reference this info. Just note, I have not yet finished configuring everything else, only the BL Touch in these scripts.
              Also, I did need to update the homex and homeall commands to use G30 instead of G1

              deployprobe.g
              homeall.g
              homez.g
              retractprobe.g
              config.g

              Thanks for your help

              Now onto the next configuration challenge.....The actual Auto-Bed Level test, with 3 z-axis motors doing the levelling for me, wahoo 🙂

              abearundefined 1 Reply Last reply Reply Quote 0
              • abearundefined
                abear @abear
                last edited by

                @abear said in RRF3 BL Touch setup on Duet WiFi v1.0 + Duex5:

                he config tool you g

                I'm not sure what "he config tool you g" means

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

                  @abear

                  he means using the using the config tool at https://configtool.reprapfirmware.org/

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