dls 32 with 2 external drivers and separate power supplies.

[Strummerone]

Hi I'm using DLC 32 on a DIY CNC with 2 external drivers on the Y axis. As I'm using external drivers Ive connected both sets of control wiring from the board to each driver via the set of pins marked Y axis (Dir,S, En etc). Problem is that if I have just one driver connected everythings fine, however when both drivers are connected, one of them (the drivers) go into fault mode( Steady red light). I read somewhere that both driver have to be on the same power supply, mine have separate 36v power supplies (Cheaper believe it or not) Is this true or am I missing something? Anyone any ideas..

[MJ666]

As long you have a common ground for your the DLC32 and the 2 external drivers there is no reason why it should not work. Can you post a schematic of your build or may be picture how it is connected?

[Strummerone]

As installed wiring.pdf

I,ve been tinkering and managed to get both stepper motors on the Y axis working from the one power supply. Only trouble is that when I connect further axis i.e X or Z neither of them want to work with the Y but if I set them up on them individually 9without the Y connected they work.

[MJ666]

How is the DLC32 powerd? I guess it is another power supply? You may need a common ground of all power supplys with strong wirering. It should not rely on the thin ground traces of the DLC32 itself only. This may lead to potential shift on your ground and causing your problems.

[Strummerone]

As Installed with ground.pdf

Please see new drawing with additional bits. Would adding the interconnecting ground to each driver (see drawing) help? I could cross bond (British expression for equipotential bonding) the power supply chassis to each other with a larger earth cable but I think the chassis is already earthed via the incoming supply. I can't get my head around why these won't work together as the DLC32 is just sending out signals. Oh and by the way, the power supply and the supply for the DLC32 are from the same source.

[MJ666]

The motor drivers are using optocouplers for the signal inputs. Having both drivers separately powered should not be a problem. May be the output power of the DLC32 pins is not sufficient to drive both motor drivers. Twice as much current is needed to drive two optocoupler LED's. If your motor drivers are near together you may route the cables from one to the other but not separately to each of them from the DLC32. The information in the link is may be also useful to boost the signal for two external motor drivers to one st of pins: https://github.com/bdring/external_stepper_motor_driver

[ham577]

I encountered a similar issue with an external driver. Additionally, as you mentioned, they seem to operate in different directions despite receiving the same signal. i noticed some industrial driver support logic voltage up to 12v and in some cases 24v because noisy industrial situation and 3.3v logic voltage cause some issue in such driver additionally remind it length of your signal cable between dlc32 and driver must lower than 12 inch for same reason use limit switch 5v pin to set logic voltage 0-5v like image below must (hopefully) solve problem

[Luis-Reis100]

Dear Strummerone , have you managed to solve the issue, having two drivers at only one DLC32 Y axis output?

[Strummerone]

My apologies for not communicating sooner. Yes I solved the 2 motor issue. My fault, I hadn't noticed that 2 of the connections got crossed. I am now looking at a way to control the drivers via the board (firmware) using another axis and will try to add some sort of safety into the equation in case one motor works and the other doesn't leading to catastrophe. Many thanks for all the help..

[Luis-Reis100]

Are you using the FluidNC as a firmware to the MKSDLc32 or the original GRBL firmware that comes with the board? I`ve read that Fluidnc allows you to better manage what you want for any axis output to perform. It seems that the output & input designation with the FluidNc is more flexible. I really don't have any experience with FluidNC, I've just read it.

Em seg., 21 de out. de 2024 às 07:35, Strummerone @.***> escreveu:

My apologies for not communicating sooner. Yes I solved the 2 motor issue. My fault, I hadn't noticed that 2 of the connections got crossed. I am now looking at a way to control the drivers via the board (firmware) using another axis and will try to add some sort of safety into the equation in case one motor works and the other doesn't leading to catastrophe. Many thanks for all the help..

— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2426282080, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMGPQQKILEYO4WMIQ6B47UTZ4TKGTAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGI4DEMBYGA . You are receiving this because you commented.Message ID: @.***>

[Strummerone]

Hi there.

Yes, I’m using Fluidic on a Makerbase DLC32 over wifi. Fluidnc is quite flexible, however I don't use the web interface much. The LCDs that come with the dlc32 won’t work once Fluidnc is loaded. I mostly use UGS to send Gcode to the machine which works fine. At the moment I haven't the time to look further into how to set up the dual motor control via Fluidic, but I will eventually get round to it, I don't like the idea that one day one of the motors dies leaving the other to run amuck. I will need to work out how to practically set up something like motion sensing or current flow sensing to detect if both motors are running, if not go to alarm. Kind regards Pete

From: Luis-Reis100 @.> Date: Tuesday, 22 October 2024 at 00:00 To: makerbase-mks/MKS-DLC32 @.> Cc: Strummerone @.>, Author @.> Subject: Re: [makerbase-mks/MKS-DLC32] dls 32 with 2 external drivers and separate power supplies. (Issue #454)

Are you using the FluidNC as a firmware to the MKSDLc32 or the original GRBL firmware that comes with the board? I`ve read that Fluidnc allows you to better manage what you want for any axis output to perform. It seems that the output & input designation with the FluidNc is more flexible. I really don't have any experience with FluidNC, I've just read it.

Em seg., 21 de out. de 2024 às 07:35, Strummerone @.***> escreveu:

My apologies for not communicating sooner. Yes I solved the 2 motor issue. My fault, I hadn't noticed that 2 of the connections got crossed. I am now looking at a way to control the drivers via the board (firmware) using another axis and will try to add some sort of safety into the equation in case one motor works and the other doesn't leading to catastrophe. Many thanks for all the help..

— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2426282080, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMGPQQKILEYO4WMIQ6B47UTZ4TKGTAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGI4DEMBYGA . You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2427889829, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BEH35FW6UFJP57TOBAPBVMDZ4WBSBAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXHA4DSOBSHE. You are receiving this because you authored the thread.Message ID: @.***>

[Luis-Reis100]

Pete,

Your concern about this issue of having one of the motors getting down is important, would severely damage the mechanical parts of the machine.

If you don't really mind, when you find a way to solve this issue, i'd ask you to share with me.

Regards, Luis Reis

Em ter., 22 de out. de 2024, 07:29, Strummerone @.***> escreveu:

Hi there.

Yes, I’m using Fluidic on a Makerbase DLC32 over wifi. Fluidnc is quite flexible, however I don't use the web interface much. The LCDs that come with the dlc32 won’t work once Fluidnc is loaded. I mostly use UGS to send Gcode to the machine which works fine. At the moment I haven't the time to look further into how to set up the dual motor control via Fluidic, but I will eventually get round to it, I don't like the idea that one day one of the motors dies leaving the other to run amuck. I will need to work out how to practically set up something like motion sensing or current flow sensing to detect if both motors are running, if not go to alarm. Kind regards Pete

From: Luis-Reis100 @.> Date: Tuesday, 22 October 2024 at 00:00 To: makerbase-mks/MKS-DLC32 @.> Cc: Strummerone @.>, Author @.> Subject: Re: [makerbase-mks/MKS-DLC32] dls 32 with 2 external drivers and separate power supplies. (Issue #454)

Are you using the FluidNC as a firmware to the MKSDLc32 or the original GRBL firmware that comes with the board? I`ve read that Fluidnc allows you to better manage what you want for any axis output to perform. It seems that the output & input designation with the FluidNc is more flexible. I really don't have any experience with FluidNC, I've just read it.

Em seg., 21 de out. de 2024 às 07:35, Strummerone @.***> escreveu:

My apologies for not communicating sooner. Yes I solved the 2 motor issue. My fault, I hadn't noticed that 2 of the connections got crossed. I am now looking at a way to control the drivers via the board (firmware) using another axis and will try to add some sort of safety into the equation in case one motor works and the other doesn't leading to catastrophe. Many thanks for all the help..

— Reply to this email directly, view it on GitHub < https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2426282080>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/BMGPQQKILEYO4WMIQ6B47UTZ4TKGTAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGI4DEMBYGA>

. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2427889829>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/BEH35FW6UFJP57TOBAPBVMDZ4WBSBAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXHA4DSOBSHE>.

You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2428905169, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMGPQQLWYQ3ANCZQNFDU5ULZ4YSHFAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYHEYDKMJWHE . You are receiving this because you commented.Message ID: @.***>

[Strummerone]

Hi again. No problem sharing however it might be a while as I’m up to my eyes in it at the moment. Regards Pete

Kind Regards

On 22 Oct 2024, at 12:29, Luis-Reis100 @.***> wrote:



Pete,

Your concern about this issue of having one of the motors getting down is important, would severely damage the mechanical parts of the machine.

If you don't really mind, when you find a way to solve this issue, i'd ask you to share with me.

Regards, Luis Reis

Em ter., 22 de out. de 2024, 07:29, Strummerone @.***> escreveu:

Hi there.

Yes, I’m using Fluidic on a Makerbase DLC32 over wifi. Fluidnc is quite flexible, however I don't use the web interface much. The LCDs that come with the dlc32 won’t work once Fluidnc is loaded. I mostly use UGS to send Gcode to the machine which works fine. At the moment I haven't the time to look further into how to set up the dual motor control via Fluidic, but I will eventually get round to it, I don't like the idea that one day one of the motors dies leaving the other to run amuck. I will need to work out how to practically set up something like motion sensing or current flow sensing to detect if both motors are running, if not go to alarm. Kind regards Pete

From: Luis-Reis100 @.> Date: Tuesday, 22 October 2024 at 00:00 To: makerbase-mks/MKS-DLC32 @.> Cc: Strummerone @.>, Author @.> Subject: Re: [makerbase-mks/MKS-DLC32] dls 32 with 2 external drivers and separate power supplies. (Issue #454)

Are you using the FluidNC as a firmware to the MKSDLc32 or the original GRBL firmware that comes with the board? I`ve read that Fluidnc allows you to better manage what you want for any axis output to perform. It seems that the output & input designation with the FluidNc is more flexible. I really don't have any experience with FluidNC, I've just read it.

Em seg., 21 de out. de 2024 às 07:35, Strummerone @.***> escreveu:

My apologies for not communicating sooner. Yes I solved the 2 motor issue. My fault, I hadn't noticed that 2 of the connections got crossed. I am now looking at a way to control the drivers via the board (firmware) using another axis and will try to add some sort of safety into the equation in case one motor works and the other doesn't leading to catastrophe. Many thanks for all the help..

— Reply to this email directly, view it on GitHub < https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2426282080>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/BMGPQQKILEYO4WMIQ6B47UTZ4TKGTAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGI4DEMBYGA>

. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2427889829>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/BEH35FW6UFJP57TOBAPBVMDZ4WBSBAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXHA4DSOBSHE>.

You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2428905169, or unsubscribe https://github.com/notifications/unsubscribe-auth/BMGPQQLWYQ3ANCZQNFDU5ULZ4YSHFAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYHEYDKMJWHE . You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/makerbase-mks/MKS-DLC32/issues/454#issuecomment-2429026422, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BEH35FRGRJDENSREKADTD5LZ4YZJFAVCNFSM6AAAAABQEDL27KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZGAZDMNBSGI. You are receiving this because you authored the thread.Message ID: @.***>