The actual message that flashes by is "drives not on, cannot be homed"
We are looking for loops that may not be closed in the system.
We are bringing a 95 EZPath back to life. The screen alarms an axis drive fault. If we hit any key, the Z axis (momentarily) moves towards the chuck. We have something crossed up and it is not obvoius. We did change out all of the original cracked up cables. The only blinking red light is D12 in the center of the AUF board.
Any ideas?
The actual message that flashes by is "drives not on, cannot be homed"
We are looking for loops that may not be closed in the system.
Sounds like the Z axis is in runaway condition, does the motor have a tach?
Try disconnecting the command signal to the drive and see if it still runs away, if it does it could either be tach problem or motor leads crossed.
Al.
CNC, Mechatronics Integration and Custom Machine Design (Skype Avail).
“Logic will get you from A to B. Imagination will take you everywhere.”
Albert E.
The Z does not jump with the JP9 plug pulled from the AXSBOB card. The "drives not on, cannot be homed" alarm still comes up.
We did find a pin not making contact on the X manual jog hand wheel cable. Plugged into JP5 also on the AXSBOB card. Changing that damaged clip now.
Also, the Z axis wiring was not changed at all during our repairs. The wires are in good shape being out of the coolant and all.
Okay. Some issues were found. (loose wire conections etc.)
Now when we go to "home" the machine, the "Z" axis doesn't jump, the Alarm "Drives not on, cannot home f4 flashes up then "Axis Driver Fault" pops up.
Are there any led lights or anything that would indicate a problem?
The two drive boards have a green and red led that stay lit on both.
The AUF board has a red led that blinks slowly labeled D12.