Editing Fault location

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help page.

Latest revision Your text
Line 33: Line 33:
 
|-
 
|-
 
| 480301|| Extracting payload from SMV2 packet failed || Check SMV2 communication
 
| 480301|| Extracting payload from SMV2 packet failed || Check SMV2 communication
|-
 
| 480401, 480402, 480403, 480404 || Inserting requested return data packet into outbound SM packet caused overflow (requested return value did not fit in the 120 byte payload).
 
 
Fault location number depends on the size of return data value which caused the overflow: 480401 for SMPRET_32B value type, 480402 for SMPRET_24B value type, 480403 for SMPRET_16B value type, 480404 for SMPRET_CMD_STATUS type.
 
|| SMV2 application error as it has requested larger amount of return data that fits in payload buffer. If you have written low level SM communications, check your payload management. If you used higher level SM library commands, please report us which function has caused this and how to reproduce the issue.
 
 
|-
 
|-
 
| 480501|| SMV2 buffer overflow ||  SMV2 application error
 
| 480501|| SMV2 buffer overflow ||  SMV2 application error
Line 95: Line 90:
 
|This fault location never appears on standard firmware releases. Try a standard firmware if possible, or ensure that motor settings are the ones that are listed as supported for the custom firmware.
 
|This fault location never appears on standard firmware releases. Try a standard firmware if possible, or ensure that motor settings are the ones that are listed as supported for the custom firmware.
 
|-
 
|-
|250101 || Drive initialization has timeouted while waiting motor current sensor signals to stabilize (while motor phases were short circuited to GND by drive). Possible reasons:
+
|250101 || Motor initialization failed due to motor has rotated during initialization process (drive has timeouted when waiting motor current to stabilize near zero while motor phases were short circuited to GND by drive) ||
* Motor initialization failed due to motor has rotated during initialization process
+
* Electrical noise is disturbing current sense circuit of drive
+
||
+
 
* Ensure that motor is standing still before initialization starts
 
* Ensure that motor is standing still before initialization starts
 
* Ensure proper cabling (shielded cable on motor and connected to drive)
 
* Ensure proper cabling (shielded cable on motor and connected to drive)
 
* If necessary, add ferrite core filter on motor phases
 
* If necessary, add ferrite core filter on motor phases
* Try if error is affected by disconnecting external devices, such as encoder cable
 
 
For wiring guide, see product wiring manuals.
 
For wiring guide, see product wiring manuals.
 
|-
 
|-
Line 118: Line 109:
 
|Actual torque exceeded target torque indicating that torque controller might have became unstable.
 
|Actual torque exceeded target torque indicating that torque controller might have became unstable.
 
|Check parameters MR and ML which may cause instability or [[overshooting]] of torque. If unsure whether they are correct, see [[Tuning torque controller]]. If no help, then increase {{Param|FOC}}. Ultimately try setting FOC to Maximum.
 
|Check parameters MR and ML which may cause instability or [[overshooting]] of torque. If unsure whether they are correct, see [[Tuning torque controller]]. If no help, then increase {{Param|FOC}}. Ultimately try setting FOC to Maximum.
|-
 
|770100, 770101
 
|Serial encoder read failed
 
|Check serial encoder settings, wiring and compatibility. If occurs randomly, try to mitigate [[EMI]] errors. If problem persists, contact us for support with configuration & encoder details. This can also start to occur if encoder cable is too long (causing too much clock delay).
 
 
|-
 
|-
 
|770301
 
|770301
Line 130: Line 117:
 
|Serial encoder warning bit active
 
|Serial encoder warning bit active
 
|Check encoder condition and placement against scale if linear encoder. May be caused by EMI also; try to mitigate [[EMI]] errors.
 
|Check encoder condition and placement against scale if linear encoder. May be caused by EMI also; try to mitigate [[EMI]] errors.
 
|-
 
|192000
 
|Drive is waiting supply voltage to fall within valid range before continuing initialization.
 
|Ensure that there is some (at least 2%) headroom between {{param|FOV}}, {{param|FUV}} and actual measured supply voltage.
 
 
|-
 
|192001
 
|Drive is waiting STO to be released before continuing initialization.
 
|
 
 
|-
 
|192002
 
|Drive is waiting drive to be Enabled before continuing initialization.
 
|
 
 
 
|}
 
|}
  
Line 156: Line 127:
 
|-
 
|-
 
| 1-2 || Current sensing range exceeded || See solutions of 120 and 600.
 
| 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
 
| 100,110,200,220,2100-2126 ||  Loading or saving settings in drive memory failed || Programming error, contact developers
Line 191: Line 164:
 
|38xxxx || Writing/reading configuration parameters failed || Device may have damaged hardware or firmware bug
 
|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 || This may be caused by something disturbing analog circuits of the drive. This error is not dependent on any parameters of drive, however connected external circuits may cause interference to trigger this fault. If drive gives this fault with latest firmware and without motor, encoder or other I/O connected, then it hardware fault may be the reason. Check if PCB has visible damage, contact support if issue repeats.
+
|250102 || Current sensor ADC offset is above the self-test threshold || Check if PCB has visible damage, contact support if issue repeats
 
+
Note: IONI firmware older than 1.7.0 may rarely trigger this fault without real reason. Use 1.7.0 or later firmware to eliminate this chance.
+
 
|-
 
|-
 
|200901|| Drive detected undervoltage at logic supply || Check logic voltage supply stability and voltage reading
 
|200901|| Drive detected undervoltage at logic supply || Check logic voltage supply stability and voltage reading
Line 200: Line 171:
 
|Reading a SimpleMotion parameter failed
 
|Reading a SimpleMotion parameter failed
 
|Contact Granite Devices if problem repeats
 
|Contact Granite Devices if problem repeats
|-
 
|192111
 
|Drive has detected internal low memory level error. Indicates a firmware bug.
 
|Contact Granite Devices and let us know how to repeat the error
 
 
|}
 
|}
 
[[Category:Argon_troubleshooting]]
 
[[Category:IONI_troubleshooting]]
 
[[Category:Granity_user_guide]]
 

Please note that all contributions to Granite Devices Knowledge Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Granite Devices Knowledge Wiki:Copyrights for details). Do not submit copyrighted work without permission!

Select categories:

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)

Template used on this page: