ABB MicroFlex e190 Servo Drive

ABB MicroFlex e190 Servo Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
20003 All axis warnings cleared (_ecAXIS_WARNINGS_CLEARED)	Cause: This information message can appear in the error log to indicate that all axis warnings have been cleared. Remedy: No Action required.
20004 Encoder battery low (_ecENCODER_BATTERY_LOW)	Cause: When using an encoder with battery backup (e.g. Smart Abs multi-turn) a battery low condition has been reported. Remedy: Consider changing the Encoder battery.
40006 Attempt to configure too many axes (_ecTOO_MANY_AXES)	Cause: The device configuration file has attempted to assign more axes than are available on the controller. Remedy: Re-run the System Configuration Wizard.
40007 CamBox segments have been skipped (_ecCAM_BOX_OVERRUN)	Cause: The cam box has skipped a segment. This can happen if the source is moving fast enough to cause a segment to be skipped. Remedy: See CAMBOX in Mint Workbench Help, look at “position array”. Either slow down the source or increase the size of the segments.
40012 A host event has failed with retries (_ecEVENT_RETRY_WARNING)	Cause: A host (i.e. ActiveX) event handler has failed to acknowledge an event that has been raised by the controller. There is a ‘time-out’ period of 1 second in which the host must acknowledge an event. Remedy: If the host does not acknowledge the event after 3 time-out periods, the controller generates warning 40012. See ERRDATA for details of the error.
40013 Attempted to assign too many servo axes (_ecTOO_MANY_SERVO_AXES)	Cause: During the processing of the ..CMCF / .DCF (device configuration file), too many servo axes were configured. Remedy: To fix this issue, use the System Config Wizard to reduce the number of configured servo axes.
40014 Attempted to assign too many stepper axes (_ecTOO_MANY_STEPPER_AXES)	Cause: During the processing of the ..CMCF / .DCF (device configuration file), too many stepper axes were configured. Remedy: To fix this issue, use the System Config Wizard to reduce the number of configured stepper axes.
40015 Attempted to assign too many virtual axes (_ecTOO_MANY_VIRTUAL_AXES)	Cause: During the processing of the ..CMCF / .DCF (device configuration file), too many virtual axes were configured. Remedy: To fix this issue, use the System Config Wizard to reduce the number of configured virtual axes.
40016 Attempted to assign too many remote axes (_ecTOO_MANY_REMOTE_AXES)	Cause: During the processing of the ..CMCF / .DCF (device configuration file), too many remote axes were configured. Remedy: To fix this issue, use the System Config Wizard to reduce the number of configured remote axes.
40021 All controller warnings cleared (_ecCONTROLLER_WARNINGS_CLEARED)	Cause: This information message can appear in the error log to indicate that all controller warnings have been cleared. Remedy: No Action Required.
40022 Last reset was not controlled (_ecRESET_NOT_CONTROLLED)	Cause: Last reset was not controlled. Remedy: To fix this issue, use the System Config Wizard to reduce the number of configured servo axes (Note: Verify if this remedy matches context, as per document source).
40023 Default MAC detected (_ecDEFAULT_MAC_DETECTED)	Cause: Default MAC has been detected, valid MAC address is not set. Remedy: Set valid MAC address.
40024 Could not open license file or Error reading license file (_ecMISSING_LICENCE_FILE)	Cause: Could not open license file or Error reading license file. Remedy: If this error is received, please contact ABB technical support.
40025 Licence file doesn’t match hardware ID (_ecFOREIGN_LICENCE_FILE_PRESENT)	Cause: Wrong licencing version or platform, or Flash unique ID does not match the one in the license file. Remedy: If this error is received, please contact ABB technical support.
40026 Invalid Licence file (_ecINVALID_LICENCE_FILE_PRESENT)	Cause: Licence data hash does not match the one in the Licence File. Remedy: If this error is received, please contact ABB technical support.
40027 Warning applying parameter value (_ecPARAM_WARNING)	Cause: This warning will be generated if an attempt is made to write to a parameter that is no longer supported. Remedy: If necessary recommission the drive to create a new parameter table.
40028 Warning fan fault (_ecFAN_FAULT_WARNING)	Cause: The fan is possibly faulty, unplugged or jammed. Remedy: Firstly ensure the latest firmware is in use (as the fan is controlled by firmware). Check the bottom of the drive to determine that the fan inlets are not blocked and the fan is rotating. If the drive fan does not turn see the drive installation manual for instructions on how to replace the fan.
4000 No autotuning error (_ecAUTOTUNE_SUCCESS)	Cause: There is no autotuning error. Remedy: No Action.
4001 Drive rating data invalid	Cause: One of the following conditions has not been met: 1. Drive bus nominal voltage < 1 2. Drive rated current <= 0 Remedy: Check memory module is connected correctly. Check power supply level is correct.
4002 Drive speed max invalid	Cause: DriveSpeedMax <= 0. Only check AutoTune test ID auoDESIGN_MOTION_CONTROL. Remedy: Re-run commissioning and check that DriveSpeedMax is set correctly.
4003 Config doesn’t support that test (_ecCONFIG_NOT_RIGHT_TYPE)	Cause: The autotuning operation does not support this controller configuration. Remedy: This error will not occur unless the configuration has been manually changed using the CONFIG keyword.
4004 Axis error has occurred (_ecAXIS_ERROR)	Cause: An asynchronous axis error or drive error has occurred during the autotuning operation. Remedy: See the Mint Workbench Motion toolbar for more information on the error.
4005 Calculated torque constant invalid	Cause: Drive had calculated a Torque Constant which is too small. Remedy: Check motor data is correct.
4006 Inductance value is zero	Cause: For the selected motor the winding inductance is zero. Remedy: To avoid this error, make sure that a motor has been selected from the database in the Drive Setup Wizard. Alternatively, if a custom motor has been selected and you are unsure of motor data, check that the “Measure motor resistance and inductance” test has been selected and run using the Autotune tool.
4007 Resistance value is zero (_ecZERO_RESISTANCE_VALUE)	Cause: For the selected motor the winding resistance is zero. Remedy: To avoid this error, make sure that a motor has been selected from the database in the Drive Setup Wizard. Alternatively, if a custom motor has been selected and you are unsure of motor data, check that the “Measure motor resistance and inductance” test has been selected and run using the Autotune tool.
4008 User has aborted test (_ecUSER_TEST_ABORT)	Cause: The autotuning operation has been manually aborted. Remedy: This will occur if the Autotune tool’s STOP button is clicked while tests are being performed.
4009 Cannot capture data during test (_ecCAPTURE_FAILED)	Cause: Many of the autotuning operations use the data capture facility. This error message can occur if the capture facility is in use prior to performing the autotuning operation. Remedy: Not normally a problem, but to prevent this before autotuning, type CP=0 in the Command window to halt any capture operations.
4010 Resistance too low, possible short circuit (_ecPOSSIBLE_SHORT_CIRCUIT)	Cause: This error can occur during the Measure motor resistance and inductance test and indicates that the effective motor winding resistance is very low. Remedy: Check that there are no short circuits between the U, V and W terminals of the motor. Check that the motor power cable is wired correctly.
4011 Autotuning doesn’t support feedback device (_ecUNSUPPORTED_FEEDBACK_TYPE)	Cause: The Test the feedback or Feedback calibration test (EnDat absolute encoders only) does not operate on this feedback type. Remedy: This error will not normally occur because Mint Workbench will not allow autotuning on unsupported feedback types. (i.e. the combination of Motor and Feedback device is not supported by Mint Workbench).
4012 Encoder resolver rotation sense is wrong (_ecFEEDBACK_SENSE_WRONG)	Cause: During the Measure the voltage constant and Measure the motor inertia tests, a torque is applied to the motor. This error will occur if the resulting motion is in the opposite direction to the torque (a positive torque should cause positive velocity). Remedy: The most common cause of this error is an incorrectly wired or set up feedback device (encoder or resolver), or an incorrectly wired motor. Select the Test the feedback option. This will indicate if there is a problem with the wiring or setup of the drive and will automatically compensate for certain wiring errors. Note that the Test the feedback test should ideally be run with the motor disconnected from the load. This error can also occur when autotuning a motor connected to some types of load (e.g. loads with high compliance or gravity offsets). It may be necessary to manually tune the system using the Fine-tuning tool.
4013 Hall sequence doesn’t behave as expected (_ecHALL_FAULT_OR_NO_ROTATION)	Cause: The Hall sequence doesn’t behave as expected. This error can occur during the “Test the feedback” test when using an incremental encoder + Halls feedback system. Remedy: The error can occur for a number of reasons, so try the following tests: Return to the Confirm Motor Information page of the Drive Setup Wizard to check these values. If the resolver is not a standard ABB product, check that the specification is compatible in the drive’s hardware manual. A common cause of this error is an incorrectly wired or set up encoder/resolver. Try manually moving the rotor and watching the position field in the Axis tab. If the position does not change, or it changes erratically, this indicates a problem with the encoder wiring. Run the “Test the feedback” test again. Ideally, the test should be run with the motor disconnected from the load, although it will operate successfully where the load is purely inertial or load friction is small. Note: Watch the movement of the rotor. For rotary motors, the shaft should rotate through just over one revolution in one direction followed by one revolution in the opposite direction. If the rotor moves significantly more or less than these distances, this indicates that the number of motor poles is not set correctly.
4015 Position control update rate invalid	Cause: Position loop control rate (ControlRate(0, 1)) < 1. Remedy: Change control rate to expected value (normally 4000).
4016 Mathematic error in gain calculations (_ecGAIN_CALCS_FAILED)	Cause: This error can occasionally occur during the Calculate current loop gains or Calculate the speed and position gains tests, indicating a numerical problem in the gain equations. It can also indicate a problem with the values of motor resistance and inductance (MOTORRS and MOTORLS) or inertia and damping. Remedy: The error can usually be cleared by changing the design bandwidth for the appropriate operation (click Options… in the Autotune tool). If that fails, try running the entire autotuning sequence again.
4017 Drive setup is invalid	Cause: This error can potentially occur in any of the autotuning operations, although it is rare. It indicates a problem with the fundamental setup of the drive such as the settings for motor rated current or peak current. Remedy: Try running the Commissioning Wizard again, making sure that the “I am starting a new application. Reset memory to factory defaults” option on the Welcome page is selected.
4018 Can’t fit model to voltage/current data (_ecCANNOT_FIT_RESISTANCE_MODEL)	Cause: During the Measure motor resistance and inductance test, the process is stopped when the drive current reaches 80% of the specified motor rated current value. Error 4018 will occur if there is not enough data in the voltage/current characteristic to perform the calculation. Remedy: Check the wiring between the drive and motor and the motor windings for open circuits.
4019 Can’t fit model to voltage/current transient (_ecCANNOT_FIT_INDUCTANCE_MODEL)	Cause: During the Measure motor resistance and inductance test, inductance is calculated from the resulting voltage/current characteristic. Error 4019 indicates that this calculation cannot be performed because of insufficient data or an unusual characteristic. Remedy: Try skipping the Measure motor resistance and inductance test. To do this, manually enter the motor resistance and inductance in the Confirm Motor Information page of the Drive Setup Wizard and confirm that the test is not selected in the Autotune tool. Once autotuning is complete, check that the response of the current controllers is satisfactory using the Fine-tuning tool’s Current tab.
4020 Can’t fit load model speed data (_ecCANNOT_FIT_LOAD_MODEL)	Cause: During the Measure the motor inertia test, the fitting process failed. A common cause for this is lack of sufficient information to fit the load model. Remedy: Click Options… in the Autotune tool and then select the Limits tab. Increase the value in the Max Travel box to allow the motor to rotate further during the test and consequently log more data. Note that loads with high coulomb or static friction will not conform well to an inertial load model. If the Measure the motor inertia test continues to fail, it may be necessary to manually tune the system using the Fine-tuning tool’s Speed and Position tabs.
4021 Motor test timed out (_ecAUTOTUNE_TEST_TIMEOUT)	Cause: During the Measure tests, the rotor did not reach a sufficient speed, or travel a sufficient distance, within the duration of the test. Error 4021 can occur if the torque (or force) generated by the motor is insufficient to overcome friction in the load. Remedy: Click Options… in the Autotune tool and then select the Limits tab. Increase the value in the Max Torque box to allow the motor to generate sufficient torque to overcome friction. If the test continues to fail, it may be necessary to manually tune the system using the Fine-tuning tool’s Speed / Velocity and Position tabs.
4022 Motor travelled too far during test (_ecAUTOTUNE_TEST_OVERTRAVEL)	Cause: Once the motor has reached a sufficient speed, the direction of applied current is reversed to bring the rotor to a halt within specified travel limits. Error 4022 indicates that the test was unable to impose these limits. Remedy: Click Options… in the Autotune tool and then select the Limits tab. Increase the value in the Max Travel box to allow the motor to rotate further during the test. Also, try reducing the value in the Max Speed box. If the test continues to fail, it may be necessary to manually tune the system.
4023 Not enough test data to analyse (_ecINSUFFICIENT_TEST_DATA)	Cause: Generally, error 4023 means that insufficient data was logged during the test to obtain accurate parameter measurement. Remedy: See errors 4018, 4019 and 4020 for the reasons why these tests fail.
4024 Flux model parameters are invalid (_ecINVALID_FLUX_MODEL)	Cause: The Measure the motor inertia test will fail with this error if the voltage constant has not been defined. Remedy: To determine the voltage constant, either select a standard motor from the database in the Drive Setup Wizard, enter a voltage constant value in the Confirm Motor Information page (see manufacturer’s motor data), or run the Measure the voltage constant test.
4025 Load model is invalid (_ecINVALID_LOAD_MODEL)	Cause: If this error occurs during the Measure the motor inertia test, it suggests that the characteristics of the load are such that inertia cannot be accurately calculated. Error 4025 can also occur during the Calculate the speed and position gains test if the values of load inertia and damping have not been defined. Remedy: See error 4020 for more information. In the second case, run the Measure the motor inertia test to measure load inertia and damping.
4026 Encoder parameter invalid	Cause: Either EncoderResolution < 1 or EncoderCycleSize = 0. Remedy: Correct Encoder parameters and re-run autotune tests.
4027 Motor inductance is not set	Cause: When motor type is AM, Lm or Llr <= 0. Remedy: To avoid this error, make sure that a motor has been selected from the database in the Drive Setup Wizard. Alternatively, if a custom motor has been selected and you are unsure of motor data, check that the “Measure motor resistance and inductance” test has been selected and run using the Autotune tool.
4028 Can’t set stator resistance (_ecCANNOT_SET_STATOR_RESISTANCE)	Cause: Can’t set stator resistance. Value calculated or set is outside the allowable range. Remedy: Error codes 4028 to 4054 will occur if the associated drive parameter is outside the allowable range of values. These errors should not normally occur. If the problems persist, make sure that a motor has been selected from the database in the Drive Setup Wizard. Alternatively, if a custom motor has been selected and you are unsure of motor data, check that the “Measure motor resistance and inductance” test has been selected and run using the Autotune tool. If the problem persists you will need to manually tune the control loops in the drive.
4029 Can’t set stator leakage inductance	Cause: Can’t set stator leakage inductance. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4030 Motor pole pitch invalid	Cause: Calculated motor pole pitch <= 0. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4031 Motor pole number invalid	Cause: Calculated motor poles < 2. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4032 Load inertia is not set	Cause: Calculated load inertia <= 0. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4033 Can’t set maximum motor flux (_ecCANNOT_SET_MOTOR_MAX_FLUX)	Cause: Can’t set motor flux model time constant. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4035 Can’t set load inertia (_ecCANNOT_SET_LOAD_INERTIA)	Cause: Can’t set load inertia. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4036 Can’t set load damping (_ecCANNOT_SET_LOAD_DAMPING)	Cause: Can’t set load damping. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4037 Can’t set controller proportional gain (_ecCANNOT_SET_GAIN_KIPROP)	Cause: Can’t set controller proportional gain. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4038 Can’t set current controller integral gain (_ecCANNOT_SET_GAIN_KIINT)	Cause: Can’t set current controller integral gain. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4039 Can’t set speed controller proportional gain (_ecCANNOT_SET_GAIN_KVPRO)	Cause: Can’t set speed controller proportional gain. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4040 Can’t set speed controller integral gain (_ecCANNOT_SET_GAIN_KVINT)	Cause: Can’t set speed controller integral gain. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4041 Can’t set position proportional gain (_ecCANNOT_SET_GAIN_KPROP)	Cause: Can’t set position proportional gain. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4042 Can’t set position derivative gain (_ecCANNOT_SET_GAIN_KDERIV)	Cause: Can’t set position derivative gain. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4043 Can’t set position integral gain (_ecCANNOT_SET_GAIN_KINT)	Cause: Can’t set position integral gain. Remedy: (See remedy for 4028). Check motor selection or manually tune.
4044 Can’t set velocity feedforward gain (_ecCANNOT_SET_GAIN_KVELFF)	Cause: Can’t set velocity feedforward gain. Remedy: N/A
4045 Can’t set velocity feedback gain (_ecCANNOT_SET_GAIN_KVEL)	Cause: Can’t set velocity feedback gain. Remedy: N/A
4046 Can’t set acceleration feedforward gain (_ecCANNOT_SET_GAIN_KACCEL)	Cause: Can’t set acceleration feedforward gain. Remedy: N/A
4047 Inertia test failed (_ecINERTIA_TEST_FAILED)	Cause: Inertia measurement failed. Remedy: N/A
4048 Voltage constant test failed (_ecVOLTAGE_CONSTANT_TEST_FAILED)	Cause: Voltage constant measurement failed. Remedy: Error codes 4028 to 4054 will occur if the associated drive parameter, calculated by one of the autotuning tests, or set by the user is outside the allowable range of values. These errors should not normally occur. If the problems persist: Make sure that a motor has been selected from the database in the Drive Setup Wizard. If a custom motor has been selected and you are unsure of motor data, check that the “Measure motor resistance and inductance” test has been selected and run using the Autotune tool. If the problem persists you will need to manually tune the control loops in the drive.
4049 Can’t set offset angle (_ecCANNOT_SET_ANGLE_OFFSET)	Cause: Can’t set motor feedback offset angle (Possible encoder fault or wrong config). Remedy: N/A
4050 Can’t set observer gain K1 (_ecCANNOT_SET_OBSERVER_GAIN_K1)	Cause: Can’t set observer gain K1. Remedy: N/A
4051 Can’t set observer gain K2 (_ecCANNOT_SET_OBSERVER_GAIN_K2)	Cause: Can’t set observer gain K2. Remedy: N/A
4052 Can’t set observer gain KJ (_ecCANNOT_SET_OBSERVER_GAIN_KJ)	Cause: Can’t set observer gain KJ. Remedy: N/A
4053 Can’t enable integral position control (_ecCANNOT_SET_KINT_MODE)	Cause: Can’t enable integral position control. Remedy: N/A
4054 Can’t set integral term limit (_ecCANNOT_SET_KINT_LIMIT)	Cause: Can’t set integral term limit. Remedy: N/A
4055 Invalid autotuning operation number (_ecINVALID_OPERATION)	Cause: This will only occur if Mint Workbench attempts to run an autotuning operation not supported by the firmware. Remedy: Check Drive parameters and Re-run Autotuning tests.
4060 Cannot enable drive (_ecCANNOT_ENABLE_DRIVE)	Cause: A drive cannot be enabled unless the hardware enable is configured but not active or the AC supply (or shared DC bus supply) is present. Remedy: Go to Mint Workbench Parameter view and Check: Enabling > DriveEnableInput setting is correct – if so ensure that the input is active before running autotune. To check drives connected voltage Go to Mint Workbench Parameter view and Check Drive > DriveBusVolts is at the correct level (325VDC for 230VAC supply).
4061 Drive communications error (_ecDRIVE_COMMS_ERROR)	Cause: Communication between the host PC and the controller has failed. Remedy: Check the serial or USB cable.
4063 Encoder fault (_ecPOSSIBLE_ENCODER_FAULT)	Cause: General Encoder fault. Remedy: Check encoder configuration, wiring and encoder operation when rotating by hand.
4065 Test move will take too long	Cause: Test move takes too long time in. Remedy: Check that test moves are set so that they will not take an excessive amount of time. Also check scaling is set correctly by checking SCALEFACTOR.
4066 Test move velocity is too high	Cause: Calculated velocity > DriveSpeedMax in velocity autotune. Remedy: Re-run commissioning and check that DriveSpeedMax is set correctly.
4067 Motor rated current undefined	Cause: Motor rated current < 0.2A. Remedy: Check Motor data is correct. If the motor current is below 0.2A then it is too small to be controlled by the drive.
4068 Current control loop is not tuned	Cause: Current loop has not been tuned before performing the Rotor parameters autotuning (applicable to asynchronous motors only). Remedy: Re-run Autotuning.
4069 Autotuning doesn’t support motor type	Cause: Cannot do the wanted Autotune for this motor type. Remedy: Check Motor data is correct.
4070 Can’t set flex control proportional gain	Cause: Can’t set flux control loop proportional gain. Remedy: Check Motor data is correct.
4071 Can’t set flex control integral gain	Cause: Cannot be shown because there is no error in API. Remedy: Check Motor data is correct.
4074 Can’t set magnetizing inductance	Cause: Cannot set motor Lm. Remedy: Check Motor data is correct.
6001 Parameter value out of range (_ecPARAM_VALUE_OUT_OF_RANGE)	Cause: The value supplied for the parameter is out of range. Remedy: The value you have entered or that is stored in the parameter file (.ptx) you have loaded does not fit within the limits specified by the drive firmware version loaded. If needed update the firmware first then load the parameter file. To do this in Mint Workbench go to Tools > Download Firmware > Select and download firmware file. Once complete try again.
6004 Parameter definition has changed (_ecPARAM_DEFINITION_ERROR)	Cause: The specified parameter exists, but its definition has changed. Remedy: Check the latest documentation for the parameter.
8000 EtherCAT AL status code (_ecETHERCAT_AL_STATUS_CODE)	Cause: This error is listed together with a Profile Code in the Mint Workbench Error Log. Note: The displayed profile code must be converted to hexadecimal to give the specific EtherCAT error code. Remedy: This error status indicates that the EtherCAT master has been sent an error code by the drive. Check the error log to determine what the “real” drive error code is.
8001 CIP configuration error (_ecCIP_CFG_ERROR)	Cause: This error is listed together with a Profile Code in the Mint Workbench Error Log. The displayed profile code must be converted to hexadecimal to give the specific CIP general status code. Remedy: This error status indicates that the EtherCAT master has been sent a CIP error code by the drive. Check the error log to determine what the “real” drive error code is.
8002 POWERLINK error code (_ecPOWERLINK_ERROR)	Cause: This error is listed together with a Profile Code in the Mint Workbench Error Log. The displayed profile code must be converted to hexadecimal to give the specific POWERLINK error code. Remedy: This error status indicates that the POWERLINK master has been sent an error code by the drive. Check the error log to determine what the “real” drive error code is.
8003 PROFInet error code (_ecPROFINET_CFG_ERROR)	Cause: This error is reported when multicast MAC filter configuration fails. Remedy: This error status indicates that the PROFInet master has tried to configure the device ID but has failed.
10000 Motion aborted (_ecABORT)	Cause: This error is caused by using the ABORT keyword or breaking a Mint program. See ABORT and ABORTMODE. Remedy: The ABORT keyword has been issued by the mint program. This may be normal in the operation. If its not, find the issue with the Mint program.
10001 Forward hard limit hit (_ecFWD_HARD_LIMIT)	Cause: Drive has been configured to have a Forward Limit input and its currently active. Remedy: Check Drive configuration, Mint Program and/or Parameter file. See LIMITFORWARD and LIMITMODE.
10002 Reverse hard limit hit (_ecREV_HARD_LIMIT)	Cause: See LIMITREVERSE and LIMITMODE. Remedy: Check Drive configuration, Mint Program and/or Parameter file. See LIMITREVERSE and LIMITMODE.
10003 Forward soft limit hit (_ecFWD_SOFT_LIMIT)	Cause: The axis may be configured to have a maximum and minimum limit of travel in software. If the axis position exceeds one of these limit values, a motion error will be generated. Remedy: Check Drive configuration, Mint Program and/or Parameter file. See SOFTLIMITFORWARD and SOFTLIMITMODE.
10004 Reverse soft limit hit (_ecREV_SOFT_LIMIT)	Cause: The axis may be configured to have a maximum and minimum limit of travel in software. If the axis position exceeds one of these limit values, a motion error will be generated. Remedy: Check Drive configuration, Mint Program and/or Parameter file. See SOFTLIMITREVERSE and SOFTLIMITMODE.
10005 Fatal following error exceeded (_ecFOLLOWING_ERROR)	Cause: FOLERRORFATAL sets the maximum permissible following error before an error is generated. The following error is defined as the demand position minus the actual motor position. If the following error exceeds the value set by FOLERRORFATAL (maximum following error) an error may be generated. Remedy: If this error occurs the axis may not be free to move, is moving when it should not (e.g. a suspended load with a bad motor brake) or there could be a limitation within the drive (e.g. current or speed limit) or motor size (e.g. Inertia) that stops it moving to the target position with the given ACCEL/DECEL rates before the following error is beyond the value set by the user. See FOLERRORFATAL and FOLERRORMODE. Note: If this error occurs when using a Smart Inc encoder, see Smart Inc encoders in Mint Help.
10006 Fatal velocity error exceeded (_ecVEL_FATAL)	Cause: VELFATAL, velocity error checking allows the measured velocity (VEL) of an axis to be compared to its demand velocity (VELDEMAND). If the difference between the two values exceeds the limit set with VELFATAL, then an error will be created. Remedy: Check the Mint program or other source of velocity demand is not attempting to run the axis faster than the programmed DRIVESPEEDMAX.
10007 Error input active (_ecERROR_INPUT)	Cause: An input is defined as an ERRORINPUT and it is activated by an error condition. Remedy: See ERRORINPUT and ERRORINPUTMODE.
10009 Invalid trajectory (_ecPROFILE_ERROR)	Cause: Trajectory generation error. The controller was unable to perform the requested profile. This can occur during CAM moves if an invalid element is detected (e.g. a negative master distance). An axis performing a cam profile can skip over very short slave segments if the master velocity is such that the slave segment is less than one profiler tick in length. If more than 5 slave segments are skipped in one profiler tick, this error will be generated. The axis will be crash stopped and disabled. Remedy: Check Mint CAM parameter file for anamolous Data points. Excel is a helpful tool to help with this.
10010 Drive enable input is inactive (_ecDRIVE_ENABLE_INACTIVE)	Cause: DRIVEENABLEINPUTMODE is configured to _emCRASH_STOP_DISABLE and the input defined by DRIVEENABLEINPUT has become inactive whilst the drive was enabled. Remedy: Check Digital Input status and correct.
10011 Drive I.T exceeded limit (_ecDRIVE_OVERLOAD)	Cause: The drive overload algorithm has integrated up to 100% and has tripped the drive to protect it. This will happen if the RMS current for the application exceeds the DRIVERATEDCURRENT value. Remedy: Check tuning, check motion profile (especially acceleration and deceleration). If necessary select a larger drive (which may also require an alternative motor).
10012 Power base is not ready to enable (_ecPOWER_BASE_NOT_READY)	Cause: The Power base has been asked to enable but is not ready. For it to be so it must have the correct voltage and supply and not be overheated. Remedy: Check of power base ambient conditions and supply voltage. Include interlocks in any program being used that check DRIVEENABLEREADY.
10013 Power module has an error (_ecPOWER_MODULE_FAULT)	Cause: There’s circuit detection in power unit and the signal is connected to the DSP. The power unit generated an error while in operation. Over current, earth fault, over temperature on power board. Remedy: Possible causes of this are Over temperature, Over Current, Brake chopper Short circuit or poor earthing or shielding (particularly of motor power cables). Power cycle to clear the error.
10014 Over current trip (_ecOVER_CURRENT)	Cause: Based on the drives currently configured DRIVERATINGZONE the drive has detected a motor overcurrent state. Measured current should not exceed the maximum current. The maximum current is related with the over current and the rated current. Remedy: Check the motor is free to rotate, has been sized correctly and there are no short circuits on the drive output wiring.
10015 Over speed trip (_ecOVER_SPEED)	Cause: The drive has detected the apparent motor velocity has exceeded the trip threshold set by DRIVESPEEDMAX and the VELFATAL parameters. Remedy: Note: If this error occurs when using a Smart Inc encoder, see Smart Inc encoders (setting a high application max speed and 200% velocity threshold may be necessary when using Smartabs). For other feedback types check the integrity of the feedback wiring and the earthing/shielding of all cables to/from the drive.
10016 Over voltage trip (_ecBUS_OVER_VOLTAGE)	Cause: The drive has shut down to protect itself after the measured dc bus voltage exceeded the preset limit. This can often occur during deceleration, particularly with large inertial loads. Remedy: Decrease deceleration rate, add a regen resistor if one is not fitted. Consider use of common dc bus if there are multiple drives where some regenerate and some motor.
10017 Under voltage trip (_ecBUS_UNDER_VOLTAGE)	Cause: The drive has shut down to protect itself after the measured dc bus voltage fell below a preset limit. This can often occur during acceleration, particularly with large inertial loads. Note: if DRIVEBUSUNDERVOLTSOVERRIDE is 0, low limit will use power data, otherwise will use DRIVEBUSUNDERVOLTSOVERRIDE. Remedy: Decrease the acceleration rate. If the fault occurs when the axis is not accelerating check the supply connections to the drive. A larger motor/drive combination may be required if the needed acceleration cannot be achieved.
10018 Motor I^2.T exceeded limit (_ecMOTOR_OVERLOAD)	Cause: The motor overload algorithm has integrated up to 100% and has tripped the drive to protect the motor. This will happen if the RMS current for the application exceeds the MOTORRATEDCURRENT value. Remedy: Check tuning, check motion profile. If necessary select a larger motor (which may also require an alternative drive).
10019 Motor temperature trip (_ecMOTOR_TEMP_INPUT)	Cause: #1. Motor Over Temperature has been detected on the drive and the drives hardwired Thermistor X10 input has detected Motor overheating from the connected motor PTC sensor. #2. Motor Over Temperature has been detected on the drive and the Motor Encoder is of a serial variety (such as Hiperface DSP which provides motor thermistor resistance as part of the feedback data). If this value exceeds MOTORTEMPERATURETRIP the drive trips with a motor overtemperature error. Remedy: When using feedback temperature monitoring, X10 connections TH1 and TH2 should be connected with a wire link (short-circuited) to suppress the normal temperature trip function. Note: MOTORTEMPERATURETRIP does not monitor the drive’s X10 motor thermistor input. Also look for a fault with feedback cable or wiring. Set MOTORTEMPERATURETRIP to a resistance that is suitable for the motor’s thermistor device. e.g. MOTORTEMPERATURETRIP(0) = 1200. Also look for a fault with feedback cable or wiring. Note: MOTORTEMPERATURETRIP operates only with motors that have a positive temperature coefficient (PTC) thermistor, where resistance increases with temperature, or with motors that have a switch that goes open-circuit at high temperatures.
10020 Phase search failure (_ecPHASE_SEARCH_FAILED)	Cause: Phase search must be completed to control a motor with type “encoder only”. Remedy: Phase search must be completed to control a motor with type “encoder only”- if it does not finish successfully check encoder settings in drive and check the correct number of motor poles has been configured.
10021 Hall signals lost or incorrect (_ecHALL_SIGNAL_LOSS)	Cause: This error indicates that a feedback type of halls only or Encoder + Halls is used and has detected an error. If this is so the halls sensor state is checked by the drive and that the Hall state detected is illegal (0 or 7). Remedy: This error would normally indicate a faulty encoder in the motor (the encoders include simulated hall signals) or bad wiring to the motor encoder. Check the quality of installation, wiring and encoder type selection. Note: You can use Mint Workbench to scope Encoder Hall State to look for problems.
10022 Encoder signals lost or incorrect (_ecENCODER_SIGNAL_LOSS)	Cause: This indicates that either there has been a total break or total disruption with the encoder signals. Remedy: Check the quality of installation, wiring and encoder type selection. Note: You can use Mint Workbench to scope Encoder Hall State and Encoder to look for problems. Note: To get more information on this error connect to the Drive with Mint Workbench go to “Parameters > Encoder > Channel 0 > Encoder Parameter(Encoder0, Fault Register)” If this contains a value other than 0 you can use this value to give you more help on the error. See help file subject: ENCODERPARAMETER. Check all earthing and shielding arrangements are as per the instruction manual.
10023 Encoder power supply loss (_ecENCODER_SUPPLY_LOSS)	Cause: Power supply to encoder has been lost or has dropped below the minimum level for the selected encoder type. Note: encoder voltage is supplied by the drive.encoder power is given from power board, then transferred from 8v to 5v by control board. Remedy: Check that there are no shorts in the encoder wiring to the encoder supply (e.g. ensure the shields are not shorting to the supply or other signal pins). If the wiring is OK and the problem persists then it is likely one of the internal power supplies is failing.
10026 PDO data is not present (Mn to Cn) (_ecPDO_DATA_MISSING_MN_TO_CN)	Cause: EtherCAT or EPL PDO data from the manager (MN) to the remote axis (CN) has been lost. This error occurs if the remote axis detects that at least two consecutive PDO packets have not been received correctly. Remedy: This error will occur on the drive if it has lost its connection to the Manager. Check that the Manager is running, configured correctly and the network is operating correctly.
10027 Remote motion command failed (_ecREMOTE_MOTION_FAILED)	Cause: Unable to load motion on the remote axis. Generally speaking, this error indicates MML in drive is not ready for operation. Remedy: This can be caused by a number of reasons, such as incorrect operating mode, the motor brake being enabled or the move buffer being full.
10028 Encoder not ready to operate (_ecENCODER_NOT_READY)	Cause: The drive is configured to use a Serial Encoder and it is not able to provide position information. Remedy: The encoder may take several seconds to become ready and this error will be generated if an attempt is made to enable the axis before the encoder is ready. This error can also occur if the resolution configured on the drive is not compatible with the encoder. The axis will be crash stopped and disabled. Note: To get more information on this error connect to the Drive with Mint Workbench go to “Parameters > Encoder > Channel 0 > Encoder Parameter(Encoder0, Fault Register)” If this contains a value other than 0 you can use this value to give you more help on the error. See help file subject: ENCODERPARAMETER.
10029 Supply phase loss detected (_ecSUPPLY_PHASE_LOSS)	Cause: The three phase drive has detected that one of the AC supply phases may been lost. The drive can normally only operate using a three phase supply. MotiFlex e100 drives have dedicated phase monitoring hardware, MotiFlex e180 drives monitor the ripple on the dc bus and if this becomes excessive then they assume an input phase has been lost. Remedy: Check the connection of the input phases. If the connections are OK and a MotiFlex e180 is tripping spuriously (e.g. because the application requires harsh repeated accel and decel cycles) then you can disable phase loss detection using PHASELOSSMODE(0) = 0.
10030 PDO data is not present (Cn to Mn) (_ecPDO_DATA_MISSING_CN_TO_MN)	Cause: PDO data from the remote axis (CN) to the manager (MN) has been lost. This error occurs if the manager detects that at least two consecutive PDO packets have not been received correctly. Remedy: This error will occur on the NextMove e100 if it detects a drive disappears from the network. This may be “normal” for an optional node (and the error must be handled via the ONERROR event). If this error is unexpected check the drive is not resetting and check the integrity of the Ethernet (EPL) cabling.
10032 PDO value out of range (_ecPDO_VALUE_OUT_OF_RANGE)	Cause: When controlling an axis using Real time Ethernet one of the PDOs sent to the drive were out of range. This is often the velocity reference PDO and can be caused when an axis is geared to a master axis/encoder and the master position/encoder value is changed via the program to a new value causing an infinite velocity demand. Remedy: Connect to the drive whilst the error is active and use the Error Log to determine which PDO is out of range. If it’s velocity then check the Mint program to ensure axes that are geared to master references are not geared when those master references position/encoder values are written to.
10033 STO active (_ecSTO_ACTIVE)	Cause: Either one or both of the Safe Torque Off inputs is not powered. This error can occur only when the drive is enabled. Remedy: Check drive STO inputs, if used check the wiring of the safety circuit or for open guards or Emergency stops etc.
10034 STO hardware fault (_ecSTO_HARDWARE_FAULT)	Cause: Either one or both of the internal fault circuit outputs has been asserted, indicating an internal hardware fault in the STO circuits. This error can occur when the drive is enabled or disabled. Remedy: Check drive STO inputs, if used check the wiring of the safety circuit or for open guards or Emergency stops etc.
10035 STO input mismatch (_ecSTO_INPUT_MISMATCH)	Cause: The drive has detected a mismatch in its internal STO registers. This error can occur when the drive is enabled or disabled. Remedy: Check the two drive STO inputs are in the same state with a multimeter. It may be necessary to adjust STOMISMATCHTIME to account for any timing discrepancies in the connected safety circuit.
10036 Encoder reading wrong or Hall fault (_ecENCODER_READING_WRONG)	Cause: The drive has detected that the measured Hall transition angle differs from the electrical angle used in the control by at least 70 degrees. Remedy: Check the quality of installation, wiring and encoder type selection. Note: You can use Mint Workbench to scope Encoder Hall State and Encoder to look for problems. Check that all earthing / shielding is as per the drive installation manual.
10037 All axis errors cleared (_ecAXIS_ERRORS_CLEARED)	Cause: This information message can appear in the error log to indicate that all axis errors have been cleared. Remedy: No action required.
10038 Encoder battery dead (_ecENCODER_BATTERY_DEAD)	Cause: This information message can appear at startup, or when the drive is enabled, if the battery backup supply for a Smart Abs encoder has failed. Remedy: Change the Encoder battery.
10039 Resolver signals lost or incorrect (_ecRESOLVER_SIGNAL_LOSS)	Cause: An error has occurred when using the Resolver Adapter (OPT-MF-201 or FB-03). The error is caused by the loss of resolver signals. Remedy: Check the wiring to the motor’s feedback device. Check the integrity of the motor connector. Check the connections inside to the adapter. Note: Check Mint Workbench parameters (Encoder > Channel 0 > Fault Register). Check all earthing/shielding is as per the drive installation manual.
10040 Hiperface DSL encoder error (_ecHIPERFACE_DSL_ENCODER_ERROR)	Cause: An error has occurred when reading the position over Hiperface DSL. Remedy: Check connection and integration of Hiperface DSL encoder. Refer to specific drive hardware documentation for detailed troubleshooting.
10041 Output frequency over limit (_ecOUTPUT_FREQ_OVER_LIMIT)	Cause: The drive has detected that the output frequency exceeded 550 Hz. This restriction is required to meet relevant European Export Control Regulation. Remedy: Reduce your application’s speed.
10042 Drive speed Maximum is out of range (_ecDRIVESPEEDMAX_OUT_OF_RANGE)	Cause: Motor velocity is above parameter DriveSpeedMax(0). Remedy: Go to parameters > Drive > DriveSpeedMax and check value is set correctly. Check Commanded Drive Speed is not too high.
10045 Position and velocity encoder deviation exceeded	Cause: The drive has detected that the axis exceeds its deviation error limit during the dual encoder operation. The drive acts according to the stop mode configured by POSVELENCODERDEVIATIONERRORMODE. Remedy: Check the motor, the encoders, other equipments and connections. Check the value of the keyword POSVELENCODERDEVIATIONFATAL is not too low.
10046 Brake chopper short circuit	Cause: An error has occurred when the drive detected that the brake chopper is short-connected at power-on. Remedy: Check the wiring to the brake chopper. The error could not be reset until the system is restarted.
30001 Controller over-temperature (_ecOVER_TEMPERATURE)	Cause: The drive has detected it is dangerously hot. Remedy: Check the drive ambient conditions allow for sufficient cooling. Note: Check drive’s internal temperature sensor. Trip occurs if temperature exceeds TEMPERATURELIMITFATAL (e.g., 80°C or 75°C depending on model).
30005 FPGA failed to initialise (_ecFPGA_INITIALISATION_ERROR)	Cause: The controller FPGA has failed to initialize. Remedy: Power cycle. If Error Persists, Replace the Drive.
30007 Error accessing non-volatile memory (_ecNON_VOL_MEMORY_FAILURE)	Cause: Unable to access non-volatile memory. Remedy: Power cycle. If Error Persists, Replace the Drive.
30008 Error applying parameter value (_ecPARAM_ERROR)	Cause: Errors have occurred during a parameter table download or during startup. Some parameters could not be applied correctly. Controller displays ‘E’. Remedy: This error is commonly associated with a parameter file (.ptx) issue. Check if parameter file is generated from an older firmware version. Read the Error Log for specific guidance on the affected parameters.
30009 General internal controller error (_ecINTERNAL_ERROR)	Cause: An internal error has occurred. Read parameter failed. Remedy: Power cycle. If Error Persists, Replace the Drive.
30010 Fan is not operating correctly (_ecFAN_LOSS)	Cause: The drive has detected that an internal cooling fan has failed. Remedy: Check the bottom of the drive to determine that the fan inlets are not blocked. Check that the fan is rotating. If the drive fan does not turn, it is a hardware failure; replace the fan.
30029 Controller under-temperature (_ecUNDER_TEMPERATURE)	Cause: The controller has detected an ambient temperature lower than -5 °C. Remedy: The ambient temperature must be increased before the drive can be enabled.
30030 All controller errors cleared (_ecCONTROLLER_ERRORS_CLEARED)	Cause: This information message can appear in the error log to indicate that all controller errors have been cleared. Remedy: No Action.
30032 Hardware revision does not support EPL (_ecHARDWARE_DOES_NOT_SUPPORT_EPL)	Cause: The controller does not support Ethernet POWERLINK. Remedy: Earlier Hardware revisions of e180 (with GCU-01 control cards before Rev A) do not support EPL. If EPL is needed, the Hardware will need to be exchanged.
NET ERR (Red) – Off No Error	Cause: The device is operating normally or is not powered. Remedy: Verify power is applied to the unit if LEDs are dark. No action required if operating normally.
NET ERR (Red) – Blinking Invalid Configuration	Cause: Invalid mailbox configuration (BOOT/PREOP), Sync manager, output/input, watchdog, DC Sync, or DC latch configuration. Remedy: Check mailbox settings in the master. Verify Sync manager configuration. Validate Input/Output configuration. Check Watchdog settings.
NET ERR (Red) – 1 flash Unspecific / Sync / Firmware Error	Cause: Unspecific error, No memory, Invalid request state change, Bootstrap not supported, No valid firmware, Sync error, PLL error, Invalid Sync manager types, or Slave needs INIT/PREOP/SAFEOP. Remedy: Check if valid firmware is loaded. Check for valid inputs/outputs availability. Verify DC Sync cycle times (Sync0/Sync1). Check for EEPROM access/errors. Perform a cold start of the slave.
NET ERR (Red) – 2 flashes Sync manager watchdog	Cause: The Sync manager watchdog has triggered. Remedy: Check communication stability with the master. Verify watchdog timeout settings.
NET RUN (Green) Status Indicator	Cause: Indicates the POWERLINK state. Remedy: Off: INITIALISATION state (or not powered). Blinking: PRE-OPERATIONAL state. 1 flash: SAFE-OPERATIONAL state. 3 flashes: Device identification (set by master to locate device). Solid On: OPERATIONAL state (Normal).
Green (Status) Node Status	Cause: Indicates the node status in POWERLINK mode. Remedy: Off: Node in NOT ACTIVE or initialization state. 1-2 flashes: Node in PRE-OPERATIONAL 1/2 state. 3 flashes: Node in READY TO OPERATE state. Blinking: Node in STOPPED state (deactivated). Flickering: Node in BASIC ETHERNET state. Solid On: Node in OPERATIONAL state.
Red (Error) POWERLINK Error	Cause: An error has occurred on the Ethernet POWERLINK interface. Remedy: Off: Working correctly. Continuously illuminated: An error has occurred; check master logs.
[- .] Drive disabled / STO unpowered	Cause: Drive disabled, and one or both STO (Safe Torque Off) inputs are not powered. Remedy: Both STO inputs must be powered. Enable the drive before operation can continue. Check optional drive enable input if configured.
[ | ] Initialization error / recovery mode	Cause: Initialization error occurred after powering the drive, or the drive is in recovery mode. Remedy: Remove all power. Check the memory unit is inserted correctly. Reapply power. If persisting, check recovery mode status (page 78 of manual).
[ – ] Drive disabled	Cause: The drive is disabled. Remedy: Enable the drive to continue operation. Check if optional drive enable input is powered.
[ = ] Suspend active	Cause: The Mint SUSPEND command has been issued and is active. Remedy: Motion ramps down to zero demand whilst active. Wait for suspend to clear or issue resume command.
[ ≡ ] Firmware loading	Cause: Firmware is loading (segments illuminated sequentially). Remedy: Wait for the numerical sequence representing firmware initialization to complete. Do not turn off power during this process.
[ 8 / A ] Hold to Analog (HTA) mode	Cause: The axis is in Hold To Analog mode. Remedy: See the Mint keyword HTA.
[ 8 ] Drive enabled, idle	Cause: The drive is enabled but currently idle. Remedy: No action required; drive is ready for commands.
[ c ] Cam move	Cause: A cam profile is in progress. Remedy: See Mint keyword CAM.
[ d ] Dwell	Cause: A dwell (wait) ‘move’ is in progress. Remedy: See Mint keyword MOVEDWELL.
[ F ] Flying shear	Cause: A flying shear is in progress. Remedy: See Mint keyword FLY.
[ 3 ] Follow move	Cause: The drive is in follow mode. Remedy: See Mint keyword FOLLOW.
[ h ] Homing	Cause: The drive is currently homing. Remedy: See Mint keyword HOME.
[ 1 ] Incremental move	Cause: An incremental linear move is in progress. Remedy: See Mint keywords INCA and INCR.
[ J ] Jog	Cause: The drive is jogging. Remedy: See Mint keywords JOG, JOGCOMMAND.
[ o ] Offset move	Cause: An offset move is in progress. Remedy: See Mint keyword OFFSET.
[ P ] Position move	Cause: A linear move is in progress. Remedy: See Mint keywords MOVEA and MOVER.
[ 9 / q ] Torque move	Cause: The drive is in torque mode. Remedy: See Mint keywords TORQUEREF, TORQUEREFSOURCE.
[ ‘ ] Firmware recovery mode	Cause: Firmware recovery mode is in operation. Remedy: See SW1 linear switches – startup functions (page 78).
[ 5 ] Stop input active	Cause: A Mint STOP command has been issued or an optional stop input is active. Remedy: Clear the stop command or input to proceed.
[ 7 ] Velocity reference move	Cause: The drive is under velocity control. Remedy: See Mint keywords VELREF.
[ 2 ] Spline move	Cause: A spline move is in progress. Remedy: See Mint keyword SPLINE.