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

    Homing problem Ender 3 pro

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    22
    498
    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.
    • rjenkinsgbundefined
      rjenkinsgb @Roeland
      last edited by

      @roeland said in Homing problem Ender 3 pro:

      without using ''M564 H0'' it just says ''G0/G1 insufficient axes homed''

      Sorry, I meant the "machine properties" display like you posted a few hours ago, but with the machine turned on while the axes are already away from the endstops & without trying to move or home anything?

      Robert J.

      Printers: Overlord pro, Kossel XL+ with Duet 6HC and "Frankentron", TronXY X5SA Pro converted to E3D toolchange with Duet 6HC and 1LC toolboards.

      Roelandundefined 1 Reply Last reply Reply Quote 0
      • Roelandundefined
        Roeland @rjenkinsgb
        last edited by

        @rjenkinsgb When the machine is turned on while the axes are already away from the endstops it gives the status "no" for all the axes that are away from the endstop.

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

          Your firmware is quite out of date. I suggest you update to at least 2.05

          Download this zip file, and then upload it as is to the system page in DWC.

          https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip

          I think this will solve the G0/G1 error. I think it's because your hoiming files are using modern syntax G1 H moves but your old firmware only knows G1 S moves for homing.

          Z-Bot CoreXY Build | Thingiverse Profile

          Roelandundefined 1 Reply Last reply Reply Quote 1
          • Roelandundefined
            Roeland @Phaedrux
            last edited by

            @phaedrux Thanks! that fixed it. But it went a bit troublesome. I got back from work and wanted to update my firmware but it kept disconnecting from my wifi. while nothing has changed with the wifi in the meantime. after several times trying to upload the software it finally succeeded. but now there is some trouble with the wifi..

            1 Reply Last reply Reply Quote 0
            • Roelandundefined Roeland has marked this topic as solved
            • Phaedruxundefined
              Phaedrux Moderator
              last edited by

              What is the trouble with the wifi exactly?

              Z-Bot CoreXY Build | Thingiverse Profile

              Roelandundefined 2 Replies Last reply Reply Quote 0
              • Roelandundefined
                Roeland @Phaedrux
                last edited by Roeland

                @phaedrux When starting up it first connects to wifi, after 20 seconds or 1 minute or so it disconnects en starts reconnecting. it reconnects en disconnects again. after a while it just says wifi module is idle.

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

                  @phaedrux I've only had this problem once befor when I first got the board about a year ago (it took a whille before I installed it on my ender), but somehowI made it work back then. And now it happens again.

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

                    Is you send M122 again what wifi server version is now installed?

                    You're still only running the latest RRF2 version after this update, there has been nearly 2 years of updates since then in RRF3 including with the wifi server firmware.

                    Now that we know your homing issue was a syntax issue and the printer seems to be otherwise working (wifi aside) I think it would be a good opportunity to complete the firmware upgrade process and get to 3.3

                    If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
                    https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
                    https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
                    https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
                    That will get your firmware and DWC up to date.

                    You can see the change logs here:
                    https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

                    For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
                    https://configtool.reprapfirmware.org/Start

                    Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

                    These documents will come in handy during the conversion.
                    https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
                    https://duet3d.dozuki.com/Wiki/Gcode

                    Z-Bot CoreXY Build | Thingiverse Profile

                    Roelandundefined 1 Reply Last reply Reply Quote 1
                    • Roelandundefined
                      Roeland @Phaedrux
                      last edited by

                      @phaedrux console.csv This is the response for M122IMG_20211118_201504[6481].jpg Picture of error. At this moment the wifi module has behaved for at least 10 minutes now. Maybe it was a temporary thing, but i still think it will be good to upgrade to RRF3

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

                        The M122 is too long to view entirely on the paneldue. You'd need to use a USB terminal to see the full response.

                        upgrading the firmware will also reflash the wifi firmware which may be enough to solve the problem as it is.

                        Z-Bot CoreXY Build | Thingiverse Profile

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

                          @phaedrux The install of RRF 3.0 was successful. and it homes as it should. The only problem I have right now is the setup of my thermistor. nozzle thermistor is n/a and bed thermistor thinks is is -273 C (almost 0 K).

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

                            Yes you'll need to go on to RRF 3.3 and get an up to date config file set from the online config tool as the syntax for setting up the hardware has changed compared to RRF2.

                            Z-Bot CoreXY Build | Thingiverse Profile

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

                              @phaedrux Uploaded the new config files, but didn't change anything, but the wrong series of thermistor was selected. It said B4032, but it was supposed to be B4700. It is fixed now. Also RRF 3.3 is successfully installed. Thank you very much!

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