Difference between revisions of "Fault location"
From Granite Devices Knowledge Wiki
| [checked revision] | [checked revision] |
(→Internal operation fault codes) |
(→Internal operation fault codes) |
||
| Line 82: | Line 82: | ||
|} | |} | ||
| − | == | + | ==Abnormal operation fault codes== |
| − | Drives are monitoring the internal functionality and the following faults indicate a problem that should | + | Drives are monitoring the internal functionality and the following faults indicate a problem that should not normally occur. These may originate from hardware problem ([[EMI]], supply voltage, bad hardware problem) or can be also a firmware bug. |
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
Revision as of 12:09, 23 June 2015
Fault location (a.k.a error codes) ID 1 & 2 that are displayed on Granity Testing tab Device state section. Fault locations are detailed numeric codes giving a hint what was the precise reason causing a fault state. The following table lists fault location numbers and their reasons.
List of Fault location values
| Fault location ID 1 or 2 | Reason | Solution |
|---|---|---|
| 120 | Short circuit protection triggered (very high & fast current rise detected) | Check wiring for shorts, ensure that motor inductance is sufficient (especially ironless & pancake motors), perform Tuning position controller, adjust FOC. |
| 600 | Overcurrent protection triggered (slower reaction but lower current level than short circuit protection) | Check wiring for shorts, ensure that motor inductance is sufficient (especially ironless & pancake motors), perform Tuning position controller, adjust FOC. |
| 3001 | Hall sensors are enabled but no valid signals present (all hall inputs 0's or 1's which is illegal state) | Check wiring and settings |
| 5500 | Motor type MT not selected | Choose MT |
| 5501 | Unsupported motor type MT not selected | Choose MT |
| 6601, 440501 | Phasing a.k.a. phase search failed | Check motor settings, wiring and supply voltage. Also happens if drive is disabled or hit limit switch during initialization. |
| 6602 | Phasing a.k.a. phase search failed due to both limit switches being open | Check limit switch settings and switch operation |
| 480301 | Extracting payload from SMV2 packet failed | Check SMV2 communication |
| 480501 | SMV2 buffer overflow | SMV2 application error |
| 480502 | SMV2 command corrupted because it has overflown payload buffer size | SMV2 application error |
| 480503 | SMV2 return data buffer overflow | SMV2 application error |
| 480601 | Invalid SMV2 command | SMV2 application error |
| 480901, 481201 | SMV2 communication timeout | SMV2 application error |
| 480801 | Invalid SMV2 SMP packet type | SMV2 application error |
| 480901 | SMV2 packet CRC error | Communication error |
| 481001 | SMV2 watchdog timeout | Communication error |
| 100201 | Unsupported feedback device selected as position feedback device FBD | |
| 100202 | Unsupported feedback device selected as velocity feedback device FB2D | |
| 890101 | Resolver feedback device detected loss of input (input signal level less than 0.1V) | Check resolver wiring |
| 140401 | Position tracing error exceeded the tolerance specified by parameter FPT | Increase FPT or re-tune motor to achieve lower tracking error, or use lower motion speeds if motor is being driven above the maximum achievable speed or acceleration |
| 140402 | Velocity tracing error exceeded the tolerance specified by parameter FVT | Increase FVT or re-tune motor to achieve lower tracking error, or use lower motion speeds if motor is being driven above the maximum achievable speed or acceleration |
| 140403 | Velocity exceeded the limit defined by FEV | Increase FEV or avoid running motor too fast |
| 140404 | Overvoltage. HV DC bus exceeded the limit defined by FOV | Increase FOV or reduce supply voltage |
| 140405 | Undervoltage. HV DC bus was under the limit defined by FUV | Decrease FUV or increase supply voltage and ensure that PSU is capable of supplying demanded current surges without droop |
| 140406 | Overtemperature | Enhance drive cooling or reduce drive current limits |
| 140407 | STO has been activated, but can be be caused by a drop in logic supply voltage | Provide stable logic supply to drive and to STO inputs |
| 140301 | Limit switch is open while drive is set-up to fault when limit switch is hit | Prevent driving to limit switch or change LFS parameter |
| 140801 | Drive has operated over 200 seconds near the overvoltage limit (FOV parameter) which may cause regenerative resistor overheating | Increase FOV at least 10% above the average supply voltage or reduce supply voltage |
| 100201, 100202, 105001, 105201 | Unsupported feedback device has been selected | Choose another feedback device from Granity |
| 101103, 101101, 101102 | Reading device address setting failed | Check address setting resistor values and connection |
| 250101 | Motor initialization failed due to motor has rotated during initialization process (drive has timeouted when waiting it to stop) | Ensure that motor is standing still before initialization starts |
| 190601 | Motor initialization failed | Check settings and wirings, and that enable & STO signals stay stable during initialization |
| 440205 | Power stage forced off due to one or more of following reasons: over voltage, over temperature, over current, STO or short circuit active | |
| 440219 | In DC motor mode, parallel wired outputs are not sharing current properly | Check that outputs are wired parallel as instructed |
| 440502 | During Phasing a.k.a. phase search drive could not reach the desired motor winding current even at maximum output voltage | Check that HV supply voltage is not dropping during power on and motor is properly wired to drive. If still occurs, reduce motor peak and/or continuous current limits or increase supply voltage. |
| 441801 | Failed measurement of motor resistance & inductance due to one or multiple reasons: 1) because measurement was unable to reach the desired current level in motor 2) Motor was not standing still during test | If you wish to use the measurement function: try to reduce current limit parameter values MCC & MMC (and click Apply, and then Measure) OR increase HV supply voltage. Also ensure that motor is not being disturbed during the measure (all motor load unmounted). |
| 441802 | Failed measurement of motor resistance & inductance due to result values being off the sanity check limits | If motor has unusually low or high inductance/resistance (below 0.1mH, over 100mH, below 0.1 ohm or above 100 ohm), set them manually instead of using automatic measure |
Abnormal operation fault codes
Drives are monitoring the internal functionality and the following faults indicate a problem that should not normally occur. These may originate from hardware problem (EMI, supply voltage, bad hardware problem) or can be also a firmware bug.
| Fault location ID 1 or 2 | Reason | Solution |
|---|---|---|
| 1-2 | Current sensing range exceeded | See solutions of 120 and 600. |
| 2050 | Error originated from I/O side | See Fault location ID 2 for details |
| 100,110,200,220,2100-2126 | Loading or saving settings in drive memory failed | Programming error, contact developers |
| 2050 | Error originated from I/O side | See Fault location ID 2 for details |
| 2320,2321,2330,2340 | Communication error between GraniteCore processors | Contact Granite Devices if problem repeats |
| 3060 | Power stage fault signal active (possible overtemperature, logic circuit undervoltage, Safe torque off | Contact Granite Devices if problem repeats |
| 3070 | Power stage fault signal 2 active (possible overtemperature, logic circuit undervoltage, Safe torque off | Contact Granite Devices if problem repeats |
| 9996-9999 | Internal range check of internal variable failed | Programming error, contact developers |
| 100202 | GraniteCore status update failed | Programming error, contact developers |
| 600101-600106 | GraniteCore connection failed | Programming error, contact developers |
| 710301 | Command queue to GraniteCore full | Programming error, contact developers |
| 200101-200801 | I/O side CPU error interrupt triggered | Programming error or hardware issue (supply voltage? EMI?) |
| 100101 | Reading init state from GraniteCore failed | Programming error, contact developers |
| 101201, 101202 | Firmware checksum mismatch | Device may have damaged hardware |
| 101201, 101202 | Firmware checksum mismatch | Device may have damaged hardware |
| 38xxxx | Writing/reading configuration parameters failed | Device may have damaged hardware or firmware bug |
| 250102 | Current sensor ADC offset is above the self-test threshold | Check if PCB has visible damage, contact support if issue repeats |
