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.9k
    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.
    • 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
                          • jay_s_ukundefined
                            jay_s_uk @wdenker
                            last edited by

                            @wdenker did you check you were actually supplying 5v to the 5V_EXT?

                            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 3 Replies Last reply Reply Quote 0
                            • wdenkerundefined
                              wdenker @jay_s_uk
                              last edited by

                              @jay_s_uk reads at 4.96 so I should be good there.

                              www.bd3dcustoms.com | BD3DCUSTOMS Supercube

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

                                @jay_s_uk the funny part of these sensors is that they will not work on a duet 2 wifi but will on a duex 5. So I have tried these sensors on the duet 3 io0-3 at this point on 3.3v or the 5v and the sensor works no problem and reports correctly when I query it with the M591 D0 but still reports every 30 seconds on the dot without any changes no filament and I could query at the same exact time every time and it would report I do have filament and then pop up a split second later saying no filament. Almost like a bug in the firmware.

                                www.bd3dcustoms.com | BD3DCUSTOMS Supercube

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

                                  @jay_s_uk So we tried swapping from high to low and low to high to validate it isn't just positioning of the sensor. So basically trick it to say no filament when there is filament and there is filament when there isn't. It doesn't pop the error in this case only when configured correctly and filament is in and reads filament is in. This is mind boggling to me. I also just moved this sensor to another printer that I know it works on. Am I missing something with a config file or something since I am on 3.4.6 to where I can tell it it has to read no filament for a certain amount of time?

                                  www.bd3dcustoms.com | BD3DCUSTOMS Supercube

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

                                    Sounds like the wiring is picking up noise. What other cables does it run near?

                                    Z-Bot CoreXY Build | Thingiverse Profile

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

                                      @Phaedrux one motor cable but we moved it away from it temporarily with no luck.

                                      www.bd3dcustoms.com | BD3DCUSTOMS Supercube

                                      1 Reply Last reply Reply Quote 0
                                      • droftartsundefined
                                        droftarts administrators @wdenker
                                        last edited by

                                        @wdenker when you say you are moving it to another printer to test, and it works, is that with a Duet 2 board? Is the non-working configuration your only Duet 3? Or is it the exact same configuration (Duet 3 6HC + 3HC, config.g and wiring)? If not, post the Duet 2 config that works, and how the sensor is wired.

                                        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
                                        • wdenkerundefined
                                          wdenker @droftarts
                                          last edited by

                                          @droftarts wired similarly and to a duex5 they don't work on a duet 2 wifi endstop port oddly enough. The configuration is M591 D0 P2 C"duex.e2stop" S1 ; where the configuration on the duet 3 is M591 D0 P2 C"io4.in" S1 ;

                                          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 duex5 IOs are inverted as standard I believe so you'll probably have to add a ! To the pin name

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