FreeAtLast
Member
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?
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?