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

    Bltouch with new firmware

    Scheduled Pinned Locked Moved Solved
    Tuning and tweaking
    6
    28
    1.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.
    • Elliotundefined
      Elliot @aidar
      last edited by

      @aidar Thank you. Yes, the black wire is an extension of the yellow. I changed my deployprobe and retractprobe files and it is better.

      1. Is there anything I should change in my config.g?
      2. I was able to start a print. It only did one probe (in the front left corner) and then started to try and print. How can I make it do the probe test on all corners and in the middle?
      1 Reply Last reply Reply Quote 0
      • aidarundefined
        aidar
        last edited by

        I would remove all M918 commands from config, as you do not have 12864 display connected (its supported on Maestro board, not on Wifi), paneldue is connected, but that is differst thing and do not need that M918 command.

        About probing - please post your homing files as well as slicer starting script.

        Elliotundefined 1 Reply Last reply Reply Quote 0
        • Elliotundefined
          Elliot @aidar
          last edited by

          @aidar these are the homing files I have:

          Homeall.g

          ; homeall.g
          ; called to home all axes
          ;
          ; generated by RepRapFirmware Configuration Tool on Sat Sep 29 2018 12:21:44 GMT-0700 (Pacific Daylight Time)
          G91                     ; relative positioning
          G1 Z2.5 F6000 S2        ; lift Z relative to current position
          M98 Pdeployprobe.g      ; deploy mechanical Z probe
          G1 S1 X-269 Y-261 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
          G1 X5 Y5 F6000          ; go back a few mm
          G1 S1 X-269 Y-261 F360  ; move slowly to X and Y axis endstops once more (second pass)
          G90                     ; absolute positioning
          G1 X51 Y20 F6000        ; go to first bed probe point and home Z
          G30                     ; home Z by probing the bed
          
          ; Uncomment the following lines to lift Z after probing
          ;G91                    ; relative positioning
          ;G1 S2 Z2.5 F100        ; lift Z relative to current position
          ;G90                    ; absolute positioning
          
          
          M98 Pretractprobe.g     ; retract mechanical Z probe
          

          homedelta.g

          ; Example Homing file for RepRapFirmware on delta printer
          
          M117 Use https://configurator.reprapfirmware.org/ to set up your printer config
          
          ;G91							; use relative positioning
          ;******* Change F250 in the following line to F2500 when you are finished commissioning
          ;******* Change 320 in the following to a higher value if your Kossel has taller towers
          ;G1 S1 X320 Y320 Z320 F2500	; move all carriages up 320mm, stopping at the endstops
          ;G1 S2 X-3 Y-3 Z-3			; move all carriages down 3mm
          ;G1 S1 X6 Y6 Z6 F250			; move carriages slowly up 6mm, stopping at the endstops
          ;G1 Z-5 F2000				; down a few mm so that we can centre the head
          ;G90							; back to absolute positioning
          ;G1 X0 Y0 F2000				; centre the head and set a reasonable feed rate
          

          homex.g

          ; homex.g
          ; called to home the X axis
          ;
          ; generated by RepRapFirmware Configuration Tool on Sat Sep 29 2018 12:21:45 GMT-0700 (Pacific Daylight Time)
          G91               ; relative positioning
          G1 Z2.5 F6000 S2  ; lift Z relative to current position
          G1 S1 X-269 F1800 ; move quickly to X axis endstop and stop there (first pass)
          G1 X5 F6000       ; go back a few mm
          G1 S1 X-269 F360  ; move slowly to X axis endstop once more (second pass)
          G1 Z-2.5 F6000 S2 ; lower Z again
          G90               ; absolute positioning
          

          homey.g

          ; homey.g
          ; called to home the Y axis
          ;
          ; generated by RepRapFirmware Configuration Tool on Sat Sep 29 2018 12:21:44 GMT-0700 (Pacific Daylight Time)
          G91               ; relative positioning
          G1 Z2.5 F6000 S2  ; lift Z relative to current position
          G1 S1 Y-261 F1800 ; move quickly to Y axis endstop and stop there (first pass)
          G1 Y5 F6000       ; go back a few mm
          G1 S1 Y-261 F360  ; move slowly to Y axis endstop once more (second pass)
          G1 Z-2.5 F6000 S2 ; lower Z again
          G90               ; absolute positioning
          

          homez.g

          ; homez.g
          ; called to home the Z axis
          ;
          ; generated by RepRapFirmware Configuration Tool on Sat Sep 29 2018 12:21:44 GMT-0700 (Pacific Daylight Time)
          G91              ; relative positioning
          G1 Z2.5 F6000 S2 ; lift Z relative to current position
          G90              ; absolute positioning
          G1 X51 Y20 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 S2 Z2.5 F100 ; lift Z relative to current position
          ;G90             ; absolute positioning
          

          Slicer Script:

          G28 ; home all axes
          G29; BLTOUCH mesh generation
          G92 E0.0
          G1 Z5;
          G1 X10 Y10 Z0 F6000;
          G1 X60.0 E9.0  F1000.0 ; intro line
          G1 X100.0 E12.5  F1000.0 ; intro line
          G92 E0.0
          
          1 Reply Last reply Reply Quote 0
          • aidarundefined
            aidar
            last edited by

            I reccomend:
            in your config M557 X50:200 Y50:200 S65 P3:3 remove either S or P parameter. As they both define probe spacing but in different way, having both of them may confuse all process. So M557 X50:200 Y50:200 P3:3 seems better.
            In homeall.g remove M98 Pdeployprobe.g and M98 Pretractprobe.g commands. Firmware knows when to call them as you probe type is defined as bltouch(P9).
            Delete homedelta.g file. Your printer is not delta, so you dont need it.
            In your slicer script put M561 between G28 and G29 commands to cancel any mesh compensation before new probing.

            Elliotundefined 1 Reply Last reply Reply Quote 1
            • Elliotundefined
              Elliot @aidar
              last edited by

              @aidar Thanks.

              I tested out the BlTouch and it deploys and retracts perfectly.

              I then tried to do a mesh probe and it does the first corner but it only pushes the bltouch halfway back into place. It then proceeds to go round the rest of the corners without trying to test with the bltouch. It just pauses for a second in each place without lowering et.

              The error I get at the end is:
              Error: Z probe already triggered at start of probing move

              1 Reply Last reply Reply Quote 0
              • mendenmhundefined
                mendenmh
                last edited by

                The probe not being pushed all the way on the touch means you may have set your probe offset wrong. The printer will give up probing if it has to go below the programmed low limit on z. If you are zeroed just about where the probe would switch, it might give up too early.

                Elliotundefined 2 Replies Last reply Reply Quote 0
                • Elliotundefined
                  Elliot @mendenmh
                  last edited by

                  @mendenmh When i home all axis it works perfectly. However, when I try to probe for mesh bed that's when I get an issue

                  1 Reply Last reply Reply Quote 0
                  • Elliotundefined
                    Elliot
                    last edited by

                    Dont know if it is also related, I have seen two different lines for M558 which one is correct and what does the 'H','R', 'A', and 'B' stand for?

                    M558 P9 H9 F120 R0.2 T18000

                    M558 P9 F100 H5 R0.2 T6000 A5 B1

                    1 Reply Last reply Reply Quote 0
                    • aidarundefined
                      aidar
                      last edited by

                      Looks like you should start reading here : https://duet3d.dozuki.com/Wiki/Gcode#Section_M558_Set_Z_probe_type

                      1 Reply Last reply Reply Quote 1
                      • Elliotundefined
                        Elliot @mendenmh
                        last edited by

                        @mendenmh Thanks. How would I go about changing this?

                        1 Reply Last reply Reply Quote 0
                        • aidarundefined
                          aidar
                          last edited by

                          Some more reading will help: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

                          Elliotundefined 1 Reply Last reply Reply Quote 0
                          • Elliotundefined
                            Elliot @aidar
                            last edited by

                            @aidar thanks. It is always good to refresh myself on that. That helped alot.

                            The one remaining issue I have is that the probe goes down on the first location on the bed. Then it goes to the next, and deploys the probe it then doesn't retract. It will then just go to the positions and not try to probe. It then gets an error. If I manually lift the probe after it then goes to the next location and the same thing happens.

                            After this is done, the bed is not leveled at all.

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

                              What are you using for your M558 right now?
                              Do you get any error messages in the console?

                              Z-Bot CoreXY Build | Thingiverse Profile

                              Elliotundefined 1 Reply Last reply Reply Quote 0
                              • Elliotundefined
                                Elliot @Phaedrux
                                last edited by

                                @Phaedrux

                                The M558 I. Am using is:

                                M558 P9 H5 F120 R0.2 T3000

                                The error I get is:

                                Error: Z probe already triggered at start of probing move

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

                                  1. What do you have in your deployprobe.g and retractprobe.g files?
                                  2. Please confirm that you have none of the following commands in any of your homing files or in bed.g:

                                  M98 Pdeployprobe.g
                                  M98 Pretractprobe.g
                                  M401
                                  M402

                                  You can send M401 and M402 manually to test whether probe deployment and retraction is working, but you should always start with the probe retracted before running a command that does probing.

                                  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

                                  Elliotundefined 1 Reply Last reply Reply Quote 1
                                  • Elliotundefined
                                    Elliot @dc42
                                    last edited by

                                    @dc42 Thanks. All worked out in the end.

                                    Seems there was something physically wrong with my bltouch.

                                    when testing it out a few days ago it didn't retract properly and got bent. I rebent it and now everything works perfectly. must have been stuck inside and this unstuck it.

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