Tabla de contenido
Idiomas disponibles
Idiomas disponibles
QUICK REFERENCE OF PARAMETERS, ALARMS AND FAULTS
Fault / Alarm
F082
Fault in Data Transfer (MMF)
F084
Auto-diagnosis Fault
A090
External Alarm
F091
External Fault
A128
Telegram Reception Timeout
A152
Electronic Board
Overtemperature
A211
Drive in Fire Mode
F228
Timeout in Receipt of
Telegrams
A700
Communication with HMI
Service
F701
Communication with HMI
Service Fault
A702
Inverter Disabled
A704
Two Movem. Enabled
A706
Refer. Not Progr. SoftPLC
A708
SoftPLC Application Stopped
F709
SoftPLC Application Stopped
F710
Size of the SoftPLC Application
F711
Fault on SoftPLC Application
14 | WECC300
Description
Fault in data transfer using MMF
accessory.
Fault
related
to
the
automatic
identification algorithm of the inverter
hardware.
External alarm via DIx (option "no
external alarm" in P263 to P266).
External fault via DIx ("no external fault"
in P263 to P266).
It indicates that the device stopped
receiving valid telegrams for a period
longer than the setting in P314.
The time counting starts as soon as it
receives the first valid telegram, with
correct address and error-checking
field.
Overtemperature alarm measured by
the sensor embedded on electronic
board.
Indicates that the drive is in Fire Mode.
It indicates that the device stopped
receiving valid telegrams for a period
longer than the setting in P314.
The time counting starts as soon as it
receives the first valid telegram, with
correct address and error-checking
field.
No communication with HMI Service,
but there is no frequency command or
reference for this source.
No communication with HMI Service;
however,
there
is
command
frequency reference for this source.
This failure occurs when there is a
SoftPLC movement block active and
the "General Enable" command is
disabled.
It occurs when 2 or more SoftPLC
movement blocks are enabled at the
same time.
This failure occurs when a SoftPLC
movement block is enabled and the
speed reference is not programmed for
the SoftPLC.
SoftPLC Application not running.
SoftPLC application not running.
The size of the SoftPLC user's
program exceeded the maximum
memory capacity.
Fault found in SoftPLC user's program.
Possible Causes
Attempt to download data from the flash memory module
to the inverter with the inverter energized.
Attempt to download a SoftPLC application incompatible
with the destination inverter.
Problems saving data downloaded to the inverter.
Poor contact in the connection between the main control
and the power pack.
Hardware not compatible with the firmware version.
Defect on the internal circuits of the inverter.
Wiring on DI1 to DI4 inputs are open or have poor contact.
Wiring on DI1 to DI4 inputs are open or have poor contact.
Check network installation, broken cable or fault/poor
contact on the connections with the network, grounding.
Ensure the master always sends telegrams to the
equipment in a time shorter than the setting in P314.
Disable this function in P314.
High temperature on electronic board, P034 > 80.0°C.
High ambient temperature around the inverter and high
output current.
The digital input programmed for activating the Fire Mode
is active.
Check network installation, broken cable or fault/poor
contact on the connections with the network, grounding.
Ensure the master always sends telegrams to the
equipment in a time shorter than the setting in P314.
Disable this function in P314.
Check that the connection cable has been made properly.
HMIS cable disconnected.
Check that connection cable has been made properly.
or
HMIS cable disconnected.
Check if the drive General Enable command is active.
Check the user's program logic.
Check the programming of the references in the Local
and/or Remote mode (P221 and P222).
SoftPLC Application is stopped (P901 = 0 and P900 = 3).
SoftPLC state presents application incompatible with the
firmware version of the frequency inverter.
SoftPLC application stopped (P901 = 0 and P900 = 3).
SoftPLC state presents incompatible application with the
firmware version of the frequency inverter.
The logic implemented on the SoftPLC is too large. Check
project size.
SoftPLC user's program stored on flash memory is
corrupted.
Timeout during execution of SoftPLC scan cycle.
Tabla de contenido
