Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Homing Issues

    Duet Hardware and wiring
    3
    29
    2357
    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.
    • Hal
      Hal last edited by Hal

      Pulling my hair out over homing.

      I have each individual home button working I think, but homeall.g seems to be giving me a ton of headache.

      when I try to use the homeall button my x and my y home and seem to work, but after my Z homes I get this error:

      0_1528854543777_g28 fail.PNG

      Here are my g files:

      ; Configuration file for Duet WiFi (firmware version 1.20 or newer)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool on Mon Jun 11 2018 01:19:12 GMT-0400 (Eastern Daylight Time)
      
      ; General preferences
      G90                            ; Send absolute coordinates...
      M83                            ; ...but relative extruder moves
      
      ; Network
      M550 PBob 1                    ; Set machine name
      M552 S0
      M587 S"network" P"password"
      M552 S1
      
      ; Drives
      M569 P0 S0                     ; Drive 0 goes forwards
      M569 P1 S1                     ; Drive 1 goes forwards
      M569 P2 S0                     ; Drive 2 goes forwards
      M569 P3 S1                     ; Drive 3 goes forwards
      M350 X16 Y16 Z16 E16 I1        ; Configure microstepping with interpolation
      M92 X80 Y80 Z4000 E418.45      ; Set steps per mm
      M566 X900 Y900 Z12 E120        ; Set maximum instantaneous speed changes (mm/min)
      M203 X6000 Y6000 Z180 E1200    ; Set maximum speeds (mm/min)
      M201 X500 Y20 Z250 E250        ; Set accelerations (mm/s^2)
      M906 X900 Y900 Z1200 E800 I30   ; Set motor currents (mA) and motor idle factor in per cent
      M84 S30                        ; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1               ; Set axis minima
      M208 X300 Y300 Z400 S0         ; Set axis maxima
      
      ; Endstops
      M574 X1 Y1 Z0 S0                  ; Set active high endstops
      
      ; ** BLTouch
      ;
      M307 H3 A-1 C-1 D-1               ; disable heater 3, BLTouch - servo pulse on heater 3 pin (expansion 8)
      M558 P9 X0 Y0 Z1 H5 F200 T5000 	        ; Type 5 for BLTouch (Normally closed switch on Z-probe inputs)
      G31 X0 Y0.0 Z0 P5 	  ; Z=trigger height, P=trigger value, not needed for contact probe, X/Y 
                                        ; distance from nozzle
      ;
      
      ; Heaters
      M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
      M143 H0 S120                   ; Set temperature limit for heater 0 to 120C
      M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
      M143 H1 S280                   ; Set temperature limit for heater 1 to 280C
      
      ; Fans
      M106 P0 S0.3 I0 F500 H-1       ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
      M106 P1 S1 I0 F500 H1 T45      ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
      M106 P2 S1 I0 F500 H1 T45      ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on
      
      ; Tools
      M563 P0 D0 H1                  ; Define tool 0
      G10 P0 X0 Y0 Z0                ; Set tool 0 axis offsets
      G10 P0 R0 S0                   ; Set initial tool 0 active and standby temperatures to 0C
      
      ; Automatic saving after power loss is not enabled
      
      ; Custom settings are not configured
      

      bed.g:

      ; bed.g
      ; called to perform automatic bed compensation via G32
      
      G28 ; home all
      G91 ; relative mode
      G1 Z5 F2000 ; move Z 4mm for clearance
      G90 ;absolute mode
      M401 ; In lieu of macro - call GCode for deploy probe
      M557 X10:270 Y10:270 S40 ; probe every 40mm from 10 to 270 in X and Y
      G29 ; run auto bed mesh level
      M402 ; In lieu of macro - call GCode to retract probe
      G1 X10 Y10 Z10 F5000
      

      Homex.g

      ; homex.g
      ; called to home the X axis
      ;
      ; Bed down a bit relative to current position
      G91 ; relative mode
      G1 Z4 S2 F200 ; raise head to avoid dragging nozzle over the bed
      G1 X-300 F3000 S1 ; move up to 240mm in the -X direction, stopping if the homing switch is triggered
      G1 X4 F600 ; move slowly 4mm in the +X direction
      G1 X-10 S1 ; move slowly 10mm in the -X direction, stopping at the homing switch
      G1 Z-4 S2 F200 ; lower the head again
      G90 ; back to absolute mode
      

      Homey.g

      ; homey.g
      ; called to home the Y axis
      
      ; Bed down a bit relative to current position
      G91 ; relative mode
      G1 Z4 S2 F200 ; raise head to avoid dragging nozzle over the bed
      G1 Y-300 F3000 S1 ; move up to 240mm in the -X direction, stopping if the homing switch is triggered
      G1 Y4 F600 ; move slowly 4mm in the +X direction
      G1 Y-10 S1 ; move slowly 10mm in the -X direction, stopping at the homing switch
      G1 Z-4 S2 F200 ; lower the head again
      G90 ; back to absolute mode
      

      Homez.g

      ; homez.g
      ; called to home the Z axis
      ;
      G91
      G1 X150 Y150
      G90
      G30 X150 Y150; Do a single probe to home our Z axis
      G90 ; Make sure we are in absolute mode
      

      Homeall.g

      ; homeall.g
      ; called to home all axes
      ;
      G28 X ;home x
      G28 Y ;home y
      G91
      G1 X150 Y150
      G90
      G30 X150 Y150; Do a single probe to home our Z axis
      G90 ; Make sure we are in absolute mode
      

      Why can I not home with Homeall,g? any help would be appreciated.

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

        @hal said in Homing Issues:

        In homez.g and homeall.g, instead of this:

        G91
        G1 X150 Y150
        G90
        G30 X150 Y150; Do a single probe to home our Z axis
        G90 ; Make sure we are in absolute mode

        use this:

        G90
        G1 X150 Y150 F6000
        G30 ; Do a single probe to home our Z axis

        Adjust the F parameter on the G1 command to a speed suitable for your printer.

        1 Reply Last reply Reply Quote 0
        • Hal
          Hal last edited by

          @dc42 said in Homing Issues:

          G90
          G1 X150 Y150 F6000
          G30 ; Do a single probe to home our Z axis

          With this update I still get the same error after Home All is acomplished or Home Z.

          Thanks

          1 Reply Last reply Reply Quote 0
          • Hal
            Hal last edited by

            Any reason the BLTouch would cause this error? I am also wondering if the feed rate is to high will it cause this to happen?

            anyways any suggestions are welcome

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

              The trigger value in your G31 command is very low. Try 50 instead of 5.

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

                @phaedrux said in Homing Issues:

                The trigger value in your G31 command is very low. Try 50 instead of 5.

                So I have been setting my Z-trigger to do my Z-offset, I read that this is how the z-offset is defined?

                If it is not then how is Z-offset set with the BLTouch?

                I also see that I have these Errors (See below):

                Error: Invalid Servo Index 0 in M280 command

                Error: Homing failed

                Error: G29: No Valid grid defined for be probing

                These may be caused by all of the same thing, but I am not sure.

                Any help would be appreciated, es[ecially for setting Z-Offset so I can fix these errors.

                Thanks.

                1 Reply Last reply Reply Quote 0
                • Hal
                  Hal last edited by

                  Just tried P50 and P80 to no avail. I still get the Z homing error.

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

                    @hal said in Homing Issues:

                    G31 X0 Y0.0 Z0 P5

                    The X and Y values should be the distance from the BLTouch pin to the nozzle.

                    The Z value will need to be measured with a G30 S-1 command. I'll link to a tutorial on how to get that setup.

                    The P value is the trigger value. 5 is very low. I use 50 for the BLTouch.

                    The invalid servo index means something is wrong either with the M558 command and how you have things wired, or the command is wrong in your deployprobe.g and retractprobe.g macros.

                    Can you post those macros from the system folder?

                    Can you describe how you have the BLTouch wired up?

                    Does the BLTouch pin deploy and retract?

                    https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

                    https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/

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

                      @phaedrux said in Homing Issues:

                      @hal said in Homing Issues:

                      G31 X0 Y0.0 Z0 P5

                      The X and Y values should be the distance from the BLTouch pin to the nozzle.

                      The Z value will need to be measured with a G30 S-1 command. I'll link to a tutorial on how to get that setup.

                      The P value is the trigger value. 5 is very low. I use 50 for the BLTouch.

                      The invalid servo index means something is wrong either with the M558 command and how you have things wired, or the command is wrong in your deployprobe.g and retractprobe.g macros.

                      Can you post those macros from the system folder?

                      Can you describe how you have the BLTouch wired up?

                      Does the BLTouch pin deploy and retract?

                      https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

                      https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/

                      By the way thank you for helping me out and giving me suggestions.

                      I did try you suggestion of adjusting the trigger level and still had the error.

                      Yes my BLtouch deploys and retracts. I have been able to use the BLtouch with the Auto bed compensation button above the homing buttons, and it seems to work fine.

                      So it kinda leaves the software as the culprit.

                      M280 P3 S10 I1 is all I have in my deployprobe.g **I should also note that I do not call these macros anywhere I use the M401 and M402 commands instead.

                      M280 P3 S90 I1 Retractprobe.g

                      I followed the wiring guide from here:

                      http://www.folgerforum.com/t/walter-s-modifications-part-3-the-duet/1582

                      Thanks

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

                        @hal M401 and M402 actually just call those macros, with the added benefit of letting the system keep track of the deployed and retracted state.
                        G30 calls the same macros to deploy and retract as well when doing a probe point.

                        It's possible that you have it wired in such a way that you must invert the signal for the servo. Try adding I1 to the M558 command in config.g, or removing the I1 from the M280 commands in the deploy and retract.

                        Can you repost what your homeall.g looks like now?

                        1 Reply Last reply Reply Quote 0
                        • Hal
                          Hal last edited by

                          Okay so I removed the I1 from the deploy and retract and my bed almost rammed into my Build Plate. Thank goodness for emergency stop.

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

                            Oh no! Sorry. I should have maybe mentioned that it's a good idea to test the BLTouch a good distance above the bed and manually trigger the pin by hand before it even gets close to the bed until you are sure it's working properly.

                            If it makes you feel any better I just did this tonight... 🤕

                            0_1529039456067_IMG_1539.jpeg

                            Caught the deployed pin on the end of the bed. The bed didn't drop before homeing Z because I mistakenly used M92 Z0 in a macro instead of G92 Z0. Instead of setting current height as Z=0 it set the z steps per mm to 0. No wonder the bed didn't drop. Oi.

                            1 Reply Last reply Reply Quote 0
                            • Hal
                              Hal last edited by

                              It is all good I caught it before it even touched the bed. So I do not believe that I am Not Not inverted.

                              goodness I am not sure what this is.

                              Here is my homeall.g:

                              G28 X ;home x
                              G28 Y ;home y
                              G90
                              G1 X150 Y150 F4000
                              G30 ; Do a single probe to home our Z axis
                              
                              1 Reply Last reply Reply Quote 0
                              • Phaedrux
                                Phaedrux Moderator last edited by

                                What happens if you manually issue a G30 command?

                                1 Reply Last reply Reply Quote 0
                                • Hal
                                  Hal last edited by

                                  Probe deploys, bed moves up, hits probe, the probe retracts, then the z axis moves down a few mm for clearance. I believe this is the correct process.

                                  I did have to home x and y before I could issue the G30 command

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

                                    But you still get a homing failed error along with the servo error?

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

                                      @phaedrux said in Homing Issues:

                                      But you still get a homing failed error along with the servo error?

                                      Funny enough I did not, and i only get the servo error if i try to print.

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

                                        Are you manually calling M401 and M402 anywhere?

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

                                          Actually, now that you mention it, I was getting some servo error messages yesterday when I was testing stall detection as a z probe. I had commented out all of the M280 servo commands but I was still getting an error message occasionally. I didn't really think much of it. I looked for other M280 commands I might have forgotten but there were none.

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

                                            @phaedrux said in Homing Issues:

                                            Are you manually calling M401 and M402 anywhere?

                                            Yes in my bed.g file

                                            1 Reply Last reply Reply Quote 0
                                            • Hal
                                              Hal last edited by Hal

                                              Well I figured out the M280 command error, it seems like I set my S3D to use P0 instead of P3, so made the change and boom no more M280 error.

                                              I am still getting the homing errors and the M29 error.

                                              maybe those errors are also causing my other errors, so here is my s3d start and stop process.

                                              start gcode from s3d

                                              M280 P3 S160 ; BLTouch alarm release
                                              G4 P100 ; delay for BLTouch
                                              G28 ; home
                                              G29 ; auto bed leveling
                                              G1 X0 Y5 Z0.2 F3000 ; get ready to prime
                                              G92 E0 ; reset extrusion distance
                                              G1 X250 E20 F600 ; prime nozzl
                                              

                                              end gcode from s3d

                                              M104 S0 ; turn off extruder
                                              M140 S0 ; turn off bed
                                              G28 X Y ; home x and y axes
                                              M84 ; disable motors
                                              

                                              thanks for any help.

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

                                                The M29 error is probably from having too many points in the grid. Try a higher s value and see if it will let you run it.

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

                                                  Actually it looks like you haven't defined a mesh grid in your config.

                                                  1 Reply Last reply Reply Quote 0
                                                  • Hal
                                                    Hal last edited by Hal

                                                    should I even have that much in here as the Bed.g file should be called, or is that invoked from S3d?

                                                    1 Reply Last reply Reply Quote 0
                                                    • Hal
                                                      Hal last edited by

                                                      alright down to 1 error homing error is still happening but auto bed leveling is running as expected.

                                                      I invoked the Bed.g file using M32 command.

                                                      maybe my issue is in the bed.g file now.

                                                      Thanks

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