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

    Initial Homing issues - Sequence of Errors

    Scheduled Pinned Locked Moved
    General Discussion
    6
    49
    2.5k
    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.
    • Vetiundefined
      Veti
      last edited by

      @b0m0a0k said in Initial Homing issues - Sequence of Errors:

      "M119 Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped"

      so none of your endstops are working?

      B0M0A0Kundefined 1 Reply Last reply Reply Quote 0
      • B0M0A0Kundefined
        B0M0A0K @Veti
        last edited by

        @veti I thought that "Not Stopped" meant they had not been triggered, certainly when I manually trigger then one at a time the corresponding light comes on on the board.

        ----------------------------------------------
        No fate but what we make ....
        1 Reply Last reply Reply Quote 0
        • A Former User?
          A Former User
          last edited by

          "not stopped" is the current status, if you run M119 while triggered, the output text will change. But if the leds work, then M119 should reflect the same state.

          Thats one step closer at least 👍

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

            so if the y endstop is working why exactly did the y home fail?

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

              please post your config and all homing files.

              B0M0A0Kundefined 1 Reply Last reply Reply Quote 0
              • B0M0A0Kundefined
                B0M0A0K @Veti
                last edited by

                @veti I think that was because of a failed Molex connection. I have repaired that now but am still trying to get homing to work. Am working my way through dc42's suggested reading.

                ----------------------------------------------
                No fate but what we make ....
                1 Reply Last reply Reply Quote 0
                • B0M0A0Kundefined
                  B0M0A0K @Veti
                  last edited by

                  @veti Hi, OK, got the files you requested but have removed the passwords from the config.g file.[0_1559075082911_Bart Config Files.zip](Uploading 100%) 0_1559075101598_config.g 0_1559075107396_homeall.g 0_1559075113958_homex.g 0_1559075118078_homey.g 0_1559075123270_homez.g

                  I hope this is how you attach the files. It wouldn't let me attached a .zip

                  ----------------------------------------------
                  No fate but what we make ....
                  1 Reply Last reply Reply Quote 0
                  • B0M0A0Kundefined
                    B0M0A0K
                    last edited by

                    A little progress here.

                    Using the information on the "Test_axes_or_motors_individually" I can confirm that the extruder can be moved through all planes and in the amounts specified via direct gcode entry. However, when I try anything in the main "Machine Control" section I still get the "G0/G1 Insufficient Axes homed".

                    ----------------------------------------------
                    No fate but what we make ....
                    1 Reply Last reply Reply Quote 0
                    • A Former User?
                      A Former User
                      last edited by

                      unless you explicitly allow moving without homing, you need to press home all before jogging the axes

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

                        Perhaps this guide would help with testing things

                        https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39

                        It's written for the Ender 3 but the methods would apply to any printer.

                        Z-Bot CoreXY Build | Thingiverse Profile

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

                          Your homing files need to be modified slightly to allow it to raise the Z axis before the homing moves.

                          For instance, your homez

                          G91                ; relative mode
                          G1 Z4 F200         ; raise head 4mm to ensure it is above the Z probe trigger height
                          G1 Z-210 F200 S1   ; move down to 210mm in the -Z direction, stopping if the homing switch is triggered
                          G90  
                          

                          Would become

                          G91                ; relative mode
                          G1 Z4 F200 S2        ; raise head 4mm to ensure it is above the Z probe trigger height
                          G1 Z-210 F200 S1   ; move down to 210mm in the -Z direction, stopping if the homing switch is triggered
                          G90   
                          

                          Notice the S2 on the first Z move to raise it. The S2 allows the axis to move before it is homed. The S1 after that is the move to the endstop.

                          The same thing would need to be changed in your other homing files. The first Z move needs the S2 switch.

                          Z-Bot CoreXY Build | Thingiverse Profile

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

                            It may be worth going through the Reprap configurator on your own and trying to input the values using this config as an example. The configs you got for the Wanhao may be for a much older version of the firmware.

                            Z-Bot CoreXY Build | Thingiverse Profile

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

                              @phaedrux said in Initial Homing issues - Sequence of Errors:

                              It may be worth going through the Reprap configurator on your own and trying to input the values using this config as an example. The configs you got for the Wanhao may be for a much older version of the firmware.

                              I tend to agree with you on this. There appear to be differences in the configuration that may be based on what version of the i3 you are using.

                              Prior to starting this upgrade I installed Repetier-Host and took screenshots of the EEPROM from my Melzi board. I have seen other examples of this that feature some differences in settings. I think this is linked to the version of the i3 and where Wanhao tweaked the config.

                              The big issue I have in running through the RepRap configurator from scratch is that I just can't seem to reconcile some of the settings it's asking for with what I have in the screenshots from my printer as it was working with the Melzi board. An example of this would be the "Max. Speed Change" setting. There isn't anything in the EEPROM that seems to match that and I don't know enough about these settings (Yet!) to make an educated guess as to whether it is safe to leave the setting at it's default on the Configurator page.

                              The Ender 3 article is a big help in just checking basic functionality and I will run through this again this evening once I am back in front of my printer.

                              At the heart of this I think is my misinterpretation of what I was seeing on the Duet Web Control screen. I thought that clicking on the "Home" buttons would perform the action needed and enter that into the config. I did not realize that I needed to have set the Gcode instruction (for whichever axes I was looking at) prior to this.

                              As a complete newbie with GCode and the Duet3D WiFi board it's all new to me. I have an inherent dislike of making assumptions so tend to grind to a halt when I don't understand something.

                              Again, I am very grateful to all here who are trying to help out. I am making progress and don't think I am too far away from completion of this upgrade.

                              0_1559126942952_Printer Information - EEPROM Settings-1.png 0_1559126948362_Printer Information - EEPROM Settings-2.png

                              ----------------------------------------------
                              No fate but what we make ....
                              Phaedruxundefined dc42undefined 2 Replies Last reply Reply Quote 0
                              • Phaedruxundefined
                                Phaedrux Moderator @B0M0A0K
                                last edited by

                                @b0m0a0k said in Initial Homing issues - Sequence of Errors:

                                Max. Speed Change

                                This refers to jerk.

                                Z-Bot CoreXY Build | Thingiverse Profile

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

                                  @b0m0a0k said in Initial Homing issues - Sequence of Errors:

                                  At the heart of this I think is my misinterpretation of what I was seeing on the Duet Web Control screen. I thought that clicking on the "Home" buttons would perform the action needed and enter that into the config. I did not realize that I needed to have set the Gcode instruction (for whichever axes I was looking at) prior to this.

                                  The configurator will generate the GCode instructions in the homex.g, homey.g, homez.g and homeall.g files for you, but they will obviously only be correct if you enter the correct information in the Endstops page of the configurator. Also you should test that the motors move in the correct directions before you test homing.

                                  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

                                  B0M0A0Kundefined 1 Reply Last reply Reply Quote 0
                                  • B0M0A0Kundefined
                                    B0M0A0K @dc42
                                    last edited by

                                    @dc42 Thanks again for taking the time to reply. I ran through the commissioning guide you pointed me to and confirmed that just about everything is working with the exception of testing homing. I am focused on getting Home X working first. When I click on Home X the print head moves towards the stopswitch, but stops before it get's there (it moves about 80mm to the left).

                                    ----------------------------------------------
                                    No fate but what we make ....
                                    A Former User? dc42undefined 2 Replies Last reply Reply Quote 0
                                    • B0M0A0Kundefined
                                      B0M0A0K @Phaedrux
                                      last edited by

                                      @phaedrux Thank you!

                                      ----------------------------------------------
                                      No fate but what we make ....
                                      1 Reply Last reply Reply Quote 0
                                      • A Former User?
                                        A Former User @B0M0A0K
                                        last edited by

                                        @b0m0a0k said in Initial Homing issues - Sequence of Errors:

                                        When I click on Home X the print head moves towards the stopswitch, but stops before it get's there (it moves about 80mm to the left).

                                        you need to increase the travel distance in the home file.

                                        it probably reads something like G1 X80 S1change the X80 part to match the length of your X axis + a little extra. (Possibly G0 instead of G1, makes no difference)

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

                                          @b0m0a0k said in Initial Homing issues - Sequence of Errors:

                                          @dc42 Thanks again for taking the time to reply. I ran through the commissioning guide you pointed me to and confirmed that just about everything is working with the exception of testing homing. I am focused on getting Home X working first. When I click on Home X the print head moves towards the stopswitch, but stops before it get's there (it moves about 80mm to the left).

                                          That could be caused by a few different things:

                                          1. In the configurator you specified that the size of your printer was much smaller than it actually is. Send M208 from the console and check that the reported min/max axis limits look right.

                                          2. You have specified the incorrect steps/mm, so that the motor is not moving as much as it should. Use G91 then G1 S2 moves to check that the motors are moving the right amount. For example, when you send G1 S2 X50 F1000 check that the amount of movement is 50mm.

                                          3. You are getting interference on the endstop wires, or you have a bad connection in one of them. This is uncommon, but possible if you have the endstop wires running right next to stepper motor wires over a considerable distance.

                                          Please post your config.g, homex.g, homey.g, homex.g and homeall.g files.

                                          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

                                          B0M0A0Kundefined 1 Reply Last reply Reply Quote 0
                                          • B0M0A0Kundefined
                                            B0M0A0K @dc42
                                            last edited by

                                            @dc42 I will get back to this tonight and post the requested files. Thanks.

                                            ----------------------------------------------
                                            No fate but what we make ....
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA