Q1: What alarms does the UPS typically display when the fan malfunctions? A: When the fan malfunctions, the UPS will typically display "Fan Fail-Set" (as shown in Figure 1 below).

Figure 1
NOTE: The Figure shows ‘0# Bypass Fan Fail Set’ fault, where ‘0#’ is the bypass module and ‘X#’ is module X.
Q2: What are the common causes when the UPS displays a "Fan Fail-Set" alarm?
A: The main causes of ‘Fan Fail-Set’ alarm on the UPS are as follows:
1) Fan/fan power cable failure
2) Fan signal cable failure (white signal cable from the fan power board to the fan)
3) Short-circuit function failure of the fan power board (the short-circuit point may vary depending on the model)
4) Fan power board failure
5) Auxiliary power board failure
6) Monitoring signal cable failure (signal cable from the monitoring board to the fan power board)
7) Monitoring board failure
Q3: What are the usual troubleshooting steps when the UPS displays 'Fan Fail-Set' alarm?
A: The usual troubleshooting steps when the UPS displays ‘Fan Fail-Set’ alarm are as follows:
1) Use a jumper cap to short-circuit the power signal interface of the fan power board, and test interfaces 1—n+1 in sequence.
If there are no alarms, it is normal. If there are alarms, the source of the fault needs to be identified. The source of the fault can be determined by replacing the fan or by interface testing (as shown in Figure 2).

Figure 2
2) If the source of the fault cannot be determined in the first step, continue to check:
① Fan power supply board:
J1: Fan PWM signal and LED indicators signal, power supply (as shown in Figure 3 below)
Figure 3
② Check if the auxiliary power board is faulty: If the power board is supplying power normally, its LED light will light up (as shown in Figure 4 below).

Figure 4
3) If the source of the fault cannot be determined in the second step, further checks are required:
① Replace the monitoring board
② Replace the cable connecting the monitoring board to the fan power board.
Higher values for P4.60 and P4.61 cause longer deceleration time during shutdown. Increase the position loop gain of P2.02.
This is the EtherCAT monitoring interface. Setting P0.15 to 0 will resolve the issue.
This method cannot clear multi-turn positions. It can be used to clear accumulated absolute position feedback, accumulated commands R2.05 and R2.04. To clear multi-turn positions, use P0.71.
After enabling the multi-turn mode, the customer expects the R0.25 value to continue increasing beyond 32,767 revolutions, but in practice it does not increase continuously.
Solution:
R0.25 represents the actual encoder's multi-turn value. This 16-bit value is hard-coded and cannot be modified. However, with the multi-turn mode activated, the cumulative position feedback value stored in R2.05 persists even after power loss following a multi-turn overflow. This ensures the absolute position is preserved and not lost during power failure."
Excessive PDO count in the PLC has caused an overly high task load rate. Deleting unnecessary PDOs will resolve the issue.
When P11.01 is enabled and a transient power-off occurs, bit 9 is set to 1 when the bus voltage is lower than the following values: 460VDC for 380VAC models; 240VDC for 220VAC models.
What are the differences and triggering conditions between P11.01 (Frequency drop at transient power-off) and P11.16 (Automatic frequency-reduction during voltage drop) on GD28 drive?
Solution:
When P11.01 is enabled, in the event of a short-term bus voltage drop, the VFD will reduce its output frequency to brake the motor, in motor brake status, it will generate energy to maintain the bus voltage.
When P11.16 is enabled, when the bus voltage decreases, the VFD's output frequency will decrease synchronously. This applies to both VF and vector modes.
For the GD350A, versions 6.09/6.10 and 3.09/3.1 can be used directly with EtherCAT communication expansion cards without requiring the burning of dedicated communication software.

Our site uses cookies to provide you with a better onsite experience. By continuing to browse the site you are agreeing to our use of cookies in accordance with our Cookie Policy.