Troubleshooting Excessive Velocity Error/PhysicalAxisFault

FreeAtLast

Member
Join Date
Mar 2019
Location
Nashville
Posts
38
Hi All,
I have a 2097-V31PR0-LM Kinetix 350 and a TLY-A110T-Hxx2 servo. It is a new setup and I've commissioned the drive: Scaling, hookup tests, polarity, Autotune, which all worked fine. The hookup tests I did were "Motor and Feedback", "Motor Feedback" and "Marker".

The only logic in the PLC are 2 residual MSG instructions which I used to Disable the EnableInputChecking and the OvertravelChecking.

As soon as I give an MSO from the motion direct commands, the servo starts spinning and after about a second the drive faults and gives F55, Physical Axis Fault, Excessive Velocity Error. Where is the command coming from, telling it to spin as soon as the MSO is given?

This may be unrelated, but when I was first setting up the drive I was able to give an MSO without the servo running away or the drive faulting. Then, I changed the application type from Basic to Point-to-Point, and the Load ratio from 0 to 1, did another autotune and then opened the manual tune window. From that point on, even though I've changed the settings back to what they originally were, an MSO command has always caused the same fault.

Any ideas?
 
Double-check, then triple-check, then check one more time each of the encoder connections and the motor output connections.

A "runaway" axis that happens right after the Motion Servo On (MSO) command turns on the position control loop is almost always a single-phased motor (one loose motor output wire) or an encoder feedback wiring problem.

When a problem like that is present during initial tuning, you can get garbage autotune results, so the procedure is usually "disconnect everything, reconnect everything, repeat tuning".

If you can spin the servo shaft by hand, that's a good way to check the feedback wiring to see if you can read the Current Position and get results that are consistent with the configuration of the encoder.
 
Unfortunately, power cycling the drive did not fix it. I've double-checked and triple-checked all the wiring and everything is wired as the manual says to wire it.

The thing that confuses me is that the hookup tests work without a problem. The motor and feedback test accurately moves the motor the commanded 360 degrees. And the Motor Feedback test accurately identifies the polarity.

What else can I check?
 
Well, unfortunately this was never fully resolved. Here is what we found: Deleting the axis and starting from scratch did seem to stop the runaway problem. However, after adding a new axis and autotuning, the unloaded shaft still (about 1/2 the time) would drift and correct itself. It would bounce back and forth through an angle of about 30deg.

When I rotated the shaft by hand, it would easily allow me to rotate it, and it would "cog" every 40 or 50 deg and sometimes not servo back to its original position.

However, this was not repeatable, and it often would servo.
One behavior that was repeatable, was that if we commanded it to jog forward it would sort of jump or cog in 50-60deg intervals. This could be smoothed out by increasing the system damping in the Manual Tuning parameters.

Rockwell tech support agreed with the previous posts, that it was behaving like it was single phasing, or not commutating.
We tried new drive, and saw the same exact behavior. For now, we aren't going to replace the motor or cables, because it seems to be managed by increasing the system damping (for example from 1.0 to 0.7).

Thanks to everyone for your help.
 
I realize I am a little late to the party here but I just resolved a "physical axis fault & excessive velocity error" and thought I would share for the next person.

Check your axis configuration! Mine was set to position loop (d'oh!).

Changed it to Velocity loop like my other axis' and viola, error's are gone.
 
same issue with PhysicalAxisFault , ExcessiveVelocityErrorFault .
we changed the drive and it now works fine .
what could be the problem with the damaged drive ?
is it repairable ?
2198-H040-ERS2 , VPL-B1651C-P
 
I realize I am a little late to the party here but I just resolved a "physical axis fault & excessive velocity error" and thought I would share for the next person.

Check your axis configuration! Mine was set to position loop (d'oh!).

Changed it to Velocity loop like my other axis' and viola, error's are gone.
I don't understand. If you can control position, you are also controlling the velocity.


The position, velocity, acceleration and jerk are all related. A velocity loop is handy when you DON'T care about position or you only have velocity feed back.
 
Every time i have this fault its usually traced to loose encoder mechanical connection or loose wiring at drive. Maybe the drive is good but the connection was loose? Do you have a spare motor and encoder to wire it up in shop? Also the autotune setting for the bandwidth that faults on error was too narrow. I can not remember exactly the parameter but if you double the error deadband range it does not give you an error. But this was on a 755 with encoder on the daughter board.
 
any thoughts ?


I doubt there's anything wrong with the original drive, rather something is probably wrong with the mechanical integrity of the load. Check welds, fasteners, etc. All of them. Hairline fractures in the load definitely will cause this.

When you tuned the replacement drive you tuned it with the compromised load, give it some time and it will further deviate from baseline and your errors will come back.
 

Similar Topics

Hey when I turn on my Siemens PLC CPU 216-2 after runing 10 minute it's stop and showing SF indication after I turn off and some time later turn...
Replies
0
Views
90
Good Morning , Not sure how many use Markem-Imaje SmartDate X60 Printers , but I'm having trouble finding a good manual for...
Replies
3
Views
346
I'll preface this by saying this is the first time I've worked on a Siemens system and I'm fairly unfamiliar with them. I might mess up some of...
Replies
29
Views
652
Hello all, First time poster, long time viewer of these forums. Could not find my solution on here. We have had issues with a Comm Fail on an...
Replies
2
Views
339
Our wire stripper machine (Komax Gamma 263 S) stopped working. All kinds of fault messages... * Short circuit on digital output on CPU2000...
Replies
0
Views
270
Back
Top Bottom