WEG CFW500 Serie Manual Del Usuario página 22

Quick Parameter Reference, Faults and Alarms
Fault / Alarm
A0046
Motor overload alarm.
Motor Overload
A0047 Overload alarm on the power pack with
IGBT Overload IGBTs.
A0050 Overtemperature alarm from the power
Power Module module temperature sensor (NTC).
Overtemperature
A0090 External alarm via DIx (option "No
External Alarm External Alarm" in P026x).
A0128 Alarm that indicates serial
Telegram communication fault. It indicates the
Reception equipment stopped receiving valid serial
Timeout telegrams for a period longer than the
setting in P0314.
A0133 It indicates that the CAN interface has
No Supply on no supply between pins 1 and 5 of the
CAN Interface connector.
A0134 Bus off error detected on the CAN
Bus Off interface.
A0135 CANopen communication error control
Node Guarding/ detected communication error using the
Heartbeat guarding mechanism.
A0136 Alarm indicates that the DeviceNet
Idle Master network master is in Idle mode.
A0137 Alarm that indicates that one or more
DeviceNet DeviceNet connections timed out.
Connection
Timeout
A0138
It indicates that the inverter received the
Profibus DP command from the Profibus DP network
Interface in Clear master to go into clear mode.
Mode
22 | CFW500
Description Possible Causes
„
Settings of P0156, P0157, and P0158 are too low
for the used motor.
„
Overload on the motor shaft.
„
Inverter output overcurrent.
„
High ambient temperature around the inverter (>50
°C (> 122 °F)) and high output current.
„
Blocked or defective fan.
„
Heatsink is too dirty, preventing the air flow.
„
Wiring on DI1 to DI8 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 P0314.
„
Disable this function in P0314.
„
Measure if there is voltage within the allowed range
between the pins 1 and 5 of the CAN interface
connector.
„
Check if the supply cables are not misconnected
or inverted.
„
Check for contact problems on the cable or
connector of the CAN interface.
„
Check for short-circuit on the CAN circuit transmission
cable.
„
Check if the cables are not misconnected or inverted.
„
Check if all the network devices use the same baud
rate.
„
Check if the termination resistors with the right value
were installed only at the end of the main bus.
„
Check if the CAN network was properly installed.
„
Check the times set on the master and on the slave
to exchange messages. In order to prevent problems
due to transmission delays and time counting, it is
recommended that the values set for error detection
by the slave be multiples of the times set for message
exchange on the master.
„
Check if the master is sending the guarding
telegrams in the time set.
„
Check the problems in the communications that may
cause missing telegrams or transmission delays.
„
Set the switch that controls the master operation for
Run or the corresponding bit on the configuration
word of the master software. If further information
is needed, refer to the documentation of the master
used.
„
Check the network master status.
„
Check network installation, broken cable or fault/
poor contact on the connections with the network.
„
Check the network master status, ensuring it is in
the run mode.