WEG CFW300 V3.0X Referencia Rápida página 26

QUICK REFERENCE OF PARAMETERS, ALARMS AND FAULTS
Fault / Alarm
A140
Profibus DP Module Access
Error
A147
EtherNet/IP Communication
Offline
A149
Timeout Modbus TCP
A163
Signal Fault AI1 4...20 mA
A164
Signal Fault AI2 4...20 mA
A177
Replace Fan
F182
Pulse Feedback Failure
A211
Drive in Fire Mode
F228
Timeout in Receipt of
Telegrams
F233
No Power Supply on the CAN
Interface
F234
Bus Off
F235
Node Guarding/ Heartbeat
F236
Idle Master
F237
DeviceNet Connection Timeout
26 | CFW300
Description
It indicates error in the access to the
Profibus DP communication module
data.
It indicates interruption in the cyclic
communication with EtherNet/IP
master.
It occurs when, for any reason, after
the cyclic communication of the
master with the product is started, this
communication is interrupted.
It indicates that the device stopped
receiving valid telegrams for a period
longer than the setting in P868.
The time counting starts as soon as it
receives the first valid telegram.
Analog input signal AI1 at 4 to 20 mA
or 20 to 4 mA is below 2 mA.
.Analog input signal AI2 at 4 to 20 mA
or 20 to 4 mA is below 2 mA.
Alarm to replace the fan (P045 >50000
hours).
Pulse feedback circuit fault of the
output voltage.
Note: it may be turned off in P397.
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.
It indicates that the CAN interface has
no power supply between pins V(-) and
V(+) of the connector.
Bus off error detected on the CAN
interface.
CANopen communication error control
detected communication error using
the guarding mechanism.
Fault indicates that the DeviceNet
network master is in Idle mode.
Fault that indicates that one or more
DeviceNet connections timed out.
Possible Causes
Check if the Profibus DP module is correctly fitted.
Hardware errors due to improper handling or installation of
the accessory, for instance, may cause this error. If possible,
carry out tests by replacing the communication accessory.
Check the status of the network master.
Check the network installation, broken cable or failed/bad
contact in the network connections.
Check network installation, broken cable or fault/poor
contact on the connections with the network, grounding.
Ensure the Modbus TCP client always sends telegrams to
the equipment in a time shorter than the setting in P868.
Disable this function in P868.
Current signal on the analog input AI1 interrupted or null.
Parameterization error on analog input AI1.
Current signal on the analog input AI2 interrupted or null.
Parameterization error on analog input AI2.
Maximum number of operation hours of the heatsink fan
exceeded.
Hardware identification fault; compare P295 and P296 to the
inverter identification label.
Inverter internal pulse feedback circuit fault.
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.
Measure if there is voltage within the allowed range between
pins V(-) and V(+) of the CAN interface connector.
Check if the power 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 specification
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 for
message exchange. 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 problems in the communication 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.