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

    Z motor on expansion board not moving

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    45
    1.8k
    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.
    • jay_s_ukundefined
      jay_s_uk @wdenker
      last edited by

      @wdenker I guess it doesn't like the Z drivers being spread across the mainboard and CAN board. Best move all Z drivers on to one and move Z or Y onto the 3HC

      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

      wdenkerundefined 1 Reply Last reply Reply Quote 0
      • wdenkerundefined
        wdenker @jay_s_uk
        last edited by

        @jay_s_uk any ideas on the filament error I get literally every 30 seconds no matter no filament movement?

        www.bd3dcustoms.com | BD3DCUSTOMS Supercube

        wdenkerundefined 1 Reply Last reply Reply Quote 0
        • wdenkerundefined
          wdenker @wdenker
          last edited by

          @wdenker can't even get it to report 3 out of 4 times.

          12/20/2023, 4:25:15 PM	M591 D0
          12/20/2023, 4:25:12 PM	M591 D0
          Simple filament sensor on pin (io1.out,serial1.tx), enabled, output high when no filament, filament present: no
          12/20/2023, 4:25:00 PM	M591 D0
          12/20/2023, 4:24:59 PM	M591 D0
          12/20/2023, 4:24:41 PM	M591 D0
          

          www.bd3dcustoms.com | BD3DCUSTOMS Supercube

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

            @wdenker it probably needs connecting to a .in rather than a .out

            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

            wdenkerundefined 1 Reply Last reply Reply Quote 0
            • wdenkerundefined
              wdenker @jay_s_uk
              last edited by

              @jay_s_uk we've tried both in and out.

              www.bd3dcustoms.com | BD3DCUSTOMS Supercube

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

                @wdenker can you confirm your wiring, ideally with pictures , and what type of filament sensor it is?

                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

                wdenkerundefined 2 Replies Last reply Reply Quote 0
                • wdenkerundefined
                  wdenker @jay_s_uk
                  last edited by

                  @jay_s_uk ah you were right. We had to switch it to 5v vs 3.3 and didn't have it on in after we swapped to the 5v. So all of my issues are resolved at this point.

                  www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                  wdenkerundefined 1 Reply Last reply Reply Quote 1
                  • wdenkerundefined
                    wdenker @wdenker
                    last edited by

                    @wdenker Well I got ahead of myself still getting the error just not as often.

                    www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                    1 Reply Last reply Reply Quote 0
                    • wdenkerundefined
                      wdenker @jay_s_uk
                      last edited by

                      @jay_s_uk Here are the pics. I have also updated config to reflect going to io2.in vs out PXL_20231220_234947688.jpg PXL_20231220_234959902.jpg

                      www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                      wdenkerundefined 1 Reply Last reply Reply Quote 0
                      • wdenkerundefined
                        wdenker @wdenker
                        last edited by

                        @Phaedrux any ideas?

                        www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                        droftartsundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
                        • droftartsundefined
                          droftarts administrators @wdenker
                          last edited by

                          @wdenker on Duet 3 boards, io.out pins can be used as inputs, but have no series resistor to offer voltage protection, so are only 3.3V tolerant. It is possible you have damaged the 3HC connecting a 5V endstop to an io.out pin.

                          Have you tried a different filament sensor? It is quite possible that the microswitch or wiring is faulty, or could be picking up interference from motor or heater wiring.

                          Ian

                          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

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

                            @wdenker are you powering the 5v_ext? have you tried using it with 3.3v as according to the trianglelab docs it also works with that

                            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

                            wdenkerundefined 1 Reply Last reply Reply Quote 0
                            • wdenkerundefined
                              wdenker @jay_s_uk
                              last edited by

                              @jay_s_uk we have tried the 3.3 on the duet and it does not work so we figured we have to use the 5 volt.

                              www.bd3dcustoms.com | BD3DCUSTOMS Supercube

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

                                @wdenker if it doesn't work with 3.3v, which the manufacturer indicates it should, then i guess theres an issue with it

                                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

                                wdenkerundefined 2 Replies Last reply Reply Quote 0
                                • wdenkerundefined
                                  wdenker @droftarts
                                  last edited by

                                  @droftarts I would think that I would have only damaged that one port if that was the case. I have tried multiple ports to validate that.

                                  www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                                  1 Reply Last reply Reply Quote 0
                                  • wdenkerundefined
                                    wdenker @jay_s_uk
                                    last edited by

                                    @jay_s_uk no none of them work with the 3.3 manufacturer claims they are 3.5 from everything I've seen and I have five working ones that I tried on the 3.3 and moved over to the duex 5 And they all work with the 5 volt.

                                    www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                                    1 Reply Last reply Reply Quote 0
                                    • wdenkerundefined
                                      wdenker @jay_s_uk
                                      last edited by

                                      @jay_s_uk The other thing I am curious about is if the sensor number out of range error in the M98 p"config.g" if that may be somehow causing it but it doesn't give any reference to what is out of range and there are 3.

                                      www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                                      jay_s_ukundefined wdenkerundefined 2 Replies Last reply Reply Quote 0
                                      • jay_s_ukundefined
                                        jay_s_uk @wdenker
                                        last edited by

                                        @wdenker your sensor number out of range is to do with the way you've set your thermostatic fans up. H100 etc isn't valid

                                        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

                                        wdenkerundefined 1 Reply Last reply Reply Quote 1
                                        • wdenkerundefined
                                          wdenker @wdenker
                                          last edited by

                                          @wdenker ah ok well any other things I could try at this point?

                                          www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                                          1 Reply Last reply Reply Quote 0
                                          • wdenkerundefined
                                            wdenker @jay_s_uk
                                            last edited by wdenker

                                            @jay_s_uk I was able to fix that I basically gave it a mcu temp to look at to turn on. Now if I could just figure out this filament sensor I would be golden. I have tried io.0-2 and 3 different sensors that work fine on a duex 5 but coincidentally will not work on the duet.

                                            www.bd3dcustoms.com | BD3DCUSTOMS Supercube

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