Inovance SV820 Servo Drive Fault Codes List

A comprehensive guide to Inovance SV820 premium servo fault codes. Troubleshoot functional safety errors, high-speed loop faults, and use InoDriverShop diagnostics.

Inovance SV820 Fault Codes Reference Table

Below is the complete list of fault codes, functional safety alarms, and troubleshooting actions associated with the SV820 series.

Inovance SV820 Servo Drive Fault Codes List

Inovance SV820 Servo Drive Fault Codes List

Fault Code and Meaning Cause and Remedy
E3.101
System parameter error		 Cause: The total number of parameters changes or values exceed limits (often after software update). Specific causes include:
1. Control power voltage drops instantaneously.
2. Instantaneous power failure during parameter storage.
3. Excessive write operations by host controller.
4. Software was updated.
5. The servo drive is faulty.

Remedy:
  • Check voltage during control power cutoff (L1C, L2C). Restore default settings (2002-20h = 1).
  • Increase power capacity or replace power supply. Restore default settings and write parameters again.
  • Power on the system again, restore default settings, and rewrite parameters.
  • Change the write method (reduce frequency). Replace servo drive if faulty.
  • Reset servo drive/motor model and restore default settings (2002-20h = 1).
  • If fault persists after initialization, replace the servo drive.
E3.102
Abnormal communication initialization of coprocessor		 Cause: Multi-core communication initialization fault or CPU core software version mismatch.
1. Software version of FPGA and CPU cores do not match.
2. The FPGA is faulty.

Remedy:
  • View FPGA (2001-03h), CUP0 (2001-04h), and CUP1 (2001-05h) versions. Contact Inovance technical support to update matching software.
  • If fault persists after several restarts, replace the servo drive.
E3.104
Abnormal communication or interrupt timeout of coprocessor		 Cause: Interrupt timeout on coprocessor/FPGA or cyclic access timeout.
1. The FPGA is faulty.
2. Abnormal communication handshake between FPGA and MCU.
3. Interrupt timeout on the MCU.

Remedy:
  • Power the servo drive off and on several times.
  • If the fault persists, replace the servo drive.
E3.105
Internal program error		 Cause: Abnormal parameter count during EEPROM read/write or abnormal value range.
1. An EEPROM fault occurs.
2. The servo drive is faulty.

Remedy:
  • Check causes according to E3.101. Restore default settings (2002-20h = 1) and power on again.
  • If fault persists after several restarts, replace the servo drive.
E3.106
Abnormal communication handshake of main processor		 Cause: Internal communication handshake issue. To distinguish specific causes, view internal fault codes in 200B-2Eh.

Remedy:
  • Refer to internal fault codes.
  • Check for related communication hardware faults.
E3.107
Main processor communication loss		 Cause: Cyclic handshake communication loss between main processor and coprocessor.
1. Internal communication failure.

Remedy:
  • Power off and on several times.
  • If fault persists, replace the servo drive.
E3.108
Parameter storage fault		 Cause: Parameter values cannot be written to or read from EEPROM.
1. Write operation is abnormal.
2. Read operation is abnormal.

Remedy:
  • Modify a parameter, power cycle, and check if saved.
  • If modification is not saved and fault persists after restarts, replace the servo drive.
E3.111
Abnormal parameters in group 2000h/2001h		 Cause: Parameter changes or limits exceeded in group 2000/2001.
1. Instantaneous power failure during parameter storage.
2. Power failure during writing serial encoder motor parameters.
3. Software is updated.
4. Servo drive is faulty.

Remedy:
  • Set servo drive model (2001-0Bh) to a wrong value, power cycle, then set to correct value and power cycle again.
  • Write serial encoder parameters using the software tool.
  • If fault persists after repeating the model setting steps, replace the servo drive.
E3.120
Mismatch of the product model		 Cause: Motor/Drive model mismatch, improper parameters, or wrong auto-tuned drive model.
1. Product (encoder, motor, drive) code does not exist (Internal code 1120 or 2120).
2. Power ratings do not match (Internal code 3120).
3. Drive unit model set improperly (mismatch with auto-tuned result).
4. FPGA software does not support motor code.

Remedy:
  • Set 2000-01h correctly per motor nameplate or replace with matching motor.
  • If drive model doesn't exist, set correctly per nameplate (Section 1.1).
  • Replace unmatched product according to configuration specifications (Section 1.4).
  • Set 2001-0Bh and 2001-3Fh to the same value, or replace drive unit.
  • Select appropriate FPGA software via 2000-01h (See 2001-03 settings for code support).
E3.121
Invalid S-ON command		 Cause: A redundant S-ON signal is sent when auxiliary functions are used.
1. S-ON switched on through communication while drive is enabled internally.

Remedy:
  • Switch off the S-ON signal sent from the host controller when using auxiliary functions (200D-03h, 04h, 0Ch).
E3.122
Motor mismatch in absolute position mode		 Cause:
1. The motor does not match in absolute position mode.
2. The motor code is set incorrectly.

Remedy:
  • View motor nameplate to verify multi-turn absolute encoder support.
  • Reset H00-00 (Motor code) according to the motor nameplate.
  • Replace with a matching motor if necessary.
E3.130
DI function setting error		 Cause:
  1. The same function is allocated to different DIs (Check parameters 2003-03h to 2003-11h).
  2. The DI function setting is wrong (Requirement: Axis No. + Supported DI function No.).

Remedy:
  • Allocate different DI functions to parameters allocated with the same function.
  • Set the values again according to requirements.
  • Restart the control circuit or switch off S-ON and send "RESET" signal to activate the allocation.
E3.131
DO function setting error		 Cause: The DO function setting is wrong. Check set values of 2004-01h (DO1 logic) and 2004-03h (DO2 logic).

Remedy:
  • Set the values again according to requirements (Axis No. + Supported DO function No.).
  • Restart the control circuit or switch off S-ON and send "RESET" signal.
E3.136
Data check error or no parameter stored in motor encoder ROM		 Cause:
  1. Servo drive model and motor model do not match.
  2. Parameter check error or no parameter in ROM of serial incremental encoder.
  3. Encoder cables connected improperly or loosely.
  4. Servo drive is faulty.

Remedy:
  • Replace by a matching servo drive and servo motor.
  • Use Inovance encoder cables; ensure secure connection without scratching/breaking.
  • Do not bundle encoder cables with power cables (RST, UVW). Route separately.
  • Connect cables according to correct wiring diagram.
  • Replace the servo drive if fault persists after restart.
E3.150
STO input protection		 Cause: The STO (Safe Torque Off) input protection applies.

Remedy:
  • Check STO input signals and wiring.
E3.201
Overcurrent		 Cause: Hardware overcurrent detected.
  1. Commands input simultaneously at start or too early.
  2. Motor cables loose/poor contact.
  3. Motor cables are grounded (short to PE).
  4. Motor UVW cables short-circuited.
  5. Motor is burnt down.
  6. Gain set improperly (motor oscillates).
  7. Encoder cable wired incorrectly, aging, or corroded.
  8. Servo drive is faulty.
  9. Regenerative resistor overcurrent.

Remedy:
  • Ensure S-ON signal is on before inputting commands; add reference filter time.
  • Tighten loosened cables.
  • Replace motor if insulation resistance is poor (MΩ-level).
  • Check for shorts/burrs and connect cables correctly.
  • Replace motor if resistance is unbalanced.
  • Carry out gain adjustment.
  • Re-solder, tighten, or replace the encoder cable.
  • Replace the servo drive.
  • Select new regenerative resistor value/model and reconnect.
E3.202
Soft start relay disconnected		 Cause: The soft start relay is disconnected.

Remedy:
  • Check internal relay or replace servo drive.
E3.206
Switching frequency error		 Cause: The motor control is abnormal.

Remedy:
  • Check motor control settings or contact manufacturer.
E3.208
FPGA sampling operation timeout		 Cause: Internal fault code (200B-2Eh).
  1. Code 2208: Encoder wiring incorrect, loose, too long, or interference.
  2. Code 3208: Current sampling timeout (Large interference or damaged internal chip).
  3. Code 0208: FPGA operation timeout.

Remedy:
  • Use shielded twisted pair cables provided by Inovance.
  • Check connectors for good contact and retracted pins.
  • Route motor and encoder cables separately from high-voltage cables.
  • Ensure servo motor and drive are grounded properly.
  • Replace servo motor or drive if hardware is damaged.
E3.210
Output shorted to ground		 Cause: The servo drive detects abnormal motor phase current or bus voltage during self-check upon power-on. Root causes include shorted power cables, shorted motor, or a faulty drive.

Remedy:
  • Disconnect the motor cables and measure whether the servo drive power cables (UVW) are shorted to ground (PE); re-connect or replace cables.
  • Measure insulation resistance between the servo drive UVW sides and the grounding cable (PE); replace the motor if resistance is low.
  • If the fault persists after removing power cables and power cycling, replace the servo drive.
E3.220
Wrong UVW phase sequence		 Cause: Incorrect UVW phase sequence is detected during angle auto-tuning.

Remedy:
  • Check whether the phase sequence of the power cable is correct.
  • Change any two phase sequences and perform angle auto-tuning again.
E3.234
Runaway		 Cause: The torque reference direction is in reverse to the speed feedback. Issues may include incorrect phase sequence, interference signals, wrong encoder model/wiring, or loose connections.

Remedy:
  • Connect the UVW cables according to the correct phase sequence.
  • Power on the servo drive again to clear interference errors.
  • Check motor/drive nameplates (e.g., SV820 series with 20-bit motor) and ensure encoder type matches.
  • Re-solder, tighten, or replace the encoder cable if corroded or loose.
E3.400
Main circuit overvoltage		 Cause: DC bus voltage exceeds threshold (420V for 220V drive). Caused by high input voltage, unstable power supply, regenerative resistor failure, insufficient braking energy absorption, or abrupt deceleration.

Remedy:
  • Measure input voltage (RST); replace or adjust power supply to meet specifications (220-240V).
  • Connect a surge protection device.
  • Measure external regenerative resistor (between P and C); replace if infinite/disconnected.
  • Set parameters 2002-1Bh and 2002-1Ch correctly for the external resistor.
  • Increase the acceleration/deceleration time.
  • If bus voltage sampling deviates greatly (200B-1Bh > 420V but actual is lower), contact technical support.
  • Replace the servo drive if fault persists.
E3.410
Main circuit undervoltage		 Cause: DC bus voltage is lower than threshold (200V). Caused by unstable power, instantaneous power failure, voltage drops during running, or phase loss.

Remedy:
  • Increase the power capacity.
  • Check if power supply is applied to other devices causing voltage dips.
  • Check main circuit wiring for phase loss; replace cables and connect properly.
  • If fault persists after power cycling, replace the servo drive.
E3.420
Main circuit phase loss		 Cause: Phase loss on three-phase drive. Caused by loose cables, single-phase supply used on 3-phase drive, or imbalanced supply.

Remedy:
  • Replace cables and connect the main circuit cables properly.
  • If using single-phase supply on a 3-phase drive (0.75kW models), set H0A-00 to 2 (Inhibit fault).
  • Replace or adjust power capacity if voltage is imbalanced/low.
  • Replace the servo drive.
E3.430
Control power undervoltage		 Cause: Phase loss occurs on the AC input of the control circuit, or input is unstable.

Remedy:
  • Check whether control power cables are well connected.
  • Re-connect or replace control power cables.
E3.500
Motor overspeed		 Cause: Actual speed exceeds threshold. Caused by incorrect phase sequence, improper threshold setting (200A-09h), input reference exceeding limits, or speed overshoot.

Remedy:
  • Connect cables according to the correct phase sequence.
  • Re-set overspeed threshold (200A-09h) according to mechanical requirements.
  • Position Control: Decrease reference increment, gear ratio, or increase accel/decel ramp.
  • Speed Control: Decrease target velocity, speed limit, and gear ratio.
  • Torque Control: Set speed limit to a value smaller than overspeed threshold.
  • Adjust gain or mechanical running conditions to reduce overshoot.
  • Replace the servo drive.
E3.602
Angle auto-tuning failure		 Cause:
Abnormal jitter occurs on the encoder feedback during angle auto-tuning, or encoder feedback data error occurs.

Remedy:
  • Check if the encoder communication suffers from interference.
  • Check the encoder cable connections.
E3.610
Servo drive overload		 Cause:
The servo motor temperature reaches the over-temperature threshold.

Remedy:
  • Check cooling conditions and motor load (Refer to solutions for E3.620).
E3.620
Motor overload		 Cause:
The servo motor temperature reaches the over-temperature threshold. Root causes include improper wiring, heavy load, frequent accel/decel, improper gain, incorrect model setting, or mechanical locked-rotor.

Remedy:
  • Connect cables according to the correct wiring diagram (use Inovance cables if possible).
  • Replace with a servo drive of larger capacity and matching motor, or reduce load.
  • Increase the acceleration/deceleration time during single-cycle running.
  • Adjust the gain again if motor vibrates or produces abnormal noise.
  • Set the servo drive model (2001-0Bh) and motor model (2000-06h) correctly.
  • Eliminate mechanical factors causing locked-rotor.
  • Replace the servo drive if faulty.
E3.630
Locked-rotor over-temperature protection		 Cause:
The actual motor speed is lower than 10 RPM but the torque reference reaches the limit and lasts for the defined time. Caused by phase loss, disconnected cables, or mechanical locked-rotor.

Remedy:
  • Check UVW output phase sequence; connect cables again according to diagram or replace cables.
  • Check cable connections; reconnect or replace encoder/power cables.
  • Eliminate mechanical factors preventing rotation (check RUN command vs motor speed).
E3.650
Heatsink over-temperature		 Cause:
The temperature of the power module is higher than the over-temperature protection threshold.

Remedy:
  • Improve cooling conditions to reduce ambient temperature.
  • Wait 30s before reset after overload; increase drive capacity or acc/dec time.
  • Replace servo drive if the fan is damaged.
  • Install the servo drive according to installation requirements (clearance/direction).
  • Replace the servo drive if fault persists after power cycle.
E3.731
Encoder battery failure		 Cause:
The battery voltage of the absolute encoder is lower than 3.0 V, or battery was not connected during power-off.

Remedy:
  • Set 200D-15h to 1 to clear the fault (if battery is connected).
  • Replace with a new battery of matching voltage.
E3.733
Encoder multi-turn counting error		 Cause:
The encoder multi-turn counting value is wrong (Encoder faulty).

Remedy:
  • Set 200D-15h to 2 to clear fault. If fault persists after power cycle, replace the motor.
E3.735
Encoder multi-turn counting overflow		 Cause:
The number of unidirectional revolutions of the absolute encoder exceeds 32767 in linear mode.

Remedy:
  • See operation instructions for absolute encoder.
  • This fault can be hidden if multi-turn position is not needed but single-turn is required.
E3.740
Encoder interference		 Cause:
Encoder communication suffers from interference (wiring, vibration, Z signal interference, or faulty encoder).

Remedy:
  • Connect encoder cables according to correct wiring diagram.
  • Ensure encoder terminals are connected securely to handle vibration.
  • Use shielded twisted pair cables; ensure good grounding; route motor and encoder cables separately.
  • Replace encoder cable. If fault persists, replace the servo motor.
E3.A33
Encoder data read/write error		 Cause:
Internal parameters of the encoder are abnormal.

Remedy:
  • Check cable connections; ensure proper routing and contact.
  • If fault persists after power cycling multiple times, replace the servo motor.
E3.B00
Excessive position deviation		 Cause:
The position deviation is larger than the value of 6065h in position control mode.

Remedy:
  • Check UVW phase sequence and connect cables correctly.
  • Reconnect or replace motor power/encoder cables.
  • Eliminate mechanical locked-rotor factors.
  • Adjust gain manually or perform gain auto-tuning.
  • Decrease position reference increment, profile velocity, or acceleration ramp.
  • Increase the value of 6065h (Following error window).
  • If position reference is not 0 but feedback is always 0, replace servo drive or motor.
E3.B01
Position reference incremental error		 Cause:
The target position increment in CSP mode is too large, or alignment issues during mode switchover.

Remedy:
  • Decrease position reference speed or acceleration/deceleration curve.
  • Assign the value of present position to the target position before mode switchover.
  • Assign present position to target position when switching to S-ON status.
  • Ensure target position is limited between [-2^31, 2^31 - 1].
  • Modify the gear ratio and related scale factors.
  • Select a motor that matches the requirement or reduce maximum running speed.
E3.B03
Electronic gear ratio over the limit		 Cause:
The electronic gear ratio exceeds the limit.

Remedy:
  • Set the gear ratio (6091-01h/6091-02h) according to the allowable range.
E3.D09
Software position setting error		 Cause: The lower limit of the software position is set to a value larger than the upper limit (Value of 607D-01 > 607D-02).

Remedy:
  • Reset the parameters so the lower limit is less than the upper limit.
E3.D10
Home setting error		 Cause: The home offset is beyond the software limit. The value of 607Ch (Home offset) is beyond the values of 607D-01 (Min. position limit) and 607D-02 (Max. position limit).

Remedy:
  • Reset the parameters.
E3.601
Homing warning		 Cause: The home is not found within the time defined, or the home/limit switch is abnormal.

Remedy:
  • If hardware DI is used, check wiring and allocation in group 2003h.
  • Monitor DI status (200B-04h) to see if the drive receives level changes.
  • If using Z signal, check the condition of the Z signal.
  • Increase the duration limit of homing (2005-24h).
  • If high-speed search is too slow, increase the speed value (6099-01h).
  • Check hardware switches; ensure limit signals are not activated simultaneously with the home signal.
E3.730
Encoder battery warning		 Cause: The battery voltage of the absolute encoder is lower than 3.0 V.

Remedy:
  • Measure battery voltage.
  • Use a new battery of matching voltage.
E3.908
Abnormal drive unit model		 Cause: The model of the drive unit detected is abnormal, contacts are poor, or EEPROM data is incorrect.

Remedy:
  • Set H01-10 to a proper value according to H01-62.
  • Ensure the drive unit is in good contact with the baseplate (check flat cable terminals).
  • If communication with EEPROM fails or version is outdated, set H0A-37 to 1 to hide this warning.
  • If temperature issues occur on specific axes (H0B45 = 0x4908), set the drive unit model (H01-10) correctly (e.g., to 6000X).
E3.909
Motor overload		 Cause: Motor temperature (60Z series) reached over-temperature threshold. Causes include poor cabling, excessive load, frequent accel/decel, or improper gain.

Remedy:
  • Connect cables according to the correct wiring diagram (recommend Inovance cables).
  • Replace with a servo drive of larger capacity and matching motor.
  • Reduce the load and increase acceleration/deceleration time.
  • Perform inertia auto-tuning and check if load inertia is too large.
  • Adjust the gain if the motor vibrates or generates noise.
  • Set the servo motor model (2000-06h) and drive model (2001-0Bh) correctly according to the nameplate.
  • Check for mechanical factors causing locked-rotor status.
  • Replace the servo drive if faulty.
E3.920
Regenerative resistor overload		 Cause: Regenerative resistor temperature exceeds set value. Issues with cabling, settings (H02-25, H02-27), or input voltage.

Remedy:
  • Check external resistor cable (P and C connection).
  • Set H02-25 correctly (1=Natural, 2=Forced air).
  • Select a proper regenerative resistor size.
  • Set H02-27 according to the actual resistance in use.
  • Check main circuit input voltage (220V/380V ranges).
  • If load inertia is too large, select a larger resistor and set H02-26 consistent with power.
  • Reduce load or increase cycle time if motor speed/braking is too high.
  • Replace the servo drive if faulty.
E3.922
Resistance of external regenerative resistor too small		 Cause: The value of H02-27 is smaller than the permissible minimum (H02-21).

Remedy:
  • Measure resistance between P and C.
  • If too small, connect a matching external resistor.
  • If resistance is correct physically, update H02-27 to match the actual resistance.
E3.939
Motor power cable disconnected		 Cause: Phase current < 10% of rated current, small speed but large internal torque reference.

Remedy:
  • Re-connect the motor power cables.
  • Replace with new cables if necessary.
E3.941
Parameter modifications activated at next power-on		 Cause: Parameters with "Effective time: Next power-on" were modified.

Remedy:
  • Power on the servo drive again.
E3.942
Parameter storage too frequent		 Cause: Total number of parameters modified at a time exceeds 200, or frequent EEPROM writes.

Remedy:
  • For parameters that do not need storage in EEPROM, set 200E-02h to 0 before writing.
E3.950
Forward overtravel		 Cause: DI function 14 (P-OT) valid or position feedback exceeds positive software limit (607D-02).

Remedy:
  • Send a reverse command to deactivate the logic of DI function 14.
  • Confirm whether the command profile is proper regarding software limits.
E3.952
Reverse overtravel		 Cause: DI function 15 (N-OT) valid or position feedback exceeds negative software limit (607D-01).

Remedy:
  • Send a reverse/forward command to deactivate the logic of DI function 15.
  • Confirm whether the command profile is proper regarding software limits.
E3.980
Encoder fault		 Cause: An internal encoder algorithm error occurred.

Remedy:
  • If fault persists after power cycling, replace the servo motor.
E3.990
Power input phase loss warning		 Cause: A 3-phase drive is running on single-phase power while H0A-00 is set to 1.

Remedy:
  • If connected to 3-phase, check for main circuit phase loss (Er.420).
  • If single-phase operation is intended and allowed, set H0A-00 to 0 (inhibit phase loss warning).
E3.998
Homing object dictionary setting error		 Cause: The homing mode (6098h) is set to a value not supported.

Remedy:
  • Set parameters according to the specifications.
E3.E20
Ethernet hardware error		 Cause: An Ethernet hardware fault occurred.

Remedy:
  • If fault persists after power cycling, replace the servo drive.
E3.E21
MAC address not programmed		 Cause: The MAC address of the servo drive is not programmed.

Remedy:
  • Consult with the service personnel of the manufacturer.
E3.E08
Abnormal switchover of network status		 Cause: Synchronization signal abnormal. Issues with cable, grounding, master clock, or network switchover logic.

Remedy:
  • Use shielded twisted pair cable and ensure good grounding.
  • Check network port for damage.
  • Check if master synchronous clock is activated.
  • If sync cycle is 0, restart network or check cabling sequence (IN/OUT).
  • Increase synchronization loss threshold (200E-21h) if cycle fluctuates.
  • Check the network status switchover program of the host controller.
E3.E09
No synchronization signal		 Cause: Clock not configured, improper master config, or reversed IN/OUT ports.

Remedy:
  • Fix master communication configuration or replace master (PLC).
  • Connect cables to IN and OUT ports in the correct sequence.
  • If slave controller chip is damaged (no signal on scope), replace the slave controller chip.
E3.E11
ESI configuration file not programmed		 Cause: ESI file missing (Slave ID is null) or drive is faulty.

Remedy:
  • Program the device configuration file.
  • If drive is faulty, replace the servo drive.
E3.E13
Synchronization cycle configuration error		 Cause: Sync cycle is not an integer multiple of the command scheduling cycle.

Remedy:
  • Modify synchronization cycle setting to be an integer multiple of command scheduling cycle.
  • Calculate via parameters H01-60 and H01-61.
E3.E15
Synchronization cycle error too large		 Cause: The error of the controller synchronization cycle exceeds the threshold.

Remedy:
  • Increase the value of 200E-21h.
 

How to Read SV820 Faults via InoDriverShop

The SV820 records more data points than any other drive in the Inovance lineup. In 2026, using the InoDriverShop PC software is the only way to fully utilize these diagnostic features.

  • Black Box Function: The SV820 features a dedicated “Black Box” that records high-frequency data immediately before and after a fault. Unlike standard snapshots, this provides a detailed waveform of the position, speed, and torque curves surrounding the event, allowing you to catch transient spikes that last only microseconds.
  • Functional Safety Diagnosis: The SV820 supports advanced safety functions (STO, SS1, SS2, SLS). If you encounter safety-related errors (Err.9xx), the software provides a specific safety status monitor. This reveals exactly which safety channel (A or B) tripped or if there was a discrepancy in the safety clock signals.
  • Frequency Analysis (Bode Plot): For “Vibration” or “Resonance” faults (Err.6xx), the SV820’s advanced tuning tools allow you to generate a Bode plot of the mechanical system. This visualizes the exact frequency of the mechanical resonance, allowing you to configure the automatic notch filters precisely.

Frequently Asked Questions (FAQ)

Q: What is the difference between an Alarm, a Fault, and a Safety Trip?

A: An Alarm (AL codes) is a warning that permits operation. A Fault (Err codes) stops the motor via the drive’s logic. A Safety Trip (often Err.9xx) is a hardware-level interruption where the safety module overrides the drive control to force a Safe Torque Off (STO) or Safe Stop 1 (SS1) condition.

Q: How do I reset an Inovance SV820 fault?

A: You can reset the drive using the following methods:

  1. Sending a Fault Reset command via the EtherCAT/PROFINET control word.
  2. Pressing the SET button on the keypad (for non-safety faults).
  3. For Safety Faults: You must first clear the safety violation (e.g., close the gate) and then trigger the specific “Safety Reset” signal defined in your safety logic.

Q: Where is the fault history stored?

A: The SV820 stores an extensive fault history in parameter group H02. Due to the “Black Box” feature, you can extract comprehensive waveform data for the most recent critical faults using the USB interface and InoDriverShop.

Comments

Post a Comment

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Complete guide to Allen Bradley Kinetix 5500 fault codes. Troubleshoot FLT codes, Single-Cable (DSL) feedback errors, shared bus faults, and perform diagnostics via Studio 5000. Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Kinetix 5500 Fault Codes Reference Table Fault Code and Meaning Cause and Remedy FLT S03 – MTR OVERSPEED FL Motor Overspeed Factory Limit Fault Cause: Motor speed has exceeded 125% of its maximum speed. Remedy: Check control loop tuning. FLT S04 – MTR OVERSPEED UL Motor Overspeed User Limit Fault Cause: Motor speed has exceeded motor overspeed user limit. Remedy: Check control loop tuning. Increase the Motor Overspeed UL attribute value. FLT S05 – MTR OVERTEMP FL Motor Overtemperature Factory Limit Fault Cause: Calculations based ...
Read more

Danfoss VACON 100 FLOW Drive Fault Codes List

Access the complete reference guide for Danfoss VACON 100 FLOW drive fault codes. Learn to diagnose Multipump communication errors, dry run faults, and use Vacon Live software. VACON 100 FLOW Fault Codes Reference Table VACON 100 FLOW Faults and Alarms VACON 100 FLOW - Fault Tracing Fault Code and Meaning Cause and Remedy Fault Code 1, ID 1 Overcurrent (Hardware Fault) Cause: There is too high a current (> 4 × IH) in the motor cable. a sudden heavy load increase a short circuit in the motor cables the motor is not the correct type the parameter settings are not properly made Remedy: Check the loading. Check the motor. Check the cables and connections. Make an identification run. Set the acceleration time longer (P3.4.1.2 and P3.4.2.2). Fault Code 1, ID 2 Overcurrent (Software Fault...
Read more

ABB ACH580 Drive Fault Codes List

Access the complete reference guide for ABB ACH580 HVAC drive fault codes. Learn to diagnose issues via the Hand-Off-Auto panel, BACnet integration, and Fireman’s Override. The ABB ACH580 is the industry-standard flagship drive for HVACR applications. Designed to control air handling units, cooling towers, and chillers, it ensures critical comfort and safety in buildings. When a malfunction occurs, the dedicated Hand-Off-Auto (HOA) control panel displays a 4-digit code alongside plain-text diagnostics, often integrated directly into the Building Management System (BMS). This guide provides the most updated reference to help you interpret these codes and maintain building environmental standards. ACH580 Fault Codes Reference Table Use the search bar below or browse the table to identify your specific error code: ABB ACH580 Drive Fault Codes List ABB ACH580 Drive Fault Codes List Fault Code and Meaning Cause and Remedy A2B1...
Read more