Troubleshooting position control faults

From Granite Devices Knowledge Wiki
Revision as of 13:01, 7 May 2017 by Tero K (Talk | contribs) (Using Granity scope)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Jump to: navigation, search
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.
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.

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[edit | edit source]

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 Position tracking error thresholdFPT) and Servo motor tuning guide

Using Granity scope[edit | edit source]

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:

  1. Choose Capture on fault as trigger
  2. Choose quite low sample rate, such as 500 Hz
  3. Choose channels Torque achieved, Torque setpoint, HV bus voltage and Tracking error
  4. Untick Continuously repeating capture
  5. Start capture
  6. Perform the operation that causes the fault

If you can't reproduce the fault while Granity is connected, you may use the offline capture feature.

In no event the Product Information or parts hereof shall be regarded as guarantee of conditions or characteristics. The Product Information or any part thereof may also not be regarded as a warranty of any kind. No liability of any kind shall be assumed by Author with respect to Product Information or any use made by you thereof, nor shall Author indemnify you against or be liable for any third party claims with respect to such information or any use thereof.

As content of this Wiki may be edited by user community, Granite Devices Oy or it's affiliates do not take any responsibility of the contents of this Wiki. Use information at your own risk. However, Granite Devices staff attempts to review all changes made to this Wiki and keep information trustworthy.

Without written consent, Granite Devices' Products or Intellectual Property shall not be used in situations or installations where living beings, material property, or immaterial property could be harmed by the operation, features or failures of Product. Products may only be used in a way where hazards like moving parts, electric shock, laser radiation, or fire can't be realized even if the content of this Wiki would suggest otherwise.