Centroid Community CNC Support Forum

Please show me how to fix the lathe X axis error. (I'm in Vietnam, I can watch videos or pictures everything).
Thank you!

I'm not very familiar with the older Centroid controls, but full power without motion is normally caused by an encoder problem. Since the motors and encoders are connected with MIL connectors, swap motors with another axis. If the error moves with the motor, then it is probably a bad encoder.


Moderators - can we move this to the legacy forum since this is not an Acorn control?

On an AC-servo system like this, an encoder problem would be more likely to cause a servo drive fault condition.

If there is no motion at all, and the message is either "411 ... full power without motion" or "410 ... position error", then the cause is more likely to be a lack of power to the VM terminals, or a hardware failure on the servo drive.

With Emergency Stop released, measure DC Volts from the VM+ terminal to the VM- terminal. It should be between 120VDC and 350VDC, depending on your system.

Without trying to home the machine (do not press Cycle Start), try jogging the Z axis. Does Z move as it should?

Thank you for your reply!
- I measure DC Volts from VM+ terminal to VM- terminal is 200v (My motor max is 140v)?
- Z axis is still ok

The Z axis moves okay.
You have adequate voltage to the X axis drive.
The X axis drive fails to move its motor.

It is very likely that you have a hardware failure on the X axis drive.

If you were in North America, I would recommend just sending it to Centroid for test and repair.

Since you are not, you may want to look into local repair, if you know a good drive technician. It is possible that the problem is limited to failed power transistors, which are relatively simple to test and to replace.

Ok, thank you!
I still wonder that the voltage for the X axis is 200v but my motor only has a max of 140v, how do I run it?.

If the drive has an error, I don't think it is IGBT failure. Parameters 374, 375, 376 are set correctly to create a debug dump file if a serious error occurs. There are no recent debug dump logs in the report. Normally, the drive flashes error 5 and the debug dump will be created to allow further analysis when something serious like an IGBT short occurs. There are also no instances of FatalError being 1 in the HSC log. This would normally be captured when serious drive damage occurs.

The HSC screen shows a list of drive status bits. LineVoltageOn should be 1 when the estop is released. In the report files, LineVoltageOn has been 0 in all recent entries. Either the log has missed the occasions when power was applied, or there is some power problem. Check the HSC screen in person to see if the LineVoltageOn bit changes to 1 on both drives.


I have never figured out exactly what the Fanuc voltage rating means. On systems where I knew the original supply voltage, V/kRPM, etc., it did not match any of the voltage specifications of the system.

Is there any way to check IGBT bro?

Usually they short out when they go bad. Use continuity / diode check on meter. There should be no short (meter beep) between any of the 3 legs on each IGBT.

Did you check the report file and see no damage?