Centroid Community CNC Support Forum

Hi All.

Looking for some assistance with a retrofit we are working through.

The install is a 3 Axis mill, and we have opted for the Oak controller and the ACDC 30 servo drives.

Working through the commissioning and we are having problems with the communication and control of the servos.

Error is Z Axis communication in fault.

Any assistance would be much appreciated.
Attached is a copy of the report.

please and thank you.

Hi

We are looking for some help or ideas to get our acdc 30 drives operational. its a 3 axis mill.
I have attached the latest report as well as the hsc screen, and you will notice that there is erroruvwinvalid and fatalerror highlighted in the hsc screen. any clues in identifying what causing this msg would be great.
I'm guessing this is the reason with our lack of movement or communication with the acdc 30's in every axis and further steps in getting this machine running.
also would like to know how to change the commutation values over to the 6 and 1 that it needs to be, or is this automatic once motors are mobile?
I have also attached pics of inside the cabinet.
thank you for any help.

Hi
here is the Attachments

Centroid name plate
Model: M39
Serial 104765

The Z axis communication fault might be from a loose jumper. Please check that the Wired Input jumper is securely in place on all of the drives. This must be resolved before doing anything to fix the commutation issue.

Regarding the commutation issue: From page 16 of the AC/DC manual, the commutation is not correct. Do you know if the Fanuc Red Cap Encoder Upgrade kit was installed on the motors? CommutationZone = 7 implies that the encoders do not have commutation tracks.

Hi Centroid467
Yeah jumpers are definitely on drives. I played with them yesterday and if they are removed the drives don't even pick up axis number.

Yes I have all new encoders fitted for fanuc red caps. All the brackets, plugs and connectors. They are all reading pulse counts so that's working.
And after watching martys video again his commutation values don't come good until he runs it afew times.

Alright, time for some more troubleshooting steps. It looks like the Z axis cable is pretty close to one of the motor output phase wires. Can you try moving it away from the motor wires and see if that makes any difference?


If that fails, could you try switching the order of the drives in the communications chain? I.E. switch the DriveComm cables to go Oak -> drive labeled Y axis -> drive labeled Z axis -> drive labeled X axis. You can also try switching around the cables and see if anything changes.

Don't try to jog them or otherwise enable motion because I am pretty sure that the motor specific tuning parameters are set based on the position in the chain.

If the communication error follows the drive labeled Z then there may be something wrong with the drive.

Okay I've moved that wire you spoke about, nothing doing there.
Just checking each drive needs a jumper pin? which I have on their x3 of (fiber optic doesn't need this?)
I have moved the communication cables around and taken drives out of the communication loop, still to the same communication fault. doesn't matter what drive.
I've checked the Leds in the drives I've got 5volt Leds, 12volt Leds and FPGA OK Leds on all drives, i don't have drive enable Leds on any drive.
Another question, I now have Asterix on every axis letter in the pid screen, what does this mean?
Yesterday i had an encoder pulse counts and today they don't want to play the game
it's a mystery at the moment appreciate your help.

I can answer one little part of your questions. The asterisk next to the drive letter means that the axis is on the index mark. You should only see that for a split second on each motor revolution. If you are seeing that constantly, then you have a problem with the encoders which is backed up by the fact that you are not seeing any counts.