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

    Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards

    Scheduled Pinned Locked Moved
    Config Tool
    6
    59
    2.7k
    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.
    • droftartsundefined
      droftarts administrators @developeralgo222
      last edited by

      @developeralgo222 I'm running out of ideas. As far as I can tell, there's nothing stopping the Duet sending step pulses to the motor driver, and it thinks the drive is moving, because the axis position is updated.

      I am wondering if the motor energising is a red herring, and it's not actually enabling, because it's not going into an alarm condition:

      ALM:Alarm indicator light: ... if the red light is flicker three times within 3 seconds, that means position ultra difference or the encoder connector is disconnected.

      I don't think it's even registering it should move, because the driver is not enabled. Does the motor energise as soon as power is applied to the driver (with the Duet off), or only once the Duet is turned on?

      How is the 3-pin 'Driver active enable select' jumper, next to Driver 1, set? I think the jumper is between EN_POL and GND, which should be correct for this drive:

      The Enable output is either low when "on" and high impedance when "off", or vice versa, depending on the position of the 'Driver Enable Polarity' (En_Pol) jumper.

      Also try changing M569 R parameter to R0:

      Rnnn Driver enable polarity: 0 = active low, 1 = active high, -1 = driver is always disabled and is not monitored (default 0)

      Another option is to try disconnecting +5V and -EN from the stepper driver, because external drivers are often active with no signal on the enable line, to allow for simpler systems which only have step and direction outputs.

      The only other thing I can think of is to put an oscilloscope on the Duet outputs.

      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

      1 Reply Last reply Reply Quote 0
      • o_lampeundefined
        o_lampe @developeralgo222
        last edited by

        @developeralgo222 said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

        (2) M98 P"config.g" when sent it disconnects and nothing happens

        I would start investigating this issue first, because it is a critical error. You might damage the onboard 5V regulator if it's a overcurrent shutdown...
        Other stuff might solve itself after you've found the reason for the disconnects.

        developeralgo222undefined 1 Reply Last reply Reply Quote 1
        • developeralgo222undefined
          developeralgo222 @o_lampe
          last edited by developeralgo222

          @o_lampe

          I finally got a MACH 3 Controller board and MACH 3 software to test the X & Y Axis motors( NEMA 34 8.5N.m (86HSE8N-BC38) ) and External Driver (HSS86) . The Motors work fine no issue they are able to move Left to Right on X-axis and Forward and back on Y-axis. Confirming that the following connections from Motor to Driver are correct (NEMA 34 Motor Power & Encoder connections) The only thing i changed for the test is the Signal wiring to comply with the MACH 3 Controller

          On Duet 3 6XD

          Signal Connection:

          External Drive (HSS86) --------> (Cable Color) ------> Duet 3 6XD Drive_x

          • PUL+ , DIR+, ENA+, ALM+ --------> (Red) ------> 5V_EXT
          • PUL- --------> (Blue) ------> Dx_STEP-
          • DIR- --------> (Yellow) ------> Dx_DIR-
          • ENA- --------> (Green) ------> Dx_EN-
          • ALM- --------> (Black) ------> Dx_ERR

          On MACH 3 Control Board with USB Motion Driver RnRMotion.dll installed

          Signal Connection:

          External Drive (HSS86) --------> (Cable Color) ------> MACH 3 Controller X-axis

          • PUL+ --------> (Red) ------> XP
          • PUL- --------> (Green) ------> GND
          • DIR+ --------> (Yellow) ------> XD
          • PUL- to DIR - (Drive side only) ----> (Black)

          It seems on MACH 3 if you compare it to Duet 6XD connections it seems they are reversed as @droftarts mentioned

          • PUL+ --------> (Red) ------> XP ( Dx_STEP+ )
          • DIR+ --------> (Yellow) ------> XD ( Dx_DIR+ )
          • ENA+ --------> (Blue) ------> XE ( Dx_ENA+ ) ******?
          • ALM+ --------> (Black) ------> XA ( Dx_ALM+ ) ******?
          • PUL- , DIR-, ENA- , ALM- --------> (Green) ------> GND

          IMG_0946.jpg

          It seems the issue is on the Duet 3 6XD side configuration and the signal connection from the external drive. Not sure how to do this on Duet 6XD

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

            @developeralgo222 it looks like the driver is switched the other way around from ‘normal’ drivers, in that it needs a +5V signal with a common ground, rather than having a common +5V that is pulled to ground by a signal. It’s a shame the data sheet is so sparse on details. Where did you find the info on wiring up the Mach 3 controller?

            I’ll have to ask @dc42 in the morning if the 6XD can do that.

            If you are thinking it’s a configuration error, especially if sending M98 P"config.g" causes a reset, create a basic config.g that only sets the X and Y axes.

            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

            developeralgo222undefined 1 Reply Last reply Reply Quote 0
            • developeralgo222undefined
              developeralgo222 @droftarts
              last edited by developeralgo222

              @droftarts said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

              @developeralgo222 it looks like the driver is switched the other way around from ‘normal’ drivers, in that it needs a +5V signal with a common ground, rather than having a common +5V that is pulled to ground by a signal. It’s a shame the data sheet is so sparse on details. Where did you find the info on wiring up the Mach 3 controller?

              Just on youtube and google search , an online user made a demo on how to test the same setup on youtube and someone explained how to connect MACH 3 controller and to NEMA 34 motors

              MACH 3 Controller connection to HSS86 Drive + Nema 34 closed Motor

              MACH3 Controller installation and Wiring

              This is a very simple NEMA 34 closed Loop/External Drive connection to 6XD not sure why it would not work

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

                @developeralgo222 does it lock up the same way as when connected to the 6XD? On the Mach3 board there’s nothing connected to enable. I suggested disconnecting the enable wires earlier.

                With enable wires connected, M17 enables and M18 disables motors.

                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

                developeralgo222undefined 1 Reply Last reply Reply Quote 0
                • developeralgo222undefined
                  developeralgo222 @droftarts
                  last edited by

                  @droftarts said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                  @developeralgo222 does it lock up the same way as when connected to the 6XD? On the Mach3 board there’s nothing connected to enable. I suggested disconnecting the enable wires earlier.

                  With enable wires connected, M17 enables and M18 disables motors.

                  Ian

                  M17: Enable/Power all stepper motors
                  M18: Disable all stepper motors

                  Does this mean it only applies to Open Loop Stepper motors or even closed Loop ?

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

                    @developeralgo222 Good point, I'm not sure. I don't have an external driver and motor setup to test.

                    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

                    developeralgo222undefined 1 Reply Last reply Reply Quote 0
                    • developeralgo222undefined
                      developeralgo222 @droftarts
                      last edited by developeralgo222

                      @droftarts said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                      @developeralgo222 Good point, I'm not sure. I don't have an external driver and motor setup to test.

                      Ian

                      Even with M17 included in the config.g for Duet 6XD. it does not move X and Y at all

                      
                      ; Enable All the drives 
                      M17  ; Enable All the drives
                      
                      droftartsundefined 1 Reply Last reply Reply Quote 0
                      • droftartsundefined
                        droftarts administrators @developeralgo222
                        last edited by

                        @developeralgo222 I asked this earlier:
                        Does it lock up the same way when enabled on the Mach3 board, as it does when connected to the 6XD?
                        On the Mach3 board there’s nothing connected to enable, which would seem to mean it needs an enable low signal. Have you tried disconnecting the enable when connected to the 6XD?

                        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

                        developeralgo222undefined 1 Reply Last reply Reply Quote 0
                        • developeralgo222undefined
                          developeralgo222 @droftarts
                          last edited by developeralgo222

                          @droftarts said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                          @developeralgo222 I asked this earlier:
                          Does it lock up the same way when enabled on the Mach3 board, as it does when connected to the 6XD?
                          On the Mach3 board there’s nothing connected to enable, which would seem to mean it needs an enable low signal. Have you tried disconnecting the enable when connected to the 6XD?

                          Ian

                          on MACH 3 it locks UP, when you power up and its energized and then when you config and Reset your MACH 3 , it unlocks and you can start jogging the motors right away . Looking at the schematics of the wiring diagram . it seems to indicate that the wiring should be

                          PUL+ --------> (Red) ------> XP ( Dx_STEP+ )
                          DIR+ --------> (Yellow) ------> XD ( Dx_DIR+ )
                          ENA+ --------> (Blue) ------> XE ( Dx_ENA+ ) ******?
                          ALM+ --------> (Black) ------> XA ( Dx_ALM+ ) ******?
                          PUL- , DIR-, ENA- , ALM- --------> (Green) ------> GND

                          How can it be done on Duet 3 6XD ? . Duet 3 6XD must have a way of doing this ?

                          1702044996925-wiring_nema34_asper_datasheet.png

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

                            @developeralgo222 The way that wiring diagram is, is EXACTLY how the 6XD is wired! It has a common +5V going to PUL+, DIR+ and ENA+. Then the PUL-, DIR- and ENA- are wired to the controller pins that pull that +5V to GND when the pin is active. This is the 'normal' way of wiring these drivers.
                            It's the Mach3 layout that doesn't match this wiring diagram, as it seems to be send +5V signals in to PUL+ and DIR+, and has a common GND connecting PUL- and DIR-.
                            However, both should work, as it's just sending a signal.

                            @developeralgo222 said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                            on MACH 3 it locks UP, when you power up and its energized and then when you config and Reset your MACH 3 , it unlocks and you can start jogging the motors right away .

                            This sounds like the functionality that we need to replicate. Like I've said, the enable wires aren't connected on either of the links you sent. My best guess is that the enable signal isn't quite right, but it seems to work with Mach3 with enable disconnected. Disconnect the enable wires.

                            Edit: Check continuity on all the wires from the Duet driver 0 connector to the motor driver. Maybe there's a bad crimp or poor connection somewhere along the line.

                            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

                            developeralgo222undefined 1 Reply Last reply Reply Quote 0
                            • developeralgo222undefined
                              developeralgo222 @droftarts
                              last edited by developeralgo222

                              @droftarts said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                              @developeralgo222 said in [Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards]
                              This sounds like the functionality that we need to replicate. Like I've said, the enable wires aren't connected on either of the links you sent. My best guess is that the enable signal isn't quite right, but it seems to work with Mach3 with enable disconnected. Disconnect the enable wires.

                              @droftarts , i disconnected and the ENABLE Wires from the External Drive and the Duet 6XD and that did the trick. Now i am able to move X and Y -axis Motors now

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

                                @developeralgo222 in that case, to make the Enable line work properly you need to move the Driver Enable Polarity jumper on the 6XD to the other position. See https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6XD_Hardware_Overview#description-of-connections.

                                b9420280-42b2-499f-b376-a1af44e15c9a-image.png

                                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

                                developeralgo222undefined 1 Reply Last reply Reply Quote 0
                                • developeralgo222undefined
                                  developeralgo222 @dc42
                                  last edited by

                                  @dc42 said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                                  @developeralgo222 in that case, to make the Enable line work properly you need to move the Driver Enable Polarity jumper on the 6XD to the other position. See https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6XD_Hardware_Overview#description-of-connections.

                                  b9420280-42b2-499f-b376-a1af44e15c9a-image.png

                                  Currently the 1 x3 Pin Jumper (Driver Active Enable Select ) is in the Active Enable Position(Left Side) . I will move it to the Active Disable position (Right Side) and then connect the ENA+ & ENA- and test again

                                  developeralgo222undefined dc42undefined 2 Replies Last reply Reply Quote 0
                                  • developeralgo222undefined
                                    developeralgo222 @developeralgo222
                                    last edited by developeralgo222

                                    @developeralgo222 said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                                    @dc42 said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                                    @developeralgo222 in that case, to make the Enable line work properly you need to move the Driver Enable Polarity jumper on the 6XD to the other position. See https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6XD_Hardware_Overview#description-of-connections.

                                    b9420280-42b2-499f-b376-a1af44e15c9a-image.png

                                    Currently the 1 x3 Pin Jumper (Driver Active Enable Select ) is in the Active Enable Position(Left Side) . I will move it to the Active Disable position (Right Side) and then connect the ENA+ & ENA- and test again

                                    i tested this by moving the Jumper to Active Disable and connecting the ENA+ to 5V power and ENA- to Dx-EN- but it did not work. The Motors are not energized or locked , i can roll them manually But they don't move if i send any command to move them from the console e.g

                                    G1
                                    G1 H2 X50
                                    G1 H2 Y50
                                    

                                    i also have M17 in the config.g but that did not help.

                                    As for now, The only way the 2 x NEMA 34 Closed Loop Motors for X & Y-Axis are able to move is by disconnecting EN+ & EN- from Duet 3 6XD and the External Drivers (HSS86)

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

                                      @developeralgo222 Is this how the drives are still set?

                                      ; Drives
                                      ;Physical Drives CAN ID = 0
                                      M569 P0.0 S0 R1 T5:5:10:10           ; X-Axis physical drive 0.0 goes forwards on CAN ID = 0 - Duet 6XD Drive 0.0 with 5us timings between pulses
                                      M569 P0.1 S1 R1 T5:5:10:10           ; Y-Axis physical drive 0.1 goes forwards on CAN ID = 0 - Duet 6XD Drive 0.1 with 5us timings between pulses
                                      

                                      Can you try changing the R1 to R0? Or if it is R0, change to R1. I'm not sure it will make a difference, but worth testing.

                                      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

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

                                        @developeralgo222 what you are aiming for is that when you boot up the Duet, the drivers are not locked (because there is a voltage across the Enable inputs of your driver, which will disable it). When you send M17 X then the voltage across the Enable pins will be removed and the X motor will lock.

                                        If you have set the Enable jumper correctly (Active Disable sounds correct for your drivers) then you should not need to provide an R parameter in your M569 commands.

                                        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

                                        developeralgo222undefined 1 Reply Last reply Reply Quote 0
                                        • developeralgo222undefined
                                          developeralgo222 @dc42
                                          last edited by

                                          @dc42 said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

                                          @developeralgo222 what you are aiming for is that when you boot up the Duet, the drivers are not locked (because there is a voltage across the Enable inputs of your driver, which will disable it). When you send M17 X then the voltage across the Enable pins will be removed and the X motor will lock.

                                          If you have set the Enable jumper correctly (Active Disable sounds correct for your drivers) then you should not need to provide an R parameter in your M569 commands.

                                          @dc42, now able to move both X and Y-axis. i need to sort out the endstops issue though . i used the suggestions from @droftarts about multiple endstops in parallel but it seems i am having a little bit of trouble in having them work properly

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

                                            @developeralgo222 I suggest you star a separate thread for that issue. Start it by describing what doesn't work and what it does instead. Include your config.g file.

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