Centroid Community CNC Support Forum

Sword wrote: ↑Sun Aug 18, 2024 3:02 pm Imgur link doesn't work, and it's hard to tell by zooming in on it here, but something doesn't look right with that E-Stop circuit. Are there two black wires going into input #1? It looks like IN1 and IN8 are looped together and to common. Really hard to see for sure.

Also, verify that the 6 encoder wires are in the correct order. Do you get a flash code from the driver?

The forum software screwed with the link. Add "i." in front of the hostname and it should work. when I edited the post, the correct URL for the image was shown. Not sure why it's getting messed with.

The E-stop is wired exactly as shown in the schematic. One side of the switch goes to IN8, the other side is tied to IN2 and COM. (gnd)
Hitting the E-stop results in an e-stop message in CNC12. This was tested before I started connecting the driver.

The encoder wires are correct based on the 'D1008 user manual - the driver cables were built by Leadshine.

No flash code from the driver - it only shows the green Power LED.

g.

ShawnM wrote: ↑Sun Aug 18, 2024 3:09 pm As Gary mentioned earlier, also remove the "drive ok" from your inputs. See if this gets the drives moving then figure out the alarm signals. You may have the alarm signal wired incorrectly or it may be a NO circuit and you have it set for NC. Either way, drag the "drive ok" input out of input 5, write those settings to Acorn and try again.

So removing the DriveOk mapping allows the motor to move properly and no DRIVE FAULT error message is thrown. So YAY!

This is the description of the Alarm inputs from the docs:

An OC output signal which is active when one of the following error protection is
activated: over-voltage, over-current, and position following error. This port can sink or source
20mA current at 24V. The resistance between ALM+ and ALM- is low impedance in normal
operation, and will change to high when the drive goes into error protection. The voltage active
level of this false output signal can be configured by configuration software.

Nothing about that jumps out at me to indicate NC vs NO operation. This is not surprising - I'm a software guy. Where in that description indicates the "ok" state?

I restored the DriveOk assignment for Input 5 and inverted the signal setting. After saving the configuration and resetting, the stepper worked as expected.

It looks like this issue has two parts - first, the schematic for the CS-D1008 is incorrect in that the ENA+/ENA- signals shouldn't be connected - and in fact can cause what appears to be a short if they are when the drive is "enabled".

Second, the chart at the upper right corner of the schematic that shows the input assignments has no indication as to setting the logic level of the DriveOk input to inverted.

Is there any chance to get that schematic corrected so the next poor sap doesn't encounter this?

Thanks for all your help folks!

g.

If no fault on the driver, change Driver or Acorn input NC/NO. Both must be set so the input is only triggered if the driver is in fault condition

Uwe

geneb wrote: ↑Sun Aug 18, 2024 1:33 pm
If the ENA connections shouldn't be used, why are they called out on the schematic provided by Centroid?

g.

I can't speak to that as I don't use their schematics, but I do read the component manuals, which should always take precedence. The manual and numerous posts on this forum clearly stated that LeadShine drives should not have the Enable circuit connected.

That manual excerpt tells me that the input should be set to normally open

This is the very reason (confusing language in manual) that I do not recommend setting DriveOk or SpindleOk input designations before the system in operational. Once running (and connected) the Acorn's input LED will tell you which is the normal or triggered state.

FYI: both the Enable and Alarm functions can be inverted via the LeadShine drive software. I don't change these I my builds as I want to simplify any down the road replacement by my customers.