Difference between revisions of "Acquiring VSD-E/XE fault reason details"
From Granite Devices Knowledge Wiki
| [checked revision] | [checked revision] |
(→Fault location expanations) |
(→Fault location expanations) |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This article describes how to use TweakTool to read ''fault location'' parameter from drive to examine the detailed reason of drive fault. | This article describes how to use TweakTool to read ''fault location'' parameter from drive to examine the detailed reason of drive fault. | ||
| − | ==TweakTool== | + | ==Acquiring fault location== |
| + | ===TweakTool=== | ||
Tweak tool is a utily to read/write raw parameters from drive by using the USB adapter. TweakTool can be downloaded from [http://granitedevices.com/assets/files/TweakTool.zip this link]. The application does not require installing, just extract the ZIP file to local disc. | Tweak tool is a utily to read/write raw parameters from drive by using the USB adapter. TweakTool can be downloaded from [http://granitedevices.com/assets/files/TweakTool.zip this link]. The application does not require installing, just extract the ZIP file to local disc. | ||
| − | |||
====Preparations==== | ====Preparations==== | ||
#Remove any cable from drive CMD port (the 16 pin flat cable) | #Remove any cable from drive CMD port (the 16 pin flat cable) | ||
| Line 8: | Line 8: | ||
#Close GDtool if it's is running | #Close GDtool if it's is running | ||
#Launch TweakTool_1.0.exe | #Launch TweakTool_1.0.exe | ||
| − | ====Reading | + | ====Reading the fault location parameter==== |
These numbers are referencing to the image below. | These numbers are referencing to the image below. | ||
#Enter 15440 to parameter number | #Enter 15440 to parameter number | ||
| Line 16: | Line 16: | ||
[[File:Tweaktool usage.png]] | [[File:Tweaktool usage.png]] | ||
| − | ==Fault location expanations== | + | ===Fault location expanations=== |
| + | Fault location changes only during fault and does not stay in memory after power-off. Read fault location after fault has occurred before shutting down drive. | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| Line 25: | Line 26: | ||
| 2|| Overcurrent < -24A per phase | | 2|| Overcurrent < -24A per phase | ||
|- | |- | ||
| − | | 10 || PLL error | + | | 10 || PLL error (1) |
|- | |- | ||
| − | | 15 || Illegal opcode | + | | 15 || Illegal opcode (1) |
|- | |- | ||
| − | | 20 || Misalign data | + | | 20 || Misalign data (1) |
|- | |- | ||
| − | | 25 || HW stack error | + | | 25 || HW stack error (1) |
|- | |- | ||
| − | | 30 || Logic undervoltage < 2.2V | + | | 30 || Logic undervoltage < 2.2V (bad 12V input or overload on 5V lines) |
|- | |- | ||
| − | | 35 || Logic undervoltage < 2.7V | + | | 35 || Logic undervoltage < 2.7V (bad 12V input or overload on 5V lines) |
|- | |- | ||
| − | | 120 || | + | | 120 || Motor output short circuit |
|- | |- | ||
| − | | 600 || Overcurrent (user limit) | + | | 600 || Overcurrent (user limit exceeded) |
|- | |- | ||
| − | | 100,110 || Loading config fail | + | | 100,110 || Loading config fail (1) |
|- | |- | ||
| − | | | + | |219 || Motor type is DC or parallel DC but power outputs of drive are not connected properly parallel. In DC mode B & C should be parallel and in parallel DC mode A & D and B & C should be wired parallel to eliminate this error. See VSD-E/XE manual for more details. |
|- | |- | ||
| − | | 10000 || No fault location info (this value after normal power-up) | + | | 200,210,220 || Saving config fail (1) |
| + | |- | ||
| + | | 9996,9997,9998,9999 || Internal variable safe range check limits exceeded (1) | ||
| + | |- | ||
| + | | 10000 || No fault location info (this value after normal power-up). Most faults don't change fault location. | ||
|} | |} | ||
| − | [[Category:VSD-E/XE | + | (1) If encountered, please send us detailed report how this happened and how to reproduce the error |
| − | + | [[Category:VSD-E/XE troubleshooting]] | |
Latest revision as of 21:01, 10 September 2014
This article describes how to use TweakTool to read fault location parameter from drive to examine the detailed reason of drive fault.
Contents
Acquiring fault location[edit | edit source]
TweakTool[edit | edit source]
Tweak tool is a utily to read/write raw parameters from drive by using the USB adapter. TweakTool can be downloaded from this link. The application does not require installing, just extract the ZIP file to local disc.
Preparations[edit | edit source]
- Remove any cable from drive CMD port (the 16 pin flat cable)
- Follow instructions from 1-5 in TweakTool screen in order to be able to communicate to drive (see screenshot below). You may need to set Force SPI mode with GDtool if it's not selected.
- Close GDtool if it's is running
- Launch TweakTool_1.0.exe
Reading the fault location parameter[edit | edit source]
These numbers are referencing to the image below.
- Enter 15440 to parameter number
- Click Read parameter
- Observe that "Command OK" reads in the status bar. If some error is reported, connection didn't succeed. Ensure that earlier steps are followed.
- Fault location value should now display in parameter value
Fault location expanations[edit | edit source]
Fault location changes only during fault and does not stay in memory after power-off. Read fault location after fault has occurred before shutting down drive.
| Value | Meaning |
|---|---|
| 1 | Overcurrent > 24A per phase |
| 2 | Overcurrent < -24A per phase |
| 10 | PLL error (1) |
| 15 | Illegal opcode (1) |
| 20 | Misalign data (1) |
| 25 | HW stack error (1) |
| 30 | Logic undervoltage < 2.2V (bad 12V input or overload on 5V lines) |
| 35 | Logic undervoltage < 2.7V (bad 12V input or overload on 5V lines) |
| 120 | Motor output short circuit |
| 600 | Overcurrent (user limit exceeded) |
| 100,110 | Loading config fail (1) |
| 219 | Motor type is DC or parallel DC but power outputs of drive are not connected properly parallel. In DC mode B & C should be parallel and in parallel DC mode A & D and B & C should be wired parallel to eliminate this error. See VSD-E/XE manual for more details. |
| 200,210,220 | Saving config fail (1) |
| 9996,9997,9998,9999 | Internal variable safe range check limits exceeded (1) |
| 10000 | No fault location info (this value after normal power-up). Most faults don't change fault location. |
(1) If encountered, please send us detailed report how this happened and how to reproduce the error
