Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards
-
@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) ------> GNDHow can it be done on Duet 3 6XD ? . Duet 3 6XD must have a way of doing this ?
-
@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
-
@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
-
@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.
-
@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.
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
-
@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.
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)
-
@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
-
@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 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
-
@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.