Difference between revisions of "Template:DriveFaultbits"

From Granite Devices Knowledge Wiki
Jump to: navigation, search
[checked revision][checked revision]
(Created page with "{| class="wikitable" |- ! Name !! Description !! Troubleshooting !! Filter time before activation |- |Tracking error || Drive stopped due to position or velocity tracking erro...")
 
Line 1: Line 1:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Name !! Description !! Troubleshooting !! Filter time before activation
+
! Name !! Description !! Troubleshooting !! Filter time before activation<sup>1</sup>
 
|-
 
|-
 
|Tracking error || Drive stopped due to position or velocity tracking error getting larger than configured limit ({{param|FPT}} or {{param|FVT}})|| Check settings, operating conditions and fault limits to resolve. || {{param|FFT}}
 
|Tracking error || Drive stopped due to position or velocity tracking error getting larger than configured limit ({{param|FPT}} or {{param|FVT}})|| Check settings, operating conditions and fault limits to resolve. || {{param|FFT}}
Line 35: Line 35:
 
|Fault location ID||See [[Fault location]]|| ||
 
|Fault location ID||See [[Fault location]]|| ||
 
|}
 
|}
 +
1) The time duration that drive will allow fault condition be ''true'' before fault status is latched. Some faults have user adjustable time delay to reduce error sensitivity in dynamic conditions, such as rapid acceleration.

Revision as of 14:28, 16 June 2017

Name Description Troubleshooting Filter time before activation1
Tracking error Drive stopped due to position or velocity tracking error getting larger than configured limit (Position tracking error thresholdFPT or Velocity tracking error thresholdFVT) Check settings, operating conditions and fault limits to resolve. Goal faults filter timeFFT
Over velocity Motor has exceeded the speed limit defined at Over speed faultFEV Goal faults filter timeFFT
Hardware Drive internal error has occurred Possibly external interference (check wiring and EMI suppression) and stability of logic supply voltage. If problem stays, contact Granite Devices support. None
Over temperature Drive temperature has exceeded its maximum value None
Feedback Failure in feedback device has been detected None
Over current Measured current was exceeding the limit value (current spike) Check wiring or try different Over current toleranceFOC value Affected by Over current toleranceFOC
Internal comm error Drive internal error has occurred Possibly external interference (check wiring and EMI suppression) and stability of logic supply voltage. If problem stays, contact Granite Devices support. None
Power stage forced off True when some of the fault states is forcing power stage off to protect drive. Motor is freely spinning unless braked mechanically. None
Under voltage HV DC bus voltage below Under voltage fault thresholdFUV value Check voltage, parameters and safe torque off None
Over voltage HV DC bus voltage above Over voltage fault thresholdFOV value Check voltage and Over voltage fault thresholdFOV. If happens during motor deceleration, then a braking resistor is needed. None
Motion range Motor has been commanded outside the allowed travel boundary. I.e. driven to limit switch when Limit switch functionLFS is set to fault stop None
Firmware error Drive internal error has occurred Possibly external interference (check wiring and EMI suppression) and stability of logic supply voltage. If problem stays, contact Granite Devices support. None
Init Initialization failed. Possible reasons: drive disabled or faulted during initialization or initialization time-outed Check enable signal, parameters, wiring and faults None
Motion Motor stall or loss of feedback signal detected Adjust Motion fault thresholdFMO to larger value or disable Goal faults filter timeFFT
SimpleMotion SimpleMotion V2 Communication error detected, possibly connection lost, invalid parameter value is sent or transfer error caused by EMI or bad wiring None
Fault location ID See Fault location

1) The time duration that drive will allow fault condition be true before fault status is latched. Some faults have user adjustable time delay to reduce error sensitivity in dynamic conditions, such as rapid acceleration.