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

    Z axis makes loud noise and wont move

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    6
    16
    731
    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.
    • Jasonpgrundefined
      Jasonpgr @dc42
      last edited by

      @dc42 The printer was working just fine before installing the new firmware. So I don't belive it is a phase issue. Should it does sound similar. The grinding is probably just the machine vibrating as the motors shake/stall or something.

      Do all the speeds and accelerations and everything look correct? Is there another config or setting file that could be conflicting somehow?

      SIamundefined 1 Reply Last reply Reply Quote 0
      • SIamundefined
        SIam @Jasonpgr
        last edited by

        @jasonpgr I don't think that this solves your problem, but the following things makes the config file clean

        This you can remove

        M350 I0 ; Configure microstepping without interpolation
        

        Here you have defined two extruders, but you don't have a second tool in your config defined

        M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
        M92 X100 Y100 Z1500 E418:418 ; Set steps per mm
        M566 X800 Y800 Z30 E100:100 ; Set maximum instantaneous speed changes (mm/min)
        M203 X10000 Y10000 Z300 E1200:1200 ; Set maximum speeds (mm/min)
        M201 X1000 Y1000 Z50 E250:250 ; Set accelerations (mm/s^2)
        M906 X1100 Y1100 Z1400 E800:800 I60 ; Set motor currents (mA) and motor idle factor in per cent
        

        Here I would say remove the second E Values or define a second tool

        I can't find further Errors so far, did you have your old config.g file ? If yes, can you post it here?

        Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
        Duet WiFi 1.02 or later + DueX5
        RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
        Duet WiFi Server: 1.26
        Duet Web Control 3.4.0beta4 (2021-09-27)

        1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @Jasonpgr
          last edited by

          @jasonpgr said in Z axis makes loud noise and wont move:

          M587 S"Jason-home" P"3382Rockwood" ; Configure access point. You can delete this line once connected

          you shouldn't include the above in your firmware as it will get written to the ESP on every boot and wear the flash out.

          What firmware are you running? post the output of M115

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          Jasonpgrundefined 1 Reply Last reply Reply Quote 0
          • Jasonpgrundefined
            Jasonpgr @jay_s_uk
            last edited by

            @jay_s_uk

            FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.0(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-06-05b3

            As for the M587 line, would it be better to comment it out using ; before the M587 part, or should I delete the line all together? I don't want to lose information I might need for trouble shooting later if I don't need to.

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @Jasonpgr
              last edited by

              @jasonpgr it's your WiFi details so just delete it.

              And really, I recommend if you're starting a rebuild to move up to version 3.3.
              If you'd rather not do that then I recommend at least upgrading to 2.05.1

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              Jasonpgrundefined 1 Reply Last reply Reply Quote 0
              • Jasonpgrundefined
                Jasonpgr @jay_s_uk
                last edited by

                @jay_s_uk
                I just did a firmware upgrade last month, and I'm still trying to get it all back up and working again since then. Did I not use the latest version? That's a little frustrating, but it seems like it's going to be the best route. Guess I'll be doing a whole new upgrade tonight.

                jay_s_ukundefined 1 Reply Last reply Reply Quote 1
                • jay_s_ukundefined
                  jay_s_uk @Jasonpgr
                  last edited by

                  @jasonpgr I think 2.0 is from around the time I got into using RRF (about 2 1/2 years ago).
                  If you do for for 3.3, I would go the route of generating a new set of config files using the config tool rather than trying to adjust yours to suit.
                  Always worth reading the release notes too

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  Jasonpgrundefined 1 Reply Last reply Reply Quote 0
                  • Jasonpgrundefined
                    Jasonpgr @jay_s_uk
                    last edited by

                    @jay_s_uk

                    Yeah. You're definitely right about that. I really struggle with the gcode and programming of stuff, so I've been putting it off again and again. I'm also guessing my firmware upgrade from a few months ago didn't work if it's a version that old.

                    Well, I'll take some good notes from my old config file, and see if I can't get it going from scratch. Probably the best thing in the long run anyway.

                    Stand by for a bunch of panicked posts from me over the next couple weeks asking questions with very obvious answers I've managed to overlook.

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

                      If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 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 RRF3. 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

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

                        @phaedrux
                        Thanks for the step by step, I really appreciate it. I have the firmware all updated I believe, and I'm working on the config tool now. I think I've got all the parameters entered correctly, except for some about the probe/z endstop under the io section. You can see the post I made last night with a screenshot of the part of the config I'm talking about.

                        https://forum.duet3d.com/topic/23842/config-tool-question

                        1 Reply Last reply Reply Quote 0
                        • Jasonpgrundefined
                          Jasonpgr
                          last edited by

                          Sooooo I'm super dumb. I finally got around to trying to troubleshoot this problem again, and it looks like the cat had chewed through one of the wires going to one of the Z stepper motors..... Soooooo all that frustration took 30 seconds and one drop of solder to fix. At least I have an upgraded set of firmware at least I guess.

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