diff options
| -rw-r--r-- | onelinify.py | 11 | ||||
| -rw-r--r-- | ours.xml | 9175 | ||||
| -rw-r--r-- | result | 22 | ||||
| -rw-r--r-- | theirs.xml | 6215 | ||||
| -rw-r--r-- | xmldiff.py | 25 |
5 files changed, 15448 insertions, 0 deletions
diff --git a/onelinify.py b/onelinify.py new file mode 100644 index 0000000..08bcb5a --- /dev/null +++ b/onelinify.py @@ -0,0 +1,11 @@ +#!/usr/bin/python + +import re +import xml.etree.ElementTree + +ours = xml.etree.ElementTree.parse('ours.xml').getroot().find('events').findall('event') + +for e in ours: + p = xml.etree.ElementTree.tostring(e) + re.sub(r'\n', '', p) + print p diff --git a/ours.xml b/ours.xml new file mode 100644 index 0000000..30da73a --- /dev/null +++ b/ours.xml @@ -0,0 +1,9175 @@ +<?xml version='1.0' encoding='UTF-8'?> +<module leipuri_version="2.0"> + <events> + <event> + <handle>CalibrationFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Calibration</event_name> + <short_description>Current measurement calibration fault</short_description> + <help_headers>Current measurement calibration fault</help_headers> + <help_texts>Measured offset of output phase current measurement or difference between output phase U2 and W2 current measurement is too great (the values are updated during current calibration). +- Try performing the current calibration again (select Current measurement +calibration at parameter 99.13). If the fault persists, contact your local ABB representative.</help_texts> + <user_manual_desc>Measured offset of output phase current measurement or difference between output phase current measurement is too great. +- Try performing the current calibration again. If the fault persists, contact your local ABB representative.</user_manual_desc> + <rnd_desc>Current measurement offset or gain error is too big.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OverCurrentPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Overcurrent</event_name> + <short_description>Output current has exceeded internal fault limit.</short_description> + <help_headers>Output current has exceeded internal fault limit</help_headers> + <help_texts>Output current has exceeded internal fault limit. +- Check motor load. +- Check acceleration times in parameter group 23 Speed reference ramp. +- Check motor and motor cable (including phasing and delta/star connection). +- Check that the start-up data in parameter group 99 corresponds to the motor rating plate. +- Check that there are no power factor correction capacitors or surge absorbers +in motor cable. +- Check encoder cable (including phasing).</help_texts> + <user_manual_desc>Output current has exceeded internal fault limit. Check: +- motor load +- acceleration times +- motor and motor cable +- start-up data (group 99) +- there are no power factor correction capacitors in motor cable +- encoder cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EarthPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Earth leakage</event_name> + <short_description>Earth fault</short_description> + <help_headers>Earth leakage fault</help_headers> + <help_texts>Load unbalance in eg, motor or motor cable +Check +-no power factor correction capacitors or surge absorbers in cable +-no earth fault in motor or cables: measure insulation resistances +If no earth fault detected, contact ABB.</help_texts> + <user_manual_desc>Load unbalance in eg, motor or motor cable +Check +-no power factor correction capacitors or surge absorbers in cable +-no earth fault in motor or cables: measure insulation resistances +If no earth fault detected, contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ShortCircuitPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Short circuit</event_name> + <short_description>Short-circuit in motor/cable. This fault cannot be reset.</short_description> + <help_headers>Short-circuit in motor cable(s) or motor</help_headers> + <help_texts>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IGBTOverLoadFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>IGBT overload</event_name> + <short_description>Excessive IGBT junction to case temperature</short_description> + <help_headers>Excessive IGBT junction to case temperature</help_headers> + <help_texts>Excessive IGBT junction to case temperature. This fault protects the IGBT(s) and can be activated by a short circuit in the motor cable. +- Check motor cable.</help_texts> + <user_manual_desc>Excessive IGBT junction to case temperature. This fault protects the IGBT(s) and can be activated by a short circuit in the motor cable. +- Check motor cable.</user_manual_desc> + <rnd_desc>dTjc fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUIDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU current difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check fault for currents</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUEFFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU earth leakage</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Earth fault detected by the branching unit: sum of all currents is exceeding the level.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUCDDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU commutation difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check fault for CDX and CDY.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>InputPhaseLossFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Input phase loss</event_name> + <short_description>Intermediate circuit DC voltage is oscillating.</short_description> + <help_headers>Intermediate circuit DC voltage is oscillating</help_headers> + <help_texts>Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse. +- Check input power line fuses. +- Check for input power supply imbalance.</help_texts> + <user_manual_desc>Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse. +- Check input power line fuses. +- Check for input power supply imbalance.</user_manual_desc> + <rnd_desc>Too much ripple in th Udc due to missing supply phase.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_ChrgRlyLostFlt</handle> + <module>DC_charge</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Charge relay lost</event_name> + <short_description>No acknowledgement from charge relay</short_description> + <help_headers>No acknowledgement from charge relay</help_headers> + <help_texts>No acknowledgement has been received from the charge relay. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>No acknowledgement has been received from the charge relay. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Charge relay lost</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>CrossConFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Wiring or earth fault</event_name> + <short_description>Incorrect input power and motor cable connection</short_description> + <help_headers>Incorrect input power and motor cable connection</help_headers> + <help_texts>Incorrect input power and motor cable connection (i.e. input power cable is connected to drive motor connection). +- Check input power connections.</help_texts> + <user_manual_desc>Incorrect input power and motor cable connection (i.e. input power cable is connected to drive motor connection). +- Check input power connections.</user_manual_desc> + <rnd_desc>AC supply connected to outputs.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OvervoltagePSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DC link overvoltage</event_name> + <short_description>DC link overvoltage fault</short_description> + <help_headers>DC link overvoltage fault</help_headers> + <help_texts>Excessive intermediate circuit DC voltage. +-Check that overvoltage control is on (parameter 30.30 Overvoltage control). +-Check that the supply voltage matches the nominal input voltage of the drive. +-Check the supply line for static or transient overvoltage. +-Check brake chopper and resistor (if present). +-Check deceleration time. +-Use coast-to-stop function (if applicable). +-Retrofit drive with brake chopper and brake resistor.</help_texts> + <user_manual_desc>DC link overvoltage +Check +-30.30 Overvoltage control +-supply voltage matches drive nominal input voltage +-supply line for static or transient overvoltage +-chopper/resistor +-decel. time +Coast-to-stop. +Retrofit drive with chopper and resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UndervoltagePSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DC link undervoltage</event_name> + <short_description>DC link undervoltage fault</short_description> + <help_headers>DC link undervoltage fault</help_headers> + <help_texts>Intermediate circuit DC voltage is not sufficient because of a missing supply phase, blown fuse or fault in the rectifier bridge. +-Check supply cabling, fuses and switchgear.</help_texts> + <user_manual_desc>Intermediate circuit DC voltage is not sufficient because of a missing supply phase, blown fuse or fault in the rectifier bridge. +-Check supply cabling, fuses and switchgear.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Standby_timeout</handle> + <module>NomValues</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Standby timeout</event_name> + <short_description>Autostart delay elapsed.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>After autorestart delay is elapsed and drive can not be started this fault is given instead of Undervoltage.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUUCDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DC voltage difference</event_name> + <short_description>DC voltage difference fault</short_description> + <help_headers>DC voltage difference fault</help_headers> + <help_texts>Difference in DC voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Difference in DC voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Difference check fault for DC-link voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUUmainDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU voltage difference</event_name> + <short_description>Main voltage difference fault</short_description> + <help_headers>Main voltage difference fault</help_headers> + <help_texts>Difference in main voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Difference in main voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Difference check fault for main voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>DCunbalanceFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DC unbalance fault</event_name> + <short_description>DC unbalance fault.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>DC unbalance of 3-level devices.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OutputPhaseLossFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Output phase loss</event_name> + <short_description>Missing motor connection</short_description> + <help_headers>Missing motor connection</help_headers> + <help_texts>Motor circuit fault due to missing motor connection (all three phases are not +connected). +- Connect motor cable.</help_texts> + <user_manual_desc>Motor circuit fault due to missing motor connection (all three phases are not +connected). +- Connect motor cable.</user_manual_desc> + <rnd_desc>Output phase loss detected.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>AutophasingFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Autophasing</event_name> + <short_description>Autophasing routine has failed.</short_description> + <help_headers>Autophasing routine has failed.</help_headers> + <help_texts>Autophasing routine has failed. +- Try other autophasing modes (see parameter 21.13 Autophasing mode) if +possible.</help_texts> + <user_manual_desc>Autophasing routine has failed. +- Try other autophasing modes (see parameter 21.13 Autophasing mode) if +possible.</user_manual_desc> + <rnd_desc>PMSM initial angle search failed or too big motor model error in closed loop.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_CableOverlFlt</handle> + <module>CableThermProt</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Motor cable overload</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_AmbTemp_AmbientTemperatureFlt</handle> + <module>Temperature_config</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Ambient temperature</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_CBTemp_FLT</handle> + <module>Electronics_temp_meas</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Control board temperature</event_name> + <short_description>Control board temperature</short_description> + <help_headers>Control board temperature</help_headers> + <help_texts>Check proper cooling of the cabinet.</help_texts> + <user_manual_desc>Control board temperature is too high.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IGBT_Overtemp_Fault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>IGBT overtemperature</event_name> + <short_description>Estimated drive IGBT temperature is excessive.</short_description> + <help_headers>Estimated drive IGBT temperature is excessive</help_headers> + <help_texts>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Too much current in off-line thermal model while thermal current limitation passivated.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>CoolingFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Cooling</event_name> + <short_description>Drive module temperature is excessive.</short_description> + <help_headers>Drive module temperature is excessive</help_headers> + <help_texts>Drive module temperature is excessive. +- Check ambient temperature. If it exceeds 40 °C (104 °F), ensure that load current does not exceed derated load capacity of drive. See appropriate Hardware Manual. +- Check drive module cooling air flow and fan operation. +- Check inside of cabinet and heatsink of drive module for dust pick-up. Clean +whenever necessary.</help_texts> + <user_manual_desc>Drive module temperature is excessive. +- Check ambient temperature. See appropriate Hardware Manual. +- Check cooling air flow and fan operation. +- Check heatsink of drive module for dust pick-up. Clean whenever necessary.</user_manual_desc> + <rnd_desc>On-line thermal model, cooling diagnostics, fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IGBTTempFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>IGBT temperature</event_name> + <short_description>Drive IGBT temperature is excessive.</short_description> + <help_headers>Drive IGBT temperature is excessive</help_headers> + <help_texts>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Tj fault limit exceeded.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TempFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Excess temperature</event_name> + <short_description>Temperature measurement from the power unit is too high</short_description> + <help_headers>Power unit module temperature is excessive.</help_headers> + <help_texts>Check ambient conditions. +Check air flow and fan operation. +Check heatsink fins for dust pick-up. +Check motor power against drive power.</help_texts> + <user_manual_desc>Power unit module temperature is excessive.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TempDifFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Excess temp difference</event_name> + <short_description>Temperature difference between power unit IGBTs is too high</short_description> + <help_headers>High temperature difference between the IGBTs of different phases.</help_headers> + <help_texts>Check the motor cabling. +Check cooling of drive module(s).</help_texts> + <user_manual_desc>Too high temperature difference between the highest and lowest measured IGBT temperatures of different phases. The amount of available temperatures depends on the frame size.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>PCB_SpaceCoolingFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PCB space cooling</event_name> + <short_description>PCB space cooling fault</short_description> + <help_headers>PCB space cooling fault</help_headers> + <help_texts>Check cooling fan inside the PCB space.</help_texts> + <user_manual_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded fault limit. +-Check cooling fan inside the PCB space.</user_manual_desc> + <rnd_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded fault limit.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_ExtTemp1_flt</handle> + <module>ExtTemp</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External temperature 1</event_name> + <short_description>External temperature 1 too high</short_description> + <help_headers>External temperature 1 too high</help_headers> + <help_texts>Check the value of parameter 35.02 +Measured temperature 1. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the fault limit for measured +temperature 1 in parameter group +35 Motor thermal protection.</help_texts> + <user_manual_desc>Check the value of parameter 35.02 +Measured temperature 1. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the fault limit for measured +temperature 1 in parameter group +35 Motor thermal protection.</user_manual_desc> + <rnd_desc>External Temperature 1</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_ExtTemp2_flt</handle> + <module>ExtTemp</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External temperature 2</event_name> + <short_description>External temperature 2 too high</short_description> + <help_headers>External temperature 2 too high</help_headers> + <help_texts>Check the value of parameter 35.03 +Measured temperature 2. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the fault limit for measured +temperature 2 in parameter group +35 Motor thermal protection.</help_texts> + <user_manual_desc>Check the value of parameter 35.03 +Measured temperature 2. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the fault limit for measured +temperature 2 in parameter group +35 Motor thermal protection.</user_manual_desc> + <rnd_desc>External Temperature 2</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FEX_01_NotFoundFault</handle> + <module>ExtTemp</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FPTC not found</event_name> + <short_description>A FPTC-01- or FPTC-02-option not found</short_description> + <help_headers>A FPTC-01- or FPTC-02-option not found</help_headers> + <help_texts>Check the FPTC-01- or FPTC-02-option activation from parameter 35.30. +Check that the FPTC-01- or FPTC-02-option is in correct option slot and firmly attached.</help_texts> + <user_manual_desc>A FPTC-01- or FPTC-02-option activated with parameter 35.30 is not in the option slot or has been removed during operation. Aux code defines the option slot 1, 2 or 3.</user_manual_desc> + <rnd_desc>A FPTC-01- or FPTC-02-option activated with parameter 35.30 is not in the option slot or has been removed during operation. Aux code defines the option slot.</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>Fault in slot 1</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Fault in slot 2</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Fault in slot 3</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list> + <item> + <cause>Wrong configuration in parameter 35.30.</cause> + <what_to_do>Check that the correct option slot for the FPTC-01- or FPTC-02-option module is activated in parameter 35.30.</what_to_do> + </item> + <item> + <cause>The FPTC-01- or FPTC-02-option module has been removed during operation.</cause> + <what_to_do>Check that the FPTC-01- or FPTC-02-01-option has not been removed and is firmly attached.</what_to_do> + </item> + <item> + <cause>A FPTC-01- or FPTC-02-option module missing.</cause> + <what_to_do>Check that a FPTC-01- or FPTC-02-option module is mounted in the correct option slot of the control unit.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FEX_01_FaultSlot1</handle> + <module>ExtTemp</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Safe motor temperature 1</event_name> + <short_description>Safe motor temperature 1</short_description> + <help_headers>Safe motor temperature 1</help_headers> + <help_texts>Motor temperature is too high or the thermistor is in short circuit or disconnected. +Check motor cooling. +Check thermistor connection.</help_texts> + <user_manual_desc>The FPTC-01- or FPTC-02-option module in option slot 1 of the control unit has activated a "Safe motor temperature"-fault. +The PTC thermistor connected to the X2 input of the option module indicates a too high temperature in the motor. +Same fault is activated also if the thermistor is short circuited or disconnected.</user_manual_desc> + <rnd_desc>The FPTC-01- or FPTC-02-module in slot 1 of the control unit indicates a fault. +The PTC thermistor connected to X2 of the option module indicates a too high motor temperature. +Fault is activated also if the thermistor is short circuited or disconnected.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Thermistor is short circuited or disconnected.</cause> + <what_to_do>Check the thermistor connection. +Measure the thermistor resistance.</what_to_do> + </item> + <item> + <cause>Motor temperature is too high.</cause> + <what_to_do>Check the cooling of the motor. +Check motor load and drive ratings.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FEX_01_FaultSlot2</handle> + <module>ExtTemp</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Safe motor temperature 2</event_name> + <short_description>Safe motor temperature 2</short_description> + <help_headers>Safe motor temperature 2</help_headers> + <help_texts>Motor temperature is too high or the thermistor is in short circuit or disconnected. +Check motor cooling. +Check thermistor connection.</help_texts> + <user_manual_desc>The FPTC-01- or FPTC-02-option module in option slot 2 of the control unit has activated a "Safe motor temperature"-fault. +The PTC thermistor connected to the X2 input of the option module indicates a too high temperature in the motor. +Same fault is activated also if the thermistor is short circuited or disconnected.</user_manual_desc> + <rnd_desc>The FPTC-01- or FPTC-02-module in slot 2 of the control unit indicates a fault. +The PTC thermistor connected to X2 of the option module indicates a too high motor temperature. +Fault is activated also if the thermistor is short circuited or disconnected.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Thermistor is short circuited or disconnected.</cause> + <what_to_do>Check the thermistor connection. +Measure the thermistor resistance.</what_to_do> + </item> + <item> + <cause>Motor temperature is too high.</cause> + <what_to_do>Check the cooling of the motor. +Check motor load and drive ratings.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FEX_01_FaultSlot3</handle> + <module>ExtTemp</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Safe motor temperature 3</event_name> + <short_description>Safe motor temperature 3</short_description> + <help_headers>Safe motor temperature 3</help_headers> + <help_texts>Motor temperature is too high or the thermistor is in short circuit or disconnected. +Check motor cooling. +Check thermistor connection.</help_texts> + <user_manual_desc>The FPTC-01- or FPTC-02-option module in option slot 3 of the control unit has activated a "Safe motor temperature"-fault. +The PTC thermistor connected to the X2 input of the option module indicates a too high temperature in the motor. +Same fault is activated also if the thermistor is short circuited or disconnected.</user_manual_desc> + <rnd_desc>The FPTC-01- or FPTC-02-module in slot 3 of the control unit indicates a fault. +The PTC thermistor connected to X2 of the option module indicates a too high motor temperature. +Fault is activated also if the thermistor is short circuited or disconnected.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Thermistor is short circuited or disconnected.</cause> + <what_to_do>Check the thermistor connection. +Measure the thermistor resistance.</what_to_do> + </item> + <item> + <cause>Motor temperature is too high.</cause> + <what_to_do>Check the cooling of the motor. +Check motor load and drive ratings.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FanCtrl_FanFault</handle> + <module>FA_FanCtrl</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Fan</event_name> + <short_description>Cooling fan stuck or disconnected</short_description> + <help_headers>Cooling fan stuck or disconnected</help_headers> + <help_texts>Cooling fan stuck or disconnected. +- Check fan operation and connection. Replace fan if faulty.</help_texts> + <user_manual_desc>Cooling fan stuck or disconnected. +- Check fan operation and connection. Replace fan if faulty.</user_manual_desc> + <rnd_desc>Fan does not follow the reference.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Aux_fan_broken</handle> + <module>FA_FanCtrl</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Auxiliary fan broken</event_name> + <short_description>This fault cannot be reset.</short_description> + <help_headers>Auxiliary fan broken</help_headers> + <help_texts>An auxiliary cooling fan (connected to the fan connectors on the control unit) is stuck or disconnected. +Check auxiliary fan(s) and connection(s). Replace fan if faulty. Make sure the front cover of the drive module is in place and tightened. This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot. +When the front cover including the auxiliary fan is removed during commissioning or maintenance, the auxiliary fan supervision can be bypassed temporarily using parameter 31.36 Aux fan fault bypass.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes> + <aux_code code="1"> + <names>Auxiliary fan 1 broken</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Auxiliary fan 2 broken</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_STOHWFlt</handle> + <module>STO</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>STO hardware failure</event_name> + <short_description>Safe torque off hardware failure fault</short_description> + <help_headers>Safe torque off hardware failure fault</help_headers> + <help_texts>Safe torque off hardware failure. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Safe torque off hardware failure. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>STO hardware failure. STO status from PU and control board differs.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>STOFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Safe torque off</event_name> + <short_description>Safe torque off circuit fault in the power unit side</short_description> + <help_headers>Safe torque off function is active</help_headers> + <help_texts>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections. For more information, see appropriate drive +hardware manual.</help_texts> + <user_manual_desc>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FPGAErrPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>PU logic error</event_name> + <short_description>Power unit logic memory error. +This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>The memory of the power unit logic is cleared.</user_manual_desc> + <rnd_desc>PU FPGA logic has lost its memory, signature register value is missing</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_RatingIDMismatchFlt</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Rating ID mismatch</event_name> + <short_description>Mismatch between PU/CU rating. This fault cannot be reset.</short_description> + <help_headers>Mismatch between actual and stored hardware information</help_headers> + <help_texts>The hardware of the drive does not match the information stored in the memory unit. This may occur eg. after a firmware update or memory unit replacement. +- Cycle the power to the drive. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>The hardware of the drive does not match the information stored in the memory unit. This may occur eg. after a firmware update or memory unit replacement. +- Cycle the power to the drive.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TempSensorFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Measurement circuit temperature</event_name> + <short_description>Problem with internal temperature measurement of the drive. +If the device has only one IGBT temperature measurement in one phase, the fault is generated, otherwise warning.</short_description> + <help_headers>Problem with internal temperature measurement of the drive</help_headers> + <help_texts>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>RedundantMeasurementPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Redundant measurement</event_name> + <short_description>Redundant measurement. +This fault cannot be reset.</short_description> + <help_headers>Redundant measurement</help_headers> + <help_texts>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. (Solar applications)</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OverTemp3LFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Overtemperature hw</event_name> + <short_description>Hardware overtemperature detection (3L target specific)</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_CuLogicError</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>CU logic error</event_name> + <short_description>Control unit's FPGA has lost its configuration. +This fault cannot be reset.</short_description> + <help_headers>CU logic error</help_headers> + <help_texts>This fault automatically reboots the control unit after a short delay.</help_texts> + <user_manual_desc>Control unit's FPGA has lost its configuration. +This fault cannot be reset. +This fault automatically reboots the control unit after a short delay.</user_manual_desc> + <rnd_desc>Control unit's FPGA has lost its configuration. +This fault cannot be reset. +</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Problem in the Control Unit hardware.</cause> + <what_to_do>Replace the Control Unit.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>LinkErrPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU communication</event_name> + <short_description>PU communication error</short_description> + <help_headers>Communication errors detected between the drive control unit and the power unit</help_headers> + <help_texts>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</help_texts> + <user_manual_desc>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_PULostFlt</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Power unit lost</event_name> + <short_description>Connection to power unit lost</short_description> + <help_headers>Connection to power unit lost</help_headers> + <help_texts>The connection between the control unit and the power unit is lost. +- Check the connection between the control unit and the power unit.</help_texts> + <user_manual_desc>The connection between the control unit and the power unit is lost. +- Check the connection between the control unit and the power unit.</user_manual_desc> + <rnd_desc>Power unit lost</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>PSL2DriverInternalFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU communication internal</event_name> + <short_description>PU communication driver internal error</short_description> + <help_headers>Internal communication error</help_headers> + <help_texts>Internal communication error. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Internal communication error. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ADCErrorPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Measurement circuit ADC</event_name> + <short_description>Power unit measurement A/D conversion failure</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>PFPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU board powerfail</event_name> + <short_description>xINT board auxiliary power failure</short_description> + <help_headers>Power unit power supply failure</help_headers> + <help_texts>Power unit power supply failure. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Power unit power supply failure.</user_manual_desc> + <rnd_desc>Auxiliary power failure of power unit board +</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>DFFPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Measurement circuit DFF</event_name> + <short_description>Too high derivative in the power unit measurement</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>HWConfigFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>PU communication conf</event_name> + <short_description>PU channel config error. This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Configuration failure of power unit communication channel(s): channel information is not matching with parameters or channels are cross connected.</user_manual_desc> + <rnd_desc>Erroneous configuration of PU communication channel(s): the actual channel ids are not matching with parameters or channels are cross connected.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ReducedRunPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Reduced run</event_name> + <short_description>Some xINTs are missing</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>Some of the configured power units are not found. The reduced run is possible if configured.</user_manual_desc> + <rnd_desc>Not all power units found, reduced run is possible</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>STSVPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU state feedback</event_name> + <short_description>PU state feedback</short_description> + <help_headers>PU state feedback</help_headers> + <help_texts>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</help_texts> + <user_manual_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</user_manual_desc> + <rnd_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>CHGFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Charging feedback</event_name> + <short_description>Charging feedback missing</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>The charging feedback is missing.</user_manual_desc> + <rnd_desc>Formerly INVD</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UnknownPUFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Unknown PU fault</event_name> + <short_description>Unknown power unit fault</short_description> + <help_headers>Unknown power unit fault</help_headers> + <help_texts>The power unit logic has generated a fault which is not known by the softaware. +-Check the logic and software compatility.</help_texts> + <user_manual_desc>The power unit logic has generated a fault which is not known by the softaware. +-Check the logic and software compatility.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_InternalSWFlt</handle> + <module>DRIVE_LOGIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Internal SW error</event_name> + <short_description>Internal SW error. +This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc/> + <rnd_desc>0x6000</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_InternalSWFlt2</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Internal SW error 2</event_name> + <short_description>PROASSERT returned false</short_description> + <help_headers>Internal SW error for PRO_ASSERT</help_headers> + <help_texts>Internal SW error for PRO_ASSERT</help_texts> + <user_manual_desc>Internal SW error for PRO_ASSERT</user_manual_desc> + <rnd_desc>Internal SW error for PRO_ASSERT</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FPGAVerIncompatible</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>FPGA version incompatible</event_name> + <short_description>FPGA version not compatible. This fault cannot be reset.</short_description> + <help_headers>Firmware and FPGA are not compatible.</help_headers> + <help_texts>Update FPGA. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Firmware and FPGA versions are incompatible with each other.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_UnrecoverableSWFault</handle> + <module>DRIVE_LOGIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Unrecoverable SW error</event_name> + <short_description>Unrecoverable SW Error. +This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>An unrecoverable error has occurred. Record fault code and auxilliary fault code and report them to factory. Cycle power to drive to recover. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>An unrecoverable error has occurred. Record fault code and auxilliary fault code and report them to factory. Cycle power to drive to recover.</user_manual_desc> + <rnd_desc>0xA681 - 42625</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Checksum_mismatch_f</handle> + <module>Checksum</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Checksum mismatch</event_name> + <short_description>The actual checksum does not match any of the active approved checksums.</short_description> + <help_headers/> + <help_texts>Parameter 96.53 "Actual checksum" does not match any of the active approved checksums (parameters 96.56-59). Check the parameter configuration and approve the actual checksum if needed using parameter 96.54 "Checksum control word".</help_texts> + <user_manual_desc>The actual checksum does not match any of the active approved checksums.</user_manual_desc> + <rnd_desc>The actual checksum does not match any of the active approved checksums.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB1MappingFileFault</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FBA A mapping file</event_name> + <short_description>Fieldbus adapter A mapping file fault</short_description> + <help_headers>Fieldbus adapter A mapping file fault</help_headers> + <help_texts>Fieldbus adapter A mapping file read error. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Fieldbus adapter A mapping file read error. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB2MappingFileFault</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FBA B mapping file</event_name> + <short_description>Fieldbus adapter B mapping file fault.</short_description> + <help_headers>Fieldbus adapter B mapping file fault</help_headers> + <help_texts>Fieldbus adapter B mapping file read error. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Fieldbus adapter B mapping file read error. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TaskOverloadFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Task overload</event_name> + <short_description>Task overload fault. +This fault cannot be reset.</short_description> + <help_headers>Task overload fault</help_headers> + <help_texts>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Task overloaded. The execution of the task takes too long time.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>StackFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Stack overflow</event_name> + <short_description>Stack overflow fault. +This fault cannot be reset.</short_description> + <help_headers>Stack overflow fault</help_headers> + <help_texts>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Stack overflow fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UffLoadFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Internal file load</event_name> + <short_description>Internal file load fault. +This fault cannot be reset.</short_description> + <help_headers>Internal file load fault</help_headers> + <help_texts>File read error. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>File read error. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Loading of an UFF file has failed. The aux code tells which UFF file is in question. Permanent fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UffLoadNotPermanentFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Internal record load</event_name> + <short_description>Internal record load fault</short_description> + <help_headers>Internal record load fault</help_headers> + <help_texts>Internal record load error. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Internal record load error. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Loading of a UFF record has failed. This fault is used when a UFF loading fails but the activated fault can be resettable. </rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ApplLoadingFault</handle> + <module>TUCAC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Application loading</event_name> + <short_description>Application loading fault. +This fault cannot be reset.</short_description> + <help_headers>Application loading fault</help_headers> + <help_texts>Application file incompatible or corrupted. +Note: This fault cannot be reset. +-Check the fault logger for a fault code extension. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Application file incompatible or corrupted. +Note: This fault cannot be reset. +-Check the fault logger for a fault code extension.</user_manual_desc> + <rnd_desc>Fault indicates that the application loading has failed. Causes for the failure can be problems in the content of the application UFF file or that the Codesys runtime-system initialization has failed.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UffLoadPuRatingIdFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Rating ID fault</event_name> + <short_description>Rating ID fault</short_description> + <help_headers>Rating ID load error</help_headers> + <help_texts>Rating ID load error. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Rating ID load error. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Loading of the Rating ID has failed. This fault is used when a UFF loading fails but the activated fault can be resettable. </rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>LicensingFault</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Licensing fault</event_name> + <short_description>Licensing fault. +This fault cannot be reset.</short_description> + <help_headers>A required license is missing.</help_headers> + <help_texts>The software on this drive requires a license that couldn't be found. The missing license is indicated by the value of the aux code field. Please contact your product vendor for further instructions. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>A license that is required for the drive to function properly is missing. The missing license is Nxxxx, where xxxx is indicated by the 4-digit value of the aux code field.</user_manual_desc> + <rnd_desc>A required license is missing.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_AdaptiveProgram</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Adaptive program</event_name> + <short_description>Adaptive program file incompatible or corrupted.</short_description> + <help_headers>Adaptive program file incompatible or corrupted.</help_headers> + <help_texts>Adaptive program file incompatible or corrupted. Check the fault logger for a fault code extension.</help_texts> + <user_manual_desc>Adaptive program has faulted. Check the fault code extension for further information.</user_manual_desc> + <rnd_desc>Harmonized fault code: 0x64A6 +Adaptive program fault. Adaptive program file incompatible or corrupted.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Adaptive program file incompatible or corrupted.</cause> + <what_to_do>Check the fault logger for a fault code extension.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>MemUnitDetached</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Memory unit detached</event_name> + <short_description>Memory unit detached. +This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Memory unit has been removed while the power is on.</user_manual_desc> + <rnd_desc>Memory Unit has been removed. Live removing or inserting of the memory unit is not supported.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>SSW_InternalFault</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Internal SSW fault</event_name> + <short_description>Internal SSW fault. +This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Internal SSW fault is generated, if a fatal error occurrs in power-up phase of System Software (SSW). +The SSW will run in a mode where only partial functionality is available. +It is still possible to download new software with a loading package.</user_manual_desc> + <rnd_desc>Internal SSW fault is generated, if a fatal error occurrs in the SSW power-up phase. +The system will run in SSW_FAULT-mode where only partial functionality is available. In this mode it is possible to download new SW with a loading package.</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>Failure when starting the OS time tick.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Failure when creating system tasks.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Failure when initializing the file system.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="8"> + <names>Failure when checking the file system.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Failure when initializing the WoRm volumes.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="20"> + <names>Failure when loading the FPGA configuration.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="40"> + <names>Failure when loading the application program.</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UserSetFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>User set fault</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>KernelEventFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Kernel overload</event_name> + <short_description>Kernel overload fault. +This fault cannot be reset.</short_description> + <help_headers>Kernel overload fault</help_headers> + <help_texts>Operating system error. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Operating system error. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Operating system error.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FaultReset</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Fault reset</event_name> + <short_description/> + <help_headers/> + <help_texts>This event indicates that fault has been reset. The cause of the fault no +longer exists and the fault reset has been requested and completed.</help_texts> + <user_manual_desc/> + <rnd_desc>Fault reset has been requested and done.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ParSysFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Parameter system</event_name> + <short_description>Parameter system fault</short_description> + <help_headers>Parameter system fault</help_headers> + <help_texts>Parameter load or save failed. +-Try forcing a save using parameter 96.07 Param save. Retry.</help_texts> + <user_manual_desc>Parameter load or save failed. +-Try forcing a save using parameter 96.07 Param save. Retry.</user_manual_desc> + <rnd_desc>Failure in the parameter system. Fix mentioned in User manual description available with TUREL101+</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BackupRestoreTimeoutFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Backup/Restore Timeout</event_name> + <short_description>Backup/Restore timeout</short_description> + <help_headers>BR timeout fault</help_headers> + <help_texts>Check panel / PC-tool communication and if it is still in backup / restore state.</help_texts> + <user_manual_desc>Thrown during backup taking or restoring operation when a panel or PC-tool fails to communicate with the drive as part of backup taking or restoring operation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB1ParConflictFault</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FBA A parameter conflict</event_name> + <short_description>Fieldbus adapter A parameter conflict fault</short_description> + <help_headers>Fieldbus adapter A parameter conflict fault</help_headers> + <help_texts>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</help_texts> + <user_manual_desc>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB2ParConflictFault</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FBA B parameter conflict</event_name> + <short_description>Fieldbus adapter B parameter conflict fault</short_description> + <help_headers>Fieldbus adapter B parameter conflict fault</help_headers> + <help_texts>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</help_texts> + <user_manual_desc>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_RefSrcParamFault</handle> + <module>FA_miscellaneous</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Reference source parametrization</event_name> + <short_description>A reference source was simultaneously connected to two or more active reference source parameters of different units.</short_description> + <help_headers>Reference source parametrization fault</help_headers> + <help_texts>A reference source was simultaneously connected to two or more parameters of different units. Additionally, these parameters are actively used as reference. +Check parameterization.</help_texts> + <user_manual_desc>A reference source was simultaneously connected to two or more active reference source parameters of different units.</user_manual_desc> + <rnd_desc>A reference source was simultaneously connected to two or more active reference source parameters of different units.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>A reference source was simultaneously connected to two or more active reference source parameters of different units.</cause> + <what_to_do>Check that the same reference is not used in two or more active reference source parameters of different units. In that case, change parametrization.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>EFBSerial1ErrFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB communication loss</event_name> + <short_description>The EFB has detected a comm loss. Check communications with system.</short_description> + <help_headers>EFB comm loss fault</help_headers> + <help_texts>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08 and 58.09 to adjust settings.</help_texts> + <user_manual_desc>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08, and 58.09 to adjust settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBConfigFileFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB configuration file</event_name> + <short_description>EFB protocol was unable to access its config file.</short_description> + <help_headers>EFB config file fault</help_headers> + <help_texts>EFB protocol was unable to access its config file. Reload firmware or replace the unit.</help_texts> + <user_manual_desc>EFB protocol was unable to access its config file. Reload firmware or replace the unit.</user_manual_desc> + <rnd_desc>Embedded fieldbus configuration file fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBParFBusNotPresentFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB invalid parameterization</event_name> + <short_description>Invalid EFB configuration. Please check EFB parameters in group 58.</short_description> + <help_headers>EFB invalid parameterization</help_headers> + <help_texts>Invalid EFB configuration. Please check EFB parameters in group 58 and verify they are consistent with the configured protocol.</help_texts> + <user_manual_desc>Invalid EFB configuration. Please check EFB parameters in group 58 and verify they are consistent with the configured protocol.</user_manual_desc> + <rnd_desc>Embedded fieldbus invalid parameterization</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBFault1</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB load fault</event_name> + <short_description>Unable to load protocol firmware or version mismatch between protocol and system fw.</short_description> + <help_headers>EFB load fault</help_headers> + <help_texts>Unable to load protocol firmware or version mismatch between protocol and system firmware.</help_texts> + <user_manual_desc>Unable to load protocol firmware or version mismatch between protocol and system firmware. Reload firmware or replace the unit.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBFault2</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB fault 2</event_name> + <short_description>This fault is not currently used at this time.</short_description> + <help_headers>EFB fault 2</help_headers> + <help_texts>This fault is not currently used at this time.</help_texts> + <user_manual_desc>This fault is not currently used at this time.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBFault3</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB fault 3</event_name> + <short_description>This fault is not currently used at this time.</short_description> + <help_headers>EFB fault 3</help_headers> + <help_texts>This fault is not currently used at this time.</help_texts> + <user_manual_desc>This fault is not currently used at this time.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>LangDataRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text data overflow</event_name> + <short_description>Language data table size is too short. Please, contact ABB.</short_description> + <help_headers>Language data table fault</help_headers> + <help_texts>The buffer size is too short for language data, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB.</help_texts> + <user_manual_desc>Internal fault. +-Reset the fault. Contact your local ABB representative if the fault persists.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for language data. Increase the buffer length in LANG_config.h file. +</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>Lang32BitRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text 32-bit table overflow</event_name> + <short_description>32 bit bointer table size is too short. Please, contact ABB.</short_description> + <help_headers>32 bit pointer table fault</help_headers> + <help_texts>32 bit bointer table size is too short for text, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB.</help_texts> + <user_manual_desc>Internal fault. +-Reset the fault. Contact your local ABB representative if the fault persists.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for 32 bit poiters. Increase the buffer length in LANG_config.h file.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>Lang64BitRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text 64-bit table overflow</event_name> + <short_description>64 bit bointer table size is too short. Please, contact ABB.</short_description> + <help_headers>64 bit pointer table fault</help_headers> + <help_texts>64 bit bointer table size is too short for text, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB.</help_texts> + <user_manual_desc>Internal fault. +-Reset the fault. Contact your local ABB representative if the fault persists.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for 64 bit poiters. Increase the buffer length in LANG_config.h file.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>LangSourceFileRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text file overflow</event_name> + <short_description>The table size is too short for opening language file. Please, contact ABB.</short_description> + <help_headers>Language file open fault</help_headers> + <help_texts>The buffer size is too short for opening language file. Please, Contact ABB.</help_texts> + <user_manual_desc>Internal fault. +-Reset the fault. Contact your local ABB representative if the fault persists.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for opening language file. Increase the buffer length in LANG_config.h file.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_OptionCommLossFlt</handle> + <module>Option_module</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Option module comm loss</event_name> + <short_description>Communication with encoder option module lost</short_description> + <help_headers>Communication with encoder option module lost</help_headers> + <help_texts>Communication between drive and encoder option module (FEN-xx) is lost. +- Check that the option modules are properly seated in their slots. +- Check that the option modules or slot connectors are not damaged. To pinpoint the problem, try installing the modules into different slots.</help_texts> + <user_manual_desc>Communication between drive and encoder option module (FEN-xx) is lost. +- Check that the option modules are properly seated in their slots. +- Check that the option modules or slot connectors are not damaged. To pinpoint the problem, try installing the modules into different slots.</user_manual_desc> + <rnd_desc>Communcation to encoder option module lost</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_PanelLossFlt</handle> + <module>PROFILE</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Control panel loss</event_name> + <short_description>Control panel loss fault</short_description> + <help_headers>Control panel loss fault</help_headers> + <help_texts>Control panel or PC tool selected as active control location for drive has ceased communicating. +-Check PC tool or control panel connection. +-Check control panel connector. +-Replace control panel in mounting platform.</help_texts> + <user_manual_desc>Control panel or PC tool selected as active control location for drive has ceased communicating. +-Check PC tool or control panel connection. +-Check control panel connector. +-Replace control panel in mounting platform.</user_manual_desc> + <rnd_desc>Connection to panel is lost and user has selected fault by comm loss function parameter</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_ExtIOCommLossFlt</handle> + <module>Option_module</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Ext I/O comm loss</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Panel_reference_conflict</handle> + <module>Panel_reference</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Panel reference conflict</event_name> + <short_description>Conflicting panel references in simultaneous use</short_description> + <help_headers>Panel reference conflict</help_headers> + <help_texts>Conflicting panel reference configuration. Check that panel is selected as reference only for one of the following sources: +• PID setpoint +• Frequency / speed reference +• Torque reference</help_texts> + <user_manual_desc>Panel cannot be selected as reference for multiple sources at the same time +Check that panel is selected as reference only for one of the following sources: +• PID setpoint +• Frequency / speed reference +• Torque reference + +Ensure that Panel ref (saved) is not used in mixed reference types.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list> + <item> + <cause>Attempt to use mixed reference types with Panel ref (saved).</cause> + <what_to_do>Ensure that Panel ref (saved) is not used in mixed reference types.</what_to_do> + </item> + <item> + <cause>Panel cannot be selected as reference for multiple sources at the same time</cause> + <what_to_do>Check that panel is selected as reference only for one of the following sources: +• PID setpoint +• Frequency / speed reference +• Torque reference</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Panel_PC_tool_version_conflict</handle> + <module>Panel_reference</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Panel/PC tool version conflict</event_name> + <short_description>Control panel or PC tool version does not support functionality required by parametrization</short_description> + <help_headers>Panel/tool version conflict</help_headers> + <help_texts>Please update the control panel firmware or deactivate conflicting drive features.</help_texts> + <user_manual_desc>Remove control panel from all reference or command inputs.</user_manual_desc> + <rnd_desc>Control panel remote command and reference not supported</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>Command and reference not supported</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list> + <item> + <cause>Control panel remote command and reference not supported</cause> + <what_to_do>Remove control panel from all reference or command inputs.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_IncompatibleOptionModuleFlt</handle> + <module>Option_module</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Incompatible option module</event_name> + <short_description>Option module not supported</short_description> + <help_headers>Option module not supported</help_headers> + <help_texts>Remove incompatible option module.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes> + <aux_code code="1"> + <names>Incompatible option module in FBA A</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Incompatible option module in FBA B</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_MotorStall_flt</handle> + <module>EVENTS_Autoreset</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Motor stall</event_name> + <short_description>Motor operating in stall region</short_description> + <help_headers>Motor operating in stall region</help_headers> + <help_texts>Motor is operating in stall region because of eg. excessive load or insufficient motor power. +- Check motor load and drive ratings. +- Check fault function parameters.</help_texts> + <user_manual_desc>Motor is operating in stall region because of eg. excessive load or insufficient motor power. +- Check motor load and drive ratings. +- Check fault function parameters.</user_manual_desc> + <rnd_desc>Motor stall</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BRResistorFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Brake resistor</event_name> + <short_description>Braking chopper power lower than required</short_description> + <help_headers>Brake chopper power lower than required</help_headers> + <help_texts>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor. +-Check the dimensioning of the brake resistor.</help_texts> + <user_manual_desc>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor. +-Check the dimensioning of the brake resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BrOvertempFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BR excess temperature</event_name> + <short_description>Excessive brake resistor temperature</short_description> + <help_headers>Excessive brake resistor temperature</help_headers> + <help_texts>Brake resistor temperature has exceeded fault limit defined by parameter 43.11 Brake resistor fault limit. +- Stop drive. Let resistor cool down. +- Check resistor overload protection function settings (parameter group 43 Brake chopper). +- Check fault limit setting, parameter 43.11 Brake resistor fault limit. +- Check that braking cycle meets allowed limits.</help_texts> + <user_manual_desc>Brake resistor temperature has exceeded fault limit defined by parameter 43.11 Brake resistor fault limit. +- Stop drive. Let resistor cool down. +- Check parameter group 43 Brake chopper. +- Check that braking cycle meets allowed limits.</user_manual_desc> + <rnd_desc>Braking resistor thermal model fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BcErPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Brake resistor wiring</event_name> + <short_description>Brake chopper wiring fault. +This fault cannot be reset.</short_description> + <help_headers>Brake chopper wiring fault</help_headers> + <help_texts>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BcScPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>BC short circuit</event_name> + <short_description>Brake chopper short circuit. +This fault cannot be reset.</short_description> + <help_headers>Brake chopper short circuit</help_headers> + <help_texts>Short circuit in brake chopper IGBT. +- Ensure brake resistor is connected and not damaged. +- Check the electrical specifications of the brake resistor against the Hardware +manual. +-Replace brake chopper (if replaceable). +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Short circuit in brake chopper IGBT. +- Ensure brake resistor is connected and not damaged. +- Check the electrical specifications of the brake resistor against the Hardware +manual. +-Replace brake chopper (if replaceable).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BcIgbtOvertempFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BC IGBT excess temp</event_name> + <short_description>Excessive brake chopper IGBT temperature</short_description> + <help_headers>Excessive brake chopper IGBT temperature</help_headers> + <help_texts>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check for excessive ambient temperature. +- Check for cooling fan failure. +- Check for obstructions in the air flow. +- Check the dimensioning and cooling of the cabinet. +- Check resistor overload protection function settings (parameter group 43 +Brake chopper). +- Check that braking cycle meets allowed limits. +- Check that drive supply AC voltage is not excessive.</help_texts> + <user_manual_desc>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check: for excessive ambient temperature, cooling fan, resistor overload protection function settings, braking duty cycle, drive supply AC voltage.</user_manual_desc> + <rnd_desc>BC IGBT thermal mode fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_BrkClseFailedFlt</handle> + <module>MechBrake_ctrl</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Mech brake closing failed</event_name> + <short_description>Mechanical brake closing failed</short_description> + <help_headers>Mechanical brake closing failed</help_headers> + <help_texts>Mechanical brake control fault. Activated eg. if brake acknowledgement is not as +expected during brake closing: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</help_texts> + <user_manual_desc>Mechanical brake control fault. Activated eg. if brake acknowledgement is not as +expected during brake closing: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</user_manual_desc> + <rnd_desc>Mechanical brake closing failed</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_BrkOpenFailedFlt</handle> + <module>MechBrake_ctrl</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Mech brake opening failed</event_name> + <short_description>Mechanical brake opening failed</short_description> + <help_headers>Mechanical brake opening failed</help_headers> + <help_texts>Mechanical brake control fault. Activated eg. if brake acknowledgement is not as +expected during brake opening: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</help_texts> + <user_manual_desc>Mechanical brake control fault. Activated eg. if brake acknowledgement is not as +expected during brake opening: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</user_manual_desc> + <rnd_desc>Mechanical brake opening failed</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_BrkOpenNotAllowedFlt</handle> + <module>MechBrake_ctrl</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Mech brk opening not allowed</event_name> + <short_description>Mechanical brake opening not allowed</short_description> + <help_headers>Mechanical brake opening not allowed</help_headers> + <help_texts>Open conditions of mechanical brake cannot be fulfilled (for example, brake has been prevented from opening by parameter 44.11): +- Check mechanical brake settings in parameter group 44 (especially 44.11). +- Check that acknowledgement signal (if used) matches actual status of brake.</help_texts> + <user_manual_desc>Open conditions of mechanical brake cannot be fulfilled (for example, brake has been prevented from opening by parameter 44.11): +- Check mechanical brake settings in parameter group 44 (especially 44.11). +- Check that acknowledgement signal (if used) matches actual status of brake.</user_manual_desc> + <rnd_desc>Mechanical brake opening not allowed</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_DOLMotorFanFault</handle> + <module>DOL_Starter</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Motor fan</event_name> + <short_description>DOL motor starter fault</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>DOL motor starter fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_MotorFeedbackFlt</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Motor speed feedback</event_name> + <short_description>Motor speed feedback</short_description> + <help_headers>Motor speed feedback not received</help_headers> + <help_texts>Check encoder configuration. In case of incorrect motor speed check encoder connection and pulse nr.</help_texts> + <user_manual_desc>No motor speed feedback received. +- Check the setting of parameter 90.41, and the actual source selected.</user_manual_desc> + <rnd_desc>Motor speed feedback + +-Encoder speed differs too much from internal speed estimate. Check electrical connection of the encoder and pulse or sin/cos nr. + +</rnd_desc> + <aux_codes> + <aux_code code="3FC"> + <names>Incorrect motor feedback configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3FD"> + <names>Incorrect motor speed</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_OverSpeedFlt</handle> + <module>TORQ_CHAIN_COMMON</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Overspeed</event_name> + <short_description>Overspeed fault</short_description> + <help_headers>Overspeed fault</help_headers> + <help_texts>Motor is turning faster than highest allowed speed due to incorrectly set minimum/maximum speed, insufficient braking torque or changes in load when using torque reference. +-Check minimum/maximum speed settings, parameters 30.11 Minimum speed and 30.12 Maximum speed. +-Check adequacy of motor braking torque. +-Check applicability of torque control. +-Check need for brake chopper and resistor(s).</help_texts> + <user_manual_desc>Motor is turning faster than highest allowed speed +Check +-par. 30.11, 30.12 +-adequacy of motor braking torque +-applicability of torque control +-need for brake chopper and resistor(s)</user_manual_desc> + <rnd_desc>Overspeed</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_EF_InternalFlt</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Encoder internal</event_name> + <short_description>Encoder interface internal fault</short_description> + <help_headers>Encoder interface internal fault</help_headers> + <help_texts>Encoder interface internal fault. Contact your local ABB representative.</help_texts> + <user_manual_desc>Internal fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Feedback driver internal fault.</rnd_desc> + <aux_codes> + <aux_code code="7D0"> + <names>Internal fault active (consult ABB representative)</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7D3"> + <names>Invalid msg queue 3 (consult ABB representative)</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7D4"> + <names>Invalid msg queue 4 (consult ABB representative)</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7D5"> + <names>Invalid msg queue 5 (consult ABB representative)</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Encoder1Flt</handle> + <module>EncoderConfig_ENC1</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Encoder</event_name> + <short_description>Encoder has encountered a problem. Please check cables and connectors.</short_description> + <help_headers>Problem with encoder</help_headers> + <help_texts>Encoder problem. +- Check the settings in parameter group 92. After any changes, use parameter 91.10 to refresh the settings. +- Check the wiring and grounding of encoder. +- Check the event log for an auxiliary code. Contact your local ABB representative, quoting the code.</help_texts> + <user_manual_desc/> + <rnd_desc>Encoder faulted</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FeedbackConfigFlt</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Speed fbk configuration</event_name> + <short_description>Speed feedback configuration incorrect</short_description> + <help_headers>Speed feedback configuration incorrect</help_headers> + <help_texts>Speed feedback configuration incorrect, eg. an encoder that is not present is selected as the feedback interface. +- Check the feedback source selection parameters in group 90 Feedback selection. In case the source is an encoder interface, check parameter settings in groups 91 Encoder module settings, 92 Encoder 1 configuration and 93 Encoder 2 configuration.</help_texts> + <user_manual_desc/> + <rnd_desc>Speed feedback configuration</rnd_desc> + <aux_codes> + <aux_code code="3E8"> + <names>Adapter 1 and adapter 2 have the same node number</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3E9"> + <names>Adapter 1 not found</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3EA"> + <names>Adapter 2 not found</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3EB"> + <names>Encoder 1 not compatible with selected adapter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3EC"> + <names>Encoder 2 not compatible with selected adapter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_LoadFeedbackFlt</handle> + <module>EncoderFeedback_Common</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Load position feedback</event_name> + <short_description>Load position feedback fault. Please check cables and connectors. Check load config pars.</short_description> + <help_headers>No load speed feedback received</help_headers> + <help_texts>Check configuration of load encoder. In case of Check encoder electrical connection and mechanical mounting. Check encoder pulse nr.</help_texts> + <user_manual_desc>No load speed feedback received. +- Check the setting of parameter 90.51, and the actual source selected. In case the source is an encoder interface, check parameter settings in groups 91, 92 and 93.</user_manual_desc> + <rnd_desc>Load feedback</rnd_desc> + <aux_codes> + <aux_code code="406"> + <names>Incorrect load feedback configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="407"> + <names>Incorrect load speed</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Emergency_ramp_failed</handle> + <module>Event_functions</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Emergency ramp failed</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>0x73B0</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Stop_failed</handle> + <module>Event_functions</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Stop failed</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>0x73B1</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OverFrequencyFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Overfrequency</event_name> + <short_description>Output frequency too high.</short_description> + <help_headers>Output frequency too high.</help_headers> + <help_texts>Output frequency too high.</help_texts> + <user_manual_desc>Output frequency too high.</user_manual_desc> + <rnd_desc>Absolute output frequency has exceeded internal fault limit.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB1CommFault</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FBA A communication</event_name> + <short_description>Fieldbus adapter module A communication fault</short_description> + <help_headers>Fieldbus adapter module A communication fault</help_headers> + <help_texts>Cyclical communication between drive and fieldbus adapter module A or between PLC and fieldbus adapter module A is lost. +-Check status of fieldbus communication. See user documentation of fieldbus interface. +-Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data In and 53 FBA A data out. +-Check cable connections. +-Check if communication master is able to communicate.</help_texts> + <user_manual_desc>Cyclical communication between drive and FBA A or between PLC and FBA A is lost +Check +-fieldbus communication status (see fieldbus interface manuals) +-settings of param. groups 50-53 +-cable connections +-if communication master is able to communicate</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB2CommFault</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FBA B communication</event_name> + <short_description>Fieldbus adapter B communication fault</short_description> + <help_headers>Fieldbus adapter B communication fault</help_headers> + <help_texts>Cyclical communication between drive and fieldbus adapter module B or between PLC and fieldbus adapter module B is lost. +-Check status of fieldbus communication. See user documentation of fieldbus interface. +-Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data In and 53 FBA A data out. +-Check cable connections. +-Check if communication master is able to communicate.</help_texts> + <user_manual_desc>Cyclical communication between drive and FBA B or between PLC and FBA B is lost. +Check +-fieldbus communication status (see fieldbus interface manuals) +-settings of param. groups 50-53 +-cable connections +-if communication master is able to communicate</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FA2FA_DDCS_Com_loss</handle> + <module>DDCS</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>INU-LSU comm loss</event_name> + <short_description>DDCS communication between drives is lost. Message update took longer than timeout.</short_description> + <help_headers>INU-LSU Com loss</help_headers> + <help_texts>Check optical fibres and FDCO adapters functionality. FDCO should have three lights on, green led and two red leds</help_texts> + <user_manual_desc/> + <rnd_desc>If Datasets are not updated in time specified by fa2fa_ddcs_com_loss_timeout, fault or warning is thrown.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_DDCS_comm_loss</handle> + <module>DDCS</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DDCS controller comm loss</event_name> + <short_description>DDCS communication between drive and external controller is lost.</short_description> + <help_headers>Master/follower communication loss</help_headers> + <help_texts>Check status of controller. See user documentation of controller. Check settings of parameter group 60 DDCS communication. Check cable connections. If necessary, replace cables.</help_texts> + <user_manual_desc/> + <rnd_desc>If Datasets are not updated in time specified by ddcs_adtimeout, fault or warning is thrown.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_MF_DDCS_Com_loss</handle> + <module>DDCS</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>M/F comm loss</event_name> + <short_description>DDCS communication between drives is lost. Message update took longer than timeout.</short_description> + <help_headers>Master/follower communication loss</help_headers> + <help_texts>Check optical fibres and FDCO adapters functionality. FDCO should have three lights on, green led and two red leds</help_texts> + <user_manual_desc/> + <rnd_desc>Master drive: Aux. code is node number of the first lost follower. +Follower drive: Aux code is 0. +</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Line_side_converter_faulted</handle> + <module>INU_LSUCtrl</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Line side unit faulted</event_name> + <short_description>Line side unit has tripped to fault. Check LSU fault log.</short_description> + <help_headers/> + <help_texts>LSU faulted. It causes INU to fault after trip delay time, when drive is in INU-ISU communication mode.</help_texts> + <user_manual_desc/> + <rnd_desc>Line side unit has tripped so INU goes to fault mode.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_LSU_charge_failed</handle> + <module>INU_LSUCtrl</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>LSU charge failed</event_name> + <short_description>LSU charge took longer than 15 seconds. Check LSU charging logic.</short_description> + <help_headers/> + <help_texts>LSU charge took longer than 15 seconds. Check LSU charging logic.</help_texts> + <user_manual_desc>LSU charge took longer than 15 seconds. Check LSU charging logic.</user_manual_desc> + <rnd_desc>LSU charge took longer than 15 seconds.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_LSU_Start</handle> + <module>INU_LSUCtrl</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>LSU start failed</event_name> + <short_description>Line side unit did not start (eg. reach READY_REF state) in time determined in parameter 60.83 (default 15s).</short_description> + <help_headers/> + <help_texts>Line side unit did not start (eg. reach READY_REF state) in time determined in parameter 60.83 LSU max charging time (default 15s).</help_texts> + <user_manual_desc>Line side unit did not start (eg. reach READY_REF state) in time determined in parameter 60.83 (default 15s).</user_manual_desc> + <rnd_desc>Line side unit did not start (eg. reach READY_REF state) in 15 seconds.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_TUCSO_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>TUCSO fault</event_name> + <short_description>FSO subsystem fault</short_description> + <help_headers>FSO subsystem fault.</help_headers> + <help_texts>FSO subsystem fault.</help_texts> + <user_manual_desc>FSO subsystem fault.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSO_FAULTS_GEN</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO general fault</event_name> + <short_description>FSO general fault</short_description> + <help_headers>FSO makes first a warning, then this General fault.</help_headers> + <help_texts>This fault always follows certain malfunctions which the FSO module indicates by warnings. The FSO module generates a warning indication first to allow the drive to control the system to a safe state after which the drive trips (to this fault).</help_texts> + <user_manual_desc>This fault always follows certain malfunctions which the FSO module indicates by warnings. The FSO module generates a warning indication first to allow the drive to control the system to a safe state after which the drive trips (to this fault).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_StopCompleted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO stop completed</event_name> + <short_description>FSO stop completed</short_description> + <help_headers>FSO stop completed</help_headers> + <help_texts>FSO module has completed STO, SS1 or SSE function.</help_texts> + <user_manual_desc>FSO module has completed STO, SS1 or SSE function.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_SafeSpeedLimit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO safe speed limit</event_name> + <short_description>FSO safe speed limit</short_description> + <help_headers>FSO safe speed limit</help_headers> + <help_texts>Motor actual speed exceeded a safe speed limit of the FSO module.</help_texts> + <user_manual_desc>Motor actual speed exceeded a safe speed limit of the FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_OutOfEmeRamp</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO out of eme ramp</event_name> + <short_description>FSO out of eme ramp</short_description> + <help_headers>FSO out of emergency ramp.</help_headers> + <help_texts>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.103 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.103 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_RampCoasted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO ramp coasted</event_name> + <short_description>FSO ramp coasted</short_description> + <help_headers>Drive coasted the motor during ramp.</help_headers> + <help_texts>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (200.163 Zero speed without encoder).</help_texts> + <user_manual_desc>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (200.163 Zero speed without encoder).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_OutOfSafeRamp</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO out of safe ramp</event_name> + <short_description>FSO out of safe ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_OutOfSDI</handle> + <module>FS_FA</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO out of SDI</event_name> + <short_description>FSO out of SDI.</short_description> + <help_headers>FSO out of SDI.</help_headers> + <help_texts>Motor was not rotating to the allowed direction.</help_texts> + <user_manual_desc>Motor was not rotating to the allowed direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_POUS_premature</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO premature POUS</event_name> + <short_description>FSO premature POUS</short_description> + <help_headers>POUS was requested while drive was still on.</help_headers> + <help_texts>POUS was requested while drive was still modulating. POUS is supposed to be activated when drive is stopped.</help_texts> + <user_manual_desc>POUS was requested while drive was still modulating. POUS is supposed to be activated when drive is stopped.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_Undef</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO undefined fault</event_name> + <short_description>FSO undefined fault</short_description> + <help_headers>FSO undefined fault</help_headers> + <help_texts>FSO new version, undefined fault in Drive event system. Contact ABB.</help_texts> + <user_manual_desc>FSO new version, undefined fault in Drive event system. Contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_passivated</handle> + <module>FS_FA</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO passivated</event_name> + <short_description>FSO passivated</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO module is passivated due safetybus problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_undefined_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx undefined fault</event_name> + <short_description>FSx undefined fault</short_description> + <help_headers>FSx undefined fault</help_headers> + <help_texts>FSx new version, undefined fault in Drive event system. Contact ABB.</help_texts> + <user_manual_desc>FSx undefined fault is not yet defined inside the drive. Gather the AUX codes from this fault and contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_internal_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx internal fault</event_name> + <short_description>FSx internal fault; change FSx and send it back to factory</short_description> + <help_headers>FSx internal fault</help_headers> + <help_texts>Replace FSx and send the faulty one back to factory. There is no way to fix the FSx.</help_texts> + <user_manual_desc>FSx internal faults, like CPU or memory or peripherals: No possibility to fix.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_STO_diagnostics_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx STO diagnostics fault</event_name> + <short_description>FSx STO fault; check STO cabling</short_description> + <help_headers>FSX STO fault</help_headers> + <help_texts>There is something wrong with STO cabling or inside the Drive.</help_texts> + <user_manual_desc>FSX STO fault; there is something wrong with STO cabling or inside the Drive.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_temperature_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx temperature fault</event_name> + <short_description>FSx temperature</short_description> + <help_headers>FSx temperature</help_headers> + <help_texts>FSX temperature fault, mainly over temperature</help_texts> + <user_manual_desc>FSX temperature fault, mainly over temperature</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_configuration_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSx configuration fault</event_name> + <short_description>FSX configuration fault; check configuration</short_description> + <help_headers>FSX configuration fault</help_headers> + <help_texts>FSX configuration fault; check configuration</help_texts> + <user_manual_desc>FSX configuration is not valid</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_communication_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx communication fault</event_name> + <short_description>FSX communication fault; FSX-CU communication fault</short_description> + <help_headers>FSX communication fault.</help_headers> + <help_texts>FSX communication fault; FSX-CU communication fault. Check all connections. See AUX code for more details.</help_texts> + <user_manual_desc>FSX communication fault; FSX-CU communication fault. Check all connections. See AUX code for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_safety_ramp_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx safety ramp fault</event_name> + <short_description>Safety ramp did not finish in predictable way</short_description> + <help_headers>FS safety ramp fault</help_headers> + <help_texts>Safety ramp did not finish in predictable way</help_texts> + <user_manual_desc>FS safety ramp fault: Safety ramp did not finish in predictable way</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_ULC_ULFault</handle> + <module>User_Load_Curve</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>ULC underload</event_name> + <short_description>ULC -- an overload fault has occurred</short_description> + <help_headers>ULC -- Underload Fault</help_headers> + <help_texts>ULC -- an underload fault has occurred</help_texts> + <user_manual_desc>ULC -- an underload fault has occurred</user_manual_desc> + <rnd_desc>ULC -- an underload fault has occurred</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_ULC_OLFault</handle> + <module>User_Load_Curve</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>ULC overload</event_name> + <short_description>ULC -- an overload fault has occurred</short_description> + <help_headers>ULC -- Overload Fault</help_headers> + <help_texts>ULC -- an overload fault has occurred</help_texts> + <user_manual_desc>ULC -- an overload fault has occurred</user_manual_desc> + <rnd_desc>ULC -- an overload fault has occurred</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_AI_Supervised_Fault</handle> + <module>FA_IO_AI</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>AI Supervision</event_name> + <short_description>Analog In Supervision</short_description> + <help_headers>Check Analog Input Values</help_headers> + <help_texts>Analog Input Value has violated user set MIN or MAX.</help_texts> + <user_manual_desc>Analog In Supervision Fault</user_manual_desc> + <rnd_desc>AI Supervision Fault</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>AI1LessMIN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>AI1GreaterMAX</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>AI2LessMIN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>AI2GreaterMAX</names> + <user_manual_desc/> + </aux_code> + <aux_code code="101"> + <names>Extension 1 AI1 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="102"> + <names>Extension 1 AI1 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="103"> + <names>Extension 1 AI2 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="104"> + <names>Extension 1 AI2 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="201"> + <names>Extension 2 AI1 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="202"> + <names>Extension 2 AI1 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="203"> + <names>Extension 2 AI2 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="204"> + <names>Extension 2 AI2 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="301"> + <names>Extension 3 AI1 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="302"> + <names>Extension 3 AI1 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="303"> + <names>Extension 3 AI2 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="304"> + <names>Extension 3 AI2 greater than maximum</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_SupervFlt</handle> + <module>Supervision</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Signal supervision</event_name> + <short_description>Signal supervision 1</short_description> + <help_headers/> + <help_texts>Check the source of the fault.</help_texts> + <user_manual_desc>Fault generated by a signal supervision function. +Check the source of the fault (parameter 32.07).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_SupervFlt2</handle> + <module>Supervision</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Signal supervision 2</event_name> + <short_description>Signal supervision 2</short_description> + <help_headers/> + <help_texts>Check the source of the fault.</help_texts> + <user_manual_desc>Fault generated by a signal supervision function. +Check the source of the fault (parameter 32.17).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_SupervFlt3</handle> + <module>Supervision</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Signal supervision 3</event_name> + <short_description>Signal supervision 3</short_description> + <help_headers/> + <help_texts>Check the source of the fault</help_texts> + <user_manual_desc>Fault generated by a signal supervision function. +Check the source of the fault (parameter 32.27).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_ExternalFault</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External fault</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc>External fault</user_manual_desc> + <rnd_desc>External fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_External1Flt</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External fault 1</event_name> + <short_description>External fault 1</short_description> + <help_headers>External fault 1</help_headers> + <help_texts>Fault in external device 1. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.01.</help_texts> + <user_manual_desc>Fault in external device 1. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.01.</user_manual_desc> + <rnd_desc>External fault 1</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_External2Flt</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External fault 2</event_name> + <short_description>External fault 2</short_description> + <help_headers>External fault 2</help_headers> + <help_texts>Fault in external device 2. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.03.</help_texts> + <user_manual_desc>Fault in external device 2. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.03.</user_manual_desc> + <rnd_desc>External fault 2</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_External3Flt</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External fault 3</event_name> + <short_description>External fault 3</short_description> + <help_headers>External fault 1</help_headers> + <help_texts>Fault in external device 3. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.05.</help_texts> + <user_manual_desc>Fault in external device 3. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.05.</user_manual_desc> + <rnd_desc>External fault 3</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_External4Flt</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External fault 4</event_name> + <short_description>External fault 4</short_description> + <help_headers>External fault 4</help_headers> + <help_texts>Fault in external device 4. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.07.</help_texts> + <user_manual_desc>Fault in external device 4. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.07.</user_manual_desc> + <rnd_desc>External fault 4</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_External5Flt</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External fault 5</event_name> + <short_description>External fault 5</short_description> + <help_headers>External fault 5</help_headers> + <help_texts>Fault in external device 5. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.09.</help_texts> + <user_manual_desc>Fault in external device 1. (This information is configured through one of programmable digital inputs.) +- Check external devices for faults. +- Check setting of parameter 31.09.</user_manual_desc> + <rnd_desc>External fault 5</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_CurrCalibWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Current calibration</event_name> + <short_description>Current calibration about to be performed</short_description> + <help_headers>Current calibration about to be performed</help_headers> + <help_texts>Current offset and gain measurement calibration will be performed at next start.</help_texts> + <user_manual_desc>Current offset and gain measurement calibration will be performed at next start.</user_manual_desc> + <rnd_desc>Current calibration active</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>OverCurrentWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Overcurrent</event_name> + <short_description>Output current has exceeded internal fault limit.</short_description> + <help_headers>Output current has exceeded internal fault limit</help_headers> + <help_texts>Output current has exceeded internal fault limit. +- Check motor load. +- Check acceleration times in parameter group 23 Speed reference ramp. +- Check motor and motor cable (including phasing and delta/star connection). +- Check that the start-up data in parameter group 99 corresponds to the motor rating plate. +- Check that there are no power factor correction capacitors or surge absorbers +in motor cable. +- Check encoder cable (including phasing).</help_texts> + <user_manual_desc>Output current has exceeded internal fault limit. Check: +- motor load +- acceleration times +- motor and motor cabl +- start-up data in parameter group 99 +- there are no power factor correction capacitor +- encoder cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>EarthWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Earth leakage</event_name> + <short_description>Earth leakage warning</short_description> + <help_headers>Earth leakage warning</help_headers> + <help_texts>Load unbalance in eg, motor or cable +Check +-no power factor correction capacitors or surge absorbers +-no earth fault in cables: measure insulation resistances +If no earth fault detected, contact ABB.</help_texts> + <user_manual_desc>Load unbalance in eg, motor or cable +Check +-no power factor correction capacitors or surge absorbers +-no earth fault in cables: measure insulation resistances +If no earth fault detected, contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ShortCircuitWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Short circuit</event_name> + <short_description>Short-circuit in motor cable(s) or motor.</short_description> + <help_headers>Short-circuit in motor cable(s) or motor</help_headers> + <help_texts>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable.</help_texts> + <user_manual_desc>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>IGBTOverLoadAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>IGBT overload</event_name> + <short_description>Excessive IGBT junction to case temperature</short_description> + <help_headers>Excessive IGBT junction to case temperature</help_headers> + <help_texts>Excessive IGBT junction to case temperature. This warning protects the IGBT(s) +and can be activated by a short circuit in the motor cable. +- Check motor cable.</help_texts> + <user_manual_desc>Excessive IGBT junction to case temperature. This warning protects the IGBT(s) +and can be activated by a short circuit in the motor cable. +- Check motor cable.</user_manual_desc> + <rnd_desc>dTjc warning</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUIDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU current difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Difference check warning for currents</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUEFWarning</handle> + <module>TUCOS_BU_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>BU earth leakage</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Earth leakage warning detected by the branching unit: sum of all currents is exceeding the level.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUCDDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU commutation difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check warning for CDX and CDY.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>OvervoltageWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>DC link overvoltage</event_name> + <short_description>DC link overvoltage warning</short_description> + <help_headers>DC link overvoltage warning</help_headers> + <help_texts>Excessive intermediate circuit DC voltage +-Check that overvoltage controller is on, parameter 30.30 Overvoltage control. +-Check mains for static or transient overvoltage. +-Check brake chopper and resistor (if used). +-Check deceleration time. +-Use coast-to-stop function (if applicable). +-Retrofit frequency converter with brake chopper and brake resistor.</help_texts> + <user_manual_desc>Excessive intermediate circuit DC voltage +Check +-p. 30.30 Overvoltage control +-mains for static or transient overvoltage +-brake chopper/resistor +-decel. time +Use coast-to-stop. +Retrofit drive with chopper and resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>UndervoltageWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>DC link undervoltage</event_name> + <short_description>DC link undervoltage warning</short_description> + <help_headers>DC link undervoltage warning</help_headers> + <help_texts>Intermediate circuit DC voltage is not sufficient due to missing mains phase, blown fuse or rectifier bridge internal fault. +-Check supply and fuses.</help_texts> + <user_manual_desc>Intermediate circuit DC voltage is not sufficient due to missing mains phase, blown fuse or rectifier bridge internal fault. +-Check supply and fuses.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_DcNotChargedWrng</handle> + <module>DC_charge</module> + <bit_handle/> + <event_type> + <warning> + <event_name>DC not charged</event_name> + <short_description>DC voltage too low</short_description> + <help_headers>DC voltage too low</help_headers> + <help_texts>The voltage of the intermediate DC circuit has not yet risen to operating level. +- Check the input voltage setting in parameter 95.01. +- Check the input voltage. +- If the problem persists, contact your local ABB representative.</help_texts> + <user_manual_desc>The voltage of the intermediate DC circuit has not yet risen to operating level. +- Check the input voltage setting in parameter 95.01. +- Check the input voltage. +- If the problem persists, contact your local ABB representative.</user_manual_desc> + <rnd_desc>DC not charged</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUUCDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU DC link difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check warning for DC link voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUUmainDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU voltage difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check warning for main voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_CableOverlWrng</handle> + <module>CableThermProt</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor cable overload</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ExtTemp_Adapter_wrng</handle> + <module>ExtTemp</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Incorrect temperature sensor setup</event_name> + <short_description>Temperature cannot be supervised due to incorrect setup or problem in the measurement circuit.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Warning code 0xA490</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ExtTemp1_wrng</handle> + <module>ExtTemp</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>External temperature 1</event_name> + <short_description>External temperature 1 too high</short_description> + <help_headers>External temperature 1 too high</help_headers> + <help_texts>Check the value of parameter 35.02 +Measured temperature 1. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the warning limit for measured +temperature 1 in parameter group +35 Motor thermal protection.</help_texts> + <user_manual_desc>Check the value of parameter 35.02 +Measured temperature 1. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the warning limit for measured +temperature 1 in parameter group +35 Motor thermal protection.</user_manual_desc> + <rnd_desc>External Temperature 1</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ExtTemp2_wrng</handle> + <module>ExtTemp</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>External temperature 2</event_name> + <short_description>External temperature 2 too high</short_description> + <help_headers>External temperature 2 too high</help_headers> + <help_texts>Check the value of parameter +35.03 Measured temperature 2. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the warning limit for measured +temperatures 2 in parameter group +35 Motor thermal protection.</help_texts> + <user_manual_desc>Check the value of parameter +35.03 Measured temperature 2. +Check the cooling of the motor (or other +equipment whose temperature is being +measured). +Check the warning limit for measured +temperatures 2 in parameter group +35 Motor thermal protection.</user_manual_desc> + <rnd_desc>External Temperature 2</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FEX_01_WarningSlot1</handle> + <module>ExtTemp</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor temperature 1</event_name> + <short_description>Motor temperature 1</short_description> + <help_headers>Motor temperature 1</help_headers> + <help_texts>Motor temperature is high or the thermistor is in short circuit or disconnected. +Check motor cooling. +Check thermistor connection.</help_texts> + <user_manual_desc>The FPTC-01- or FPTC-02- option module in option slot 1 of the control unit indicates a warning. +The PTC thermistor connected to X3 of the option module indicates a high motor temperature. +Warning is activated also if the thermistor is short circuited or disconnected.</user_manual_desc> + <rnd_desc>The FPTC-01- or FPTC-02-module in slot 1 of the control unit indicates a warning. +The PTC thermistor connected to X3 of the option module indicates a high motor temperature. +Warning is activated also if the thermistor is short circuited or disconnected.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Thermistor is short circuited or disconnected.</cause> + <what_to_do>Check the thermistor connection. +Measure the thermistor resistance.</what_to_do> + </item> + <item> + <cause>Motor temperature is too high.</cause> + <what_to_do>Check the cooling of the motor. +Check motor load and drive ratings.</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FEX_01_WarningSlot2</handle> + <module>ExtTemp</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor temperature 2</event_name> + <short_description>Motor temperature 2</short_description> + <help_headers>Motor temperature 2</help_headers> + <help_texts>Motor temperature is high or the thermistor is in short circuit or disconnected. +Check motor cooling. +Check thermistor connection.</help_texts> + <user_manual_desc>The FPTC-01- or FPTC-02- option module in option slot 2 of the control unit indicates a warning. +The PTC thermistor connected to X3 of the option module indicates a high motor temperature. +Warning is activated also if the thermistor is short circuited or disconnected.</user_manual_desc> + <rnd_desc>The FPTC-01- or FPTC-02-module in slot 2 of the control unit indicates a warning. +The PTC thermistor connected to X3 of the option module indicates a high motor temperature. +Warning is activated also if the thermistor is short circuited or disconnected.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Thermistor is short circuited or disconnected.</cause> + <what_to_do>Check the thermistor connection. +Measure the thermistor resistance.</what_to_do> + </item> + <item> + <cause>Motor temperature is too high.</cause> + <what_to_do>Check the cooling of the motor. +Check motor load and drive ratings.</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FEX_01_WarningSlot3</handle> + <module>ExtTemp</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor temperature 3</event_name> + <short_description>Motor temperature 3</short_description> + <help_headers>Motor temperature 3</help_headers> + <help_texts>Motor temperature is high or the thermistor is in short circuit or disconnected. +Check motor cooling. +Check thermistor connection.</help_texts> + <user_manual_desc>The FPTC-01- or FPTC-02- option module in option slot 3 of the control unit indicates a warning. +The PTC thermistor connected to X3 of the option module indicates a high motor temperature. +Warning is activated also if the thermistor is short circuited or disconnected.</user_manual_desc> + <rnd_desc>The FPTC-01- or FPTC-02-module in slot 3 of the control unit indicates a warning. +The PTC thermistor connected to X3 of the option module indicates a high motor temperature. +Warning is activated also if the thermistor is short circuited or disconnected.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Thermistor is short circuited or disconnected.</cause> + <what_to_do>Check the thermistor connection. +Measure the thermistor resistance.</what_to_do> + </item> + <item> + <cause>Motor temperature is too high.</cause> + <what_to_do>Check the cooling of the motor. +Check motor load and drive ratings.</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_CBTemp_WRNG</handle> + <module>Electronics_temp_meas</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Control board temperature</event_name> + <short_description>Control board temperature</short_description> + <help_headers>Control board temperature</help_headers> + <help_texts>Check proper cooling of the cabinet or +if there is a sensor fault, aux. code = 1, change the control board.</help_texts> + <user_manual_desc>Control board temperature is too high. +Or there is a sensor fault (aux. code = 1), change the control board.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>IGBT_OvertempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>IGBT overtemperature</event_name> + <short_description>Estimated drive IGBT temperature is excessive.</short_description> + <help_headers>Estimated drive IGBT temperature is excessive</help_headers> + <help_texts>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Too much current in off-line thermal model while thermal current limitation passivated.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>CoolingAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Cooling</event_name> + <short_description>Drive module temperature is excessive.</short_description> + <help_headers>Drive module temperature is excessive</help_headers> + <help_texts>Drive module temperature is excessive. +- Check ambient temperature. If it exceeds 40 °C (104 °F), ensure that load current does not exceed derated load capacity of drive. See appropriate Hardware Manual. +- Check drive module cooling air flow and fan operation. +- Check inside of cabinet and heatsink of drive module for dust pick-up. Clean +whenever necessary.</help_texts> + <user_manual_desc>Drive module temperature is excessive. +- Check ambient temperature. See appropriate Hardware Manual. +- Check cooling air flow and fan operation. +- Check heatsink of drive module for dust pick-up. Clean whenever necessary.</user_manual_desc> + <rnd_desc>On-line thermal model, cooling diagnostics alarm.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>TempWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Excess temperature</event_name> + <short_description>Temperature measurement from the power unit is too high</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>Measured temperature from power unit is too high.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>TempDifWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Excess temperature difference</event_name> + <short_description>Temperature difference between power unit IGBTs is too high</short_description> + <help_headers>High temperature difference between the IGBTs of different phases.</help_headers> + <help_texts>Check the motor cabling. +Check cooling of drive module(s).</help_texts> + <user_manual_desc>High temperature difference between the IGBTs of different phases.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>PCB_SpaceCoolingWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PCB space cooling</event_name> + <short_description>PCB space cooling warning</short_description> + <help_headers>PCB space cooling warning</help_headers> + <help_texts>Check cooling fan inside the PCB space.</help_texts> + <user_manual_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded warning limit. +-Check cooling fan inside the PCB space.</user_manual_desc> + <rnd_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded warning limit.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>IGBTTempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>IGBT temperature</event_name> + <short_description>Drive IGBT temperature is excessive.</short_description> + <help_headers>Drive IGBT temperature is excessive</help_headers> + <help_texts>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Tj has exceeded alarm limit</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_AmbTemp_AmbientTemperatureWrng</handle> + <module>Temperature_config</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Ambient temperature</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>LinkErrWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU communication</event_name> + <short_description>Communication errors detected between the drive control unit and the power unit.</short_description> + <help_headers>Communication errors detected between the drive control unit and the power unit</help_headers> + <help_texts>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</help_texts> + <user_manual_desc>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</user_manual_desc> + <rnd_desc>Some PU communication diagnostic counter is counting => warning</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FanCtrl_FanWarning</handle> + <module>FA_FanCtrl</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Fan</event_name> + <short_description>Cooling fan stuck or disconnected</short_description> + <help_headers>Cooling fan stuck or disconnected</help_headers> + <help_texts>Cooling fan stuck or disconnected. +- Check fan operation and connection. Replace fan if faulty.</help_texts> + <user_manual_desc>Cooling fan stuck or disconnected. +- Check fan operation and connection. Replace fan if faulty.</user_manual_desc> + <rnd_desc>Fan does not follow the reference.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FanCtrl_AuxFanWarning</handle> + <module>FA_FanCtrl</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Auxiliary fan missing</event_name> + <short_description>Auxiliary fan is not connected or broken.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>Auxiliary fan is not connected or broken. Check the auxiliary fan connection or replace the fan.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>STOWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Safe torque off</event_name> + <short_description>Safe torque off circuit fault in the power unit side</short_description> + <help_headers>Safe torque off function is active</help_headers> + <help_texts>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections. For more information, see appropriate drive +hardware manual.</help_texts> + <user_manual_desc>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>TempSensorWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Measurement circuit temperature</event_name> + <short_description>Problem with internal temperature measurement of the drive</short_description> + <help_headers>Problem with internal temperature measurement of the drive</help_headers> + <help_texts>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>PFWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU board powerfail</event_name> + <short_description>Power unit power supply failure</short_description> + <help_headers>Power unit power supply failure</help_headers> + <help_texts>Power unit power supply failure. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Power unit power supply failure. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>PSL2DriverInternalWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU communication internal</event_name> + <short_description>Communication errors detected between the drive control unit and the power unit.</short_description> + <help_headers>Communication errors detected between the drive control unit and the power unit.</help_headers> + <help_texts>Communication errors detected between the drive control unit and the power unit. +- Check the connections between the drive control unit and the power unit.</help_texts> + <user_manual_desc>Communication errors detected between the drive control unit and the power unit. +- Check the connections between the drive control unit and the power unit.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ADCErrorWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Measurement circuit ADC</event_name> + <short_description>Measurement circuit fault</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>DFFWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Measurement circuit DFF</event_name> + <short_description>Measurement circuit fault</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>STSVWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU state feedback</event_name> + <short_description>PU state feedback</short_description> + <help_headers>PU state feedback</help_headers> + <help_texts>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</help_texts> + <user_manual_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</user_manual_desc> + <rnd_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>CHGWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Charging feedback</event_name> + <short_description>Charging feedback missing</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>The charging feedback is missing.</user_manual_desc> + <rnd_desc>Formerly INVD</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>RedundantMeasurementPSWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Redundant measurement</event_name> + <short_description>Redundant measurement</short_description> + <help_headers>Redundant measurement</help_headers> + <help_texts>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. (Solar applications)</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>OverTemp3LWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Overtemperature hw</event_name> + <short_description>Overtemperature hw detection (3L target specific)</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_SF_below_requested</handle> + <module>Switching_Frequency</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Switching frequency below requested</event_name> + <short_description>Actual switching frequency average is below what is required by the output frequency for adequate control performance.</short_description> + <help_headers>Switching frequency below requested</help_headers> + <help_texts>Check the hardware configuration for instances that may limit switching frequency reference.</help_texts> + <user_manual_desc>Actual switching frequency average is below what is required by the output frequency for adequate control performance. + +Check the hardware configuration for instances that may limit switching frequency reference.</user_manual_desc> + <rnd_desc>Actual switching frequency average is below what is required by the output frequency for adequate control performance.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_InternalSWWrng</handle> + <module>DRIVE_LOGIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Internal SW error</event_name> + <short_description>Internal SW error</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>0xA681 - 42625</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>FlashConsumptionSpeed</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Flash erase speed exceeded</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_PUSAVE_warning</handle> + <module>PU Save</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Data saving to power unit</event_name> + <short_description>An error detected in saving data to power unit.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>An error detected in saving data to power unit.</user_manual_desc> + <rnd_desc>An error detected in saving data to power unit. +Industial and standard drives harmonized event code is 0xA683</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_SDCardWrng</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>SD card</event_name> + <short_description>SD card</short_description> + <help_headers>SD card is not operational.</help_headers> + <help_texts>Check that the SD card is properly inserted in the control unit and that it is in working condition.</help_texts> + <user_manual_desc>SD card is not operating properly (with BCU control unit only). Saving power unit diagnostic data on SD card may not be possible.</user_manual_desc> + <rnd_desc>SD card is not operational.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_Power_fail_saving</handle> + <module>Power fail</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Power fail saving</event_name> + <short_description>Power fail saving</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>Power fail saving is requested too frequently. Due to the limited saving interval some of the requests do not trigger the saving and power fail data might be lost. This might be caused by DC voltage oscillation. +Check supply voltage.</user_manual_desc> + <rnd_desc>Power fail saving is requested too frequently. Due to the limited saving interval some of the requests do not trigger the saving and power fail data might be lost. This might be caused by DC voltage oscillation around the power fail UDC level.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_Checksum_mismatch_w</handle> + <module>Checksum</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Checksum mismatch</event_name> + <short_description>The actual checksum does not match any of the active approved checksums.</short_description> + <help_headers/> + <help_texts>Parameter 96.53 "Actual checksum" does not match any of the active approved checksums (parameters 96.56-59). Check the parameter configuration and approve the actual checksum if needed using parameter 96.54 "Checksum control word".</help_texts> + <user_manual_desc>The actual checksum does not match any of the active approved checksums.</user_manual_desc> + <rnd_desc>The actual checksum does not match any of the active approved checksums.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_Checksum_configuration_w</handle> + <module>Checksum</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Checksum configuration</event_name> + <short_description>Checksum has not been configured.</short_description> + <help_headers/> + <help_texts>Contact your local ABB representative for configuring checksum functionality or set parameter 96.54 "Checksum action" to "No action".</help_texts> + <user_manual_desc>Checksum functionality has not been configured and "Checksum action" has been set to some other than "No action".</user_manual_desc> + <rnd_desc>Checksum functionality has not been configured and "Checksum action" has been set to some other than "No action".</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_par_map_configuration</handle> + <module>ParameterMap</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Parameter map configuration</event_name> + <short_description>Parameter map configuration</short_description> + <help_headers>Parameter map configuration</help_headers> + <help_texts>Too many parameters in configuration file</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_mapped_par_value_cut</handle> + <module>ParameterMap</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Mapped parameter value cut</event_name> + <short_description>Mapped parameter value cut</short_description> + <help_headers>Mapped parameter value cut</help_headers> + <help_texts>Check parameter scaling and format.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>MotorNomValueAlarm</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor nominal value</event_name> + <short_description>Incorrect motor parameter values, or wrong drive dimensioning</short_description> + <help_headers>Incorrect motor parameter values, or wrong drive dimensioning</help_headers> + <help_texts>The motor parameters are set incorrectly. +- Check the settings of the motor configuration parameters in group 99. +The drive is not dimensioned correctly. +- Check that the drive is sized correctly for the motor.</help_texts> + <user_manual_desc>The motor parameters are set incorrectly. +- Check the settings of the motor configuration parameters in group 99. +The drive is not dimensioned correctly. +- Check that the drive is sized correctly for the motor.</user_manual_desc> + <rnd_desc>Motor data not given or motor/inu ratio not acceptable.</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>Motor slip frequency is too small</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Too big error between synch. and nominal speed</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Motor nom speed is higher than synch with p=1</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Motor nom current is not within allowed limits</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Motor nom voltage is not within allowed limits</names> + <user_manual_desc/> + </aux_code> + <aux_code code="6"> + <names>Motor nom power is higher than apparent power</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7"> + <names>Nom power not consistent with nom speed&torque</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>NoMotDataAlarm</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>No motor data</event_name> + <short_description>Parameters in group 99 have not been set.</short_description> + <help_headers>Parameters in group 99 have not been set</help_headers> + <help_texts>Parameters in group 99 have not been set. +- Check that all the required parameters in group 99 have been set. +Note: It is normal for this warning to appear during the start-up until the motor +data is entered.</help_texts> + <user_manual_desc>Parameters in group 99 have not been set. +- Check that all the required parameters in group 99 have been set. +Note: It is normal for this warning to appear during the start-up until the motor +data is entered.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_CatUnselectedWrng</handle> + <module>DC_charge</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Supply voltage unselected</event_name> + <short_description>Supply voltage unselected</short_description> + <help_headers>Supply voltage unselected</help_headers> + <help_texts>Set supply voltage in parameter 95.01.</help_texts> + <user_manual_desc>The supply voltage has not been defined. +Set supply voltage in parameter 95.01</user_manual_desc> + <rnd_desc>Supply voltage unselected</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_User_Lock_Open</handle> + <module>UserPasscode</module> + <bit_handle/> + <event_type> + <warning> + <event_name>User lock is open</event_name> + <short_description>User lock is open</short_description> + <help_headers>User lock is open</help_headers> + <help_texts>Activate the lock by inputting an invalid pass code to parameter "96.02 Pass code".</help_texts> + <user_manual_desc>Activate the lock by inputting an invalid pass code to "Pass code" parameter.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_Passcode_not_confirmed</handle> + <module>UserPasscode</module> + <bit_handle/> + <event_type> + <warning> + <event_name>User pass code not confirmed</event_name> + <short_description>User pass code not confirmed</short_description> + <help_headers>User pass code not confirmed</help_headers> + <help_texts>User pass code has been inputted to "Change user pass code" parameter but has not been confirmed with "Confirm user pass code" parameter.</help_texts> + <user_manual_desc>User pass code has been inputted to "Change user pass code" parameter but has not been confirmed with "Confirm user pass code" parameter.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>FB1ParConflictWrng</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FBA A parameter conflict</event_name> + <short_description>Fieldbus adapter A parameter conflict warning</short_description> + <help_headers>Fieldbus adapter A parameter conflict warning</help_headers> + <help_texts>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</help_texts> + <user_manual_desc>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>FB2ParConflictWrng</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FBA B Parameter conflict</event_name> + <short_description>Fieldbus adapter B parameter conflict warning</short_description> + <help_headers>Fieldbus adapter B parameter conflict warning</help_headers> + <help_texts>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</help_texts> + <user_manual_desc>The drive does not have a functionality requested by PLC, or requested functionality has not been activated. +-Check PLC programming. +-Check settings of parameter groups 50 Fieldbus adapter (FBA) and 51 FBA A settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_RefSrcParamWrng</handle> + <module>FA_miscellaneous</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Reference source parametrization</event_name> + <short_description>A reference source was simultaneously connected to two or more active reference source parameters of different units.</short_description> + <help_headers>Reference source parametrization</help_headers> + <help_texts>A reference source was simultaneously connected to two or more parameters of different units. Additionally, these parameters are actively used as reference. +Check parameterization.</help_texts> + <user_manual_desc>A reference source was simultaneously connected to two or more active reference source parameters of different units.</user_manual_desc> + <rnd_desc>A reference source was simultaneously connected to two or more active reference source parameters of different units.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>A reference source was simultaneously connected to two or more active reference source parameters of different units.</cause> + <what_to_do>Check that the same reference is not used in two or more active reference source parameters of different units. In that case, change parametrization.</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_AIParWrng</handle> + <module>FA_IO_AI</module> + <bit_handle/> + <event_type> + <warning> + <event_name>AI parametrization</event_name> + <short_description>AI parametrization error</short_description> + <help_headers>AI parametrization error</help_headers> + <help_texts>The current/voltage jumper setting of an analog input does not correspond to parameter settings. +Adjust either the jumper setting (on the drive control unit) or parameter 12.15/12.25. +Note: Control board reboot (either by cycling the power or through parameter 96.08 Control board boot) is required to validate any changes in the jumper settings.</help_texts> + <user_manual_desc>The current/voltage jumper setting of an analog input does not correspond to parameter settings. +Adjust either the jumper setting (on the drive control unit) or parameter 12.15/12.25. +Note: Control board reboot (either by cycling the power or through parameter 96.08 Control board boot) is required to validate any changes in the jumper settings.</user_manual_desc> + <rnd_desc>AI parametrization error.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ULC_configuration</handle> + <module>User_Load_Curve</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>ULC configuration</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>Invalid speed table</names> + <user_manual_desc>Invalid speed table</user_manual_desc> + </aux_code> + <aux_code code="1"> + <names>Invalid frequency table</names> + <user_manual_desc>Invalid frequency table</user_manual_desc> + </aux_code> + <aux_code code="2"> + <names>Invalid underload table</names> + <user_manual_desc>Invalid underload table</user_manual_desc> + </aux_code> + <aux_code code="3"> + <names>Invalid overload table</names> + <user_manual_desc>Invalid overload table</user_manual_desc> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MotorStall_wrng</handle> + <module>EVENTS_Autoreset</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor stall</event_name> + <short_description>Motor operating in stall region</short_description> + <help_headers>Motor operating in stall region</help_headers> + <help_texts>Motor is operating in stall region because of eg. excessive load or insufficient motor power. +- Check motor load and drive ratings. +- Check fault function parameters.</help_texts> + <user_manual_desc>Motor is operating in stall region because of eg. excessive load or insufficient motor power. +- Check motor load and drive ratings. +- Check fault function parameters.</user_manual_desc> + <rnd_desc>Motor stall</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_DOLMotorFanWarn</handle> + <module>DOL_Starter</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor fan</event_name> + <short_description>DOL motor starter warning</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>DOL motor starter warning</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_AdapterTempWrng</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FEN temperature</event_name> + <short_description>Error in temperature measurement with sensor connected to FEN encoder interface</short_description> + <help_headers>Error in temperature measurement with sensor connected to FEN encoder interface</help_headers> + <help_texts>1. Error in temperature measurement when temperature sensor (KTY or PTC)connected to encoder interface FEN-xx is used. +- Check that parameter 35.11/35.21 setting corresponds to actual encoder +interface installation. +2. Error in temperature measurement when KTY sensor connected to encoder interface FEN-01 is used. +- FEN-01 does not support temperature measurement with KTY sensor. Use PTC sensor or other encoder interface module.</help_texts> + <user_manual_desc/> + <rnd_desc>Error in temperature measurement when temperature sensor connected to encoder interface FEN-xx is used.</rnd_desc> + <aux_codes> + <aux_code code="4B0"> + <names>Adapter 1 not configured</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4B1"> + <names>Adapter 1 VIE logic too old</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4B2"> + <names>Adapter 1 temperature comm. loss</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4BA"> + <names>Adapter 2 not configured</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4BB"> + <names>Adapter 2 VIE logic too old</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4BC"> + <names>Adapter 2 temperature comm. loss</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BRResistorWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Brake resistor</event_name> + <short_description>Brake chopper power lower than required.</short_description> + <help_headers>Brake chopper power lower than required.</help_headers> + <help_texts>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor.</help_texts> + <user_manual_desc>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BcErWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Brake resistor wiring</event_name> + <short_description>Brake resistor wiring warning</short_description> + <help_headers>Brake resistor wiring warning</help_headers> + <help_texts>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged.</help_texts> + <user_manual_desc>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BrOvertempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>BR excess temperature</event_name> + <short_description>Excessive brake resistor temperature</short_description> + <help_headers>Excessive brake resistor temperature</help_headers> + <help_texts>Brake resistor temperature has exceeded warning limit defined by parameter 43.12 Brake resistor warning limit. +- Stop drive. Let resistor cool down. +- Check resistor overload protection function settings (parameter group 43 Brake chopper). +- Check parameter 43.12 Brake resistor warning limit. +- Check that braking cycle meets allowed limits.</help_texts> + <user_manual_desc>Brake resistor temperature has exceeded warning limit defined by parameter 43.12 Brake resistor warning limit. +- Stop drive. Let resistor cool down. +- Check parameter group 43 Brake chopper. +- Check that braking cycle meets allowed limits.</user_manual_desc> + <rnd_desc>Braking resistor thermal model alarm.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BrDataAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BR data</event_name> + <short_description>Incorrect braking resistor data.</short_description> + <help_headers>Incorrect braking resistor data</help_headers> + <help_texts>Incorrect braking resistor data. +Aux code = 1: The braking resistor resistance value is too low. +- Check that braking resistor resistance is sufficient. +Aux code = 2: The thermal protection of braking resistor is enabled but braking resistor thermal time constant is is not given. +- Check that braking resistor thermal time constant is given. +Aux code = 3: The thermal protection of braking resistor is enabled but braking resistor maximum power is is not given. +- Check that braking resistor maximum power is given.</help_texts> + <user_manual_desc>The braking resistor value is too low +- Check that braking resistor resistance is sufficient. +The thermal protection of braking resistor is enabled but data is not given +- Check that braking resistor thermal time constant and maximum power are given.</user_manual_desc> + <rnd_desc>Braking resistor data is invalid (either too small resistor or thermal protection data not given altough thermal protection is enabled).</rnd_desc> + <aux_codes> + <aux_code code="0x1"> + <names>R Br too low</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x2"> + <names>Br Tau Th not given</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x3"> + <names>Br P Max not given</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_TTLOutputWrng</handle> + <module>EncoderFeedback_Common</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>TTL output</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes> + <aux_code code="4D8"> + <names>TTL out 1 invalid configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4D9"> + <names>TTL out 1 overfrequency</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4DA"> + <names>TTL out 1 invalid reference signal</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4DB"> + <names>TTL out 2 invalid configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4DC"> + <names>TTL out 2 overfrequency</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4DD"> + <names>TTL out 2 invalid reference signal</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4E2"> + <names>Incorrect TTL out SW reference configuration</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_PositionLatchWrng</handle> + <module>EncoderFeedback_Common</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Position latch</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc>Position latch warning</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="4C4"> + <names>Latch 1 adapter comm loss</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4C5"> + <names>Latch 1 configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4C9"> + <names>Latch 2 adapter comm loss</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4CA"> + <names>Latch 2 configuration</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FeedbackConfigWrng</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Speed feedback configuration</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc>Feedback configuration has changed and encoder parameters must be refreshed.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_OptionCommLossWrng</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Encoder option comm loss</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ExtIOCommLossWrng</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <warning> + <event_name>ExtIO comm loss</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BcScWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BC short circuit</event_name> + <short_description>Brake chopper short circuit</short_description> + <help_headers>Brake chopper short circuit</help_headers> + <help_texts>Short circuit in brake chopper IGBT. +-Replace brake chopper. +-Ensure brake resistor is connected and not damaged.</help_texts> + <user_manual_desc>Short circuit in brake chopper IGBT. +-Replace brake chopper. +-Ensure brake resistor is connected and not damaged.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BcIgbtOvertempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>BC IGBT excess temperature</event_name> + <short_description>Excessive brake chopper IGBT temperature</short_description> + <help_headers>Excessive brake chopper IGBT temperature</help_headers> + <help_texts>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check for excessive ambient temperature. +- Check for cooling fan failure.Check for obstructions in the air flow. +- Check the dimensioning and cooling of the cabinet. +- Check resistor overload protection function settings (parameters 43.06…43.10). +- Check that braking cycle meets allowed limits. +- Check that drive supply AC voltage is not excessive.</help_texts> + <user_manual_desc>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check: for excessive ambient temperature, cooling fan, resistor overload protection function settings, braking duty cycle, drive supply AC voltage.</user_manual_desc> + <rnd_desc>BC IGBT thermal model warning</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_BrkClseFailedWrng</handle> + <module>MechBrake_ctrl</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Mechanical brake closing failed</event_name> + <short_description>Mechanical brake closing failed</short_description> + <help_headers>Mechanical brake closing failed</help_headers> + <help_texts>Mechanical brake control warning. Activated eg. if brake acknowledgement is not as +expected during brake closing: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</help_texts> + <user_manual_desc>Mechanical brake control warning. Activated eg. if brake acknowledgement is not as +expected during brake closing: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</user_manual_desc> + <rnd_desc>Mechanical brake closing failed</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_BrkOpenFailedWrng</handle> + <module>MechBrake_ctrl</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Mechanical brake opening failed</event_name> + <short_description>Mechanical brake opening failed</short_description> + <help_headers>Mechanical brake opening failed</help_headers> + <help_texts>Mechanical brake control warning. Activated eg. if brake acknowledgement is not as expected during brake opening: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</help_texts> + <user_manual_desc>Mechanical brake control warning. Activated eg. if brake acknowledgement is not as expected during brake opening: +- Check mechanical brake connection. +- Check mechanical brake settings in parameter group 44. +- Check that acknowledgement signal matches actual status of brake.</user_manual_desc> + <rnd_desc>Mechanical brake opening failed</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_BrkOpenNotAllowedWrng</handle> + <module>MechBrake_ctrl</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Mechanical brake opening not allowed</event_name> + <short_description>Mechanical brake opening not allowed</short_description> + <help_headers>Mechanical brake opening not allowed</help_headers> + <help_texts>Open conditions of mechanical brake cannot be fulfilled (for example, brake has been prevented from opening by parameter 44.11): +- Check mechanical brake settings in parameter group 44 (especially 44.11). +- Check that acknowledgement signal (if used) matches actual status of brake.</help_texts> + <user_manual_desc>Open conditions of mechanical brake cannot be fulfilled (for example, brake has been prevented from opening by parameter 44.11): +- Check mechanical brake settings in parameter group 44 (especially 44.11). +- Check that acknowledgement signal (if used) matches actual status of brake.</user_manual_desc> + <rnd_desc>Mechanical brake opening not allowed</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FIO11AIParWrng</handle> + <module>FA_ExtIO_Module1</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Extension AI parameterization</event_name> + <short_description>Extension AI parameterization</short_description> + <help_headers/> + <help_texts>Resolve mismatch between jumper settings in FIO/FAIO module and unit selection parameter</help_texts> + <user_manual_desc>Warns mismatch between parameter settings and hardware settings</user_manual_desc> + <rnd_desc>Warns mismatch between parameter settings and hardware settings</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ExtIO_conf_failure_warning</handle> + <module>FA_ExtIO_Module1</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Extension I/O configuration failure</event_name> + <short_description>Mismatch between extension I/O module type and type parameter.</short_description> + <help_headers>Mismatch between extension I/O module type and type parameter.</help_headers> + <help_texts>Extension I/O module type and type parameter don't match. +-Check that extension I/O module is correctly seated to the correct slot/node selected in parameter setup. To pinpoint the problem, try installing the modules into different slots/nodes. +-Check that extension I/O module type and type parameter match.</help_texts> + <user_manual_desc>Extension I/O module type and type parameter don't match. +-Check that extension I/O module is correctly seated to the correct slot/node selected in parameter setup. To pinpoint the problem, try installing the modules into different slots/nodes. +-Check that extension I/O module type and type parameter match.</user_manual_desc> + <rnd_desc>Mismatch between extension I/O module type and type parameter.</rnd_desc> + <aux_codes> + <aux_code code="0x0001"> + <names>Extension I/O module 1</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x0002"> + <names>Extension I/O module 2</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x0003"> + <names>Extension I/O module 3</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MotorFeedbackWrng</handle> + <module>EncoderFeedback_Common</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor speed feedback</event_name> + <short_description>Motor speed feedback has failed and drive continues operation with open loop control.</short_description> + <help_headers>Motor speed feedback not received</help_headers> + <help_texts>No motor speed feedback is received. +- Check the settings of the parameters in groups 90 Feedback selection, 91 +Encoder module settings, 92 Encoder 1 configuration and 93 Encoder 2 configuration. +- Check encoder installation.</help_texts> + <user_manual_desc>No motor speed feedback is received. +- Check the settings of the parameters in groups 90 Feedback selection, 91 +Encoder module settings, 92 Encoder 1 configuration and 93 Encoder 2 configuration. +- Check encoder installation.</user_manual_desc> + <rnd_desc>Motor speed feedback</rnd_desc> + <aux_codes> + <aux_code code="3FC"> + <names>Incorrect motor feedback configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3FD"> + <names>Incorrect motor speed</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_LoadFeedbackWrng</handle> + <module>EncoderFeedback_Common</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Load speed feedback</event_name> + <short_description>No load speed feedback received</short_description> + <help_headers>No load speed feedback received</help_headers> + <help_texts>No load speed feedback received. +- Check the setting of parameter 90.51, and the actual source selected. In case the source is an encoder interface, check parameter settings in groups 91, 92 and 93.</help_texts> + <user_manual_desc>No load speed feedback received. +- Check the setting of parameter 90.51, and the actual source selected. In case the source is an encoder interface, check parameter settings in groups 91, 92 and 93.</user_manual_desc> + <rnd_desc>Load feedback</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>Incorrect load feedback gear configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Incorrect feedconstant gear configuration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>No load feedback encoder</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>FB1CommWrng</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FBA A communication</event_name> + <short_description>Fieldbus adapter module A communication warning</short_description> + <help_headers>Fieldbus adapter module A communication warning</help_headers> + <help_texts>Cyclical communication between drive and fieldbus adapter module A or between PLC and fieldbus adapter module A is lost. +-Check status of fieldbus communication. See user documentation of fieldbus interface. +-Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data In and 53 FBA A data out. +-Check cable connections. +-Check if communication master is able to communicate.</help_texts> + <user_manual_desc>Cyclical communication between drive and FBA A or between PLC and FBA A is lost +Check +-fieldbus communication status (see fieldbus interface manuals) +-settings of param. groups 50-53 +-cable connections +-if communication master is able to communicate</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>FB2CommWrng</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FBA B communication</event_name> + <short_description>Fieldbus adapter module B communication warning</short_description> + <help_headers>Fieldbus adapter module B communication warning</help_headers> + <help_texts>Cyclical communication between drive and fieldbus adapter module B or between PLC and fieldbus adapter module B is lost. +-Check status of fieldbus communication. See user documentation of fieldbus interface. +-Check settings of parameter groups 50 Fieldbus adapter (FBA), 51 FBA A settings, 52 FBA A data In and 53 FBA A data out. +-Check cable connections. +-Check if communication master is able to communicate.</help_texts> + <user_manual_desc>Cyclical communication between drive and FBA B or between PLC and FBA B is lost +Check +-fieldbus communication status (see fieldbus interface manuals) +-settings of param. groups 50-53 +-cable connections +-if communication master is able to communicate</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_DDCS_conm_loss_warning</handle> + <module>DDCS</module> + <bit_handle/> + <event_type> + <warning> + <event_name>DDCS controller comm loss</event_name> + <short_description>DDCS communication between drive and external controller is lost.</short_description> + <help_headers>Master/follower communication loss</help_headers> + <help_texts>Check status of controller. See user documentation of controller. Check settings of parameter group 60 DDCS communication. Check cable connections. If necessary, replace cables.</help_texts> + <user_manual_desc/> + <rnd_desc>If Datasets are not updated in time specified by ddcs_adtimeout, fault or warning is thrown.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MF_DDCS_Com_loss_warning</handle> + <module>DDCS</module> + <bit_handle/> + <event_type> + <warning> + <event_name>M/F comm loss</event_name> + <short_description>DDCS communication between drives is lost. Data update took longer than timeout.</short_description> + <help_headers>Master/follower communication loss</help_headers> + <help_texts>Check optical fibres and FDCO adapters functionality. FDCO should have three lights on, green led and two red leds</help_texts> + <user_manual_desc/> + <rnd_desc>Master drive: Aux. code is node number of the lost follower. +Follower drive: Aux code is 0. +</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>EFBSerial1ErrWarning</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>EFB comm loss</event_name> + <short_description>The EFB has detected a comm loss. Check communications with system.</short_description> + <help_headers>EFB comm loss warning</help_headers> + <help_texts>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08 and 58.09 to adjust settings.</help_texts> + <user_manual_desc>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08, and 58.09 to adjust settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_Warnings</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO general warnings</event_name> + <short_description>FSO general warnings.</short_description> + <help_headers>FSO general warnings.</help_headers> + <help_texts>FSO general warnings. Mainly for some unrisky situations, like transition to comfiguration mode. See aux codes for details.</help_texts> + <user_manual_desc>FSO general warnings. Mainly for some unrisky situations, like transition to comfiguration mode. See aux for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_INT</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO internal fault</event_name> + <short_description>FSO internal fault.</short_description> + <help_headers>Boot the module once, see the Aux code for more details.</help_headers> + <help_texts>Internal fault in the FSO module. Boot the module once, if the problem is still there, replace the FSO module. Contact your local ABB representative. See the Aux code for more details.</help_texts> + <user_manual_desc>Internal fault in the FSO module. Boot the module once, if the problem is still there, replace the FSO module. Contact your local ABB representative. See the Aux code for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_IO</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO IO fault</event_name> + <short_description>FSO IO fault.</short_description> + <help_headers>Problems in the I/O cabling</help_headers> + <help_texts>FSO IO fault. Check the FSO I/O cabling. See the Aux code for more details.</help_texts> + <user_manual_desc>FSO IO fault. Check the FSO I/O cabling. See the Aux code for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_STO</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO STO fault</event_name> + <short_description>FSO STO fault. Problems in the STO cabling or inside the drive. Check the FSO STO cabling.</short_description> + <help_headers>Problems in the STO cabling or inside the drive.</help_headers> + <help_texts>FSO STO fault. Problems in the STO cabling or inside the drive. Check the FSO STO cabling.</help_texts> + <user_manual_desc>FSO STO fault.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_STOREQ</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO STO request</event_name> + <short_description>FSO STO request.</short_description> + <help_headers>External STO request.</help_headers> + <help_texts>FSO STO request. FSO module received an external STO request eitehr from IO or safebus.</help_texts> + <user_manual_desc>FSO STO request. FSO module received an external STO request eitehr from IO or safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_COMM</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO communication fault</event_name> + <short_description>FSO communication fault.</short_description> + <help_headers>Check the data cable.</help_headers> + <help_texts>FSO has detected a communication fault. All the communications goes through the data cable between FSO and Drive, check the connection.</help_texts> + <user_manual_desc>FSO has detected a communication fault. All the communications goes through the data cable between FSO and Drive, check the connection.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_SBUS</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safetybus fault</event_name> + <short_description>FSO safetybus fault.</short_description> + <help_headers>Something wrong with the safetybus.</help_headers> + <help_texts>FSO safetybus fault. Something wrong with the safetybus. See aux codes for more details.</help_texts> + <user_manual_desc>FSO safetybus fault. Something wrong with the safetybus. See aux codes for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_CONF</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO configuration fault</event_name> + <short_description>FSO configuration fault.</short_description> + <help_headers>Check the safety module parameter settings.</help_headers> + <help_texts>FSO configuration fault. Check the safety module parameter settings. Settings can be changed only with Composer pro tool.</help_texts> + <user_manual_desc>FSO configuration fault. Check the safety module parameter settings. Settings can be changed only with Composer pro tool.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_SafeEnc_Fault</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safety encoder fault</event_name> + <short_description>Safety encoder fault</short_description> + <help_headers>Safety encoder fault</help_headers> + <help_texts>Safety encoder fault, see aux codes for details</help_texts> + <user_manual_desc>Safety encoder fault, see aux codes for details</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_ENCLESS</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO encoderless fault</event_name> + <short_description>FSO encoderless speed estimation fault.</short_description> + <help_headers>Speed estimate is too high</help_headers> + <help_texts>FSO encoderless speed estimation fault. +• Check the behavior of the driven load compared with the drive control parameter settings. +• Check suitability of the drive train and the motor. +• Adapt control parameters if gear play or torsional rigidity causes problems.</help_texts> + <user_manual_desc>FSO encoderless speed estimation fault. +• Check the behavior of the driven load compared with the drive control parameter settings. +• Check suitability of the drive train and the motor. +• Adapt control parameters if gear play or torsional rigidity causes problems.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_TEMP</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO temperature fault</event_name> + <short_description>FSO over temperature</short_description> + <help_headers>FSO module temperature is excessive.</help_headers> + <help_texts>FSO over temperature. +• Check ambient conditions. Boot the FSO module (power switch off/on). +• Replace the FSO-11 module. Contact your local ABB representative.</help_texts> + <user_manual_desc>FSO over temperature. +• Check ambient conditions. Boot the FSO module (power switch off/on). +• Replace the FSO-11 module. Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_Undef</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO undefined warning</event_name> + <short_description>FSO undefined warning</short_description> + <help_headers>New FSO, undefined warning.</help_headers> + <help_texts>FSO new version, undefined warning in Drive event system.</help_texts> + <user_manual_desc>FSO new version, undefined warning in Drive event system.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSx_undefined_warning</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSx undefined warning</event_name> + <short_description>FSx undefined warning</short_description> + <help_headers>New FSx, undefined warning.</help_headers> + <help_texts>FSx new version, undefined warning in Drive event system.</help_texts> + <user_manual_desc>FSx undefined warning is not yet defined inside the drive. Gather the aux codes from this warning and contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSx_safety_bus_warning</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSx safety bus warning</event_name> + <short_description></short_description> + <help_headers></help_headers> + <help_texts></help_texts> + <user_manual_desc></user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_Encoder1Wrng</handle> + <module>EncoderConfig_ENC1</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Encoder</event_name> + <short_description>Problem with encoder</short_description> + <help_headers>Problem with encoder</help_headers> + <help_texts>Encoder problem. +- Check the settings in parameter group 92. After any changes, use parameter 91.10 to refresh the settings. +- Check the wiring and grounding of encoder. +- Check the event log for an auxiliary code. Contact your local ABB representative, quoting the code.</help_texts> + <user_manual_desc/> + <rnd_desc>Encoder faulted</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_PanelLossWrng</handle> + <module>PROFILE</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Control panel loss</event_name> + <short_description>Panel loss warning</short_description> + <help_headers>Panel loss warning</help_headers> + <help_texts>Control panel or PC tool selected as active control location for drive has ceased communicating. +-Check PC tool or control panel connection. +-Check control panel connector. +-Replace control panel in mounting platform.</help_texts> + <user_manual_desc>Control panel or PC tool selected as active control location for drive has ceased communicating. +-Check PC tool or control panel connection. +-Check control panel connector. +-Replace control panel in mounting platform.</user_manual_desc> + <rnd_desc>Connection to panel is lost. The drive is following last actual or failure reference according user selection by parameter 49.05 Comm loss action. </rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_MotorBearingWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor bearing</event_name> + <short_description>Maintenance timer/counter limit exceeded</short_description> + <help_headers>Maintenance timer/counter limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23 +4: parameter 33.53 +5: parameter 33.63</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23 +4: parameter 33.53 +5: parameter 33.63</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_OutputRelayWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Output relay</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_MotorStartsWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor starts</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_PowerUpsWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Power ups</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_MainContactorWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Main contactor</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_DCChargeWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>DC charge</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +2: parameter 33.33 +3: parameter 33.43</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_OnTime1Wrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>On-Time 1</event_name> + <short_description>Maintenance timer limit exceeded</short_description> + <help_headers>Maintenance timer limit exceeded</help_headers> + <help_texts>On-time timer 1 has exceeded limit. +- Check the source of the monitored signal (parameter 33.13) and limit (33.11). +- Check parameters 33.10 … 33.14.</help_texts> + <user_manual_desc>On-time timer 1 has exceeded limit. +- Check the source of the monitored signal (parameter 33.13) and limit (33.11). +- Check parameters 33.10 . 33.14.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_OnTime2Wrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>On-Time 2</event_name> + <short_description>Maintenance timer limit exceeded.</short_description> + <help_headers>Maintenance timer limit exceeded.</help_headers> + <help_texts>On-time timer 2 has exceeded limit. +- Check the source of the monitored signal (parameter 33.23) and limit (33.21). +- Check parameters 33.20 … 33.24.</help_texts> + <user_manual_desc>On-time timer 2 has exceeded limit. +- Check the source of the monitored signal (parameter 33.23) and limit (33.21). +- Check parameters 33.20 . 33.24.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_Edge1Wrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Edge counter 1</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Signal edge counter 1 has exceeded limit. +- Check the source of the monitored signal (parameter 33.33) and limit (33.31). +- Check parameters 33.30 … 33.35.</help_texts> + <user_manual_desc>Signal edge counter 1 has exceeded limit. +- Check the source of the monitored signal (parameter 33.33) and limit (33.31). +- Check parameters 33.30 . 33.35.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_Edge2Wrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Edge counter 2</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Signal edge counter 2 has exceeded limit. +- Check the source of the monitored signal (parameter 33.43) and limit (33.41). +- Check parameters 33.40 … 33.45.</help_texts> + <user_manual_desc>Signal edge counter 2 has exceeded limit. +- Check the source of the monitored signal (parameter 33.43) and limit (33.41). +- Check parameters 33.40 . 33.45.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_Value1Wrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Value counter 1</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Value counter 1 has exceeded limit. +- Check the source of the monitored signal (parameter 33.53) and limit (33.51). +- Check parameters 33.50 … 33.55.</help_texts> + <user_manual_desc>Value counter 1 has exceeded limit. +- Check the source of the monitored signal (parameter 33.53) and limit (33.51). +- Check parameters 33.50 . 33.55.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_Value2Wrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Value counter 2</event_name> + <short_description>Maintenance counter limit exceeded</short_description> + <help_headers>Maintenance counter limit exceeded</help_headers> + <help_texts>Value counter 2 has exceeded limit. +- Check the source of the monitored signal (parameter 33.63) and limit (33.61). +- Check parameters 33.60 … 33.65.</help_texts> + <user_manual_desc>Value counter 2 has exceeded limit. +- Check the source of the monitored signal (parameter 33.63) and limit (33.61). +- Check parameters 33.60 . 33.65.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_DeviceCleanWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Device clean</event_name> + <short_description>Maintenance timer limit exceeded</short_description> + <help_headers>Maintenance timer limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_DCCapacitorWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>DC capacitor</event_name> + <short_description>Maintenance timer limit exceeded</short_description> + <help_headers>Maintenance timer limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_CabinetFanWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Cabinet fan</event_name> + <short_description>Maintenance timer limit exceeded</short_description> + <help_headers>Maintenance timer limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_CoolingFanWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Cooling fan</event_name> + <short_description>Maintenance timer limit exceeded</short_description> + <help_headers>Maintenance timer limit exceeded</help_headers> + <help_texts>Consider replacing the drive cooling fan (see parameter 05.04).</help_texts> + <user_manual_desc>Consider replacing the drive cooling fan (see parameter 05.04).</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_MCOUNTER_AddCoolFanWrng</handle> + <module>MaintenanceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Additional cooling fan</event_name> + <short_description>Maintenance timer limit exceeded</short_description> + <help_headers>Maintenance timer limit exceeded</help_headers> + <help_texts>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</help_texts> + <user_manual_desc>Check the event log for an auxiliary code for this message. Check the source of the warning corresponding to the code: +0: parameter 33.13 +1: parameter 33.23</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>On-time 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>On-time 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Edge 1 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Edge 2 counter</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Value 1 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Value 2 integrator</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Fan on time counter</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>AI_Supervised_Warning</handle> + <module>FA_IO_AI</module> + <bit_handle/> + <event_type> + <warning> + <event_name>AI Supervised Warning</event_name> + <short_description>Analog In Supervision</short_description> + <help_headers>Check Analog Input Values</help_headers> + <help_texts>Analog Input Value has violated user set MIN or MAX.</help_texts> + <user_manual_desc>Analog In Supervision Warning</user_manual_desc> + <rnd_desc>AI Supervision Warning</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>AI1LessMIN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>AI1GreaterMAX</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>AI2LessMIN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>AI2GreaterMAX</names> + <user_manual_desc/> + </aux_code> + <aux_code code="101"> + <names>Extension 1 AI1 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="102"> + <names>Extension 1 AI1 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="103"> + <names>Extension 1 AI2 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="104"> + <names>Extension 1 AI2 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="201"> + <names>Extension 2 AI1 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="202"> + <names>Extension 2 AI1 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="203"> + <names>Extension 2 AI2 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="204"> + <names>Extension 2 AI2 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="301"> + <names>Extension 3 AI1 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="302"> + <names>Extension 3 AI1 greater than maximum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="303"> + <names>Extension 3 AI2 less than minimum</names> + <user_manual_desc/> + </aux_code> + <aux_code code="304"> + <names>Extension 3 AI2 greater than maximum</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_SupervWrng</handle> + <module>Supervision</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Signal supervision</event_name> + <short_description>Signal supervision 1</short_description> + <help_headers/> + <help_texts>Check the source of the warning.</help_texts> + <user_manual_desc>Warning generated by a signal supervision function. +Check the source of the warning (parameter 32.07).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_SupervWrng2</handle> + <module>Supervision</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Signal supervision 2</event_name> + <short_description>Signal supervision 2</short_description> + <help_headers/> + <help_texts>Check the source of the warning.</help_texts> + <user_manual_desc>Warning generated by a signal supervision function. +Check the source of the warning (parameter 32.17).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_SupervWrng3</handle> + <module>Supervision</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Signal supervision 3</event_name> + <short_description>Signal supervision 3</short_description> + <help_headers/> + <help_texts>Check the source of the warning</help_texts> + <user_manual_desc>Warning generated by a signal supervision function. +Check the source of the warning (parameter 32.27).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list> + <item> + <cause>Warning generated by a signal supervision function.</cause> + <what_to_do>Check the source of the warning (parameter 32.07).</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ULC_OLWarning</handle> + <module>User_Load_Curve</module> + <bit_handle/> + <event_type> + <warning> + <event_name>ULC overload</event_name> + <short_description>ULC -- an overload warning has occurred</short_description> + <help_headers>ULC -- Overload Warning</help_headers> + <help_texts>ULC -- an overload warning has occurred</help_texts> + <user_manual_desc>ULC -- an overload warning has occurred</user_manual_desc> + <rnd_desc>ULC -- an overload warning has occurred</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ULC_ULWarning</handle> + <module>User_Load_Curve</module> + <bit_handle/> + <event_type> + <warning> + <event_name>ULC underload</event_name> + <short_description>ULC -- an underload warning has occurred</short_description> + <help_headers>ULC -- Underload Warning</help_headers> + <help_texts>ULC -- an underload warning has occurred</help_texts> + <user_manual_desc>ULC -- an underload warning has occurred</user_manual_desc> + <rnd_desc>ULC -- an underload warning has occurred</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_SCOUNTER</handle> + <module>ServiceCounter</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Fan service counter</event_name> + <short_description>Maintenance recommended according to the service counter</short_description> + <help_headers>Fan service counter notification</help_headers> + <help_texts>Maintenance is recommended according to the fan counter. Check service counters in diagnostics group to identify parts needing maintenance. After replacement, reset the counter to a default value.</help_texts> + <user_manual_desc>Fan maintenance is recommended according to the in-built service counter. +Check fan counters in diagnostics group to identify parts needing maintenance. After replacement, reset the counter to a default value.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>Main fan</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>Auxiliary fan</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Auxiliary fan 2</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Cabinet fan</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>PCB space fan</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list> + <item> + <cause>Aux code defines which fan counter has generated the warning.</cause> + <what_to_do>0 - Main fan +1 - Auxiliary fan +2 - Auxiliary fan 2 +3 - Cabinet fan +4 - PCB space fan</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_External1Wrng</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <warning> + <event_name>External warning 1</event_name> + <short_description>External warning 1</short_description> + <help_headers>External warning 1</help_headers> + <help_texts>Warning generated by external device 1. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.01.</help_texts> + <user_manual_desc>Warning generated by external device 1. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.01.</user_manual_desc> + <rnd_desc>External warning 1</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_External2Wrng</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <warning> + <event_name>External warning 2</event_name> + <short_description>External warning 2</short_description> + <help_headers>External warning 2</help_headers> + <help_texts>Warning generated by external device 2. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.03.</help_texts> + <user_manual_desc>Warning generated by external device 2. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.03.</user_manual_desc> + <rnd_desc>External warning 2</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_External3Wrng</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <warning> + <event_name>External warning 3</event_name> + <short_description>External warning 3</short_description> + <help_headers>External warning 1</help_headers> + <help_texts>Warning generated by external device 3. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.05.</help_texts> + <user_manual_desc>Warning generated by external device 3. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.05.</user_manual_desc> + <rnd_desc>External warning 3</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_External4Wrng</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <warning> + <event_name>External warning 4</event_name> + <short_description>External warning 4</short_description> + <help_headers>External warning 4</help_headers> + <help_texts>Warning generated by external device 4. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.07.</help_texts> + <user_manual_desc>Warning generated by external device 4. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.07.</user_manual_desc> + <rnd_desc>External warning 4</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_External5Wrng</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <warning> + <event_name>External warning 5</event_name> + <short_description>External warning 5</short_description> + <help_headers>External warning 1</help_headers> + <help_texts>Warning generated by external device 5. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.09.</help_texts> + <user_manual_desc>Warning generated by external device 5. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.09.</user_manual_desc> + <rnd_desc>External warning 5</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_StopCompleted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO stop completed</event_name> + <short_description>FSO stop completed</short_description> + <help_headers>FSO stop completed.</help_headers> + <help_texts>FSO module has completed STO, SS1 or SSE function.</help_texts> + <user_manual_desc>FSO module has completed STO, SS1 or SSE function.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SafeSpeedLimit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safe speed limit</event_name> + <short_description>FSO safe speed limit</short_description> + <help_headers>FSO safe speed limit</help_headers> + <help_texts>Motor actual speed exceeded a safe speed limit of the FSO module.</help_texts> + <user_manual_desc>Motor actual speed exceeded a safe speed limit of the FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfEmeRamp</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO out of eme ramp</event_name> + <short_description>FSO out of eme ramp</short_description> + <help_headers>Motor speed was not inside the eme ramp.</help_headers> + <help_texts>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.103 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.103 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_RampCoasted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO ramp coasted</event_name> + <short_description>FSO ramp coasted</short_description> + <help_headers>Drive coasted instead of ramping.</help_headers> + <help_texts>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (200.163 Zero speed without encoder).</help_texts> + <user_manual_desc>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (200.163 Zero speed without encoder).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSafeRamp</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO out of safe ramp</event_name> + <short_description>FSO out of safe ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSDI</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO out of SDI</event_name> + <short_description>FSO out of SDI.</short_description> + <help_headers>FSO out of SDI.</help_headers> + <help_texts>Motor was not rotating to the allowed direction.</help_texts> + <user_manual_desc>Motor was not rotating to the allowed direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_POUS_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO POUS request</event_name> + <short_description>FSO POUS request</short_description> + <help_headers>FSO POUS request and activation.</help_headers> + <help_texts>Prevention Of Unexpected Startup was requested via inputs or safebus, and it was activated.</help_texts> + <user_manual_desc>Prevention Of Unexpected Startup was requested via inputs or safebus, and it was activated.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_passivated</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO passivated</event_name> + <short_description>FSO passivated</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO module is passivated due safetybus problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_STO_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO STO request</event_name> + <short_description>FSO STO request</short_description> + <help_headers>FSO STO external request</help_headers> + <help_texts>FSO module received an external STO request from the inputs or the safebus.</help_texts> + <user_manual_desc>FSO module received an external STO request from the inputs or the safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SSE_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SSE request</event_name> + <short_description>FSO SSE request</short_description> + <help_headers>FSO SSE external request</help_headers> + <help_texts>FSO module received an external SSE request from the inputs or the safebus.</help_texts> + <user_manual_desc>FSO module received an external SSE request from the inputs or the safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SS1_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SS1 request</event_name> + <short_description>FSO SS1 request</short_description> + <help_headers>FSO SS1 external request</help_headers> + <help_texts>FSO module received an external SS1 request from the inputs or the safebus.</help_texts> + <user_manual_desc>FSO module received an external SS1 request from the inputs or the safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS1hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS1 hit</event_name> + <short_description>FSO SLS1 hit</short_description> + <help_headers>FSO SLS1 limit hit</help_headers> + <help_texts>FSO module detected a SLS1 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS1 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS2hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS2 hit</event_name> + <short_description>FSO SLS2 hit</short_description> + <help_headers>FSO SLS2 limit hit</help_headers> + <help_texts>FSO module detected a SLS2 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS2 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS3hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS3 hit</event_name> + <short_description>FSO SLS3 hit</short_description> + <help_headers>FSO SLS3 limit hit</help_headers> + <help_texts>FSO module detected a SLS3 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS3 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS4hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS4 hit</event_name> + <short_description>FSO SLS4 hit</short_description> + <help_headers>FSO SLS4 limit hit</help_headers> + <help_texts>FSO module detected a SLS4 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS4 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SMShit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SMS hit</event_name> + <short_description>FSO SMS hit</short_description> + <help_headers>FSO SMS limit hit</help_headers> + <help_texts>FSO module detected a SMS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SMS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SAR0hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SAR0 hit</event_name> + <short_description>FSO SAR0 hit</short_description> + <help_headers>FSO SAR0 limit violation.</help_headers> + <help_texts>FSO module detected a SAR0 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.103 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR0 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.103 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SAR1hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SAR1 hit</event_name> + <short_description>FSO SAR1 hit</short_description> + <help_headers>FSO SAR1 limit violation.</help_headers> + <help_texts>FSO module detected a SAR1 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.106 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR1 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.106 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSDIp</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SDIp hit</event_name> + <short_description>FSO SDI-p hit</short_description> + <help_headers>FSO SDI-p hit</help_headers> + <help_texts>Motor was not rotating to the positive direction.</help_texts> + <user_manual_desc>Motor was not rotating to the positive direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSDIn</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SDIn hit</event_name> + <short_description>FSO SDI-n hit</short_description> + <help_headers>FSO SDI-n hit</help_headers> + <help_texts>Motor was not rotating to the negative direction.</help_texts> + <user_manual_desc>Motor was not rotating to the negative direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_RampTimeHit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO ramp time hit</event_name> + <short_description>FSO time monitored ramp hit</short_description> + <help_headers>FSO time monitored ramp hit</help_headers> + <help_texts>FSO module detected a violation of a time monitored ramp. +Make sure that the drive can decelerate the load within the time defined for ramp time monitoring.</help_texts> + <user_manual_desc>FSO module detected a violation of a time monitored ramp. +Make sure that the drive can decelerate the load within the time defined for ramp time monitoring. +• Check the drive ramp time settings. +• Check that the drive can in fact accomplish the deceleration along the ramp defined. +Make sure that the limit for ramp time monitoring of the FSO module exceeds the actual drive ramp time. The parameter vary depending on the safety function. For the SS1 function it is 200.38 SS1 delay for STO.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_ZeroSpdHit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO zero spd hit</event_name> + <short_description>FSO zero speed rush</short_description> + <help_headers>Drive speed rushed during zero speed delay.</help_headers> + <help_texts>Drive speed rushed during zero speed delay.</help_texts> + <user_manual_desc>Drive speed rushed during zero speed delay.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SpdSynFail</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO speed sync fail</event_name> + <short_description>FSO speed sync fail</short_description> + <help_headers>FSO detected a difference between the monitored motor speeds.</help_headers> + <help_texts>FSO module detected a difference between the two monitored motor speed values (200.239 FSO speed ch1 and 200.240 FSO speed ch2). +Restart the drive and FSO module.</help_texts> + <user_manual_desc>FSO module detected a difference between the two monitored motor speed values (200.239 FSO speed ch1 and 200.240 FSO speed ch2). +Restart the drive and FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_varSLShit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO varSLS hit</event_name> + <short_description>FSO variable SLS hit</short_description> + <help_headers>FSO variable SLS hit</help_headers> + <help_texts>FSO module detected a variable SLS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a variable SLS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_passivation</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safebus passivation</event_name> + <short_description>FSO passivation</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO safe bus passivation due communication problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FA2FA_DDCS_Com_loss_warning</handle> + <module>DDCS</module> + <bit_handle/> + <event_type> + <warning> + <event_name>INU-LSU comm loss</event_name> + <short_description>DDCS communication between drives is lost. Data update took longer than timeout.</short_description> + <help_headers>INU-LSU Com loss</help_headers> + <help_texts>Check optical fibres and FDCO adapters functionality. FDCO should have three lights on, green led and two red leds</help_texts> + <user_manual_desc/> + <rnd_desc>If Datasets are not updated in time specified by fa2fa_ddcs_com_loss_timeout, fault or warning is thrown.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_Line_side_unit_warning</handle> + <module>INU_LSUCtrl</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Line side unit warning</event_name> + <short_description>Line side unit warning</short_description> + <help_headers/> + <help_texts>Line side unit has an active warning. For more detailed information connect to LSU directly.</help_texts> + <user_manual_desc/> + <rnd_desc>Line side unit has an active warning. For more detailed information connect to LSU directly.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_pidsleep_wrng</handle> + <module>PID_Process_set1</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Process PID sleep mode</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>44940</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_Speed_controller_autotuning</handle> + <module>Speed_Controller_Autotune</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Speed controller autotuning</event_name> + <short_description>Speed controller autotuning</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>TC not ready</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>Speed step too small</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>No Acceleration or deceleration</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list> + <item> + <cause>Drive was not running before receiving autotuning command.</cause> + <what_to_do>Start the drive before giving autotune command.</what_to_do> + </item> + <item> + <cause>Motor did not accelerate to the maximum or minimum speed.</cause> + <what_to_do>Increase the autotune torque step size (par 25.38) or decrease the autotune speed step size (par 25.39)</what_to_do> + </item> + <item> + <cause>Torque reference was not risen to the correct value before the autotuning maximum speed was detected.</cause> + <what_to_do>Reduce the autotune torque step size (par 25.38) or increase the autotune speed step size (par 25.39)</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_autoreset_wrng</handle> + <module>EVENTS_Autoreset</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Autoreset</event_name> + <short_description>A fault is about to be autoreset</short_description> + <help_headers>A fault is about to be autoreset</help_headers> + <help_texts>Informative warning. +- See the settings in parameter group 31 Fault functions.</help_texts> + <user_manual_desc>A fault is about to be autoreset. Informative warning. +- See the settings in parameter group 31 Fault functions.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_EmOffWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Emergency stop (off2)</event_name> + <short_description>Emergency stop command (off2) received</short_description> + <help_headers>Emergency stop command (off2) received</help_headers> + <help_texts>Drive has received an emergency stop (mode selection off2) command. +- Check that it is safe to continue operation. +- Return emergency stop pushbutton to normal position. +- Restart drive.</help_texts> + <user_manual_desc>Drive has received an emergency stop (mode selection off2) command. +- Check that it is safe to continue operation. +- Return emergency stop pushbutton to normal position. +- Restart drive.</user_manual_desc> + <rnd_desc>Emergency off2 (coast)</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_EmStopWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Emergency stop (off1 or off3)</event_name> + <short_description>Emergency stop command (off1 or off3) received</short_description> + <help_headers>Emergency stop command (off1 or off3) received</help_headers> + <help_texts>Drive has received an emergency stop (mode selection off1 or off3) command. +- Check that it is safe to continue operation. +- Return emergency stop pushbutton to normal position. +- Restart drive.</help_texts> + <user_manual_desc>Drive has received an emergency stop (mode selection off1 or off3) command. +- Check that it is safe to continue operation. +- Return emergency stop pushbutton to normal position. +- Restart drive.</user_manual_desc> + <rnd_desc>Emergency stop off1 (normal ramp) or off3 (emergency stop ramp) activated.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_follower_wrn</handle> + <module>DDCS</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Follower</event_name> + <short_description>A fault active on follower drive.</short_description> + <help_headers>Follower drive has active warning or fault</help_headers> + <help_texts>A fault active on follower drive.</help_texts> + <user_manual_desc>Drive on the same M/F-link has an active warning/fault and thus causing warning also on the master drive. +Check the follower drive for further information.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="2"> + <names>Node 2</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Node 3</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Node 4</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_StartEnableWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Enable start signal missing</event_name> + <short_description>No enable start signal received</short_description> + <help_headers>No enable start signal received</help_headers> + <help_texts>No enable start signal received. +- Check the setting of (and source selected by) parameter 20.19.</help_texts> + <user_manual_desc>No enable start signal received. +- Check the setting of (and source selected by) parameter 20.19.</user_manual_desc> + <rnd_desc>Enable start signal missing</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_RunEnableWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Run enable missing</event_name> + <short_description>No run enable signal received</short_description> + <help_headers>No run enable signal received</help_headers> + <help_texts>No run enable signal received. +- Check the setting of (and source selected by) parameter 20.12. +- Switch run enable signal on (eg. in the fieldbus control word).</help_texts> + <user_manual_desc>No run enable signal received. +- Check the setting of (and source selected by) parameter 20.12. +- Switch run enable signal on (eg. in the fieldbus control word).</user_manual_desc> + <rnd_desc>Run enable missing</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_ExtPowWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>External power signal missing</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc>External power feedback signal missing. +The feedback is different than the parameter setting.</user_manual_desc> + <rnd_desc>External power feedback signal missing. +The feedback is different than the parameter setting.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_IDrunWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Identification run selected</event_name> + <short_description>Motor identification run about to be performed</short_description> + <help_headers>Motor identification run about to be performed</help_headers> + <help_texts>Motor identification run will be performed at next start.</help_texts> + <user_manual_desc>Motor identification run will be performed at next start.</user_manual_desc> + <rnd_desc>ID run active</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_AutoPhasingWrng</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Autophasing</event_name> + <short_description>Autophasing about to be performed</short_description> + <help_headers>Autophasing about to be performed</help_headers> + <help_texts>Autophasing routine will be performed at next start to determine the angular position of the magnetic flux (with a permanent magnet synchronous motor) or the magnetic axis (with a synchronous reluctance motor).</help_texts> + <user_manual_desc>Autophasing routine will be performed at next start to determine the angular position of the magnetic flux (with a permanent magnet synchronous motor) or the magnetic axis (with a synchronous reluctance motor).</user_manual_desc> + <rnd_desc>Autophasing active</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>STOPureEvent</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>STO event</event_name> + <short_description>Safe torque off function is active.</short_description> + <help_headers>Safe torque off function is active</help_headers> + <help_texts>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections. For more information, see appropriate drive +hardware manual.</help_texts> + <user_manual_desc>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>PowerUp</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>Power up</event_name> + <short_description>Diagnostic information about the last boot cycle</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>The drive has been powered up.</rnd_desc> + <aux_codes> + <aux_code code="0x0000000"> + <names>Boot Type: Undefined</names> + <user_manual_desc>No information about boot type available</user_manual_desc> + </aux_code> + <aux_code code="0x00000001"> + <names>Boot Type: Cold boot</names> + <user_manual_desc>Drive was powered-on</user_manual_desc> + </aux_code> + <aux_code code="0x00000002"> + <names>Boot Type: Warm boot - OK</names> + <user_manual_desc>Drive was restarted expectedly</user_manual_desc> + </aux_code> + <aux_code code="0x00000003"> + <names>Boot Type: Warm boot - ERR</names> + <user_manual_desc>Drive had critical error and restart was needed. Information should be saved in SSW internal diagnostics</user_manual_desc> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>IDRunDone</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>ID run done</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc>ID run has been performed successfully</user_manual_desc> + <rnd_desc>ID run has been performed successfully + +</rnd_desc> + <aux_codes> + <aux_code code="0"> + <names>None</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>Normal</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Reduced</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Standstill</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Autophasing</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Current measurement calibration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="6"> + <names>Advanced</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7"> + <names>Advanced standstill</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_SSW_InternalDiagnostics</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>SW internal diagnostics</event_name> + <short_description>SW internal diagnostics</short_description> + <help_headers>SW internal diagnostics</help_headers> + <help_texts>Event gives additional information about the situation in case if CPU has been booted due to internal SW malfunction.</help_texts> + <user_manual_desc>System SW diagnostics has recorded an exceptional event during normal execution of the system SW. +The aux code of the event contains more information for ABB Drives.</user_manual_desc> + <rnd_desc>System SW has noticed an exception in execution of the software. The aux code of the event contains more information.</rnd_desc> + <aux_codes> + <aux_code code="0x10000000"> + <names>Program counter value</names> + <user_manual_desc>Sub event nr 1. Report to ABB Drives. Value of the program counter. + Aux. code: 0x1xxxxxxx + xxxxxxx = value of the program counter</user_manual_desc> + </aux_code> + <aux_code code="0x20000000"> + <names>Stack pointer value</names> + <user_manual_desc>Sub event nr 2. Report to ABB Drives. Value of the stack pointer. + Aux. code: 0x2xxxxxxx + xxxxxxx = value of the stack pointer</user_manual_desc> + </aux_code> + <aux_code code="0x30000000"> + <names>Packed crash data</names> + <user_manual_desc>Sub event nr 3. Report to ABB Drives. Crash details: + Aux. code: 0x3000xyzz + x - interrupt nesting level + y - crash count + zz - exception number.</user_manual_desc> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_Checksum_mismatch_pe</handle> + <module>Checksum</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>Checksum mismatch</event_name> + <short_description/> + <help_headers/> + <help_texts>Parameter 96.53 "Actual checksum" does not match any of the active approved checksums (parameters 96.56-59). Check the parameter configuration and approve the actual checksum if needed using parameter 96.54 "Checksum control word".</help_texts> + <user_manual_desc>The actual checksum does not match any of the active approved checksums.</user_manual_desc> + <rnd_desc>The actual checksum does not match any of the active approved checksums.</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSO_Events</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO general event</event_name> + <short_description>FSO general event</short_description> + <help_headers>FSO general event</help_headers> + <help_texts>FSO general event, see aux codes for details.</help_texts> + <user_manual_desc>FSO general event, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSO_DIAGS</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO diagnostics</event_name> + <short_description>FSO boottime diags.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>FSO boottime diags. Only for manufacturing tests, TUCSO (FSO subsystem) will forget these.</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_Undef</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO undefined event</event_name> + <short_description>FSO undefined event</short_description> + <help_headers>FSO undefined event.</help_headers> + <help_texts>FSO new version, undefined event in Drive event system.</help_texts> + <user_manual_desc>FSO new version, undefined event in Drive event system.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_FSECh1Diag</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSE-31 ch1 diagnostics</event_name> + <short_description>FSE-31 ch1 diag</short_description> + <help_headers>FSE-31 ch1 diag</help_headers> + <help_texts>FSE-31 channel 1 diagnostics data, see aux codes for details.</help_texts> + <user_manual_desc>FSE-31 channel 1 diagnostics data, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_FSECh2Diag</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSE-31 ch2 diagnostics</event_name> + <short_description>FSE-31 ch2 diag</short_description> + <help_headers>FSE-31 ch2 diag</help_headers> + <help_texts>FSE-31 channel 2 diagnostics data, see aux codes for details.</help_texts> + <user_manual_desc>FSE-31 channel 2 diagnostics data, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_External1PureEvent</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>External pure event 1</event_name> + <short_description>External pure event 1</short_description> + <help_headers>External pure event 1</help_headers> + <help_texts>Pure event generated by external device 1. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.01.</help_texts> + <user_manual_desc>Pure event generated by external device 1. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.01.</user_manual_desc> + <rnd_desc>External pure event 1</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_External2PureEvent</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>External pure event 2</event_name> + <short_description>External pure event 2</short_description> + <help_headers>External pure event 2</help_headers> + <help_texts>Pure event generated by external device 2. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.03.</help_texts> + <user_manual_desc>Pure event generated by external device 2. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.03.</user_manual_desc> + <rnd_desc>External pure event 2</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_External3PureEvent</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>External pure event 3</event_name> + <short_description>External pure event 3</short_description> + <help_headers>External pure event 3</help_headers> + <help_texts>Pure event generated by external device 3. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.05.</help_texts> + <user_manual_desc>Pure event generated by external device 3. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.05.</user_manual_desc> + <rnd_desc>External pure event 3</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_External4PureEvent</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>External pure event 4</event_name> + <short_description>External pure event 4</short_description> + <help_headers>External pure event 4</help_headers> + <help_texts>Pure event generated by external device 4. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.07.</help_texts> + <user_manual_desc>Pure event generated by external device 4. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.07.</user_manual_desc> + <rnd_desc>External pure event 4</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_External5PureEvent</handle> + <module>EVENTS_External</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>External pure event 5</event_name> + <short_description>External pure event 5</short_description> + <help_headers>External pure event 5</help_headers> + <help_texts>Pure event generated by external device 4. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.09.</help_texts> + <user_manual_desc>Pure event generated by external device 5. (This information is configured through one of programmable digital inputs.) +- Check external devices. +- Check setting of parameter 31.09.</user_manual_desc> + <rnd_desc>External pure event 5</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_StopCompleted</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO stop completed</event_name> + <short_description>FSO stop completed</short_description> + <help_headers>FSO stop completed</help_headers> + <help_texts>FSO module has completed STO, SS1 or SSE function.</help_texts> + <user_manual_desc>FSO module has completed STO, SS1 or SSE function.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SafeSpeedLimit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO safe speed limit</event_name> + <short_description>FSO safe speed limit</short_description> + <help_headers>FSO safe speed limit</help_headers> + <help_texts>Motor actual speed exceeded a safe speed limit of the FSO module.</help_texts> + <user_manual_desc>FSO safe speed limit. Motor actual speed exceeded a safe speed limit of the FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfEmeRamp</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO out of eme ramp</event_name> + <short_description>FSO out of eme ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window during the SSE function. Make sure that the drive can decelerate the load using the ramp times.</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window during the SSE function. Make sure that the drive can decelerate the load using the ramp times.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_RampCoasted</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO ramp coasted</event_name> + <short_description>FSO ramp coasted</short_description> + <help_headers>Drive coasted the motor to stop during the ramp.</help_headers> + <help_texts>Drive coasted the motor to stop instead of using the ramp. Check that the FSO module zero speed limit for the deceleration ramp is not excessive</help_texts> + <user_manual_desc>Drive coasted the motor to stop instead of using the ramp. Check that the FSO module zero speed limit for the deceleration ramp is not excessive</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSafeRamp</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO out of safe ramp</event_name> + <short_description>FSO out of safe ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSDI</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO out of SDI</event_name> + <short_description>FSO out of SDI.</short_description> + <help_headers>FSO out of SDI.</help_headers> + <help_texts>Motor was not rotating to the allowed direction.</help_texts> + <user_manual_desc>Motor was not rotating to the allowed direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_passivated</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO passivated</event_name> + <short_description>FSO passivated</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO module is passivated due safetybus problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_STO_request</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO STO request</event_name> + <short_description>FSO STO request</short_description> + <help_headers>External STO request.</help_headers> + <help_texts>FSO module received an external STO request.</help_texts> + <user_manual_desc>FSO module received an external STO request.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SSE_Request</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SSE request</event_name> + <short_description>FSO SSE request</short_description> + <help_headers>External SSE request</help_headers> + <help_texts>FSO module received an external SSE request.</help_texts> + <user_manual_desc>FSO module received an external SSE request.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SS1_Request</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SS1 request</event_name> + <short_description>FSO SS1 request</short_description> + <help_headers>External SS1 request.</help_headers> + <help_texts>FSO module received an external SS1 request.</help_texts> + <user_manual_desc>FSO module received an external SS1 request.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS1hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS1 hit</event_name> + <short_description>FSO SLS1 hit</short_description> + <help_headers>FSO SLS1 hit</help_headers> + <help_texts>FSO module detected a SLS1 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS1 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS2hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS2 hit</event_name> + <short_description>FSO SLS2 hit</short_description> + <help_headers>FSO SLS2 hit</help_headers> + <help_texts>FSO module detected a SLS2 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS2 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS3hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS3 hit</event_name> + <short_description>FSO SLS3 hit</short_description> + <help_headers>FSO SLS3 hit</help_headers> + <help_texts>FSO module detected a SLS3 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS3 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS4hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS4 hit</event_name> + <short_description>FSO SLS4 hit</short_description> + <help_headers>FSO SLS4 hit</help_headers> + <help_texts>FSO module detected a SLS4 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS4 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SMShit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SMS hit</event_name> + <short_description>FSO SMS hit</short_description> + <help_headers>FSO SMS hit</help_headers> + <help_texts>FSO module detected a SMS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SMS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SAR0hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SAR0 hit</event_name> + <short_description>FSO SAR0 hit</short_description> + <help_headers>FSO SAR0 limit violation.</help_headers> + <help_texts>FSO module detected a SAR0 limit violation.Make sure that the drive can +decelerate the load using the ramp time (103 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR0 limit violation.Make sure that the drive can +decelerate the load using the ramp time (103 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SAR1hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SAR1 hit</event_name> + <short_description>FSO SAR1 hit</short_description> + <help_headers>FSO SAR1 limit violation.</help_headers> + <help_texts>FSO module detected a SAR1 limit violation. Make sure that the drive can +decelerate the load using the ramp time (106 SAR1 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR1 limit violation. Make sure that the drive can +decelerate the load using the ramp time (106 SAR1 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSDIp</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SDIp hit</event_name> + <short_description>FSO SDI-p hit</short_description> + <help_headers>FSO SDI-p hit</help_headers> + <help_texts>Motor was not rotating to the positive direction.</help_texts> + <user_manual_desc>Motor was not rotating to the positive direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSDIn</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SDIn hit</event_name> + <short_description>FSO SDI-n hit</short_description> + <help_headers>FSO SDI-n hit</help_headers> + <help_texts>Motor was not rotating to the negative direction.</help_texts> + <user_manual_desc>Motor was not rotating to the negative direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_RampTimeHit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO ramp time hit</event_name> + <short_description>FSO time monitored ramp hit</short_description> + <help_headers>FSO time monitored ramp hit</help_headers> + <help_texts>FSO module detected a violation of a time monitored ramp. Make sure that the drive can decelerate the load within the time defined for ramp time monitoring.</help_texts> + <user_manual_desc>FSO module detected a violation of a time monitored ramp. Make sure that the drive can decelerate the load within the time defined for ramp time monitoring. +• Check the drive ramp time settings. +• Check that the drive can in fact accomplish the deceleration along the ramp defined. +Make sure that the limit for ramp time monitoring of the FSO module exceeds the actual drive ramp time. The parameter vary depending on the safety function. For the SS1 function it is 38 SS1 delay for STO.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_ZeroSpdHit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO zero spd hit</event_name> + <short_description>FSO zero speed rush.</short_description> + <help_headers>FSO zero speed rush.</help_headers> + <help_texts>Drive speed was rushing during zero speed delay.</help_texts> + <user_manual_desc>Drive speed was rushing during zero speed delay.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SpdSynFail</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO speed sync fail</event_name> + <short_description>FSO speed sync fail</short_description> + <help_headers>Difference between the two monitored motor speeds.</help_headers> + <help_texts>FSO module detected a difference between the two monitored motor speed values (200.239 FSO speed ch1 and 200.240 FSO speed ch2). Restart the drive and FSO module.</help_texts> + <user_manual_desc>FSO module detected a difference between the two monitored motor speed values (200.239 FSO speed ch1 and 200.240 FSO speed ch2). Restart the drive and FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_varSLShit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO varSLS hit</event_name> + <short_description>FSO variable SLS hit</short_description> + <help_headers>FSO variable SLS hit</help_headers> + <help_texts>FSO module detected a variable SLS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a variable SLS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_passivation</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO safebus passivation</event_name> + <short_description>FSO passivation</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO safe bus passivation due communication problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>LanguageFB1Notice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>LanguageFB2Notice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>LanguageToolNotice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>ResetDefaultFB1Ntc</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc> + <text language_id="en"/> + </rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ResetDefaultFB2Ntc</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc> + <text language_id="en"/> + </rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_CommunicationBreak15s</handle> + <module>SSW</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Used to indicate that heartbeat will be lost for maximum time of 15 seconds and that tool/panel should not disconnect drive completely during that time.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ParsChangedToolNotice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Notice for the tool channels that the parameter system has changed.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_AccessLevelNotice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Given when any access level is selected and new menu visibilities are created.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_IDRunDone</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>ID run completed</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>FB1RefLimitsChangedNtc</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>FB2RefLimitsChangedNtc</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>FB1ActiveWarningChangedNtc</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>FB2ActiveWarningChangedNtc</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>FB1FDSSParsRefreshNtc</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>FB2FDSSParsRefreshNtc</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>FB1CtrlModeChangedNtc</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>FB2CtrlModeChangedNtc</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_STO1LostFlt</handle> + <module>STO</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Safe torque off 1 loss</event_name> + <short_description>Safe torque off 1 fault</short_description> + <help_headers>Safe torque off 1 fault</help_headers> + <help_texts>Safe Torque Off function is active, i.e. STO circuit 1 is broken. +-Check safety circuit connections. For more information, see appropriate drive hardware manual, description of parameter 31.22 and Application guide - Safe torque off function for ACSM1, ACS850 and ACQ810 drives (3AFE68929814 [English]).</help_texts> + <user_manual_desc>Safe Torque Off function is active, i.e. STO circuit 1 is broken. +-Check safety circuit connections. See drive hardware manual, description of par. 31.22 and ACSM1, ACS850 and ACQ810 STO Application guide (3AFE68929814 [English]).</user_manual_desc> + <rnd_desc>Safe torque off 1 circuit open</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_STO2LostFlt</handle> + <module>STO</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Safe torque off 2 loss</event_name> + <short_description>Safe torque off 2 fault</short_description> + <help_headers>Safe torque off 2 fault</help_headers> + <help_texts>Safe Torque Off function is active, i.e. STO circuit 2 is broken. +-Check safety circuit connections. For more information, see appropriate drive hardware manual, description of parameter 31.22 (page 119), and Application guide - Safe torque off function for ACSM1, ACS850 and ACQ810 drives (3AFE68929814 [English]).</help_texts> + <user_manual_desc>Safe Torque Off function is active, i.e. STO circuit 2 is broken. +-Check safety circuit connections. See drive hardware manual, description of par. 31.22 and ACSM1, ACS850 and ACQ810 STO Application guide (3AFE68929814 [English]).</user_manual_desc> + <rnd_desc>Safe torque off 2 circuit open</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Memory_unit_missing</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Memory unit missing</event_name> + <short_description>Drive bootloader does not detect memory unit.</short_description> + <help_headers/> + <help_texts>Memory unit is missing. Insert the memory unit properly.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Memory_unit_incompatible</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Memory unit incompatible</event_name> + <short_description>Memory unit is inserted, but it is incompatible.</short_description> + <help_headers/> + <help_texts>Memory unit is not compatible to this product. Insert the compatible memory unit.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Memory_unit_FW_incompatible</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Memory unit FW incompatible</event_name> + <short_description>Memory unit is inserted, but the firmware is not compatible to this drive type.</short_description> + <help_headers/> + <help_texts>Memory unit has incompatible firmware to this product type. Insert the compatible memory unit properly.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Memory_unit_FW_load_failed</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Memory unit FW load failed</event_name> + <short_description>Memory unit is inserted and compatible, but FW can't be loaded from memory unit.</short_description> + <help_headers/> + <help_texts>Ensure that memory unit is installed correctly. If problem persists replace the memory unit.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IDRunFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>ID run</event_name> + <short_description>Motor ID run failed.</short_description> + <help_headers>Motor ID run failed</help_headers> + <help_texts>Motor ID run was not completed successfully. +- Check the event log for an auxiliary code. See appropriate actions for each aux. code below. +Aux code = 1: Current limit is too low. +Aux code = 2: Maximum speed and/or field weakening point is too low. +Aux code = 3: Maximum torque is too low. +Aux code = 4: Current measurement calibration error. +Aux code = 5…8: Inductance estimation error. +Aux code = 9: Asynchronous motor acceleration error. +Aux code = 10: Asynchronous motor deceleration error. +Aux code = 11: Asynchronous motors speed dropped to zero. +Aux code = 12: PM motor acceleration error 1. +Aux code = 13: PM motor acceleration error 2. +Aux code = 14…16: PM motor speed dropped to zero. +Aux code = 17: SynRM pulse test error +Aux code = 18: Too big motor for advanced standstill ID run +Aux code = 19: Asynchronous motor data error</help_texts> + <user_manual_desc>Motor ID run was not completed successfully. +- Check the event log for an auxiliary code. See appropriate actions for each aux code in the manual.</user_manual_desc> + <rnd_desc>ID run failure.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>DiagnosticsFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Diagnostics</event_name> + <short_description>Diagnostics failed.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>INU or motor diagnostics failure.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_follower_flt</handle> + <module>DDCS</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Follower</event_name> + <short_description>A fault active on follower drive.</short_description> + <help_headers>Follower drive has faulted.</help_headers> + <help_texts>A fault active on follower drive.</help_texts> + <user_manual_desc>Drive on the same M/F-link has faulted and caused the master drive to fault. +Check the follower drive for further information</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="2"> + <names>Node 2</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Node 3</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Node 4</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB1ForceTripFault</handle> + <module>TUCFI_FB0_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FB A force trip</event_name> + <short_description>Fieldbus adapter A force trip fault</short_description> + <help_headers>Fieldbus adapter A force trip fault</help_headers> + <help_texts>A fault trip command has been received through fieldbus adapter A. +-Check the fault information provided by the PLC.</help_texts> + <user_manual_desc>A fault trip command has been received through fieldbus adapter A. +-Check the fault information provided by the PLC.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FB2ForceTripFault</handle> + <module>TUCFI_FB1_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FB B force trip</event_name> + <short_description>Fieldbus adapter B force trip fault</short_description> + <help_headers>Fieldbus adapter B force trip fault</help_headers> + <help_texts>A fault trip command has been received through fieldbus adapter B. +-Check the fault information provided by the PLC.</help_texts> + <user_manual_desc>A fault trip command has been received through fieldbus adapter B. +-Check the fault information provided by the PLC.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBForceTripFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB force trip</event_name> + <short_description>This fault is not currently used at this time.</short_description> + <help_headers>EFB force trip</help_headers> + <help_texts>This fault is not currently used at this time.</help_texts> + <user_manual_desc>This fault is not currently used at this time.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_undefined_event</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSx undefined event</event_name> + <short_description></short_description> + <help_headers>FSx undefined event.</help_headers> + <help_texts>FSx new version, undefined event in Drive event system.</help_texts> + <user_manual_desc>FSx new version, undefined event in Drive event system.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSx_diagnostics</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSx diagnostics</event_name> + <short_description>FSx diag</short_description> + <help_headers>FSx diag</help_headers> + <help_texts>FSx diagnostics data, see aux codes for details.</help_texts> + <user_manual_desc>FSx diagnostics data, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + </events> +</module> @@ -0,0 +1,22 @@ +<handle>CalibrationFault</handle> + +<module>TUCTC_Events</module> + +<bit_handle /> + +<event_type> + <fault fast_presampling="false" permanent="false"> + <event_name>Calibration</event_name> + <short_description>Current measurement calibration fault</short_description> + <help_headers>Current measurement calibration fault</help_headers> + <help_texts>Measured offset of output phase current measurement or difference between output phase U2 and W2 current measurement is too great (the values are updated during current calibration). +- Try performing the current calibration again (select Current measurement +calibration at parameter 99.13). If the fault persists, contact your local ABB representative.</help_texts> + <user_manual_desc>Measured offset of output phase current measurement or difference between output phase current measurement is too great. +- Try performing the current calibration again. If the fault persists, contact your local ABB representative.</user_manual_desc> + <rnd_desc>Current measurement offset or gain error is too big.</rnd_desc> + <aux_codes /> + <cause_list /> + </fault> + </event_type> + diff --git a/theirs.xml b/theirs.xml new file mode 100644 index 0000000..a68434e --- /dev/null +++ b/theirs.xml @@ -0,0 +1,6215 @@ +<?xml version='1.0' encoding='UTF-8'?> +<module leipuri_version="2.0"> + <events> + <event> + <handle>OverCurrentPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Overcurrent</event_name> + <short_description>Output current has exceeded internal fault limit.</short_description> + <help_headers>Output current has exceeded internal fault limit</help_headers> + <help_texts>Output current has exceeded internal fault limit. +- Check motor load. +- Check acceleration times in parameter group 23 Speed reference ramp. +- Check motor and motor cable (including phasing and delta/star connection). +- Check that the start-up data in parameter group 99 corresponds to the motor rating plate. +- Check that there are no power factor correction capacitors or surge absorbers +in motor cable. +- Check encoder cable (including phasing).</help_texts> + <user_manual_desc>Output current has exceeded internal fault limit. Check: +- motor load +- acceleration times +- motor and motor cable +- start-up data (group 99) +- there are no power factor correction capacitors in motor cable +- encoder cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OvervoltagePSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DC link overvoltage</event_name> + <short_description>DC link overvoltage fault</short_description> + <help_headers>DC link overvoltage fault</help_headers> + <help_texts>Excessive intermediate circuit DC voltage. +-Check that overvoltage control is on (parameter 30.30 Overvoltage control). +-Check that the supply voltage matches the nominal input voltage of the drive. +-Check the supply line for static or transient overvoltage. +-Check brake chopper and resistor (if present). +-Check deceleration time. +-Use coast-to-stop function (if applicable). +-Retrofit drive with brake chopper and brake resistor.</help_texts> + <user_manual_desc>DC link overvoltage +Check +-30.30 Overvoltage control +-supply voltage matches drive nominal input voltage +-supply line for static or transient overvoltage +-chopper/resistor +-decel. time +Coast-to-stop. +Retrofit drive with chopper and resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ShortCircuitPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Short circuit</event_name> + <short_description>Short-circuit in motor cable(s) or motor.</short_description> + <help_headers>Short-circuit in motor cable(s) or motor</help_headers> + <help_texts>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable.</help_texts> + <user_manual_desc>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UndervoltagePSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DC link undervoltage</event_name> + <short_description>DC link undervoltage fault</short_description> + <help_headers>DC link undervoltage fault</help_headers> + <help_texts>Intermediate circuit DC voltage is not sufficient because of a missing supply phase, blown fuse or fault in the rectifier bridge. +-Check supply cabling, fuses and switchgear.</help_texts> + <user_manual_desc>Intermediate circuit DC voltage is not sufficient because of a missing supply phase, blown fuse or fault in the rectifier bridge. +-Check supply cabling, fuses and switchgear.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EarthPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Earth leakage</event_name> + <short_description>Earth leakage fault</short_description> + <help_headers>Earth leakage fault</help_headers> + <help_texts>Load unbalance in eg, motor or motor cable +Check +-no power factor correction capacitors or surge absorbers in cable +-no earth fault in motor or cables: measure insulation resistances +If no earth fault detected, contact ABB.</help_texts> + <user_manual_desc>Load unbalance in eg, motor or motor cable +Check +-no power factor correction capacitors or surge absorbers in cable +-no earth fault in motor or cables: measure insulation resistances +If no earth fault detected, contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>RedundantMeasurementPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Redundant measurement</event_name> + <short_description>Redundant measurement</short_description> + <help_headers>Redundant measurement</help_headers> + <help_texts>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. (Solar applications)</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IGBT_Overtemp_Fault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>IGBT overtemperature</event_name> + <short_description>Estimated drive IGBT temperature is excessive.</short_description> + <help_headers>Estimated drive IGBT temperature is excessive</help_headers> + <help_texts>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Too much current in off-line thermal model while thermal current limitation passivated.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BcErPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Brake resistor wiring</event_name> + <short_description>Brake chopper wiring fault</short_description> + <help_headers>Brake chopper wiring fault</help_headers> + <help_texts>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged.</help_texts> + <user_manual_desc>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BcScPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>BC short circuit</event_name> + <short_description>Brake chopper short circuit</short_description> + <help_headers>Brake chopper short circuit</help_headers> + <help_texts>Short circuit in brake chopper IGBT. +- Ensure brake resistor is connected and not damaged. +- Check the electrical specifications of the brake resistor against the Hardware +manual. +-Replace brake chopper (if replaceable).</help_texts> + <user_manual_desc>Short circuit in brake chopper IGBT. +- Ensure brake resistor is connected and not damaged. +- Check the electrical specifications of the brake resistor against the Hardware +manual. +-Replace brake chopper (if replaceable).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BcIgbtOvertempFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BC IGBT excess temperature</event_name> + <short_description>Excessive brake chopper IGBT temperature</short_description> + <help_headers>Excessive brake chopper IGBT temperature</help_headers> + <help_texts>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check for excessive ambient temperature. +- Check for cooling fan failure. +- Check for obstructions in the air flow. +- Check the dimensioning and cooling of the cabinet. +- Check resistor overload protection function settings (parameter group 43 +Brake chopper). +- Check that braking cycle meets allowed limits. +- Check that drive supply AC voltage is not excessive.</help_texts> + <user_manual_desc>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check: for excessive ambient temperature, cooling fan, resistor overload protection function settings, braking duty cycle, drive supply AC voltage.</user_manual_desc> + <rnd_desc>BC IGBT thermal mode fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BrOvertempFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BR excess temperature</event_name> + <short_description>Excessive brake resistor temperature</short_description> + <help_headers>Excessive brake resistor temperature</help_headers> + <help_texts>Brake resistor temperature has exceeded fault limit defined by parameter 43.11 Brake resistor fault limit. +- Stop drive. Let resistor cool down. +- Check resistor overload protection function settings (parameter group 43 Brake chopper). +- Check fault limit setting, parameter 43.11 Brake resistor fault limit. +- Check that braking cycle meets allowed limits.</help_texts> + <user_manual_desc>Brake resistor temperature has exceeded fault limit defined by parameter 43.11 Brake resistor fault limit. +- Stop drive. Let resistor cool down. +- Check parameter group 43 Brake chopper. +- Check that braking cycle meets allowed limits.</user_manual_desc> + <rnd_desc>Braking resistor thermal model fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TempSensorFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Measurement circuit temperature</event_name> + <short_description>Problem with internal temperature measurement of the drive. +If the device has only one IGBT temperature measurement in one phase, the fault is generated, otherwise warning.</short_description> + <help_headers>Problem with internal temperature measurement of the drive</help_headers> + <help_texts>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>CrossConFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Wiring or earth fault</event_name> + <short_description>Incorrect input power and motor cable connection</short_description> + <help_headers>Incorrect input power and motor cable connection</help_headers> + <help_texts>Incorrect input power and motor cable connection (i.e. input power cable is connected to drive motor connection). +- Check input power connections.</help_texts> + <user_manual_desc>Incorrect input power and motor cable connection (i.e. input power cable is connected to drive motor connection). +- Check input power connections.</user_manual_desc> + <rnd_desc>AC supply connected to outputs.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>InputPhaseLossFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Input phase loss</event_name> + <short_description>Intermediate circuit DC voltage is oscillating.</short_description> + <help_headers>Intermediate circuit DC voltage is oscillating</help_headers> + <help_texts>Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse. +- Check input power line fuses. +- Check for input power supply imbalance.</help_texts> + <user_manual_desc>Intermediate circuit DC voltage is oscillating due to missing input power line phase or blown fuse. +- Check input power line fuses. +- Check for input power supply imbalance.</user_manual_desc> + <rnd_desc>Too much ripple in th Udc due to missing supply phase.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OutputPhaseLossFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Output phase loss</event_name> + <short_description>Missing motor connection</short_description> + <help_headers>Missing motor connection</help_headers> + <help_texts>Motor circuit fault due to missing motor connection (all three phases are not +connected). +- Connect motor cable.</help_texts> + <user_manual_desc>Motor circuit fault due to missing motor connection (all three phases are not +connected). +- Connect motor cable.</user_manual_desc> + <rnd_desc>Output phase loss detected.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IDRunFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>ID run</event_name> + <short_description>Motor ID run failed.</short_description> + <help_headers>Motor ID run failed</help_headers> + <help_texts>Motor ID run was not completed successfully. +- Check the event log for an auxiliary code. See appropriate actions for each aux. code below. +Aux code = 1: Current limit is too low. +Aux code = 2: Maximum speed and/or field weakening point is too low. +Aux code = 3: Maximum torque is too low. +Aux code = 4: Current measurement calibration error. +Aux code = 5…8: Inductance estimation error. +Aux code = 9: Asynchronous motor acceleration error. +Aux code = 10: Asynchronous motor deceleration error. +Aux code = 11: Asynchronous motors speed dropped to zero. +Aux code = 12: PM motor acceleration error 1. +Aux code = 13: PM motor acceleration error 2. +Aux code = 14…16: PM motor speed dropped to zero. +Aux code = 17: SynRM pulse test error +Aux code = 18: Too big motor for advanced standstill ID run +Aux code = 19: Asynchronous motor data error</help_texts> + <user_manual_desc>Motor ID run was not completed successfully. +- Check the event log for an auxiliary code. See appropriate actions for each aux code in the manual.</user_manual_desc> + <rnd_desc>ID run failure.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>CalibrationFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Calibration</event_name> + <short_description>Current measurement calibration fault</short_description> + <help_headers>Current measurement calibration fault</help_headers> + <help_texts>Measured offset of output phase current measurement or difference between output phase U2 and W2 current measurement is too great (the values are updated during current calibration). +- Try performing the current calibration again (select Current measurement +calibration at parameter 99.13). If the fault persists, contact your local ABB representative.</help_texts> + <user_manual_desc>Measured offset of output phase current measurement or difference between output phase current measurement is too great. +- Try performing the current calibration again. If the fault persists, contact your local ABB representative.</user_manual_desc> + <rnd_desc>Current measurement offset or gain error is too big.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>AutophasingFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Autophasing</event_name> + <short_description>Autophasing routine has failed.</short_description> + <help_headers>Autophasing routine has failed.</help_headers> + <help_texts>Autophasing routine has failed. +- Try other autophasing modes (see parameter 21.13 Autophasing mode) if +possible.</help_texts> + <user_manual_desc>Autophasing routine has failed. +- Try other autophasing modes (see parameter 21.13 Autophasing mode) if +possible.</user_manual_desc> + <rnd_desc>PMSM initial angle search failed or too big motor model error in closed loop.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>LinkErrPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU communication</event_name> + <short_description>Communication errors detected between the drive control unit and the power unit.</short_description> + <help_headers>Communication errors detected between the drive control unit and the power unit</help_headers> + <help_texts>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</help_texts> + <user_manual_desc>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OverTemp3LFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Overtemperature hw</event_name> + <short_description>Hardware overtemperature detection (3L target specific)</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ExternalFault</handle> + <module>TUREL_FA_STUB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>External</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>External fault triggered either from +- digital input 3 or +- by setting g_u16TestNewFault = 1 or +- error in the charge relay control</rnd_desc> + <aux_codes> + <aux_code code="0x00000000"> + <names>AUX_EXTERNAL_FAULT_TEST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x00000001"> + <names>AUX_CHARGE_RELAY_FAILED</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>STOFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Safe torque off</event_name> + <short_description>Safe torque off function is active.</short_description> + <help_headers>Safe torque off function is active</help_headers> + <help_texts>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections. For more information, see appropriate drive +hardware manual.</help_texts> + <user_manual_desc>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_IncompatibleOptionModuleFlt</handle> + <module>Option_module</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Incompatible option module</event_name> + <short_description>Option module not supported</short_description> + <help_headers>Option module not supported</help_headers> + <help_texts>Remove incompatible option module.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes> + <aux_code code="1"> + <names>Incompatible option module in FBA A</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Incompatible option module in FBA B</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IGBTOverLoadFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>IGBT overload</event_name> + <short_description>Excessive IGBT junction to case temperature</short_description> + <help_headers>Excessive IGBT junction to case temperature</help_headers> + <help_texts>Excessive IGBT junction to case temperature. This fault protects the IGBT(s) and can be activated by a short circuit in the motor cable. +- Check motor cable.</help_texts> + <user_manual_desc>Excessive IGBT junction to case temperature. This fault protects the IGBT(s) and can be activated by a short circuit in the motor cable. +- Check motor cable.</user_manual_desc> + <rnd_desc>dTjc fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IGBTTempFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>IGBT temperature</event_name> + <short_description>Drive IGBT temperature is excessive.</short_description> + <help_headers>Drive IGBT temperature is excessive</help_headers> + <help_texts>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Tj fault limit exceeded.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>CoolingFault</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Cooling</event_name> + <short_description>Drive module temperature is excessive.</short_description> + <help_headers>Drive module temperature is excessive</help_headers> + <help_texts>Drive module temperature is excessive. +- Check ambient temperature. If it exceeds 40 °C (104 °F), ensure that load current does not exceed derated load capacity of drive. See appropriate Hardware Manual. +- Check drive module cooling air flow and fan operation. +- Check inside of cabinet and heatsink of drive module for dust pick-up. Clean +whenever necessary.</help_texts> + <user_manual_desc>Drive module temperature is excessive. +- Check ambient temperature. See appropriate Hardware Manual. +- Check cooling air flow and fan operation. +- Check heatsink of drive module for dust pick-up. Clean whenever necessary.</user_manual_desc> + <rnd_desc>On-line thermal model, cooling diagnostics, fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>DCunbalanceFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>DC unbalance fault</event_name> + <short_description>DC unbalance fault.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>DC unbalance of 3-level devices.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ADCErrorPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Measurement circuit ADC</event_name> + <short_description>Measurement circuit fault</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>PCB_SpaceCoolingFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PCB space cooling</event_name> + <short_description>PCB space cooling fault</short_description> + <help_headers>PCB space cooling fault</help_headers> + <help_texts>Check cooling fan inside the PCB space.</help_texts> + <user_manual_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded fault limit. +-Check cooling fan inside the PCB space.</user_manual_desc> + <rnd_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded fault limit.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Temperature difference between ambient and drive module PCB space temperature difference has exceeded fault limit.</cause> + <what_to_do>Check cooling fan inside the PCB space.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_CuLogicError</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>CU logic error</event_name> + <short_description>Control unit's FPGA has lost its configuration. +This fault cannot be reset.</short_description> + <help_headers>CU logic error</help_headers> + <help_texts>This fault automatically reboots the control unit after a short delay.</help_texts> + <user_manual_desc>Control unit's FPGA has lost its configuration. +This fault cannot be reset. +This fault automatically reboots the control unit after a short delay.</user_manual_desc> + <rnd_desc>Control unit's FPGA has lost its configuration. +This fault cannot be reset. +</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Problem in the Control Unit hardware.</cause> + <what_to_do>Replace the Control Unit.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>SSW_InternalFault</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Internal SSW fault</event_name> + <short_description>Internal SSW fault. +This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Internal SSW fault is generated, if a fatal error occurrs in power-up phase of System Software (SSW). +The SSW will run in a mode where only partial functionality is available. +It is still possible to download new software with a loading package.</user_manual_desc> + <rnd_desc>Internal SSW fault is generated, if a fatal error occurrs in the SSW power-up phase. +The system will run in SSW_FAULT-mode where only partial functionality is available. In this mode it is possible to download new SW with a loading package.</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>Failure when starting the OS time tick.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Failure when creating system tasks.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Failure when initializing the file system.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="8"> + <names>Failure when checking the file system.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>Failure when initializing the WoRm volumes.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="20"> + <names>Failure when loading the FPGA configuration.</names> + <user_manual_desc/> + </aux_code> + <aux_code code="40"> + <names>Failure when loading the application program.</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TaskOverloadFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Task overload</event_name> + <short_description>Task overload fault. +This fault cannot be reset.</short_description> + <help_headers>Task overload fault</help_headers> + <help_texts>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Task overloaded. The execution of the task takes too long time.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>KernelEventFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Kernel overload</event_name> + <short_description>Kernel overload fault. +This fault cannot be reset.</short_description> + <help_headers>Kernel overload fault</help_headers> + <help_texts>Operating system error. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Operating system error. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Operating system error.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>StackFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Stack overflow</event_name> + <short_description>Stack overflow fault. +This fault cannot be reset.</short_description> + <help_headers>Stack overflow fault</help_headers> + <help_texts>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Internal fault. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Stack overflow fault</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FPGAVerIncompatible</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>FPGA version incompatible</event_name> + <short_description>Firmware and FPGA are not compatible.</short_description> + <help_headers>Firmware and FPGA are not compatible.</help_headers> + <help_texts>Update FPGA</help_texts> + <user_manual_desc>Firmware and FPGA versions are incompatible with each other.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_InternalSWFlt2</handle> + <module>DRIVE_LOGIC</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Internal SW error 2</event_name> + <short_description>Internal SW error</short_description> + <help_headers>Internal SW error</help_headers> + <help_texts>Internal SW error</help_texts> + <user_manual_desc>Internal SW error</user_manual_desc> + <rnd_desc>Internal SW error</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBSerial1ErrFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB comm loss</event_name> + <short_description>The EFB has detected a comm loss. Check communications with system.</short_description> + <help_headers>EFB comm loss fault</help_headers> + <help_texts>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08, and 58.09 to adjust settings.</help_texts> + <user_manual_desc>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08, and 58.09 to adjust settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBConfigFileFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB config file</event_name> + <short_description>EFB protocol was unable to access its config file.</short_description> + <help_headers>EFB config file fault</help_headers> + <help_texts>EFB protocol was unable to access its config file. Reload firmware or replace the unit.</help_texts> + <user_manual_desc>EFB protocol was unable to access its config file. Reload firmware or replace the unit.</user_manual_desc> + <rnd_desc>Embedded fieldbus configuration file fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBForceTripFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB force trip</event_name> + <short_description>This fault is not currently used at this time.</short_description> + <help_headers>EFB force trip</help_headers> + <help_texts>This fault is not currently used at this time.</help_texts> + <user_manual_desc>This fault is not currently used at this time.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBFault1</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB load fault</event_name> + <short_description>Unable to load protocol firmware or version mismatch between protocol and system firmware.</short_description> + <help_headers>EFB load fault</help_headers> + <help_texts>Unable to load protocol firmware or version mismatch between protocol and system firmware. Reload firmware or replace the unit.</help_texts> + <user_manual_desc>Unable to load protocol firmware or version mismatch between protocol and system firmware. Reload firmware or replace the unit.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBFault2</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB fault 2</event_name> + <short_description>This fault is not currently used at this time.</short_description> + <help_headers>EFB fault 2</help_headers> + <help_texts>This fault is not currently used at this time.</help_texts> + <user_manual_desc>This fault is not currently used at this time.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBFault3</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB fault 3</event_name> + <short_description>This fault is not currently used at this time.</short_description> + <help_headers>EFB fault 3</help_headers> + <help_texts>This fault is not currently used at this time.</help_texts> + <user_manual_desc>This fault is not currently used at this time.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UffLoadFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Internal file load</event_name> + <short_description>Internal file load fault. +This fault cannot be reset.</short_description> + <help_headers>Internal file load fault</help_headers> + <help_texts>File read error. +Note: This fault cannot be reset. +-Contact your local ABB representative. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>File read error. +Note: This fault cannot be reset. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Loading of an UFF file has failed. The aux code tells which UFF file is in question. Permanent fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UffLoadNotPermanentFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Internal record load</event_name> + <short_description>Internal record load fault</short_description> + <help_headers>Internal record load fault</help_headers> + <help_texts>Internal record load error. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Internal record load error. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Loading of a UFF record has failed. This fault is used when a UFF loading fails but the activated fault can be resettable. </rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UffLoadPuRatingIdFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Rating ID fault</event_name> + <short_description>Rating ID fault</short_description> + <help_headers>Rating ID load error</help_headers> + <help_texts>Rating ID load error. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Rating ID load error. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Loading of the Rating ID has failed. This fault is used when a UFF loading fails but the activated fault can be resettable. </rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>LicensingFault</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Licensing fault</event_name> + <short_description>Licensing fault. +This fault cannot be reset.</short_description> + <help_headers>A required license is missing.</help_headers> + <help_texts>The software on this drive requires a license that couldn't be found. The missing license is indicated by the value of the aux code field. Please contact your product vendor for further instructions. +This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>A license that is required for the drive to function properly is missing. The missing license is Nxxxx, where xxxx is indicated by the 4-digit value of the aux code field.</user_manual_desc> + <rnd_desc>A required license is missing.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>A license that is required for the drive to function properly is missing.</cause> + <what_to_do>Record the aux codes of all active licensing faults and contact your product vendor for further instructions.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ApplLoadingFault</handle> + <module>TUCAC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Application loading</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc>Loading of the CoDeSys application has failed.</user_manual_desc> + <rnd_desc>Fault indicates that the application loading has failed. Causes for the failure can be problems in the content of the application UFF file or that the Codesys runtime-system initialization has failed.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>SynchronizationFault</handle> + <module>TUCLC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Synchronization fault</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Runaway current synchronization fault.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>IsolationFault</handle> + <module>TUCLC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Isolation fault</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Isolation fault. Ground impedance is too small.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_PowerUnitLogicDownloadHasFailed</handle> + <module>TUCOS_Power_Unit</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Power unit logic's download has failed</event_name> + <short_description>Download of new logic configuration file to the PU has failed. New download can be started. A power-up is required to exit the download mode, but the PU's FPGA configuration could be corrupted and prevents drive's normal operation.</short_description> + <help_headers>Power unit logic's download has failed</help_headers> + <help_texts>Download of new logic configuration file to the PU has failed. Drive is in a special mode. New download can be started. A power-up is required to exit the special mode, but the PU's FPGA configuration could be corrupted and prevents drive's normal operation.</help_texts> + <user_manual_desc>Download of new logic configuration file to the PU has failed. Drive is in a special mode. New download can be started. A power-up is required to exit the special mode, but the PU's FPGA configuration could be corrupted and prevents drive's normal operation.</user_manual_desc> + <rnd_desc>Download of new logic configuration file to the PU has failed. New download can be started. A power-up is required to exit the special mode, but the PU's FPGA configuration could be corrupted and prevents drive's normal operation.</rnd_desc> + <aux_codes> + <aux_code code="0x2000"> + <names>Error code</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_DriveRestartIsRequired</handle> + <module>TUCOS_Power_Unit</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Control unit restart is required</event_name> + <short_description>New logic configuration file has been downloaded to the PU. Drive is in a special mode and a power-up is required to exit the download mode.</short_description> + <help_headers>Control unit restart is required</help_headers> + <help_texts>New logic configuration file has been downloaded to the PU. Drive is in a special mode and a power-up is required to exit the download mode.</help_texts> + <user_manual_desc>New logic configuration file has been downloaded to the PU. Drive is in a special mode and a power-up is required to exit the download mode.</user_manual_desc> + <rnd_desc>New logic configuration file has been downloaded to the PU. Drive is in a special mode and a power-up is required to exit the download mode. +</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>PFPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU board powerfail</event_name> + <short_description>Power unit power supply failure</short_description> + <help_headers>Power unit power supply failure</help_headers> + <help_texts>Power unit power supply failure. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Power unit power supply failure.</user_manual_desc> + <rnd_desc>Auxiliary power failure of power unit board +</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>DFFPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Measurement circuit DFF</event_name> + <short_description>Measurement circuit fault</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>PSL2DriverInternalFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU communication internal</event_name> + <short_description>Internal communication error</short_description> + <help_headers>Internal communication error</help_headers> + <help_texts>Internal communication error. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Internal communication error. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TempFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Excess temperature</event_name> + <short_description>Power unit module temperature is excessive.</short_description> + <help_headers>Power unit module temperature is excessive.</help_headers> + <help_texts>Check ambient conditions. +Check air flow and fan operation. +Check heatsink fins for dust pick-up. +Check motor power against drive power.</help_texts> + <user_manual_desc>Power unit module temperature is excessive.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>TempDifFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Excess temperature difference</event_name> + <short_description>High temperature difference between the IGBTs of different phases.</short_description> + <help_headers>High temperature difference between the IGBTs of different phases.</help_headers> + <help_texts>Check the motor cabling. +Check cooling of drive module(s).</help_texts> + <user_manual_desc>Too high temperature difference between the highest and lowest measured IGBT temperatures of different phases. The amount of available temperatures depends on the frame size.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BRResistorFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Brake resistor</event_name> + <short_description>Brake chopper power lower than required</short_description> + <help_headers>Brake chopper power lower than required</help_headers> + <help_texts>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor. +-Check the dimensioning of the brake resistor.</help_texts> + <user_manual_desc>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor. +-Check the dimensioning of the brake resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUEFFault</handle> + <module>TUCOS_BU_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU earth leakage</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Earth fault detected by the branching unit: sum of all currents is exceeding the level.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUIDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU current difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check fault for currents</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUUCDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU DC link difference</event_name> + <short_description>DC voltage difference fault</short_description> + <help_headers>DC voltage difference fault</help_headers> + <help_texts>Difference in DC voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Difference in DC voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Difference check fault for DC-link voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUCDDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU commutation difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check fault for CDX and CDY.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BUUmainDiffFault</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>BU voltage difference</event_name> + <short_description>Main voltage difference fault</short_description> + <help_headers>Main voltage difference fault</help_headers> + <help_texts>Difference in main voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</help_texts> + <user_manual_desc>Difference in main voltages between parallel-connected inverter modules. +-Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Difference check fault for main voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>HWConfigFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>PU communication configuration</event_name> + <short_description>PU channel configuration is not matching with the setting</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>Configuration failure of power unit communication channel(s): channel information is not matching with parameters or channels are cross connected.</user_manual_desc> + <rnd_desc>Erroneous configuration of PU communication channel(s): the actual channel ids are not matching with parameters or channels are cross connected.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ReducedRunPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Reduced run</event_name> + <short_description>Some xINTs are missing</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>Some of the configured power units are not found. The reduced run is possible if configured.</user_manual_desc> + <rnd_desc>Not all power units found, reduced run is possible</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FPGAErrPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>PU logic error</event_name> + <short_description>power unit logic memory error</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>The memory of the power unit logic is cleared.</user_manual_desc> + <rnd_desc>PU FPGA logic has lost its memory, signature register value is missing</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>MemUnitDetached</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="true" fast_presampling="false"> + <event_name>Memory Unit Detached</event_name> + <short_description>Memory unit detached. +This fault cannot be reset.</short_description> + <help_headers/> + <help_texts>This fault requires a reboot of the control unit either by switching the power off and on, or using parameter 98.06 Control board boot.</help_texts> + <user_manual_desc>Memory unit has been removed while the power is on.</user_manual_desc> + <rnd_desc>Memory Unit has been removed. Live removing or inserting of the memory unit is not supported.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>STSVPSFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>PU state feedback</event_name> + <short_description>PU state feedback</short_description> + <help_headers>PU state feedback</help_headers> + <help_texts>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</help_texts> + <user_manual_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</user_manual_desc> + <rnd_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>CHGFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Charging feedback</event_name> + <short_description>Charging feedback missing</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>The charging feedback is missing.</user_manual_desc> + <rnd_desc>Formerly INVD</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UnknownPUFault</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Unknown PU fault</event_name> + <short_description>Unknown power unit fault</short_description> + <help_headers>Unknown power unit fault</help_headers> + <help_texts>The power unit logic has generated a fault which is not known by the softaware. +-Check the logic and software compatility.</help_texts> + <user_manual_desc>The power unit logic has generated a fault which is not known by the softaware. +-Check the logic and software compatility.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>DiagnosticsFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Diagnostics</event_name> + <short_description>Diagnostics failed.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>INU or motor diagnostics failure.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OverFrequencyFault</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Overfrequency</event_name> + <short_description>Output frequency too high.</short_description> + <help_headers>Output frequency too high.</help_headers> + <help_texts>Output frequency too high.</help_texts> + <user_manual_desc>Output frequency too high.</user_manual_desc> + <rnd_desc>Absolute output frequency has exceeded internal fault limit.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>LangDataRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text data overflow</event_name> + <short_description>Language data table size is too short. Please, contact ABB.</short_description> + <help_headers>Language data table fault</help_headers> + <help_texts>The buffer size is too short for language data, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB.</help_texts> + <user_manual_desc>The table size is too short for language data, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB, if this fault is active. +The fault can be reseted and drive can be used normally.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for language data. Increase the buffer length in LANG_config.h file. +</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>Lang32BitRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text 32-bit table overflow</event_name> + <short_description>32 bit bointer table size is too short. Please, contact ABB.</short_description> + <help_headers>32 bit pointer table fault</help_headers> + <help_texts>32 bit bointer table size is too short for text, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB.</help_texts> + <user_manual_desc>32 bit bointer table size is too short for text, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB, if this fault is active. +The fault can be reseted and drive can be used normally.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for 32 bit poiters. Increase the buffer length in LANG_config.h file.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>Lang64BitRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text 64-bit table overflow</event_name> + <short_description>64 bit bointer table size is too short. Please, contact ABB.</short_description> + <help_headers>64 bit pointer table fault</help_headers> + <help_texts>64 bit bointer table size is too short for text, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB.</help_texts> + <user_manual_desc>64 bit bointer table size is too short for text, which are tried to locate into the drive's RAM, for string-by-string search. Please, Contact ABB, if this fault is active. +The fault can be reseted and drive can be used normally.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for 64 bit poiters. Increase the buffer length in LANG_config.h file.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>LangSourceFileRAMTableFault</handle> + <module>TUCOS_LANG_EXT_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Text file overflow</event_name> + <short_description>The table size is too short for opening language file. Please, contact ABB.</short_description> + <help_headers>Language file open fault</help_headers> + <help_texts>The buffer size is too short for opening language file. Please, Contact ABB.</help_texts> + <user_manual_desc>The table size is too short for opening language file. Please, Contact ABB, if this fault is active. +The fault can be reseted and drive can be used normally.</user_manual_desc> + <rnd_desc>RAM buffer size is too short for opening language file. Increase the buffer length in LANG_config.h file.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ParSysFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Parameter system</event_name> + <short_description>Parameter system fault</short_description> + <help_headers>Parameter system fault</help_headers> + <help_texts>Parameter load or save failed. +-Try forcing a save using parameter 96.07 Param save. Retry.</help_texts> + <user_manual_desc>Parameter load or save failed. +-Try forcing a save using parameter 96.07 Param save. Retry.</user_manual_desc> + <rnd_desc>Failure in the parameter system. Fix mentioned in User manual description available with TUREL101+</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>UserSetFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>User Set Fault</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>BackupRestoreTimeoutFault</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Backup/Restore Timeout</event_name> + <short_description>Backup/Restore timeout</short_description> + <help_headers>BR timeout fault</help_headers> + <help_texts>Check panel / PC-tool communication and if it is still in backup / restore state.</help_texts> + <user_manual_desc>Thrown during backup taking or restoring operation when a panel or PC-tool fails to communicate with the drive as part of backup taking or restoring operation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>EFBParFBusNotPresentFault</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>EFB invalid parameterization</event_name> + <short_description>Invalid EFB configuration. Please check EFB parameters in group 58.</short_description> + <help_headers>EFB invalid parameterization</help_headers> + <help_texts>Invalid EFB configuration. Please check EFB parameters in group 58 and verify they are consistent with the configured protocol.</help_texts> + <user_manual_desc>Invalid EFB configuration. Please check EFB parameters in group 58 and verify they are consistent with the configured protocol.</user_manual_desc> + <rnd_desc>Embedded fieldbus invalid parameterization</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_APFault1</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>AP Fault 1</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_APFault2</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>AP Fault 2</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_APFault3</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>AP Fault 3</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_APFault4</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>AP Fault 4</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_APFault5</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>AP Fault 5</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_AdaptiveProgram</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Adaptive program</event_name> + <short_description>Adaptive program file incompatible or corrupted.</short_description> + <help_headers>Adaptive program file incompatible or corrupted.</help_headers> + <help_texts>Adaptive program file incompatible or corrupted. Check the fault logger for a fault code extension.</help_texts> + <user_manual_desc>Adaptive program has faulted. Check the fault code extension for further information.</user_manual_desc> + <rnd_desc>Harmonized fault code: 0x64A6 +Adaptive program fault. Adaptive program file incompatible or corrupted.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Adaptive program file incompatible or corrupted.</cause> + <what_to_do>Check the fault logger for a fault code extension.</what_to_do> + </item> + </cause_list> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_Standby_timeout</handle> + <module>NomValues</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Standby timeout</event_name> + <short_description>Autostart delay elapsed.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>After autorestart delay is elapsed and drive can not be started this fault is given instead of Undervoltage.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>FaultReset</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>Fault reset</event_name> + <short_description/> + <help_headers/> + <help_texts>This event indicates that fault has been reset. The cause of the fault no +longer exists and the fault reset has been requested and completed.</help_texts> + <user_manual_desc/> + <rnd_desc>Fault reset has been requested and done.</rnd_desc> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>OverCurrentWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Overcurrent</event_name> + <short_description>Output current has exceeded internal fault limit.</short_description> + <help_headers>Output current has exceeded internal fault limit</help_headers> + <help_texts>Output current has exceeded internal fault limit. +- Check motor load. +- Check acceleration times in parameter group 23 Speed reference ramp. +- Check motor and motor cable (including phasing and delta/star connection). +- Check that the start-up data in parameter group 99 corresponds to the motor rating plate. +- Check that there are no power factor correction capacitors or surge absorbers +in motor cable. +- Check encoder cable (including phasing).</help_texts> + <user_manual_desc>Output current has exceeded internal fault limit. Check: +- motor load +- acceleration times +- motor and motor cabl +- start-up data in parameter group 99 +- there are no power factor correction capacitor +- encoder cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>OvervoltageWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>DC link overvoltage</event_name> + <short_description>DC link overvoltage warning</short_description> + <help_headers>DC link overvoltage warning</help_headers> + <help_texts>Excessive intermediate circuit DC voltage +-Check that overvoltage controller is on, parameter 30.30 Overvoltage control. +-Check mains for static or transient overvoltage. +-Check brake chopper and resistor (if used). +-Check deceleration time. +-Use coast-to-stop function (if applicable). +-Retrofit frequency converter with brake chopper and brake resistor.</help_texts> + <user_manual_desc>Excessive intermediate circuit DC voltage +Check +-p. 30.30 Overvoltage control +-mains for static or transient overvoltage +-brake chopper/resistor +-decel. time +Use coast-to-stop. +Retrofit drive with chopper and resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>STOWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Safe torque off</event_name> + <short_description>Safe torque off function is active.</short_description> + <help_headers>Safe torque off function is active</help_headers> + <help_texts>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections. For more information, see appropriate drive +hardware manual.</help_texts> + <user_manual_desc>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ShortCircuitWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Short circuit</event_name> + <short_description>Short-circuit in motor cable(s) or motor.</short_description> + <help_headers>Short-circuit in motor cable(s) or motor</help_headers> + <help_texts>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable.</help_texts> + <user_manual_desc>Short-circuit in motor cable(s) or motor. +- Check motor and motor cable. +- Check there are no power factor correction capacitors or surge absorbers +in motor cable.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>UndervoltageWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>DC link undervoltage</event_name> + <short_description>DC link undervoltage warning</short_description> + <help_headers>DC link undervoltage warning</help_headers> + <help_texts>Intermediate circuit DC voltage is not sufficient due to missing mains phase, blown fuse or rectifier bridge internal fault. +-Check supply and fuses.</help_texts> + <user_manual_desc>Intermediate circuit DC voltage is not sufficient due to missing mains phase, blown fuse or rectifier bridge internal fault. +-Check supply and fuses.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>EarthWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Earth leakage</event_name> + <short_description>Earth leakage warning</short_description> + <help_headers>Earth leakage warning</help_headers> + <help_texts>Load unbalance in eg, motor or cable +Check +-no power factor correction capacitors or surge absorbers +-no earth fault in cables: measure insulation resistances +If no earth fault detected, contact ABB.</help_texts> + <user_manual_desc>Load unbalance in eg, motor or cable +Check +-no power factor correction capacitors or surge absorbers +-no earth fault in cables: measure insulation resistances +If no earth fault detected, contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BcErWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Brake resistor wiring</event_name> + <short_description>Brake resistor wiring warning</short_description> + <help_headers>Brake resistor wiring warning</help_headers> + <help_texts>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged.</help_texts> + <user_manual_desc>Brake resistor short circuit or brake chopper control fault. +-Check brake chopper and brake resistor connection. +-Ensure brake resistor is not damaged.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BcScWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BC short circuit</event_name> + <short_description>Brake chopper short circuit</short_description> + <help_headers>Brake chopper short circuit</help_headers> + <help_texts>Short circuit in brake chopper IGBT. +-Replace brake chopper. +-Ensure brake resistor is connected and not damaged.</help_texts> + <user_manual_desc>Short circuit in brake chopper IGBT. +-Replace brake chopper. +-Ensure brake resistor is connected and not damaged.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BrOvertempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>BR excess temperature</event_name> + <short_description>Excessive brake resistor temperature</short_description> + <help_headers>Excessive brake resistor temperature</help_headers> + <help_texts>Brake resistor temperature has exceeded warning limit defined by parameter 43.12 Brake resistor warning limit. +- Stop drive. Let resistor cool down. +- Check resistor overload protection function settings (parameter group 43 Brake chopper). +- Check parameter 43.12 Brake resistor warning limit. +- Check that braking cycle meets allowed limits.</help_texts> + <user_manual_desc>Brake resistor temperature has exceeded warning limit defined by parameter 43.12 Brake resistor warning limit. +- Stop drive. Let resistor cool down. +- Check parameter group 43 Brake chopper. +- Check that braking cycle meets allowed limits.</user_manual_desc> + <rnd_desc>Braking resistor thermal model alarm.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BcIgbtOvertempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>BC IGBT excess temperature</event_name> + <short_description>Excessive brake chopper IGBT temperature</short_description> + <help_headers>Excessive brake chopper IGBT temperature</help_headers> + <help_texts>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check for excessive ambient temperature. +- Check for cooling fan failure.Check for obstructions in the air flow. +- Check the dimensioning and cooling of the cabinet. +- Check resistor overload protection function settings (parameters 43.06…43.10). +- Check that braking cycle meets allowed limits. +- Check that drive supply AC voltage is not excessive.</help_texts> + <user_manual_desc>Brake chopper IGBT temperature has exceeded internal fault limit. +- Let chopper cool down. +- Check: for excessive ambient temperature, cooling fan, resistor overload protection function settings, braking duty cycle, drive supply AC voltage.</user_manual_desc> + <rnd_desc>BC IGBT thermal model warning</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BrDataAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BR data</event_name> + <short_description>Incorrect braking resistor data.</short_description> + <help_headers>Incorrect braking resistor data</help_headers> + <help_texts>Incorrect braking resistor data. +Aux code = 1: The braking resistor resistance value is too low. +- Check that braking resistor resistance is sufficient. +Aux code = 2: The thermal protection of braking resistor is enabled but braking resistor thermal time constant is is not given. +- Check that braking resistor thermal time constant is given. +Aux code = 3: The thermal protection of braking resistor is enabled but braking resistor maximum power is is not given. +- Check that braking resistor maximum power is given.</help_texts> + <user_manual_desc>The braking resistor value is too low +- Check that braking resistor resistance is sufficient. +The thermal protection of braking resistor is enabled but data is not given +- Check that braking resistor thermal time constant and maximum power are given.</user_manual_desc> + <rnd_desc>Braking resistor data is invalid (either too small resistor or thermal protection data not given altough thermal protection is enabled).</rnd_desc> + <aux_codes> + <aux_code code="0x1"> + <names>R Br too low</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x2"> + <names>Br Tau Th not given</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x3"> + <names>Br P Max not given</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>IGBT_OvertempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>IGBT overtemperature</event_name> + <short_description>Estimated drive IGBT temperature is excessive.</short_description> + <help_headers>Estimated drive IGBT temperature is excessive</help_headers> + <help_texts>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Estimated drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Too much current in off-line thermal model while thermal current limitation passivated.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>NoMotDataAlarm</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>No motor data</event_name> + <short_description>Parameters in group 99 have not been set.</short_description> + <help_headers>Parameters in group 99 have not been set</help_headers> + <help_texts>Parameters in group 99 have not been set. +- Check that all the required parameters in group 99 have been set. +Note: It is normal for this warning to appear during the start-up until the motor +data is entered.</help_texts> + <user_manual_desc>Parameters in group 99 have not been set. +- Check that all the required parameters in group 99 have been set. +Note: It is normal for this warning to appear during the start-up until the motor +data is entered.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>MotorNomValueAlarm</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Motor nominal value</event_name> + <short_description>Incorrect motor parameter values, or wrong drive dimensioning</short_description> + <help_headers>Incorrect motor parameter values, or wrong drive dimensioning</help_headers> + <help_texts>The motor parameters are set incorrectly. +- Check the settings of the motor configuration parameters in group 99. +The drive is not dimensioned correctly. +- Check that the drive is sized correctly for the motor.</help_texts> + <user_manual_desc>The motor parameters are set incorrectly. +- Check the settings of the motor configuration parameters in group 99. +The drive is not dimensioned correctly. +- Check that the drive is sized correctly for the motor.</user_manual_desc> + <rnd_desc>Motor data not given or motor/inu ratio not acceptable.</rnd_desc> + <aux_codes> + <aux_code code="1"> + <names>Motor slip frequency is too small</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Too big error between synch. and nominal speed</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Motor nom speed is higher than synch with p=1</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Motor nom current is not within allowed limits</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Motor nom voltage is not within allowed limits</names> + <user_manual_desc/> + </aux_code> + <aux_code code="6"> + <names>Motor nom power is higher than apparent power</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7"> + <names>Nom power not consistent with nom speed&torque</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>IGBTOverLoadAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>IGBT overload</event_name> + <short_description>Excessive IGBT junction to case temperature</short_description> + <help_headers>Excessive IGBT junction to case temperature</help_headers> + <help_texts>Excessive IGBT junction to case temperature. This warning protects the IGBT(s) +and can be activated by a short circuit in the motor cable. +- Check motor cable.</help_texts> + <user_manual_desc>Excessive IGBT junction to case temperature. This warning protects the IGBT(s) +and can be activated by a short circuit in the motor cable. +- Check motor cable.</user_manual_desc> + <rnd_desc>dTjc warning</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>IGBTTempAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>IGBT temperature</event_name> + <short_description>Drive IGBT temperature is excessive.</short_description> + <help_headers>Drive IGBT temperature is excessive</help_headers> + <help_texts>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</help_texts> + <user_manual_desc>Drive IGBT temperature is excessive. +- Check ambient conditions. +- Check air flow and fan operation. +- Check heatsink fins for dust pick-up. +- Check motor power against drive power.</user_manual_desc> + <rnd_desc>Tj has exceeded alarm limit</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>CoolingAlarm</handle> + <module>TUCTC_TUCLC_common_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Cooling</event_name> + <short_description>Drive module temperature is excessive.</short_description> + <help_headers>Drive module temperature is excessive</help_headers> + <help_texts>Drive module temperature is excessive. +- Check ambient temperature. If it exceeds 40 °C (104 °F), ensure that load current does not exceed derated load capacity of drive. See appropriate Hardware Manual. +- Check drive module cooling air flow and fan operation. +- Check inside of cabinet and heatsink of drive module for dust pick-up. Clean +whenever necessary.</help_texts> + <user_manual_desc>Drive module temperature is excessive. +- Check ambient temperature. See appropriate Hardware Manual. +- Check cooling air flow and fan operation. +- Check heatsink of drive module for dust pick-up. Clean whenever necessary.</user_manual_desc> + <rnd_desc>On-line thermal model, cooling diagnostics alarm.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ADCErrorWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Measurement circuit ADC</event_name> + <short_description>Measurement circuit fault</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>PCB_SpaceCoolingWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PCB space cooling</event_name> + <short_description>PCB space cooling warning</short_description> + <help_headers>PCB space cooling warning</help_headers> + <help_texts>Check cooling fan inside the PCB space.</help_texts> + <user_manual_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded warning limit. +-Check cooling fan inside the PCB space.</user_manual_desc> + <rnd_desc>Temperature difference between ambient and drive module PCB space temperature difference has exceeded warning limit.</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Temperature difference between ambient and drive module PCB space temperature difference has exceeded warning limit.</cause> + <what_to_do>Check cooling fan inside the PCB space.</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_PowerUnitLogicUpdateInProgress</handle> + <module>TUCOS_Power_Unit</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Power unit's logic update in progress</event_name> + <short_description>New logic configuration file is downloaded to the PU. Drive is in a special mode and can not be started.</short_description> + <help_headers>Power unit's logic update in progress</help_headers> + <help_texts>New logic configuration file is downloaded to the PU. Drive is in a special mode and can not be started.</help_texts> + <user_manual_desc>New logic configuration file is downloaded to the PU. Drive is in a special mode and can not be started.</user_manual_desc> + <rnd_desc>New logic configuration file is downloaded to the PU. Drive is in a special mode and can not be started. +</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>PFWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU board powerfail</event_name> + <short_description>Power unit power supply failure</short_description> + <help_headers>Power unit power supply failure</help_headers> + <help_texts>Power unit power supply failure. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Power unit power supply failure. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>DFFWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Measurement circuit DFF</event_name> + <short_description>Measurement circuit fault</short_description> + <help_headers>Measurement circuit fault</help_headers> + <help_texts>Measurement circuit fault. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Measurement circuit fault. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>PSL2DriverInternalWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU communication internal</event_name> + <short_description>Communication errors detected between the drive control unit and the power unit.</short_description> + <help_headers>Communication errors detected between the drive control unit and the power unit.</help_headers> + <help_texts>Communication errors detected between the drive control unit and the power unit. +- Check the connections between the drive control unit and the power unit.</help_texts> + <user_manual_desc>Communication errors detected between the drive control unit and the power unit. +- Check the connections between the drive control unit and the power unit.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>TempWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Excess temperature</event_name> + <short_description>Temperature measurement from the power unit is too high</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>Measured temperature from power unit is too high.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>TempSensorWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Measurement circuit temperature</event_name> + <short_description>Problem with internal temperature measurement of the drive</short_description> + <help_headers>Problem with internal temperature measurement of the drive</help_headers> + <help_texts>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Problem with internal temperature measurement of the drive. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>TempDifWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Excess temperature difference</event_name> + <short_description>High temperature difference between the IGBTs of different phases.</short_description> + <help_headers>High temperature difference between the IGBTs of different phases.</help_headers> + <help_texts>Check the motor cabling. +Check cooling of drive module(s).</help_texts> + <user_manual_desc>High temperature difference between the IGBTs of different phases.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BRResistorWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Brake resistor</event_name> + <short_description>Brake chopper power lower than required.</short_description> + <help_headers>Brake chopper power lower than required.</help_headers> + <help_texts>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor.</help_texts> + <user_manual_desc>Brake resistor broken or not connected. +-Check that a brake resistor has been connected. +-Check the condition of the brake resistor.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUEFWarning</handle> + <module>TUCOS_BU_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>BU earth leakage</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Earth leakage warning detected by the branching unit: sum of all currents is exceeding the level.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUIDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU current difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Difference check warning for currents</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUUCDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU DC link difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check warning for DC link voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUCDDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU commutation difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check warning for CDX and CDY.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>LinkErrWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU communication</event_name> + <short_description>Communication errors detected between the drive control unit and the power unit.</short_description> + <help_headers>Communication errors detected between the drive control unit and the power unit</help_headers> + <help_texts>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</help_texts> + <user_manual_desc>Communication errors detected between the drive control unit and the power unit. +- Check the connection between the drive control unit and the power unit.</user_manual_desc> + <rnd_desc>Some PU communication diagnostic counter is counting => warning</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>STSVWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>PU state feedback</event_name> + <short_description>PU state feedback</short_description> + <help_headers>PU state feedback</help_headers> + <help_texts>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</help_texts> + <user_manual_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</user_manual_desc> + <rnd_desc>State feedback supervision supervises the state feedback signals from the output phases and compares the signals to the actual control signals. All of the output phases are sampled invidually.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>CHGWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Charging feedback</event_name> + <short_description>Charging feedback missing</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>The charging feedback is missing.</user_manual_desc> + <rnd_desc>Formerly INVD</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>BUUmainDiffWarning</handle> + <module>TUCOS_BU_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>BU voltage difference</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Branching unit difference check warning for main voltage</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>RedundantMeasurementPSWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Redundant measurement</event_name> + <short_description>Redundant measurement</short_description> + <help_headers>Redundant measurement</help_headers> + <help_texts>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative.</help_texts> + <user_manual_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. +- Contact your local ABB representative.</user_manual_desc> + <rnd_desc>Redundant measurement supervision has indicated a difference in the duplicated measurements that is outside the limits. (Solar applications)</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>OverTemp3LWarning</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Overtemperature hw</event_name> + <short_description>Overtemperature hw detection (3L target specific)</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>FlashConsumptionSpeed</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Flash erase speed exceeded</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_PUSAVE_warning</handle> + <module>PU Save</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>Data saving to power unit</event_name> + <short_description>An error detected in saving data to power unit.</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>An error detected in saving data to power unit.</user_manual_desc> + <rnd_desc>An error detected in saving data to power unit. +Industial and standard drives harmonized event code is 0xA683</rnd_desc> + <aux_codes/> + <cause_list> + <item> + <cause>Power unit saving does not work properly.</cause> + <what_to_do>Replace the power unit. +If saving to power unit is not necessary, the warning can be cleared by disabling the feature with parameter 96.30.</what_to_do> + </item> + </cause_list> + </warning> + </event_type> + </event> + <event> + <handle>EFBSerial1ErrWarning</handle> + <module>TUCOS_EFB_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>EFB comm loss</event_name> + <short_description>The EFB has detected a comm loss. Check communications with system.</short_description> + <help_headers>EFB comm loss warning</help_headers> + <help_texts>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08, and 58.09 to adjust settings.</help_texts> + <user_manual_desc>The embedded fieldbus (EFB) interface has detected a comm loss. Please check communications with master / PLC / supervisory controller. See parameters 58.07, 58.08, and 58.09 to adjust settings.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_SDCardWrng</handle> + <module>TUCOS_GENERAL_Events</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>SD card</event_name> + <short_description>SD card</short_description> + <help_headers>SD card is not operational.</help_headers> + <help_texts>Check that the SD card is properly inserted in the control unit and that it is in working condition.</help_texts> + <user_manual_desc>SD card is not operating properly (with BCU control unit only). Saving power unit diagnostic data on SD card may not be possible.</user_manual_desc> + <rnd_desc>SD card is not operational.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>DummyWarning3</handle> + <module>TUREL_FA_STUB_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Dummy 3</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Dummy warning for testing purposes.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>DummyWarning2</handle> + <module>TUREL_FA_STUB_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Dummy 2</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Dummy warning for testing purposes.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>DummyWarning</handle> + <module>TUREL_FA_STUB_Events</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Dummy 1</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>Dummy warning for testing purposes.</rnd_desc> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_mapped_par_value_cut</handle> + <module>ParameterMap</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Mapped parameter value cut</event_name> + <short_description>Mapped parameter value cut</short_description> + <help_headers>Mapped parameter value cut</help_headers> + <help_texts>Check parameter scaling and format.</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_par_map_configuration</handle> + <module>ParameterMap</module> + <bit_handle/> + <event_type> + <warning> + <event_name>Parameter map configuration</event_name> + <short_description>Parameter map configuration</short_description> + <help_headers>Parameter map configuration</help_headers> + <help_texts>Too many parameters in configuration file</help_texts> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_APWarning1</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <warning> + <event_name>AP Warning 1</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_APWarning2</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <warning> + <event_name>AP Warning 2</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_APWarning3</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <warning> + <event_name>AP Warning 3</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_APWarning4</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <warning> + <event_name>AP Warning 4</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_APWarning5</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <warning> + <event_name>AP Warning 5</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_APPure1</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>AP Pure Event 1</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_APPure2</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>AP Pure Event 2</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_APPure3</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>AP Pure Event 3</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_APPure4</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>AP Pure Event 4</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_APPure5</handle> + <module>AP_Program</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>AP Pure Event 5</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>STOPureEvent</handle> + <module>TUCOS_PSL2_DRIVER_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>STO event</event_name> + <short_description>Safe torque off function is active.</short_description> + <help_headers>Safe torque off function is active</help_headers> + <help_texts>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections. For more information, see appropriate drive +hardware manual.</help_texts> + <user_manual_desc>Safe torque off function is active, i.e. safety circuit signal(s) connected to connector XSTO is broken during start, or while drive is stopped and parameter 31.22 STO diagnostics is set to Fault. +- Check safety circuit connections.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>IDRunDone</handle> + <module>TUCTC_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>ID run done</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc>ID run has been performed successfully</user_manual_desc> + <rnd_desc>ID run has been performed successfully + +</rnd_desc> + <aux_codes> + <aux_code code="0"> + <names>None</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>Normal</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>Reduced</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>Standstill</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>Autophasing</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>Current measurement calibration</names> + <user_manual_desc/> + </aux_code> + <aux_code code="6"> + <names>Advanced</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7"> + <names>Advanced standstill</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_TUCSO_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>TUCSO fault</event_name> + <short_description>FSO subsystem fault</short_description> + <help_headers>FSO subsystem fault.</help_headers> + <help_texts>FSO subsystem fault.</help_texts> + <user_manual_desc>FSO subsystem fault.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSO_FAULTS_GEN</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO general fault</event_name> + <short_description>FSO general fault</short_description> + <help_headers>FSO makes first a warning, then this General fault.</help_headers> + <help_texts>This fault always follows certain malfunctions which the FSO module indicates by warnings. The FSO module generates a warning indication first to allow the drive to control the system to a safe state after which the drive trips (to this fault).</help_texts> + <user_manual_desc>This fault always follows certain malfunctions which the FSO module indicates by warnings. The FSO module generates a warning indication first to allow the drive to control the system to a safe state after which the drive trips (to this fault).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_StopCompleted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO stop completed</event_name> + <short_description>FSO stop completed</short_description> + <help_headers>FSO stop completed</help_headers> + <help_texts>FSO module has completed STO, SS1 or SSE function.</help_texts> + <user_manual_desc>FSO module has completed STO, SS1 or SSE function.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_SafeSpeedLimit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO safe speed limit</event_name> + <short_description>FSO safe speed limit</short_description> + <help_headers>FSO safe speed limit</help_headers> + <help_texts>Motor actual speed exceeded a safe speed limit of the FSO module.</help_texts> + <user_manual_desc>Motor actual speed exceeded a safe speed limit of the FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_OutOfEmeRamp</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO out of eme ramp</event_name> + <short_description>FSO out of eme ramp</short_description> + <help_headers>FSO out of emergency ramp.</help_headers> + <help_texts>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_RampCoasted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO ramp coasted</event_name> + <short_description>FSO ramp coasted</short_description> + <help_headers>Drive coasted the motor during ramp.</help_headers> + <help_texts>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (FSOGEN.51 Zero speed without encoder).</help_texts> + <user_manual_desc>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (FSOGEN.51 Zero speed without encoder).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_OutOfSafeRamp</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO out of safe ramp</event_name> + <short_description>FSO out of safe ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_OutOfSDI</handle> + <module>FS_FA</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO out of SDI</event_name> + <short_description>FSO out of SDI.</short_description> + <help_headers>FSO out of SDI.</help_headers> + <help_texts>Motor was not rotating to the allowed direction.</help_texts> + <user_manual_desc>Motor was not rotating to the allowed direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_POUS_premature</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_FLT</flag> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO premature POUS</event_name> + <short_description>FSO premature POUS</short_description> + <help_headers>POUS was requested while drive was still on.</help_headers> + <help_texts>POUS was requested while drive was still modulating. POUS is supposed to be activated when drive is stopped.</help_texts> + <user_manual_desc>POUS was requested while drive was still modulating. POUS is supposed to be activated when drive is stopped.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_Undef</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO undefined fault</event_name> + <short_description>FSO undefined fault</short_description> + <help_headers>FSO undefined fault</help_headers> + <help_texts>FSO new version, undefined fault in Drive event system. Contact ABB.</help_texts> + <user_manual_desc>FSO new version, undefined fault in Drive event system. Contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSOF_passivated</handle> + <module>FS_FA</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSO passivated</event_name> + <short_description>FSO passivated</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO module is passivated due safetybus problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSO_Warnings</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO general warnings</event_name> + <short_description>FSO general warnings.</short_description> + <help_headers>FSO general warnings.</help_headers> + <help_texts>FSO general warnings. Mainly for some unrisky situations, like transition to configuration mode. See aux codes for details.</help_texts> + <user_manual_desc>FSO general warnings. Mainly for some unrisky situations, like transition to configuration mode. See aux for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_INT</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO internal fault</event_name> + <short_description>FSO internal fault.</short_description> + <help_headers>Boot the module once, see the Aux code for more details.</help_headers> + <help_texts>Internal fault in the FSO module. Boot the module once, if the problem is still there, replace the FSO module. Contact your local ABB representative. See the Aux code for more details.</help_texts> + <user_manual_desc>Internal fault in the FSO module. Boot the module once, if the problem is still there, replace the FSO module. Contact your local ABB representative. See the Aux code for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_IO</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO IO fault</event_name> + <short_description>FSO IO fault.</short_description> + <help_headers>Problems in the I/O cabling</help_headers> + <help_texts>FSO IO fault. Check the FSO I/O cabling. See the Aux code for more details.</help_texts> + <user_manual_desc>FSO IO fault. Check the FSO I/O cabling. See the Aux code for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_STO</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO STO fault</event_name> + <short_description>FSO STO fault. Problems in the STO cabling or inside the drive. Check the FSO STO cabling.</short_description> + <help_headers>Problems in the STO cabling or inside the drive.</help_headers> + <help_texts>FSO STO fault. Problems in the STO cabling or inside the drive. Check the FSO STO cabling.</help_texts> + <user_manual_desc>FSO STO fault.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_STOREQ</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO STO request</event_name> + <short_description>FSO STO request.</short_description> + <help_headers>External STO request.</help_headers> + <help_texts>FSO STO request. FSO module received an external STO request eitehr from IO or safebus.</help_texts> + <user_manual_desc>FSO STO request. FSO module received an external STO request eitehr from IO or safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_COMM</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO communication fault</event_name> + <short_description>FSO communication fault.</short_description> + <help_headers>Check the data cable.</help_headers> + <help_texts>FSO has detected a communication fault. All the communications goes through the data cable between FSO and Drive, check the connection.</help_texts> + <user_manual_desc>FSO has detected a communication fault. All the communications goes through the data cable between FSO and Drive, check the connection.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_SBUS</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safetybus fault</event_name> + <short_description>FSO safetybus fault.</short_description> + <help_headers>Something wrong with the safetybus.</help_headers> + <help_texts>FSO safetybus fault. Something wrong with the safetybus. See aux codes for more details.</help_texts> + <user_manual_desc>FSO safetybus fault. Something wrong with the safetybus. See aux codes for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_CONF</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO configuration fault</event_name> + <short_description>FSO configuration fault.</short_description> + <help_headers>Check the safety module parameter settings.</help_headers> + <help_texts>FSO configuration fault. Check the safety module parameter settings. Settings can be changed only with Composer pro tool.</help_texts> + <user_manual_desc>FSO configuration fault. Check the safety module parameter settings. Settings can be changed only with Composer pro tool.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_SafeEnc_Fault</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safety encoder fault</event_name> + <short_description>Safety encoder fault</short_description> + <help_headers>Safety encoder fault</help_headers> + <help_texts>Safety encoder fault, see aux codes for details</help_texts> + <user_manual_desc>Safety encoder fault, see aux codes for details</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_ENCLESS</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO encoderless fault</event_name> + <short_description>FSO encoderless speed estimation fault.</short_description> + <help_headers>Speed estimate is too high</help_headers> + <help_texts>FSO encoderless speed estimation fault. +• Check the behavior of the driven load compared with the drive control parameter settings. +• Check suitability of the drive train and the motor. +• Adapt control parameters if gear play or torsional rigidity causes problems.</help_texts> + <user_manual_desc>FSO encoderless speed estimation fault. +• Check the behavior of the driven load compared with the drive control parameter settings. +• Check suitability of the drive train and the motor. +• Adapt control parameters if gear play or torsional rigidity causes problems.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSO_WARNDF_TEMP</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO temperature fault</event_name> + <short_description>FSO over temperature</short_description> + <help_headers>FSO module temperature is excessive.</help_headers> + <help_texts>FSO over temperature. +• Check ambient conditions. Boot the FSO module (power switch off/on). +• Replace the FSO-11 module. Contact your local ABB representative.</help_texts> + <user_manual_desc>FSO over temperature. +• Check ambient conditions. Boot the FSO module (power switch off/on). +• Replace the FSO-11 module. Contact your local ABB representative.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_Undef</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO undefined warning</event_name> + <short_description>FSO undefined warning</short_description> + <help_headers>New FSO, undefined warning.</help_headers> + <help_texts>FSO new version, undefined warning in Drive event system.</help_texts> + <user_manual_desc>FSO new version, undefined warning in Drive event system.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_StopCompleted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO stop completed</event_name> + <short_description>FSO stop completed</short_description> + <help_headers>FSO stop completed.</help_headers> + <help_texts>FSO module has completed STO, SS1 or SSE function.</help_texts> + <user_manual_desc>FSO module has completed STO, SS1 or SSE function.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SafeSpeedLimit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safe speed limit</event_name> + <short_description>FSO safe speed limit</short_description> + <help_headers>FSO safe speed limit</help_headers> + <help_texts>Motor actual speed exceeded a safe speed limit of the FSO module.</help_texts> + <user_manual_desc>Motor actual speed exceeded a safe speed limit of the FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfEmeRamp</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO out of eme ramp</event_name> + <short_description>FSO out of eme ramp</short_description> + <help_headers>Motor speed was not inside the eme ramp.</help_headers> + <help_texts>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window during the SSE function. +Make sure that the drive can decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_RampCoasted</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO ramp coasted</event_name> + <short_description>FSO ramp coasted</short_description> + <help_headers>Drive coasted instead of ramping.</help_headers> + <help_texts>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (FSOGEN.51 Zero speed without encoder).</help_texts> + <user_manual_desc>Drive coasted the motor to stop instead of using the ramp. +Check that the FSO module speed limit for stopping the ramp deceleration is not excessive (FSOGEN.51 Zero speed without encoder).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSafeRamp</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO out of safe ramp</event_name> + <short_description>FSO out of safe ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSDI</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO out of SDI</event_name> + <short_description>FSO out of SDI.</short_description> + <help_headers>FSO out of SDI.</help_headers> + <help_texts>Motor was not rotating to the allowed direction.</help_texts> + <user_manual_desc>Motor was not rotating to the allowed direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_POUS_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO POUS request</event_name> + <short_description>FSO POUS request</short_description> + <help_headers>FSO POUS request and activation.</help_headers> + <help_texts>Prevention Of Unexpected Startup was requested via inputs or safebus, and it was activated.</help_texts> + <user_manual_desc>Prevention Of Unexpected Startup was requested via inputs or safebus, and it was activated.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_passivated</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO passivated</event_name> + <short_description>FSO passivated</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO module is passivated due safetybus problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_STO_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO STO request</event_name> + <short_description>FSO STO request</short_description> + <help_headers>FSO STO external request</help_headers> + <help_texts>FSO module received an external STO request from the inputs or the safebus.</help_texts> + <user_manual_desc>FSO module received an external STO request from the inputs or the safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SSE_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SSE request</event_name> + <short_description>FSO SSE request</short_description> + <help_headers>FSO SSE external request</help_headers> + <help_texts>FSO module received an external SSE request from the inputs or the safebus.</help_texts> + <user_manual_desc>FSO module received an external SSE request from the inputs or the safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SS1_Request</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SS1 request</event_name> + <short_description>FSO SS1 request</short_description> + <help_headers>FSO SS1 external request</help_headers> + <help_texts>FSO module received an external SS1 request from the inputs or the safebus.</help_texts> + <user_manual_desc>FSO module received an external SS1 request from the inputs or the safebus.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS1hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS1 hit</event_name> + <short_description>FSO SLS1 hit</short_description> + <help_headers>FSO SLS1 limit hit</help_headers> + <help_texts>FSO module detected a SLS1 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS1 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS2hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS2 hit</event_name> + <short_description>FSO SLS2 hit</short_description> + <help_headers>FSO SLS2 limit hit</help_headers> + <help_texts>FSO module detected a SLS2 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS2 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS3hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS3 hit</event_name> + <short_description>FSO SLS3 hit</short_description> + <help_headers>FSO SLS3 limit hit</help_headers> + <help_texts>FSO module detected a SLS3 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS3 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SLS4hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SLS4 hit</event_name> + <short_description>FSO SLS4 hit</short_description> + <help_headers>FSO SLS4 limit hit</help_headers> + <help_texts>FSO module detected a SLS4 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS4 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SMShit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SMS hit</event_name> + <short_description>FSO SMS hit</short_description> + <help_headers>FSO SMS limit hit</help_headers> + <help_texts>FSO module detected a SMS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SMS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SAR0hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SAR0 hit</event_name> + <short_description>FSO SAR0 hit</short_description> + <help_headers>FSO SAR0 limit violation.</help_headers> + <help_texts>FSO module detected a SAR0 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR0 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SAR1hit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SAR1 hit</event_name> + <short_description>FSO SAR1 hit</short_description> + <help_headers>FSO SAR1 limit violation.</help_headers> + <help_texts>FSO module detected a SAR1 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.112 SAR1 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR1 limit violation. +Make sure that the drive can decelerate the load using the ramp time (200.112 SAR1 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSDIp</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SDIp hit</event_name> + <short_description>FSO SDI-p hit</short_description> + <help_headers>FSO SDI-p hit</help_headers> + <help_texts>Motor was not rotating to the positive direction.</help_texts> + <user_manual_desc>Motor was not rotating to the positive direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_OutOfSDIn</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO SDIn hit</event_name> + <short_description>FSO SDI-n hit</short_description> + <help_headers>FSO SDI-n hit</help_headers> + <help_texts>Motor was not rotating to the negative direction.</help_texts> + <user_manual_desc>Motor was not rotating to the negative direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_RampTimeHit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO ramp time hit</event_name> + <short_description>FSO time monitored ramp hit</short_description> + <help_headers>FSO time monitored ramp hit</help_headers> + <help_texts>FSO module detected a violation of a time monitored ramp. +Make sure that the drive can decelerate the load within the time defined for ramp time monitoring.</help_texts> + <user_manual_desc>FSO module detected a violation of a time monitored ramp. +Make sure that the drive can decelerate the load within the time defined for ramp time monitoring. +• Check the drive ramp time settings. +• Check that the drive can in fact accomplish the deceleration along the ramp defined. +Make sure that the limit for ramp time monitoring of the FSO module exceeds the actual drive ramp time. The parameter vary depending on the safety function. For the SS1 function it is SS1.14 SS1 delay for STO.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_ZeroSpdHit</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_SEP_AUX_WRNG</flag> + </event_flags> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO zero spd hit</event_name> + <short_description>FSO zero speed rush</short_description> + <help_headers>Drive speed rushed during zero speed delay.</help_headers> + <help_texts>Drive speed rushed during zero speed delay.</help_texts> + <user_manual_desc>Drive speed rushed during zero speed delay.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_SpdSynFail</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO speed sync fail</event_name> + <short_description>FSO speed sync fail</short_description> + <help_headers>FSO detected a difference between the monitored motor speeds.</help_headers> + <help_texts>FSO module detected a difference between the two monitored motor speed values (200.01FSO speed ch1 and 200.02 FSO speed ch2). +Restart the drive and FSO module.</help_texts> + <user_manual_desc>FSO module detected a difference between the two monitored motor speed values (200.01 FSO speed ch1 and 200.02 FSO speed ch2). +Restart the drive and FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_varSLShit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO varSLS hit</event_name> + <short_description>FSO variable SLS hit</short_description> + <help_headers>FSO variable SLS limit hit.</help_headers> + <help_texts>FSO module detected a variable SLS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a variable SLS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSOW_passivation</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSO safebus passivation</event_name> + <short_description>FSO passivation</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO safe bus passivation due communication problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>PowerUp</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>Power up</event_name> + <short_description>Diagnostic information about the last boot cycle</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>The drive has been powered up.</rnd_desc> + <aux_codes> + <aux_code code="0x0000000"> + <names>Boot Type: Undefined</names> + <user_manual_desc>No information about boot type available</user_manual_desc> + </aux_code> + <aux_code code="0x00000001"> + <names>Boot Type: Cold boot</names> + <user_manual_desc>Drive was powered-on</user_manual_desc> + </aux_code> + <aux_code code="0x00000002"> + <names>Boot Type: Warm boot - OK</names> + <user_manual_desc>Drive was restarted expectedly</user_manual_desc> + </aux_code> + <aux_code code="0x00000003"> + <names>Boot Type: Warm boot - ERR</names> + <user_manual_desc>Drive had critical error and restart was needed. Information should be saved in SSW internal diagnostics</user_manual_desc> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_SSW_InternalDiagnostics</handle> + <module>TUCOS_GENERAL_Events</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>SSW internal diagnostics</event_name> + <short_description>Diagnostic event from the system SW.</short_description> + <help_headers>System SW diagnostics</help_headers> + <help_texts>System SW diagnostics has recorded an exceptional event during normal execution of the system SW. +The aux code of the event contains more information for ABB Drives.</help_texts> + <user_manual_desc>System SW diagnostics has recorded an exceptional event during normal execution of the system SW. +The aux code of the event contains more information for ABB Drives.</user_manual_desc> + <rnd_desc>System SW has noticed an exception in execution of the software. The aux code of the event contains more information.</rnd_desc> + <aux_codes> + <aux_code code="0x10000000"> + <names>Program counter value</names> + <user_manual_desc>Sub event nr 1. Report to ABB Drives. Value of the program counter. + Aux. code: 0x1xxxxxxx + xxxxxxx = value of the program counter</user_manual_desc> + </aux_code> + <aux_code code="0x20000000"> + <names>Stack pointer value</names> + <user_manual_desc>Sub event nr 2. Report to ABB Drives. Value of the stack pointer. + Aux. code: 0x2xxxxxxx + xxxxxxx = value of the stack pointer</user_manual_desc> + </aux_code> + <aux_code code="0x30000000"> + <names>Packed crash data</names> + <user_manual_desc>Sub event nr 3. Report to ABB Drives. Crash details: + Aux. code: 0x3000xyzz + x - interrupt nesting level + y - crash count + zz - exception number.</user_manual_desc> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_PowerUnitLogicUpdateEvent</handle> + <module>TUCOS_Power_Unit</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>Power unit's logic update transaction</event_name> + <short_description>An event generated during download of the logic configuration file to the PU. +Check the aux code for more information.</short_description> + <help_headers>Power unit's logic update event</help_headers> + <help_texts>An event generated during download of the logic configuration file to the PU. +Check the aux code for more information.</help_texts> + <user_manual_desc>An event generated during download of the logic configuration file to the PU. +Check the aux code for more information.</user_manual_desc> + <rnd_desc>An event generated during download of the logic configuration file to the PU. +Check the aux code for more information. +</rnd_desc> + <aux_codes> + <aux_code code="0x0000"> + <names>Download starts</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x1000"> + <names>Download successful</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0x2000"> + <names>Download failed</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSO_Events</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO general event</event_name> + <short_description>FSO general event</short_description> + <help_headers>FSO general event</help_headers> + <help_texts>FSO general event, see aux codes for details.</help_texts> + <user_manual_desc>FSO general event, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSO_DIAGS</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO diagnostics</event_name> + <short_description/> + <help_headers/> + <help_texts/> + <user_manual_desc/> + <rnd_desc>FSO boottime diags. Only for manufacturing tests, TUCSO (FSO subsystem) will forget these.</rnd_desc> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_Undef</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO undefined event</event_name> + <short_description>FSO undefined event</short_description> + <help_headers>FSO undefined event.</help_headers> + <help_texts>FSO new version, undefined event in Drive event system.</help_texts> + <user_manual_desc>FSO new version, undefined event in Drive event system.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_FSECh1Diag</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSE-31 ch1 diagnostics</event_name> + <short_description>FSE-31 ch1 diag</short_description> + <help_headers>FSE-31 ch1 diag</help_headers> + <help_texts>FSE-31 channel 1 diagnostics data, see aux codes for details.</help_texts> + <user_manual_desc>FSE-31 channel 1 diagnostics data, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_FSECh2Diag</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSE-31 ch2 diagnostics</event_name> + <short_description>FSE-31 ch2 diag</short_description> + <help_headers>FSE-31 ch2 diag</help_headers> + <help_texts>FSE-31 channel 2 diagnostics data, see aux codes for details.</help_texts> + <user_manual_desc>FSE-31 channel 2 diagnostics data, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_StopCompleted</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO stop completed</event_name> + <short_description>FSO stop completed</short_description> + <help_headers>FSO stop completed</help_headers> + <help_texts>FSO module has completed STO, SS1 or SSE function.</help_texts> + <user_manual_desc>FSO module has completed STO, SS1 or SSE function.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SafeSpeedLimit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO safe speed limit</event_name> + <short_description>FSO safe speed limit</short_description> + <help_headers>FSO safe speed limit</help_headers> + <help_texts>Motor actual speed exceeded a safe speed limit of the FSO module.</help_texts> + <user_manual_desc>FSO safe speed limit. Motor actual speed exceeded a safe speed limit of the FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfEmeRamp</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO out of eme ramp</event_name> + <short_description>FSO out of eme ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window during the SSE function. Make sure that the drive can decelerate the load using the ramp times. (200.102 SAR0 ramp time to zero)</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window during the SSE function. Make sure that the drive can decelerate the load using the ramp times. (200.102 SAR0 ramp time to zero)</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_RampCoasted</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO ramp coasted</event_name> + <short_description>FSO ramp coasted</short_description> + <help_headers>Drive coasted the motor to stop during the ramp.</help_headers> + <help_texts>Drive coasted the motor to stop instead of using the ramp. Check that the FSO module zero speed limit for the deceleration ramp is not excessive (FSOGEN.51 Zero speed without encoder).</help_texts> + <user_manual_desc>Drive coasted the motor to stop instead of using the ramp. Check that the FSO module zero speed limit for the deceleration ramp is not excessive (FSOGEN.51 Zero speed without encoder).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSafeRamp</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO out of safe ramp</event_name> + <short_description>FSO out of safe ramp</short_description> + <help_headers>Motor speed was not inside the ramp window.</help_headers> + <help_texts>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</help_texts> + <user_manual_desc>Motor speed was not inside the ramp window. Make sure that the drive can decelerate the load using the ramp times.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSDI</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO out of SDI</event_name> + <short_description>FSO out of SDI.</short_description> + <help_headers>FSO out of SDI.</help_headers> + <help_texts>Motor was not rotating to the allowed direction.</help_texts> + <user_manual_desc>Motor was not rotating to the allowed direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_passivated</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO passivated</event_name> + <short_description>FSO passivated</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO module is passivated due safetybus problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_STO_request</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO STO request</event_name> + <short_description>FSO STO request</short_description> + <help_headers>External STO request.</help_headers> + <help_texts>FSO module received an external STO request.</help_texts> + <user_manual_desc>FSO module received an external STO request.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SSE_Request</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SSE request</event_name> + <short_description>FSO SSE request</short_description> + <help_headers>External SSE request</help_headers> + <help_texts>FSO module received an external SSE request.</help_texts> + <user_manual_desc>FSO module received an external SSE request.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SS1_Request</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SS1 request</event_name> + <short_description>FSO SS1 request</short_description> + <help_headers>External SS1 request.</help_headers> + <help_texts>FSO module received an external SS1 request.</help_texts> + <user_manual_desc>FSO module received an external SS1 request.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS1hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS1 hit</event_name> + <short_description>FSO SLS1 hit</short_description> + <help_headers>FSO SLS1 hit</help_headers> + <help_texts>FSO module detected a SLS1 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS1 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS2hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS2 hit</event_name> + <short_description>FSO SLS2 hit</short_description> + <help_headers>FSO SLS2 hit</help_headers> + <help_texts>FSO module detected a SLS2 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS2 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS3hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS3 hit</event_name> + <short_description>FSO SLS3 hit</short_description> + <help_headers>FSO SLS3 hit</help_headers> + <help_texts>FSO module detected a SLS3 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS3 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SLS4hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SLS4 hit</event_name> + <short_description>FSO SLS4 hit</short_description> + <help_headers>FSO SLS4 hit</help_headers> + <help_texts>FSO module detected a SLS4 speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SLS4 speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SMShit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SMS hit</event_name> + <short_description>FSO SMS hit</short_description> + <help_headers>FSO SMS hit</help_headers> + <help_texts>FSO module detected a SMS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a SMS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SAR0hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SAR0 hit</event_name> + <short_description>FSO SAR0 hit</short_description> + <help_headers>FSO SAR0 limit violation.</help_headers> + <help_texts>FSO module detected a SAR0 limit violation.Make sure that the drive can +decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR0 limit violation.Make sure that the drive can +decelerate the load using the ramp time (200.102 SAR0 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SAR1hit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SAR1 hit</event_name> + <short_description>FSO SAR1 hit</short_description> + <help_headers>FSO SAR1 limit violation.</help_headers> + <help_texts>FSO module detected a SAR1 limit violation. Make sure that the drive can +decelerate the load using the ramp time (200.112 SAR1 ramp time to zero).</help_texts> + <user_manual_desc>FSO module detected a SAR1 limit violation. Make sure that the drive can +decelerate the load using the ramp time (200.112 SAR1 ramp time to zero).</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSDIp</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SDIp hit</event_name> + <short_description>FSO SDI-p hit</short_description> + <help_headers>FSO SDI-p hit</help_headers> + <help_texts>Motor was not rotating to the positive direction.</help_texts> + <user_manual_desc>Motor was not rotating to the positive direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_OutOfSDIn</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO SDIn hit</event_name> + <short_description>FSO SDI-n hit</short_description> + <help_headers>FSO SDI-n hit</help_headers> + <help_texts>Motor was not rotating to the negative direction.</help_texts> + <user_manual_desc>Motor was not rotating to the negative direction.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_RampTimeHit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO ramp time hit</event_name> + <short_description>FSO time monitored ramp hit</short_description> + <help_headers>FSO time monitored ramp hit</help_headers> + <help_texts>FSO module detected a violation of a time monitored ramp. Make sure that the drive can decelerate the load within the time defined for ramp time monitoring.</help_texts> + <user_manual_desc>FSO module detected a violation of a time monitored ramp. Make sure that the drive can decelerate the load within the time defined for ramp time monitoring. +• Check the drive ramp time settings. +• Check that the drive can in fact accomplish the deceleration along the ramp defined. +Make sure that the limit for ramp time monitoring of the FSO module exceeds the actual drive ramp time. The parameter vary depending on the safety function. For the SS1 function it is SS1.14 SS1 delay for STO.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_ZeroSpdHit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO zero spd hit</event_name> + <short_description>FSO zero speed rush.</short_description> + <help_headers>FSO zero speed rush.</help_headers> + <help_texts>Drive speed was rushing during zero speed delay.</help_texts> + <user_manual_desc>Drive speed was rushing during zero speed delay.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_SpdSynFail</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO speed sync fail</event_name> + <short_description>FSO speed sync fail</short_description> + <help_headers>Difference between the two monitored motor speeds.</help_headers> + <help_texts>FSO module detected a difference between the two monitored motor speed values (200.01 FSO speed ch1 and 200.01 FSO speed ch2). Restart the drive and FSO module.</help_texts> + <user_manual_desc>FSO module detected a difference between the two monitored motor speed values (200.01 FSO speed ch1 and 200.02 FSO speed ch2). Restart the drive and FSO module.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_varSLShit</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO varSLS hit</event_name> + <short_description>FSO variable SLS hit</short_description> + <help_headers>FSO variable SLS speed limit violation.</help_headers> + <help_texts>FSO module detected a variable SLS speed limit violation.</help_texts> + <user_manual_desc>FSO module detected a variable SLS speed limit violation.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSOE_passivation</handle> + <module>FS_FA</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSO safebus passivation</event_name> + <short_description>FSO passivation</short_description> + <help_headers/> + <help_texts/> + <user_manual_desc>FSO safe bus passivation due communication problems</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>LanguageToolNotice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc/> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_CommunicationBreak15s</handle> + <module>SSW</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Used to indicate that heartbeat will be lost for maximum time of 15 seconds and that tool/panel should not disconnect drive completely during that time.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ParsChangedToolNotice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Notice for the tool channels that the parameter system has changed.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_AccessLevelNotice</handle> + <module>PROPAR</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Given when any access level is selected and new menu visibilities are created.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_ToolNotice_FLT</handle> + <module>Channel_logs_notice</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Notice for tool channel: New items have been written to fault log. +Based on this notice the tool channel can refresh the active fault list and/or the fault log. +</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_FB1Notice_FLT</handle> + <module>Channel_logs_notice</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc>Notice for field bus 1 channel: New items have been written to fault log. +Based on this notice the FB1 channel can refresh the active fault list and/or the fault log.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_FB2Notice_FLT</handle> + <module>Channel_logs_notice</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc>Notice for field bus 2 channel: New items have been written to fault log. +Based on this notice the FB2 channel can refresh the active fault list and/or the fault log.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_ToolNotice_WRNG</handle> + <module>Channel_logs_notice</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Notice for tool channel: New items have been written to event log. +Based on this notice the tool channel can refresh the active warning list and/or the event log.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_FB1Notice_WRNG</handle> + <module>Channel_logs_notice</module> + <bit_handle/> + <event_type> + <notice receiver="FBus1"> + <rnd_desc>Notice for field bus 1 channel: New items have been written to event log. +Based on this notice the FB1 channel can refresh the active warning list and/or the event log.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_FB2Notice_WRNG</handle> + <module>Channel_logs_notice</module> + <bit_handle/> + <event_type> + <notice receiver="FBus2"> + <rnd_desc>Notice for field bus 2 channel: New items have been written to event log. +Based on this notice the FB2 channel can refresh the active warning list and/or the event log.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>DummyNotice</handle> + <module>TUREL_FA_STUB_Events</module> + <bit_handle/> + <event_type> + <notice receiver="Tool"> + <rnd_desc>Dummy notice for testing purposes.</rnd_desc> + </notice> + </event_type> + </event> + <event> + <handle>ehndl_FSx_undefined_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx undefined fault</event_name> + <short_description>FSx undefined fault</short_description> + <help_headers>FSx undefined fault</help_headers> + <help_texts>FSx new version, undefined fault in Drive event system. Contact ABB.</help_texts> + <user_manual_desc>FSx undefined fault is not yet defined inside the drive. Gather the AUX codes from this fault and contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_internal_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx internal fault</event_name> + <short_description>FSx internal fault; change FSx and send it back to factory</short_description> + <help_headers>FSx internal fault</help_headers> + <help_texts>Replace FSx and send the faulty one back to factory. There is no way to fix the FSx.</help_texts> + <user_manual_desc>FSx internal faults, like CPU or memory or peripherals: No possibility to fix.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="216"> + <names>WSB_STATE_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="214"> + <names>WSB_PSOUT_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="215"> + <names>WSB_STOP_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="212"> + <names>WSB_CHKIN_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="213"> + <names>WSB_SYNCO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="210"> + <names>WSB_CHKIN_TIMEOUT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="211"> + <names>WSB_CHKIN_INVERS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="133"> + <names>WOS_TRS_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="132"> + <names>WOS_TSP_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="131"> + <names>WOS_TSP_SEM</names> + <user_manual_desc/> + </aux_code> + <aux_code code="130"> + <names>WOS_TSP_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="137"> + <names>WOS_MQC_OS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="136"> + <names>WOS_CPUL_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="135"> + <names>WOS_CPUL_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="134"> + <names>WOS_TRS_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="139"> + <names>WOS_MQC_INV_TASK</names> + <user_manual_desc/> + </aux_code> + <aux_code code="138"> + <names>WOS_MQC_INV_BUF</names> + <user_manual_desc/> + </aux_code> + <aux_code code="93"> + <names>HAL_DEV_STOCB_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="24"> + <names>CTRL_MAIN_HIM_INV_MSG_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="25"> + <names>CTRL_WDG_HIM_MSG_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="26"> + <names>CTRL_WDG_HIM_INV_MSG_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="27"> + <names>CTRL_CLOCK_BTSRM_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="20"> + <names>CTRL_MAIN_RCT_INV_EVENT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="21"> + <names>CTRL_CLOCK_HIM_MSG_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="22"> + <names>CTRL_CLOCK_HIM_INV_MSG_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="23"> + <names>CTRL_MAIN_HIM_MSG_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="160"> + <names>WOS_EVPS_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="28"> + <names>CTRL_CLOCK_GWTI_INVALID_ARG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>BOOT_MAIN_SWITCH_DEFAULT_BRANCH</names> + <user_manual_desc/> + </aux_code> + <aux_code code="94"> + <names>HAL_HET_RESERVED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0"> + <names>E_FLT_FSx_INTERNAL_NO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>BOOT_MAIN_PM_INV_EVENT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="8"> + <names>COMM_NONSAFE_INV_ERR_CODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="96"> + <names>HAL_TEMPR_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="120"> + <names>WOS_TC_OS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="121"> + <names>WOS_TC_INV_FUNC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="122"> + <names>WOS_TC_INV_STACK</names> + <user_manual_desc/> + </aux_code> + <aux_code code="123"> + <names>WOS_TC_INV_STACKSZ</names> + <user_manual_desc/> + </aux_code> + <aux_code code="124"> + <names>WOS_TC_INV_OUTP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="125"> + <names>WOS_TC_PRI</names> + <user_manual_desc/> + </aux_code> + <aux_code code="126"> + <names>WOS_TC_TOO_MANY</names> + <user_manual_desc/> + </aux_code> + <aux_code code="127"> + <names>WOS_TC_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="128"> + <names>WOS_TID_INV_OUTP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="129"> + <names>WOS_TID_NA</names> + <user_manual_desc/> + </aux_code> + <aux_code code="69"> + <names>DIAG_CPU_L2L3</names> + <user_manual_desc/> + </aux_code> + <aux_code code="118"> + <names>WOS_NESTED_SCH</names> + <user_manual_desc/> + </aux_code> + <aux_code code="59"> + <names>DIAG_TEST_EWT_INV_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="58"> + <names>DIAG_TEST_SWT_INV_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="55"> + <names>DIAG_TEST_VOLTAGE_INV_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="54"> + <names>DIAG_TEST_WDG_INV_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="57"> + <names>DIAG_MAIN_RTS_INV_STK_SIZE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="56"> + <names>DIAG_TEST_VOLTAGE_INV_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="51"> + <names>DIAG_MAIN_RBT2_INV_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="50"> + <names>DIAG_MAIN_HTM_TMON_TIMEOUT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="53"> + <names>DIAG_TEST_WDG_INV_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="52"> + <names>DIAG_MAIN_RBT3_INV_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="64"> + <names>DIAG_CPU_FEE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="90"> + <names>HAL_DEV_WRI_INV_LN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="164"> + <names>WOS_CONV_MS_INV_OUTP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="201"> + <names>WSB_PSIN_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="199"> + <names>WSB_START_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="198"> + <names>WSB_CONF_RESP_FAIL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="147"> + <names>WOS_MQPO_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="195"> + <names>WSB_CONF_CRC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="194"> + <names>WSB_CONF_ADDR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="197"> + <names>WSB_CONF_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="178"> + <names>SAFETY_STO_INV_CONDITION</names> + <user_manual_desc/> + </aux_code> + <aux_code code="191"> + <names>WSB_INIT_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="203"> + <names>WSB_PSIN_LEN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="193"> + <names>WSB_CONF_SIL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="192"> + <names>WSB_CONF_WAIT_PARS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="115"> + <names>HAL_WDG_RESET_LOW_HWWDG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="177"> + <names>SAFETY_STO_INV_SW_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="117"> + <names>HAL_WDG_RESET_LOW_TRIG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="89"> + <names>HAL_DEV_RDI_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="111"> + <names>HAL_WDG_RESET_HIGH_HWWDG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="110"> + <names>HAL_WDG_RESET_HIGH_POWERGOOD</names> + <user_manual_desc/> + </aux_code> + <aux_code code="113"> + <names>HAL_WDG_RESET_HIGH_TRIG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="112"> + <names>HAL_WDG_RESET_HIGH_NERROR_PIN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="82"> + <names>HAL_INIT_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="181"> + <names>SAFETY_TRIG_STATE_LOW</names> + <user_manual_desc/> + </aux_code> + <aux_code code="80"> + <names>HAL_NULL_CB</names> + <user_manual_desc/> + </aux_code> + <aux_code code="81"> + <names>HAL_NULL_ARG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="119"> + <names>WOS_LOCKED_SCH</names> + <user_manual_desc/> + </aux_code> + <aux_code code="87"> + <names>HAL_DEV_STO_TEST_NA</names> + <user_manual_desc/> + </aux_code> + <aux_code code="84"> + <names>HAL_DEV_STO_DELAYED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="204"> + <names>WSB_PSIN_FULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="140"> + <names>WOS_MQC_INV_OUTP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="206"> + <names>WSB_PLIN_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="179"> + <names>SAFETY_STO_INV_LOCK</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7"> + <names>COMM_NULL_POINTER</names> + <user_manual_desc/> + </aux_code> + <aux_code code="108"> + <names>HAL_HET1_OVERFLOW</names> + <user_manual_desc/> + </aux_code> + <aux_code code="109"> + <names>HAL_HET1_NULL_IRQ</names> + <user_manual_desc/> + </aux_code> + <aux_code code="102"> + <names>HAL_WDTS_BUSY</names> + <user_manual_desc/> + </aux_code> + <aux_code code="103"> + <names>HAL_WDTP_START</names> + <user_manual_desc/> + </aux_code> + <aux_code code="100"> + <names>HAL_TIMER_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="101"> + <names>HAL_WDTS_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="106"> + <names>HAL_DEV_ROII_INV_ARG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="107"> + <names>HAL_TEMP_ADC_FAILURE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="104"> + <names>HAL_WDTR_STOP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="105"> + <names>HAL_DEV_ROII_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="39"> + <names>DIAG_MAIN_DTI_INV_STATUS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="38"> + <names>DIAG_MAIN_DTI_TEST_TIMEOUT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="167"> + <names>SAFETY_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="33"> + <names>CTRL_MAIN_HCM_CU_MSG_NOT_PACKED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="32"> + <names>CTRL_MAIN_USFS_INV_FUNC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="31"> + <names>CTRL_MAIN_USM_INV_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="30"> + <names>CTRL_WDG_STSRM_INVALID_MSG_TYPE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="37"> + <names>DIAG_MAIN_DTI_INV_TEST_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="36"> + <names>DIAG_MAIN_HIDM_INV_MSG_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="35"> + <names>DIAG_MAIN_RDT_INV_EVENT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="34"> + <names>DIAG_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="114"> + <names>HAL_WDG_RESET_LOW_POWERGOOD</names> + <user_manual_desc/> + </aux_code> + <aux_code code="86"> + <names>HAL_DEV_STO_DIAG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="29"> + <names>CTRL_WDG_STSRM_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="60"> + <names>DIAG_MAIN_HATM_TOO_BIG_DRIFT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="61"> + <names>DIAG_HW_WDG_BITE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="62"> + <names>DIAG_POWERGOOD_BITE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="63"> + <names>DIAG_MAIN_RTS_NO_SLOTS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="97"> + <names>HAL_TIMER_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65"> + <names>DIAG_CPU_SRAM</names> + <user_manual_desc/> + </aux_code> + <aux_code code="66"> + <names>DIAG_CPU_FLASH</names> + <user_manual_desc/> + </aux_code> + <aux_code code="67"> + <names>DIAG_CPU_CCM</names> + <user_manual_desc/> + </aux_code> + <aux_code code="68"> + <names>DIAG_CPU_PMM</names> + <user_manual_desc/> + </aux_code> + <aux_code code="176"> + <names>SAFETY_STO_INV_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="175"> + <names>SAFETY_HID_STO_TEST_TO</names> + <user_manual_desc/> + </aux_code> + <aux_code code="174"> + <names>SAFETY_INVALID_ARG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="173"> + <names>SAFETY_SA_INV_PARAM</names> + <user_manual_desc/> + </aux_code> + <aux_code code="172"> + <names>SAFETY_HDSFR_INV_PARAMS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="171"> + <names>SAFETY_HASFR_INV_SOURCE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="170"> + <names>SAFETY_HASFR_INV_FUNC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="182"> + <names>SCOMM_NULL_PTR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="183"> + <names>SCOMM_SHIM_UNKNOWN_MSG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="180"> + <names>SAFETY_RBST_INV_SW_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>BOOT_START_DIAG_FAILED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="186"> + <names>SCOMM_PI_LENGTH_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="187"> + <names>SCOMM_PASS_PARAMS_RECV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="184"> + <names>SCOMM_INV_EVENT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="6"> + <names>BOOT_MAIN_HCM_CU_MSG_NOT_PACKED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="188"> + <names>SCOMM_PASS_PROFILE_LEN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="189"> + <names>WSB_INIT_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="202"> + <names>WSB_PSIN_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="196"> + <names>WSB_CONF_LEN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="185"> + <names>SCOMM_PI_UNKNOWN_TYPE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="142"> + <names>WOS_MQPL_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="190"> + <names>WSB_INIT_PROF</names> + <user_manual_desc/> + </aux_code> + <aux_code code="99"> + <names>HAL_TIMER_TOO_LONG_DLY</names> + <user_manual_desc/> + </aux_code> + <aux_code code="98"> + <names>HAL_TIMER_BUSY</names> + <user_manual_desc/> + </aux_code> + <aux_code code="168"> + <names>SAFETY_INV_EVENT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="169"> + <names>SAFETY_SHIM_UNKNOWN_MSG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="91"> + <names>HAL_DEV_WRI_INV_ST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="165"> + <names>WOS_CONV_MS_OVF</names> + <user_manual_desc/> + </aux_code> + <aux_code code="166"> + <names>WOS_MEC_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="92"> + <names>HAL_DEV_STOCB_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="95"> + <names>HAL_HET_OFFSET</names> + <user_manual_desc/> + </aux_code> + <aux_code code="161"> + <names>WOS_EVPS_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="162"> + <names>WOS_AP2OP_INV_OUTP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="163"> + <names>WOS_AP2OP_INV_PRIO</names> + <user_manual_desc/> + </aux_code> + <aux_code code="11"> + <names>COMM_NONSAFE_INV_LEN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>COMM_NONSAFE_INV_TYPE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="13"> + <names>CTRL_TASK_REG_INVALID_PERIOD</names> + <user_manual_desc/> + </aux_code> + <aux_code code="12"> + <names>CTRL_TASK_REG_INVALID_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="15"> + <names>CTRL_TASK_REG_INVALID_INIT_VAL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="14"> + <names>CTRL_TASK_REG_INVALID_SHIFT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="17"> + <names>CTRL_WDG_RHI_INV_TASK</names> + <user_manual_desc/> + </aux_code> + <aux_code code="16"> + <names>CTRL_CLOCK_ICT_INVALID_TABLE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="19"> + <names>CTRL_CLOCK_RCT_INV_EVENT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="18"> + <names>CTRL_WDG_RSWT_INV_EVENT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="88"> + <names>HAL_DEV_STO_BOOT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="116"> + <names>HAL_WDG_RESET_LOW_NERROR_PIN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="151"> + <names>WOS_MQGC_INV</names> + <user_manual_desc/> + </aux_code> + <aux_code code="150"> + <names>WOS_MQPO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="153"> + <names>WOS_EVPE_INV_OUTP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="152"> + <names>WOS_MQGC_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="155"> + <names>WOS_EVPE_TIMEOUT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="154"> + <names>WOS_EVPE_ISR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="157"> + <names>WOS_EVPL_INV_OUTP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="156"> + <names>WOS_EVPE_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="159"> + <names>WOS_EVPL_NA</names> + <user_manual_desc/> + </aux_code> + <aux_code code="158"> + <names>WOS_EVPL_ISR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="83"> + <names>HAL_DEV_STO_INV_OP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65535"> + <names>ERR_UNKNOWN</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65536"> + <names>E_FLT_FSx_INTERNAL_LAST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="48"> + <names>DIAG_MAIN_GTEC_HW_COMPATIBILITY_TEST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="49"> + <names>DIAG_MAIN_GTEC_INV_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="46"> + <names>DIAG_MAIN_GTEC_VOLT_MON_TEST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="47"> + <names>DIAG_MAIN_GTEC_SW_COMPATIBILITY_TEST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="44"> + <names>DIAG_MAIN_GTEC_CPU_FLASH_TEST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="45"> + <names>DIAG_MAIN_GTEC_WATCHDOG_TEST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="42"> + <names>DIAG_MAIN_CS_CHECK_FAILED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="43"> + <names>DIAG_MAIN_GTEC_CPU_STARTUP</names> + <user_manual_desc/> + </aux_code> + <aux_code code="40"> + <names>DIAG_MAIN_HBT_INV_TEST_MODE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="41"> + <names>DIAG_MAIN_FS_FILL_FAILED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>COMMON_NULL_ADDRESS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>BOOT_MAIN_HIM_INV_MSG_ID</names> + <user_manual_desc/> + </aux_code> + <aux_code code="9"> + <names>COMM_NONSAFE_INV_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="85"> + <names>HAL_DEV_STO_SAFE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="146"> + <names>WOS_MQPL_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="200"> + <names>WSB_CNM_EXCHANGE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="144"> + <names>WOS_MQPL_ISR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="145"> + <names>WOS_MQPL_NA</names> + <user_manual_desc/> + </aux_code> + <aux_code code="205"> + <names>WSB_PSIN_IGNORE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="143"> + <names>WOS_MQPL_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="207"> + <names>WSB_CHKIN_NULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="141"> + <names>WOS_MQC_TOO_MANY</names> + <user_manual_desc/> + </aux_code> + <aux_code code="209"> + <names>WSB_CHKIN_CRC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="208"> + <names>WSB_CHKIN_PASS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="148"> + <names>WOS_MQPO_INV_MSG</names> + <user_manual_desc/> + </aux_code> + <aux_code code="149"> + <names>WOS_MQPO_FULL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="77"> + <names>DIAG_GOLDEN_REGISTER_SET_FAIL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="76"> + <names>DIAG_GOLDEN_CRC_SET_FAIL</names> + <user_manual_desc/> + </aux_code> + <aux_code code="75"> + <names>DIAG_REGISTERS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="74"> + <names>DIAG_CRCS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="73"> + <names>DIAG_ESM_OUTPUT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="72"> + <names>DIAG_CPU_MPU</names> + <user_manual_desc/> + </aux_code> + <aux_code code="71"> + <names>DIAG_CPU_DCC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="70"> + <names>DIAG_CPU_VIM</names> + <user_manual_desc/> + </aux_code> + <aux_code code="79"> + <names>HAL_UNKNOWN_INT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="78"> + <names>DIAG_ESM_FAILURE</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_STO_diagnostics_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx STO diagnostics fault</event_name> + <short_description>FSx STO fault; check STO cabling</short_description> + <help_headers>FSX STO fault</help_headers> + <help_texts>There is something wrong with STO cabling or inside the Drive.</help_texts> + <user_manual_desc>FSX STO fault; there is something wrong with STO cabling or inside the Drive.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="1"> + <names>SAFETY_STO_DEACT_FAILED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0"> + <names>E_FLT_FSx_STO_DIAGNOSTICS_NO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>SAFETY_STO_INV_STO_HI_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>SAFETY_STO_PULSE_FAILED</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>SAFETY_SLT_INV_LO_FB_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>SAFETY_STO_HI_GONE_LOW</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7"> + <names>HAL_INIT_STO_STATE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="6"> + <names>SAFETY_STO_INV_FEEDBACK</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65536"> + <names>E_FLT_FSx_STO_DIAGNOSTICS_LAST</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_temperature_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx temperature fault</event_name> + <short_description>FSx temperature</short_description> + <help_headers>FSx temperature</help_headers> + <help_texts>FSX temperature fault, mainly over temperature</help_texts> + <user_manual_desc>FSX temperature fault, mainly over temperature</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="1"> + <names>DIAG_MAIN_GTEC_TEMP_TEST</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0"> + <names>E_FLT_FSx_TEMPERATURE_NO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>DIAG_MAIN_HTM_TMON_S1_LIMIT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>DIAG_MAIN_HTM_TMON_DEVIATION</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>DIAG_MAIN_HTM_TMON_S2_LIMIT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65536"> + <names>E_FLT_FSx_TEMPERATURE_LAST</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_configuration_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="false"> + <event_name>FSx configuration fault</event_name> + <short_description>FSX configuration fault; check configuration</short_description> + <help_headers>FSX configuration fault</help_headers> + <help_texts>FSX configuration fault; check configuration</help_texts> + <user_manual_desc>FSX configuration is not valid</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0"> + <names>E_FLT_FSx_CONFIGURATION_NO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65536"> + <names>E_FLT_FSx_CONFIGURATION_LAST</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_communication_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx communication fault</event_name> + <short_description>FSX communication fault; FSX-CU communication fault</short_description> + <help_headers>FSX communication fault.</help_headers> + <help_texts>FSX communication fault; FSX-CU communication fault. Check all connections. See AUX code for more details.</help_texts> + <user_manual_desc>FSX communication fault; FSX-CU communication fault. Check all connections. See AUX code for more details.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="1"> + <names>WSB_HARD_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0"> + <names>E_FLT_FSx_COMMUNICATION_NO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65536"> + <names>E_FLT_FSx_COMMUNICATION_LAST</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_safety_ramp_fault</handle> + <module>FS_BASIC</module> + <event_flags> + <flag>EVNT_IMMEDIATE_FLT</flag> + </event_flags> + <bit_handle/> + <event_type> + <fault permanent="false" fast_presampling="true"> + <event_name>FSx safety ramp fault</event_name> + <short_description>Safety ramp did not finish in predictable way</short_description> + <help_headers>FS safety ramp fault</help_headers> + <help_texts>Safety ramp did not finish in predictable way</help_texts> + <user_manual_desc>FS safety ramp fault: Safety ramp did not finish in predictable way</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="1"> + <names>SS1T_TIMELIMIT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0"> + <names>E_FLT_FSx_SAFETY_RAMP_NO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65536"> + <names>E_FLT_FSx_SAFETY_RAMP_LAST</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </fault> + </event_type> + </event> + <event> + <handle>ehndl_FSx_undefined_warning</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSx undefined warning</event_name> + <short_description>FSx undefined warning</short_description> + <help_headers>New FSx, undefined warning.</help_headers> + <help_texts>FSx new version, undefined warning in Drive event system.</help_texts> + <user_manual_desc>FSx undefined warning is not yet defined inside the drive. Gather the aux codes from this warning and contact ABB.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSx_safety_bus_warning</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <warning> + <event_name>FSx safety bus warning</event_name> + <short_description></short_description> + <help_headers></help_headers> + <help_texts></help_texts> + <user_manual_desc></user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="11"> + <names>PSAFE_FPRAM_DEV_SPECIFIC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="10"> + <names>PSAFE_FPRAM_CRC1_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="13"> + <names>PSAFE_FPRAM_RESTORE_IPAR_WDG_TIME</names> + <user_manual_desc/> + </aux_code> + <aux_code code="12"> + <names>PSAFE_FPRAM_SAVE_IPAR_WDG_TIME</names> + <user_manual_desc/> + </aux_code> + <aux_code code="15"> + <names>PSAFE_FPRAM_GRANDE_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="14"> + <names>PSAFE_FPRAM_IPAR_CRC_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="17"> + <names>PSAFE_PASS_CRC_FAILURE</names> + <user_manual_desc/> + </aux_code> + <aux_code code="16"> + <names>PSAFE_PASS_NEW_FPARAMS</names> + <user_manual_desc/> + </aux_code> + <aux_code code="19"> + <names>PSAFE_PASS_BY_PLC</names> + <user_manual_desc/> + </aux_code> + <aux_code code="18"> + <names>PSAFE_PASS_WD_TIMEOUT</names> + <user_manual_desc/> + </aux_code> + <aux_code code="1"> + <names>PSAFE_FPRAM_DEST_ADDR_MISMATCH</names> + <user_manual_desc/> + </aux_code> + <aux_code code="0"> + <names>E_WRN_FSx_SAFETY_BUS_NO_ERR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="3"> + <names>PSAFE_FPRAM_SOURCE_ADDR_MISMATCH</names> + <user_manual_desc/> + </aux_code> + <aux_code code="2"> + <names>PSAFE_FPRAM_DEST_ADDR_VALIDITY</names> + <user_manual_desc/> + </aux_code> + <aux_code code="5"> + <names>PSAFE_FPRAM_WD_VALUE_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="4"> + <names>PSAFE_FPRAM_SOURCE_ADDR_VALIDITY</names> + <user_manual_desc/> + </aux_code> + <aux_code code="7"> + <names>PSAFE_FPRAM_FCRCLENGTH_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="6"> + <names>PSAFE_FPRAM_SIL_REQ_TOO_HIGH</names> + <user_manual_desc/> + </aux_code> + <aux_code code="9"> + <names>PSAFE_FPRAM_BLOCKID_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="8"> + <names>PSAFE_FPRAM_VERSION_ERROR</names> + <user_manual_desc/> + </aux_code> + <aux_code code="65536"> + <names>E_WRN_FSx_SAFETY_BUS_LAST</names> + <user_manual_desc/> + </aux_code> + </aux_codes> + <cause_list/> + </warning> + </event_type> + </event> + <event> + <handle>ehndl_FSx_undefined_event</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSx undefined event</event_name> + <short_description></short_description> + <help_headers>FSx undefined event.</help_headers> + <help_texts>FSx new version, undefined event in Drive event system.</help_texts> + <user_manual_desc>FSx new version, undefined event in Drive event system.</user_manual_desc> + <rnd_desc/> + <aux_codes/> + <cause_list/> + </pure_event> + </event_type> + </event> + <event> + <handle>ehndl_FSx_diagnostics</handle> + <module>FS_BASIC</module> + <bit_handle/> + <event_type> + <pure_event> + <event_name>FSx diagnostics</event_name> + <short_description>FSx diag</short_description> + <help_headers>FSx diag</help_headers> + <help_texts>FSx diagnostics data, see aux codes for details.</help_texts> + <user_manual_desc>FSx diagnostics data, see aux codes for details.</user_manual_desc> + <rnd_desc/> + <aux_codes> + <aux_code code="0x00000001"> + <names>CPU start up tests (combined)</names> + <user_manual_desc>CPU start up tests (combined)</user_manual_desc> + </aux_code> + <aux_code code="0x00000002"> + <names>SW image CRC test</names> + <user_manual_desc>SW image CRC test</user_manual_desc> + </aux_code> + <aux_code code="0x00000004"> + <names>Own temperature test </names> + <user_manual_desc>Own temperature test </user_manual_desc> + </aux_code> + <aux_code code="0x00000008"> + <names>External HW watchdog test</names> + <user_manual_desc>External HW watchdog test</user_manual_desc> + </aux_code> + <aux_code code="0x00000010"> + <names>3V3 and 1V2 voltage test</names> + <user_manual_desc>3V3 and 1V2 voltage test</user_manual_desc> + </aux_code> + <aux_code code="0x00000020"> + <names>HW compatibility test</names> + <user_manual_desc>HW compatibility test</user_manual_desc> + </aux_code> + <aux_code code="0x00000040"> + <names>STO output 1 test</names> + <user_manual_desc>STO output 1 test</user_manual_desc> + </aux_code> + <aux_code code="0x00000080"> + <names>STO output 2 test</names> + <user_manual_desc>STO output 2 test</user_manual_desc> + </aux_code> + <aux_code code="0x00000100"> + <names>CPU FEE</names> + <user_manual_desc>CPU FEE</user_manual_desc> + </aux_code> + <aux_code code="0x00000200"> + <names>CPU SRAM</names> + <user_manual_desc>CPU SRAM</user_manual_desc> + </aux_code> + <aux_code code="0x00000400"> + <names>CPU FLASH</names> + <user_manual_desc>CPU FLASH</user_manual_desc> + </aux_code> + <aux_code code="0x00000800"> + <names>CPU CCM</names> + <user_manual_desc>CPU CCM</user_manual_desc> + </aux_code> + <aux_code code="0x00001000"> + <names>CPU PMM</names> + <user_manual_desc>CPU PMM</user_manual_desc> + </aux_code> + <aux_code code="0x00002000"> + <names>CPU L2L3</names> + <user_manual_desc>CPU L2L3</user_manual_desc> + </aux_code> + <aux_code code="0x00004000"> + <names>CPU VIM</names> + <user_manual_desc>CPU VIM</user_manual_desc> + </aux_code> + <aux_code code="0x00008000"> + <names>CPU DCC</names> + <user_manual_desc>CPU DCC</user_manual_desc> + </aux_code> + <aux_code code="0x00010000"> + <names>CPU MPU</names> + <user_manual_desc>CPU MPU</user_manual_desc> + </aux_code> + <aux_code code="0x00020000"> + <names>ESM OUTPUT</names> + <user_manual_desc>ESM OUTPUT</user_manual_desc> + </aux_code> + <aux_code code="0x00040000"> + <names>CRCS</names> + <user_manual_desc>CRCS</user_manual_desc> + </aux_code> + <aux_code code="0x00080000"> + <names>REGISTERS</names> + <user_manual_desc>REGISTERS</user_manual_desc> + </aux_code> + </aux_codes> + <cause_list/> + </pure_event> + </event_type> + </event> + </events> +</module> diff --git a/xmldiff.py b/xmldiff.py new file mode 100644 index 0000000..9812515 --- /dev/null +++ b/xmldiff.py @@ -0,0 +1,25 @@ +#!/usr/bin/python + +import xml.etree.ElementTree + +ours = xml.etree.ElementTree.parse('ours.xml').getroot().find('events') +theirs = xml.etree.ElementTree.parse('theirs.xml').getroot().find('events') + +ours_set = set([x.find('handle').text for x in ours.findall('event')]) +theirs_set = set([x.find('handle').text for x in theirs.findall('event')]) + +only_ours = ours_set.difference(theirs_set) +only_theirs = theirs_set.difference(ours_set) + +ev_diff = ours_set.symmetric_difference(theirs_set) +ev_intersection = ours_set.intersection(theirs_set) + +print 'ours:' +print ' ' + str(len(ours)) + ' events in total' +print ' ' + str(len(only_ours)) + ' only here' + +print 'theirs:' +print ' ' + str(len(theirs)) + ' events in total' +print ' ' + str(len(only_theirs)) + ' only here' + +print 'in both: ' + str(len(ev_intersection)) |