Troubleshooting position control faults - Revision history

Tero K: /* Using Granity scope */

2017-05-07T13:01:06Z

‎Using Granity scope

Tero K at 14:13, 6 May 2017

2017-05-06T14:13:10Z

Tero K at 14:11, 6 May 2017

2017-05-06T14:11:25Z

Tero K at 14:10, 6 May 2017

2017-05-06T14:10:55Z

Tero K: Created page with "File:trackingerror_troubleshooting_1.png|thumb|400px|'''Example case A.''' (1) Tracking error originally occurs because motor output current gets saturated to maximum config..."

2017-05-06T14:09:01Z

Created page with "File:trackingerror_troubleshooting_1.png|thumb|400px|'''Example case A.''' (1) Tracking error originally occurs because motor output current gets saturated to maximum config..."

New page

[[File:trackingerror_troubleshooting_1.png|thumb|400px|'''Example case A.''' (1) Tracking error originally occurs because motor output current gets saturated to maximum configured [[MMC]] parameter value of 2.0 Amps (first graph). (2) This leads to growing position tracking error (second graph) and fault gets triggered when error grows larger than 300 counts (set by parameter [[FPT]]). The third graph shows [[HV DC bus]] voltage which stays within valid range, so no reason for fault there.]]
[[File:trackingerror_troubleshooting_2.png|thumb|400px|'''Example case B.''' Fault error occurs because [[HV DC bus]] voltage drops under high motor current load. This causes Undervoltage fault to activate, and possibly other faults (such as Tracking error) to follow.]]
Position control fault can occur due to several reasons. This page gives tips how to troubleshoot the reason of the fault.
==Using fault status information==
Method for finding the root cause of the fault: check [[Fault location]] from Granity Testing tab (scroll down the page to find Fault location numbers). This indicates the fault that occurred first of all faults, and is likely the reason causing rest of the faults as well.

Some most typical reasons that may happen:
* Insufficient torque on motor: motor will lag behind if it is not allowed to produce enough torque to overcome load resistance (see scope examples below). Solutions: decrease acceleration/velocity rates or increase motor current limits to get more torque.
* Undervoltage fault: [[HV DC bus]] power supply dropped voltage under the load and caused drive to fault stop
* Tracking error occurred: too tight tracking error tolerance (see {{param|FPT}}) and [[Servo motor tuning guide]]
==Using Granity scope==
One of most effective ways to find reason for fault is to use scope capture in Granity. In this example, we capture signals revealing fault reason in example cases:
#Choose Capture on fault as trigger
#Choose quite low sample rate, such as 500 Hz
#Choose channels Torque achieved, Torque setpoint, HV bus voltage and Tracking error
#Untick ''Continuously repeating capture''
#Start capture
#Perform the operation that causes the fault

If you can't reproduce the fault while Granity is connected, you may use the [[Downloading offline scope capture in Granity|offline capture feature]].

{{tip|The method above is most effective with latest firmware version and Granity version that support offline capture and capture trigger delay. In older versions ''Capture on fault'' records data only ''after'' the fault, which may not provide very useful information, while the new version records also events ''before'' the fault.}}

@@ Line 27: / Line 27: @@
-If your drive firmware and Granity supports trigger delay, there will be ''[TDL] Capture time delay spinbox'' in the Testing page.}}
+If your drive firmware and Granity supports trigger delay, there will be ''[TBT] Capture before trigger event'' spinbox in the Testing page.}}
 [[Category:Troubleshooting]]
 [[Category:Granity troubleshooting]]
 [[Category:Granity user guide]]

@@ Line 24: / Line 24: @@
 If you can't reproduce the fault while Granity is connected, you may use the [[Downloading offline scope capture in Granity|offline capture feature]].
-{{tip|The method above is most effective with latest firmware version and Granity version that support offline capture and capture trigger delay. In older versions ''Capture on fault'' records data only ''after'' the fault, which may not provide very useful information, while the new version records also events ''before'' the fault.}}
+{{tip|The method above is most effective with latest firmware version and Granity version that support offline capture and capture trigger delay. In older versions ''Capture on fault'' records data only ''after'' the fault, which may not provide very useful information, while the new version records also events ''before'' the fault.
 [[Category:Troubleshooting]]
 [[Category:Granity troubleshooting]]
 [[Category:Granity user guide]]

@@ Line 1: / Line 1: @@
 [[File:trackingerror_troubleshooting_1.png|thumb|400px|'''Example case A.''' (1) Tracking error originally occurs because motor output current gets saturated to maximum configured [[MMC]] parameter value of 2.0 Amps (first graph). (2) This leads to growing position tracking error (second graph) and fault gets triggered when error grows larger than 300 counts (set by parameter [[FPT]]). The third graph shows [[HV DC bus]] voltage which stays within valid range, so no reason for fault there.
 The reason is also apparent from [[Fault location]] 140401.
 ]]
 [[File:trackingerror_troubleshooting_2.png|thumb|400px|'''Example case B.''' Fault error occurs because [[HV DC bus]] voltage drops under high motor current load. This causes Undervoltage fault to activate, and possibly other faults (such as Tracking error) to follow.
 The reason is also apparent from [[Fault location]] 140405.
 ]]
@@ Line 27: / Line 25: @@
 {{tip|The method above is most effective with latest firmware version and Granity version that support offline capture and capture trigger delay. In older versions ''Capture on fault'' records data only ''after'' the fault, which may not provide very useful information, while the new version records also events ''before'' the fault.}}

@@ Line 1: / Line 1: @@
-[[File:trackingerror_troubleshooting_1.png|thumb|400px|'''Example case A.''' (1) Tracking error originally occurs because motor output current gets saturated to maximum configured [[MMC]] parameter value of 2.0 Amps (first graph). (2) This leads to growing position tracking error (second graph) and fault gets triggered when error grows larger than 300 counts (set by parameter [[FPT]]). The third graph shows [[HV DC bus]] voltage which stays within valid range, so no reason for fault there.]]
+[[File:trackingerror_troubleshooting_1.png|thumb|400px|'''Example case A.''' (1) Tracking error originally occurs because motor output current gets saturated to maximum configured [[MMC]] parameter value of 2.0 Amps (first graph). (2) This leads to growing position tracking error (second graph) and fault gets triggered when error grows larger than 300 counts (set by parameter [[FPT]]). The third graph shows [[HV DC bus]] voltage which stays within valid range, so no reason for fault there.
 [[File:trackingerror_troubleshooting_2.png|thumb|400px|'''Example case B.''' Fault error occurs because [[HV DC bus]] voltage drops under high motor current load. This causes Undervoltage fault to activate, and possibly other faults (such as Tracking error) to follow.]]
 Position control fault can occur due to several reasons. This page gives tips how to troubleshoot the reason of the fault.
 ==Using fault status information==