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.
    • PR1ORundefined
      PR1OR @jay_s_uk
      last edited by

      @jay_s_uk Screenshot 2020-09-14 at 21.28.23.png

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

        Your config you posted is for firmware version 1.21 and your installed version is 3.11.
        First thing I would suggest you do is re do your config using the online configurator https://configtool.reprapfirmware.org/Start, ensuring that the firmware version selected is version 3.0 or later

        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 0
        • PR1ORundefined
          PR1OR @jay_s_uk
          last edited by

          @jay_s_uk ok perfecti will try this. I didnt actually create this file i got it off someone. If i just copy what is there except the firmware version do you think this will work or do i need to work out all the parameters?

          1 Reply Last reply Reply Quote 0
          • A Former User?
            A Former User
            last edited by

            please see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files

            you should probably browse https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md and https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md for all the changes made since that version.

            -or- use the config tool linked to to generate a new starting point instead of converting the old.

            you can find a lot of the things to put into the config tool from the old config; refer to https://duet3d.dozuki.com/Wiki/Gcode if you don't understand all the different configuration gcode.

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

              @jay_s_uk - i amended the .json file and updated the version to 3+

              Ive dont it and am now getting a different error code.

              Screenshot 2020-09-14 at 21.42.45.png

              I also have a couple of Qs about how the settings for the tool that you may be able to help me with

              Screenshot 2020-09-14 at 21.37.04.png

              on this page i dont know what endstop pin to select and this was the one on the configuration already is that right (im using a BL touch)?

              the ender 3 has 3 fans (two on the extruder and one for the board but im reading this as its set to only have two is that correct?

              also the Z prob pins are alittle confusing too does this look right?

              Screenshot 2020-09-14 at 21.38.26.png

              on this page i wasnt able to select the z probe which doesnt seem correct

              i also wasnt able to select the BL touch either which wasnt any help

              If you can help with this lot i would really appreciate it.

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

                @bearer sorry just seen this.

                I will have a read tonight and see what i can do.

                Thank you!!

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

                  The configurator has a built in Ender 3 profile, you can select the duet wifi and RRF3 and it should give you a largely accurate config, provided of course that you have wired things in the expected way. I would suggest trying to get the wiring to match the expected way first.

                  Also, when sharing samples of gcode, it's probably best to copy and paste the text into your post rather than post a photo. It's much easier for those on mobile devices and we can quote sections more easily. You can use the little code tag button </> to put it in a code block to make it even more readable.

                  code_text
                  

                  Download this json file and then use the web configurator to load it by clicking on "Ues existing configuration" here: https://configtool.reprapfirmware.org/Start

                  config.json

                  That should give you a stock ender 3, duet wifi, rrf3, bltouch config example.

                  From there you can either edit the motor/endstop assignments to match what you have wired, or you can move the wires to the default ports on the board and have it match the example.

                  Z-Bot CoreXY Build | Thingiverse Profile

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

                    @Phaedrux Thanks! and apologises for the screenshot i will know for the future (rofl)

                    so that config.json doesnt download unfortunately, however i have seen that the pre configured ender 3 pro so i will probably use that. I have just the ender 3 but i believe they use the same original board and believe that the are the same except the frame is more sterdy and the PCU is better. but will check the measurements because the print sizes maybe slightly different also. from what ive read on the above links it should just be slight amendments to the gcodes which doesnt seem tooo difficult :s but makinig sure i know what im doing

                    1 Reply Last reply Reply Quote 0
                    • 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
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA