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

    6XD driver enable does not seem to react

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    2
    8
    225
    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.
    • DuetCDHundefined
      DuetCDH
      last edited by DuetCDH

      I am in the early stages of setting up a 6XD on a Quad IVc pick-n-place machine and I have an issue with the "enable" signal on the external driver header.

      For initial testing, I have LEDs connected between each of the outputs (Enable, Step, Dir) and the 5v pin on the driver header (a 400 ohm resistor in series with each LED).

      The "Enable polarity" jumper is in the "Active Enable" (Left) position.

      Upon powerup,, step and dire LEDs are off and Enable is ON

      When I home the axis, the Enable LED goes out and the Dir LED comes on (I assume Step LED also flashes but too short for me to see).

      If I place the "Enable polarity" jumper is in the right position (and power cycle) nothing changes.

      My driver needs GND to enable it ...

      Thanks in advance,

      Chuck Hackett

      DuetCDHundefined 1 Reply Last reply Reply Quote 0
      • DuetCDHundefined
        DuetCDH @DuetCDH
        last edited by

        @DuetCDH Added info - I found a forum msg "Custom Duet Maestro Step Drivers Enable Pin allways off" where a reply indicated that VIN needed to be above11.x or processor would not enable the driver. I had no VIN (at the moment powered from USB). I added a VIN of 14v and V12 now reads 12v but issue remains. Driver Enable always gnd on power up and not gnd after "Home" regardless of the position of the Driver Polarity jumper.

        dc42undefined 1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators @DuetCDH
          last edited by dc42

          @DuetCDH do the solder joints on the enable polarity jumper pins on the underside of the board look OK?

          Which firmware version are you using?

          PS - please also check which 6XD board version you have (as printed on the board) and run M115 to check that the board version has been identified correctly.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          DuetCDHundefined 1 Reply Last reply Reply Quote 0
          • DuetCDHundefined
            DuetCDH @dc42
            last edited by

            @dc42 Solder joints look fine.

            M115 reports: FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6XD FIRMWARE_VERSION: 3.5.1 ELECTRONICS: Duet 3 MB6XD v1.01 or later FIRMWARE_DATE: 2024-04-19 14:39:48

            Board silkscreen version is 1.02

            DuetCDHundefined dc42undefined 2 Replies Last reply Reply Quote 0
            • DuetCDHundefined
              DuetCDH @DuetCDH
              last edited by

              @DuetCDH This is my M569 line:
              M569 P0.0 S1 R0 T5:5:10:0 ; driver 0.0 goes forwards and requires an active-low enable signal (X axis)

              dc42undefined 1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @DuetCDH
                last edited by dc42

                @DuetCDH said in 6XD driver enable does not seem to react:

                @dc42 Solder joints look fine.

                M115 reports: FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6XD FIRMWARE_VERSION: 3.5.1 ELECTRONICS: Duet 3 MB6XD v1.01 or later FIRMWARE_DATE: 2024-04-19 14:39:48

                Board silkscreen version is 1.02

                Please upgrade to firmware 3.5.4 (or you could try 3.6.0-rc.2). The version 1.02 board is not fully supported by firmware versions prior to 3.5.3.

                EDIT: I've just checked the code and I think there may be an issue with driving the Enable signal on Driver 2 in firmware 3.5.3 and 3.5.4, so maybe best stick to 3.5.1 for now.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                1 Reply Last reply Reply Quote 0
                • dc42undefined
                  dc42 administrators @DuetCDH
                  last edited by

                  @DuetCDH said in 6XD driver enable does not seem to react:

                  @DuetCDH This is my M569 line:
                  M569 P0.0 S1 R0 T5:5:10:0 ; driver 0.0 goes forwards and requires an active-low enable signal (X axis)

                  The R0 parameter is that line is overriding the jumper selection. I think that removing it or replacing it with R1 will do what you want. The "active low" designation of R0 isn't entirely accurate here, it means that the output is not driven to energise the driver.

                  Duet WiFi hardware designer and firmware engineer
                  Please do not ask me for Duet support via PM or email, use the forum
                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                  DuetCDHundefined 1 Reply Last reply Reply Quote 0
                  • DuetCDHundefined
                    DuetCDH @dc42
                    last edited by

                    @dc42 Success! Thank you!

                    I removed the "R0" and "Enable" now acts as expected and my X Axis moves!

                    Now to connect the other axis and the limits so I can home properly.

                    Thanks again!

                    Chuck

                    1 Reply Last reply Reply Quote 0
                    • DuetCDHundefined DuetCDH marked this topic as a question
                    • DuetCDHundefined DuetCDH has marked this topic as solved
                    • First post
                      Last post
                    Unless otherwise noted, all forum content is licensed under CC-BY-SA