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

    Creality BLtouch kit compatibility and wiring

    Scheduled Pinned Locked Moved Solved
    Third-party add-ons
    4
    51
    3.8k
    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.
    • JoergS5undefined
      JoergS5 @usescoasters
      last edited by

      @usescoasters I have a little correction to your homeall:
      G1 H2 Z0 F6000
      after homing Z, and before homing Y, Z0 should be something like Z5 or more, otherwise your Y homing will scrub on the bed and the probing of Z which comes next may have problems also.

      1 Reply Last reply Reply Quote 0
      • usescoastersundefined
        usescoasters @Phaedrux
        last edited by usescoasters

        @Phaedrux According to the config.g file it says its running firmware 2.03 so I'll try updating it. I have one question though sinch the user interface of the configurator of that version is slightly different.

        It asks for a modulation pin input for the z probe. If my wiring is exactly the same as this, what should I set this to? I assume either zprobe.mod or zprobe.mod(inverted).

        EDIT: I tentatively install version 3 firmware with what I think are the right settings and now it gives me an error when I type in the M280 P3 S10 I1 command.

        It says "invalid servo index 3 in M280 command".

        1 Reply Last reply Reply Quote 0
        • usescoastersundefined
          usescoasters @Phaedrux
          last edited by usescoasters

          @Phaedrux I had a chance to look through the gcode documentation on the duet3d website and I see I have to assign a GPIO port in servo mode to the duex pwm 1 channel for RRF3.

          After looking through the new config.g the tool gave me I can see it assigned M950 S0 C"deux.pwm1", so the pwm channel is defined as port 0. But when I Input M280 P0 S10 into the gcode console I still recieve the error.

          Error: M280: Invalid servo index 0 in M280 command

          Here's the new files
          homez.g
          homeall.g
          deployprobe.g
          config.g

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

            In config.g in your M558 remove +!zprobe.mod and add a ^ in front of zprobe.in

            M558 P9 C"^zprobe.in" H5 F120 T6000

            The rest looks correct now if you're actually plugged into Duex PWM1 and you're using version 3.1.1.

            Please send M115 in the console to confirm the firmware version and send M98 Pconfig.g and report back with any errors.

            Z-Bot CoreXY Build | Thingiverse Profile

            usescoastersundefined 1 Reply Last reply Reply Quote 0
            • usescoastersundefined
              usescoasters @Phaedrux
              last edited by

              @Phaedrux Now something strange is happening. I'm certain I selected version 3 software and even looking back at my config.g is says it was generated by Configuration Tool v3.1.3:

              ; Configuration file for Duet WiFi (firmware version 3)

              ; executed by the firmware on start-up

              ;

              ; generated by RepRapFirmware Configuration Tool v3.1.3 on Fri Jun 19 2020 13:20:18 GMT-0400 (Eastern Daylight Time)

              But the M115 command returns this:

              M115

              FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2019-12-13b1

              Either it's not updating the system files when I upload the zip folder or I'm not understanding something. Is it refering to the same thing or another piece of firmware?

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

                Yes it appears that the firmware update was unsuccessful. Going from 2.05 will require updating to 3.0 first, and then 3.1.1. The intermediate upgrade to 3.0 is required to update the programing files before you can go to 3.1.1.

                From the release notes: https://github.com/Duet3D/RepRapFirmware/releases/tag/3.1.1

                Back up the contents of your /sys folder before upgrading to RRF 3.x in case you need to revert to RRF 2
                Many changes to config.g are needed when upgrading from RRF 2.x to 3.x. See https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files for a summary. It may be simpler to use the online configurator to generate new files for scratch.

                Users of RepRapFirmware 2.x cannot upgrade directly to this release because the binaries for the Duet 2 series are too large for the Duet 2 IAP programs. So you must upgrade to RepRapFirmware 3.0 first, then you can upgrade immediately to version 3.1.1. Alternatively, you can use Bossa over USB to upgrade directly to RepRapFirmware 3.1.1 but in this case you will need to upload DWC 3.1.1 and the appropriate IAP file separately.

                Once you are actually updated to 3.1.1 your config should work.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • MartinNYHCundefined
                  MartinNYHC
                  last edited by

                  Could someone please summarize, how to properly connect the Creality BLTouch (Red, Blue, Yellow, Black, White cables) to the Duet 2? I'm still not able to get it running and all the pists about the different colors are quite confusing.

                  Thanks, Martin

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

                    @MartinNYHC https://imgur.com/iUym2OG

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • MartinNYHCundefined
                      MartinNYHC
                      last edited by

                      OMG...why they are not just stick to a standard 🙄

                      Thanks for that!!!

                      1 Reply Last reply Reply Quote 0
                      • MartinNYHCundefined
                        MartinNYHC
                        last edited by

                        Sorry, but I need to double check. It is still confusing to me because the picture show colors in a different order than my Creality BLTouch. Mine has Red, Blue, Yellow, Black, White from richt to left.

                        Just want to make sure that I don't cable it wrong and damage the Duet 2 board.

                        Thanks, Martin

                        JoergS5undefined 1 Reply Last reply Reply Quote 0
                        • JoergS5undefined
                          JoergS5 @MartinNYHC
                          last edited by JoergS5

                          @MartinNYHC I saw a lot of different combinations.

                          I expect the best chance of correct assignment is to check the order at the connector and deciding from that which single cable and color is which connection.

                          My Geetech clone, Smart 2.0 and Smart 3.1, all cables have colors brown-red-yellow-black-white and at all three the 5-pin connector have the same order, so chances are high that when you look at the 5-pin connector, you can find out the correct color-function assignment.

                          For Duet wiring, please check https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch then.

                          1 Reply Last reply Reply Quote 0
                          • MartinNYHCundefined
                            MartinNYHC
                            last edited by

                            For those of you who have a beautiful "Red, Blue, Yellow, Black, White"-cable-BLTouch:

                            Blue goes to expansion pin 1 (+5V)
                            Red goes to expansion pin 2 (GND)
                            Yellow goes to expansion pin HEATERx
                            White goes to Z_PROBE_IN
                            Black goes to GND on ZPROBE port

                            Maybe this can also be added to the documentation.

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