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

    unusual/unnerving noises + error codes

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    6
    76
    4.2k
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      @Phaedrux said in unusual/unnerving noises + error codes:

      config.json

      You might have to right click and save as and rename it config.json. I just tested it and it works.

      the only thing I changed was the board type, the firmware version, and the bltouch, plus a few other minor things.

      Z-Bot CoreXY Build | Thingiverse Profile

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

        @Phaedrux So i have not uploaded this why is great. however when just trying to home the x axis. it keeps eratically shaking and throwing out these error codes. I have looked for the G1 code but it only seems to be on the tool section of the config.g so im now confused again.

        Can you help?

        Warning: Obsolete use of S parameter on G1 command. Use H parameter instead.

        G28 X Warning: Obsolete use of S parameter on G1 command. Use H parameter instead.

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

          @PR1OR check your homing files and everywhere the G1 command uses an S command e.g.

          G1 S1 X-500
          

          change it to H

          G1 H1 X-500
          

          Check your homeall.g, homex.g, homey.g and homez.g

          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

          PR1ORundefined 1 Reply Last reply Reply Quote 1
          • PR1ORundefined
            PR1OR @jay_s_uk
            last edited by

            @jay_s_uk said in unusual/unnerving noises + error codes:

            here the G1

            this has removed this message. thanks!

            now it just shakes still for a while then gives me this

            G28 X
            Error: Homing failed

            PR1ORundefined 1 Reply Last reply Reply Quote 0
            • PR1ORundefined
              PR1OR @PR1OR
              last edited by

              if i try and home all i get the same weird shaking on the X and Y axis the Z doesnt move and i eventually get this error message

              G28
              Error: G0/G1: insufficient axes homed

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

                i would suggest looking at your wiring for the x axis motor then.
                My guess is you have some of the cables mixed up.
                I would suggest reading this https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Connecting_stepper_motors

                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

                PR1ORundefined 1 Reply Last reply Reply Quote 1
                • PR1ORundefined
                  PR1OR @jay_s_uk
                  last edited by

                  @jay_s_uk So after following the link i can confirm that all motors are connected correctly now and sound alot better. Now to the end stops + Probe.

                  Obviously at the moment i still cant home the axis (X and Y) because the end stops seem to not be working. Ive done some reading and found that M574 give a status, which is below. However when putting the gcode in it send a message saying 'Response too long see console'

                  m574
                  

                  Endstop configuration:
                  X: low end motor stall (any motor)
                  Y: low end motor stall (any motor)
                  Z: low end Z probe

                  any ideas?

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

                    can you post your latest config.g?
                    That response seems to indicate that you're trying to use stall detection rather than an actual endstop

                    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

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

                      @PR1OR said in unusual/unnerving noises + error codes:

                      'Response too long see console'

                      And if you go to the console do you see the result?

                      How do you have the endstops wired? The two wires from the endstops should be connected to the outer two pins of the board connector. Doesn't really matter which wire goes where.

                      https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+1:+Wiring/37#s119

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • PR1ORundefined
                        PR1OR
                        last edited by

                        ![0_1600205801008_IMG_1528.JPEG](Uploading 100%) @Phaedrux said in unusual/unnerving noises + error codes:

                        w do you have the endstops wired

                        so that was the result :s

                        Screenshot 2020-09-15 at 22.33.45.png

                        Below is a picture of the wiring, ive been using dupont wire until ive made sure they are wired correctly. but from what you are saying the seem to be fine. The LEDs are on (green, i read somewhere they should be red but i assume this was an old/new board) when the the endstop switch isnt pressed. When it is it turns off. So i found from wiring diagram that the LEDs didnt correspond to the plugs like it does in the diagram

                        Untitled.png

                        PR1ORundefined 1 Reply Last reply Reply Quote 0
                        • PR1ORundefined
                          PR1OR @PR1OR
                          last edited by

                          just had a thought and checked the axis limits as the ender 3 pro has a bigger print area. i have now updated that but still having issues

                          PR1ORundefined 1 Reply Last reply Reply Quote 0
                          • PR1ORundefined
                            PR1OR @PR1OR
                            last edited by

                            could it be something to do with the gcodes for the end stops?

                            Like the changing S to H?

                            ; Endstops
                            M574 X1 Y1 S3 ; set endstops controlled by motor stall detection
                            M574 Z1 S2 ; set endstops controlled by probe

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

                              @PR1OR said in unusual/unnerving noises + error codes:

                              ; Endstops
                              M574 X1 Y1 S3 ; set endstops controlled by motor stall detection

                              S3 is stall detection. Try S1.

                              Z-Bot CoreXY Build | Thingiverse Profile

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

                                @Phaedrux updated to S1 and i got this

                                G28
                                Error: Failed to enable endstops

                                1 Reply Last reply Reply Quote 0
                                • PR1ORundefined
                                  PR1OR
                                  last edited by

                                  however i played with it a little and S2 works but it only moves each axis by a couple of mm before stoping

                                  but it does say its homed which i think is getting somewhere

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

                                    ; Endstops
                                    M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
                                    M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop

                                    Try that instead

                                    It looks like you had stall detection for homing selected in the configurator so it didn't have any endstop switches defined.

                                    Z-Bot CoreXY Build | Thingiverse Profile

                                    PR1ORundefined 1 Reply Last reply Reply Quote 0
                                    • ziggymanpopoundefined
                                      ziggymanpopo
                                      last edited by

                                      From what i seen in the video im wondering are you sure the z stepper is wired correctly
                                      It sounds like one of the steppers is not paired properly y moves then x .... does it start the noise before it hits the x stop?? If so you wont know the z is correct untill it hits the x stop if the shaking starts then ...when you hit the xstop i would say the z stepper is causing the problem with the strpper fighting itself... i noticed that the x gantry didnt start down. It might be the video. Or just me 😁 ill watch it again

                                      PR1ORundefined 1 Reply Last reply Reply Quote 0
                                      • ziggymanpopoundefined
                                        ziggymanpopo
                                        last edited by

                                        What i do is start homming then manualy trip the limit to see if it in fact work.. just cause the led goes out doent mean the g code responded

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

                                          @Phaedrux said in unusual/unnerving noises + error codes:

                                          ; Endstops
                                          M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
                                          M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop

                                          Perfect thank you!! this has worked!! i can now home my X and Y axis

                                          is there anything for the Z probe though?

                                          i get this as a return when homing all

                                          Error: in file macro line 9: G30: Z probe 0 not found
                                          Error: Homing failed

                                          1 Reply Last reply Reply Quote 0
                                          • PR1ORundefined
                                            PR1OR @ziggymanpopo
                                            last edited by

                                            @ziggymanpopo

                                            So it was as Phaedrux had said above the code wasnt correct. Once id checked/sorted the wiring out it was only happening when both X and Y got to the end stop

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