Forum falowników

 www.falowniki.info

Code Alarm (fieldbus code) Cause What to do
2000 BRAKE START TOROUE (0xFF74) Programmable fault: 35.09 BRAKE FAULT FUNC Mechanlcal brake alarm. Alarm is activated if required motor startlng torque, 35.06 BRAKE OPEN TORO, is not achieved. Check brake open torque setting, parameter 35.06. Check drive torque and current limits. See firmware błock LIMITS on page 82.
2001 BRAKE NOT CLOSED (0xFF75) Programmable fault: 35.09 BRAKE FAULT FUNC Mechanlcal brake control alarm. Alarm is activated eg. if brake acknowledgement is not as expected during brake closing. Check mechanical brake connection. Check mechanical brake settings, parameters 35.01...35.09. To determine whether problem is with acknowledgement signal or brake: Check if brake is closed or open.
2002 BRAKE NOTOPEN (0xFF76) Programmable fault: 35.09 BRAKE FAULT FUNC Mechanlcal brake control alarm. Alarm is activated eg. if brake acknowledgement is not as expected during brake opening. Check mechanical brake connection. Check mechanical brake settings. parameters 35.01...35.08. To determine whether problem is with acknowledgement signal or brake: Check if brake is closed or open.
2003 SAFE TOROUE OFF (0xFF7A) Programmable fault: 46.07 STO DIAGNOSTIC Safe Torque Off function is active, i.e. safety circuit signal(s) connected to connector X6 is lost while drive is stopped and parameter46.07 STO DIAGNOSTIC setting is ALARM. Check safety circuit connectjons. For more Information, see appropriate dhve hardware manuał.
2004 STO MODE CHANGE (0xFF7D) Error in changing Safe Torque Off supen/ision, i.e. parameter 46.07 STO DIAGNOSTIC setting could not be changed to value ALARM. Contact your local ABB representative.
2005 MOTOR TEMPERATURĘ (0x4380) Programmable fault: 45.01 MOT TEMP PROT Estimated motor temperaturę (based on motorthermal model) has exceeded alarm limit defined by parameter 45.03 MOT TEMP ALM LIM. Check motor ratings and load. Let motor cool down. Ensure proper motor cooling: Check cooling fan, clean cooling surfaces. etc. Check value of alarm limit. Check motor thermal model settings, parameters 45.06...45.08 and 45.10 MOT THERM TIME.
    Measured motor temperaturę has exceeded alarm limit defined by parameter 45.03 MOT TEMP ALM LIM. Check that actual number of sensors corresponds to value set by parameter 45.02 MOT TEMP SOURCE. Check motor ratings and load. Let motor cool down. Ensure proper motor cooling: Check cooling fan, clean cooling surfaces, etc. Check value of alarm limit.
2006 EMERGENCY OFF (0xFF90) Drive has received emergency OFF2 command. To restart dhve, activate RUN ENABLE signal (source selected by parameter 10.09 RUN ENABLE) and start drive.
2007 RUN ENABLE (0xFF91) No Run enable signal is received. Check setting of parameter 10.09 RUN ENABLE Switch signal on or check wihng of selected source.
2008 ID-RUN (0xFF84) Motor Identification run is on. This alami belongs to normal start-up procedurę. Wart until drive indicates that motor identification is completed.
    Motor Identification is required. This alarm belongs to normal start-up procedurę. Select how motor identification should be periormed, parameter 99.13 ID RUN MODE. Start identification routines by pressing Start key.
2009 EMERGENCY STOP (0xFF92) Drive has received emergency stop command {OFF1/OFF3). Check that it is safe to continue operation. Return emergency stop push button to normal positjon. Restart drive.
2011 BR OVERHEAT (0x7112) Brake resistor temperaturę has exceeded alarm limit defined by parameter 48.07 BR TEMP ALARM LIM. Stop drive. Let resistor cool down. Check resistor overload protection function settings, parameters 48.03.. .48.05. Check alarm limit setting, parameter 48.07. Check that braking cycle meets allowed limits.
2012 BC OVERHEAT (0x7181) Brake chopper IGBT temperaturę has exceeded internal alarm limit. Let chopper cool down. Check resistor overload protection function settings, parameters 48.03.. .48.05. Check that braking cycle meets allowed limits. Check that drive supply AC voltage is not excessive.
2013 DEVICE OVERTEMP (0x4210) Measured drive temperaturę has exceeded internal alarm limit. Check ambient conditions. Check airflow and fan operation. Check heatsink fins for dust pick-up. Check motor power against unit power.
2014 INTBOARD OVERTEMP (0x7182) interiace board (between power unit and control unit) temperaturę has exceeded internal alarm limit. Letdrive cool down.
2015 BC MODOVERTEMP (0x7183) input bhdge or brake chopper temperaturę has exceeded internal alarm limit. Let drive cool down.
2016 IGBT OVERTEMP (0x7184) Drive temperaturę based on thermal model has exceeded internal alarm limit. Check ambient conditions. Check airfiow and fan operation. Check heatsink fins for dust pick-up. Check motor power against unit power
2017 FIELDBUS COMM (0x7510) Programmable fault: 50.02 COMM LOSS FUNC Cyclical communication between drive and fieldbus adapter module or between PLC and fieldbus adapter module is lost. Ch^ck status of fieldbus communication. See approphate User s Manuał of fieldbus adapter module. Check fieldbus parameter settings. See firmware błock FIELDBUS on page 141. Check cable connections. Check if communication master can communicate.
2018 LOCAL CTRL LOSS (0x5300) Programmable fault: 46.03 LOCAL CTRL LOSS 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.
2019 Al SUPERVISION (0x8110) Programmable fault: 13.12 Al SUPRVISION AnalogueinputAM orAI2slgnal has reached limit defined by parameterl3.13AI SUPERVIS ACT Check analogue input AU/2 source and connections. Check analogue input AU/2 minimum and maximum limit settings. parameters 13.02 and 13.03/13.07 and 13.08.
2022 ENCODER 1 FAILURE (0x7301) Encoder 1 has been activated by parameter but the encoder interface (FEN-xx) cannot be found. Check parameter 90.01 ENCODER 1 SEL setting corresponds to encoder interface 1 (FEN-xx) installed in drive Slot 1/2 {signal 9.20 OPTION SLOT 1 / 9.21 OPTION SLOT 2). Note: The new setting will only take effect after parameter 90.10 ENC PAR REFRESH is used or after the JCU control unit is powered up the next time.
2023 ENCODER 2 FAILURE (0x7381) Encoder 2 has been activated by parameler but the encoder interface (FEN-xx) cannot be found. Check parameter 90.02 ENCODER 2 SEL setting corresponds to encoder interface 2 (FEN-xx) installed In drive Slot 1/2 (slgnal 9.20 OPTION SLOT 1 / 9.21 OPTION SLOT 2). Note: The new setting will only take effect after parameter 90.10 ENC PAR REFRESH is used or after the JCU control unit is powered upthenext time.
EnDat or SSI encoder is used In continuous mode as encoder 2. [I.e. 90.02 ENCODER 2 SEL = FEN-11 ABS and 91 02 ABS ENC INTERF = EnDat (or 91.02 ABS ENC INTERF = SSI) and 91.30 ENDAT MODE = CONTINUOUS {or 91.25 SSI MODE = CONTINUOUS).] If possible, use single position transfer instead of continuous position transfer (i.e. if encoder has incremental sin/cos signals): - Change parameter 91.25 SSI MODE / 91.30 ENDAT MODE to value INITIAL POS. Otherwise use EndatfSSI encoder as encoder1: -Change parameter 90.01 ENCODER 1 SEL to value FEN-11 ABS and parameter 90.02 ENCODER 2 SEL to value NONE Note: The new setting will only take effect after parameter 90.10 ENC PAR REFRESH is used or after the JCU control unit is powered upthe nexttime.
2026 ENC EMULATION FAILURE (0x7384) Encoder emulation error If position value used in emulation is measured by encoder: - Check that FEN-xx encoder used in emulation (90.03 EMUL MODE SEL) corresponds to FEN-xx encoder interface 1 or (and) 2 activated by parameter 90.01/90.02 ENCODER 1/2. (Parameter 90.01/90.02 activates the position calculation of the used FEN-xx input). if position value used in emulation is determined by drive software: - Check that FEN-xx encoder used in emulation (90.03 EMUL MODE SEL) corresponds to FEN-xx encoder interface 1 or (and) 2 activated by parameter 90.01/90.02 ENCODER 1/2 (because position data used in emulation is written to FEN-xx during encoder data request). Encoder interface 2 is recommended. Note: The new setting will only take effect after parameter 90.10 ENC PAR REFRESH is used or after the JCU control unit is powered upthenext time.
2027 FEN TEMP MEAS FA1LURE (0x7385) Error in temperaturę measurement when temperaturę sensor (KTY or PTC) connected to encoder interface FEN-xx is used. Check mat parameter 45.02 MOT TEMP SOURCE settings correspond to encoder interface installation (9.20 OPTION SLOT 1 / 9.21 OPTION SLOT 2): If one FEN-xx module is used: - Parameter 45.02 MOT TEMP SOURCE setting must be either KTY ist FEN or PTC ist FEN. FEN-xx module can be in either Slot 1 or Slot 2. If two FEN-xx modules are used: - When parameter 45.02 MOT TEMP SOURCE setting is KTY 1st FEN or PTC 1st FEN, me encoder installed in dhve Slot 1 is used. - When parameter 45.02 MOT TEMP SOURCE setting is KTY 2nd FEN or PTC 2nd FEN, me encoder installed in drive Slot 2 is used.
    Error in temperaturę measurement when KTY sensor connected to encoder interface FEN-01 is used. FEN-01 does not support temperaturę measurement with KTY sensor. Use PTC sensor or other encoder interface module.
2028 ENC EMUL MAX FREQ (0x7386) TTL pulse frequency used in encoder emulation .exceeds maximum aliowed limit (500 kHz). Decrease parameter 93.21 EMUL PULSE NR value. Note: The new setting will only take effect after parameter 90.10 ENC PAR REFRESH is used or after the JCU control unit is powered up the next time.
2029 ENC EMUL REF ERROR (0x7387) Encoder emulation has failed due to failure in wńting new fposition) reference for emulation. Contact your local ABB representative.
2030 RESOLVER AUTOTUNE ERR (0x7388) Resolver autotuning routines, which are automatically started when resolver input is activated for the first time, have failed. Check cable between resolver and resolver interface module (FEN-21) and order of connector signal wires at both ends of cable. Check resolver parameter settings. For resolver parameters and Information, see firmware błock RESOLVER CONF on page 172. Note: Resolver autotuning routines should always be performed after resolver cable connection has been modified. Autotuning routines can be activated by setting parameter 92.02 EXC SIGNAL AMPL or 92.03 EXC SIGNAL FREQ. and then setting parameter 90.10 ENC PAR REFRESH to 1.
2031 ENCODER 1 CABLE (0x7389) Encoder 1 cabie fault detected. Check cable between FEN-xx interface and encoder 1. After any modifications in cabling, re-configure interface by swltchlng drive power off and on, or by activating parameter 90.10 ENC PAR REFRESH.
2032 ENCODER 2 CABLE (0x73SA) Encoder 2 cable fault detected. Check cable between FEN-xx interface and encoder 2. After any modifications in cabling, re-configure interface by switchlng drive power off and on, or by activating parameter 90.10 ENC PAR REFRESH.
2033 D2D COMMUNICATION (0x7511) Programmable fault: 57.02 COMM LOSS FUNC Drive-to-drive communication break detected. Check the drive-to-drive cabling.


WebSystem  tel. 048 383.01.44   | wortal-> www.falowniki.pl | forum-> www.falowniki.info | porównaj-> www.falowniki.com.pl

Warto zobaczyć

Giełda falowników

Falownik Lenze 9300 Vector 110kW

Falownik Lenze 9300 Vector 110kW EVF9335-EVV030

Więcej…

Softstart eTran 7,5kW SET200-7.5

Softstart eTran 7,5kW SET200-7.5

Więcej…

Softstart eTran 11kW SET500-11

Softstart eTran 11kW SET500-11 

Więcej…

Siemens Simovert 45kVA 6SE-1245-2AA00

Siemens Simovert 45kVA 6SE-1245-2AA00

Więcej…

Siemens Simovert 22kVA 6SE-1222-2AA02

Siemens Simovert 22kVA 6SE-1222-2AA02

Więcej…

Siemens Simovert 22kVA 6SE-1222-2AA03

Siemens Simovert 22kVA 6SE-1222-2AA03

Więcej…
dobór falowniki Wortal napędów energoelektronicznych www.falowniki.pi . Napędy energoelektroniczne do regulacji prędkości obrotowej silników elektrycznych.

Copyright © 2010 www.falowniki.pl