Difference between revisions of "Fault location"
From Granite Devices Knowledge Wiki
| [checked revision] | [checked revision] |
(combine tables & add servodrive class faults of ioni) |
(→List of Fault location values) |
||
| Line 48: | Line 48: | ||
|480601|| Invalid SMV2 command ||SMV2 application error | |480601|| Invalid SMV2 command ||SMV2 application error | ||
|- | |- | ||
| − | |480901||SMV2 communication timeout||SMV2 application error | + | |480901, 481201||SMV2 communication timeout||SMV2 application error |
|- | |- | ||
|480801||Invalid SMV2 SMP packet type ||SMV2 application error | |480801||Invalid SMV2 SMP packet type ||SMV2 application error | ||
|- | |- | ||
|480901||SMV2 packet CRC error || Communication error | |480901||SMV2 packet CRC error || Communication error | ||
| + | |- | ||
| + | |481001||SMV2 watchdog timeout || Communication error | ||
|- | |- | ||
|710301||Command queue to GraniteCore full||Programming error, contact developers | |710301||Command queue to GraniteCore full||Programming error, contact developers | ||
| Line 81: | Line 83: | ||
|- | |- | ||
|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 | |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 | |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 | ||
| + | |- | ||
| + | |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 | ||
| + | |||
|} | |} | ||
[[category:Granity user guide]] | [[category:Granity user guide]] | ||
Revision as of 12:43, 6 March 2015
Fault location 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 |
|---|---|---|
| 1-2 | Current sensing range exceeded | See solutions of 120 and 600. |
| 100,110,200,220,2100-2126 | Loading or saving settings in drive memory failed | Programming error, contact developers |
| 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. |
| 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 |
| 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 |
| 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 |
| 5500 | Motor type MT not selected | Choose MT |
| 5501 | Unsupported motor type MT not selected | Choose MT |
| 6601 | 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 |
| 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 |
| 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 |
| 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 |
| 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 | Undervoltage at 5V line | Provide stable 5V supply to drive |
| 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 |
| 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 |
