Wiring multiple closed loop steppers

[friolator]

Lathe setup, I'm replacing the open loop steppers with Closed Loop. StepperOnline motors, using StepperOnline CL57Y drivers. Looking at the schematics in the knowledgebase, I see there's one for setting up a single motor with this driver. I also see there are schematics for setting up multiple closed loop motors (albeit with a slightly different driver), and the wiring is much different - using the DB25 connector instead of the ST1/ST2 connections on the board.

If I have two CL57Y drivers, should I wire them up as follows?

DRIVER 1:
* PUL+ = +24VDC
* PUL- = ST1
* DIR+ = COM
* DIR- = DR1
* MF+ = COM
* MF- = EN1
* ALM+ = IN5
* ALM- = COM

DRIVER 1:
* PUL+ = +24VDC
* PUL- = ST2
* DIR+ = COM
* DIR- = DR2
* MF+ = COM
* MF- = EN2
* ALM+ = IN5 (Piggyback with Driver 1, or does this get its own input?)
* ALM- = COM

...Or do I have to do the wiring up through the DB25? If so, is "MF+/-" on the driver the same as Enable on, say, the CL86T?

[cnckeith]

latest schematics are on the schematics page here
https://www.centroidcnc.com/centroid_di ... browse.php

search "Acorn online" to see all stepper online schematics

[friolator]

latest schematics are on the schematics page here
https://www.centroidcnc.com/centroid_di ... browse.php

search "Acorn online" to see all stepper online schematics

Yes. I know that, and I referenced it above. But that doesn't answer my question.

[cnckeith]

latest schematics are on the schematics page here
https://www.centroidcnc.com/centroid_di ... browse.php

search "Acorn online" to see all stepper online schematics

Yes. I know that, and I referenced it above. But that doesn't answer my question.

i thought you were looking at an old schematic.

what is the question? if you are asking if you should do something different than what the Centroid provided CL57Y schematic shows...then the answer is no.

wire it like the schematic shows.

https://www.centroidcnc.com/dealersuppo ... 034.r2.pdf

[friolator]

I'm looking at ACORN_rev4, STEPPERONLINE CL57Y Drive for the single drive, which is the driver I have 2 of.

There's also a multiple drive setup that uses the DB25 connector, but for a slightly different driver (the CL86T): ACORN_rev4, Multiple STEPPERONLINE CL86T Drives

And the single-drive setup for the CL86Y looks the same as the one for the CL57Y I'm using. So my question is: do I need use the multiple-drive CL86T schematic as a reference, or do I hook up my two steppers using ST1/ST2 terminals as I outlined above?

[cnckeith]

I'm looking at ACORN_rev4, STEPPERONLINE CL57Y Drive for the single drive, which is the driver I have 2 of.

There's also a multiple drive setup that uses the DB25 connector, but for a slightly different driver (the CL86T): ACORN_rev4, Multiple STEPPERONLINE CL86T Drives

And the single-drive setup for the CL86Y looks the same as the one for the CL57Y I'm using. So my question is: do I need to do the multiple-drive CL86T schematic as a reference, or do I hook up my two steppers using ST1/ST2 terminals as I outlined above?

use the CL57Y and just wire up a second motor just like the first. don't use the CL86T schematic that has as that is not your drive.

[friolator]

I have one of the motors working and I'm hooking up the second to test.

Does the DRIVE OK (ALM+) connection for the Y axis driver piggyback on the Acorn's Input 5 along with the alarm for the Z axis driver, or does it go to a different Acorn input? if the latter, do I then have to to set that up in software?

[dpascucci_support]

You can either use one input for multiple drive fault signals using the DriveOk input or wire the individual drive fault signals to different inputs using Axis(1,2,3,4)DriveOk
List of Acorn canned inputs/outputs can be found here: https://www.centroidcnc.com/centroid_di ... s_v4.8.pdf

[friolator]

ok, thanks. So if I put them both on the same terminal the only downside would be that I won't know which motor alarmed if it happens, but if I keep them separate I will?

[Sword]

Those drives should have a LED that will flash with fault code, so that would give you a visual of which one is faulting.