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

    Configure dual extruder via expansion board

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    18
    736
    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.
    • JayTundefined
      JayT @jay_s_uk
      last edited by

      @jay_s_uk I believe, you need to re-read the post and understand that I am not reporting a bug on the version being used. Instead I am asking about configuring the motors of a dual extruder via expansion 1XD. I am guessing you are wise enough to reply a question in a civilized way for the forum users and not spam their posts with sarcasm.

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

        @jayt and there have been a number of fixes since then to CAN communications so what are you trying to achieve by flagging DC42 and Phaedrux?

        edit: you're config looks fine in its isolated condition but as always a full config is needed

        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
          last edited by

          Please post your full config and the results of M122 and M98 P"config.g" once you've updated to 3.3 or 3.4 Beta3 and tested again.

          Z-Bot CoreXY Build | Thingiverse Profile

          JayTundefined 1 Reply Last reply Reply Quote 1
          • JayTundefined
            JayT @Phaedrux
            last edited by

            @Phaedrux @jay_s_uk : Thank you for confirming on config posted so far.

            I have already tried with 3.4beta2, prints sometimes hanged in between and one of the posts mentioned the issue as well
            https://forum.duet3d.com/topic/24683/3-4beta2-motors-hang/6?_=1630040704353.
            If this is resolved with 3.4beta3, I will flash and get back to you guys with required details , if the second motor issue still persists

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

              @jayt yes, that's fixed in beta 3

              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

              JayTundefined 1 Reply Last reply Reply Quote 0
              • JayTundefined
                JayT @jay_s_uk
                last edited by JayT

                @jay_s_uk : with 3.4 beta3 as well, the second extruder from the board B41 does not work.
                Observations so far:
                pins on the 1XD-board itself don't show any signal. For B40 (driving motor 1 of extruder), I am able to read signal on the pins, when I select the extruder and do extrusion.

                I will share other details by EOD, after doing some checks.
                Meanwhile, can you suggest anything that I need to cross check in config? Any condition/instruction not set that may restrict 2nd motor?
                (Also in my previous reply for 3.4beta2, I wasn't using dual extruder)

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

                  @jayt i assume you have a G4 S2 or similar in your config.g before any expansion boards are referred to?
                  Might be worth posting your whole config so we can have a quick look over
                  and what are the arrangements of these jumpers on both 1XD boards?
                  828d105c-76f6-4ddd-adef-78ae6b06dc4a-image.png

                  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

                  JayTundefined 1 Reply Last reply Reply Quote 1
                  • JayTundefined
                    JayT @jay_s_uk
                    last edited by

                    @jay_s_uk

                    I have attached the config file.
                    NOTE:

                    1. IF I run M115 B40 or M115 B41, I get positive response. both communicate well & the LEDs blinking is in sync. Same 3.4 beta3 on all boards.
                    2. Also I noticed, if I configure single board with B40 address and run the second extruder it works. So this confirms no problem with second motor or the board. Something in config is weird?
                    3. I haven't used G4 commands.
                      NOTE: config is too raw, just for trial purpose. main purpose is to try running dual extruder via exp- 1XDs.
                    4. B40 (no jumpers), B41-XD : jumper on CAN-FD-OUT.
                      Mainboard to B40 in -> B40 out -> B41-in-> Jumper on the B41-out.
                    5. I tried removing all jumpers too to see just in case it works.
                      421ad481-73f8-48d4-bceb-d9daadbe9b32-image.png
                      0dc8aa88-e358-483b-a468-4d29e9589ecd-image.png

                    (not able to upload file , so pasted images of the config).

                    JayTundefined jay_s_ukundefined 3 Replies Last reply Reply Quote 1
                    • JayTundefined
                      JayT @JayT
                      last edited by

                      @jayt

                      observation 6: No hiccups, no timeouts.
                      additionally, I tried to run Extruder from B40 and monitor pin signals for motor. I receive signal for 1XDBoard 40 but not for 1XDboard 41 pin, when I run extruder 2

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

                        @jayt add

                        G4 S2
                        

                        after the network settings. (the M586 lines)
                        Its required when using CAN connected boards.

                        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 1
                        • jay_s_ukundefined
                          jay_s_uk @JayT
                          last edited by jay_s_uk

                          @jayt also, your M563 for the second tool is missing D1 so it won't use an extruder
                          And you've also got fans listed for your tools but I didn't see them in your config

                          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

                          JayTundefined 1 Reply Last reply Reply Quote 2
                          • JayTundefined
                            JayT @jay_s_uk
                            last edited by

                            @jay_s_uk

                            Thank you !!!!!

                            I guess it was more of the D1' missing in the line with M563.
                            I haven't configured fans yet.

                            Can you explain why G4 S2 is must for CAN connected boards?

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

                              @jayt to give them time to establish a link with the main board and get in sync ready to accept commands as sometimes, config.g is ran before they are ready.
                              they recommend S1 here but i've seen reports where 1 second isn't enough so I usually recommend S2 (2 seconds)
                              https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Startup_Time

                              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

                              JayTundefined 1 Reply Last reply Reply Quote 2
                              • JayTundefined
                                JayT @jay_s_uk
                                last edited by

                                @jay_s_uk : ok got it. you can mark this thread as Solved.
                                Thank you again!

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