According to our experience over the years, if the F7802 jumps out, in all likelihood, it is the following places that are "off the chain:
1. DC bus status "wrong” (the most common)
This is the number one suspect. Performance is usually: a power, DC bus voltage climbed up particularly slow, or just up on the shivering, can not be stabilized. The system waits and waits, just can't wait for the stable "working voltage”.
The reason behind it is quite real:
* Incoming three-phase power itself is not very stable.
* rectifier / feeder module is old, poor condition.
* DC circuit capacitor aging, can not store electricity (a common problem of old equipment).
The machine looks to be energized, but the driver's heart is clear: I have this bottom of the virtual, not yet "ready”.
2. Power supply module of their own "temper tantrum”
In the system with an independent power supply module, this situation is not uncommon. The module may not be burned or blown, but the internal self-test did not pass, or a protection status (such as over-temperature) is not lifted, or inside a monitoring card "confused”. In short, it is there on its own "self-closed”, can not send a "Ready” signal, the brain to see, F7802 wait.
3. Startup time was "dragged to death”
This is particularly typical of old equipment, or put a long time without powering on the machine. Capacitor performance degradation, low ambient temperature, will make the DC bus voltage build-up slower. The result is that the voltage is actually creeping up, but the system's "window of time” has expired. If the system can't wait, it determines that you are "not ready for timeout” and alarms you directly.
4. DRIVE-CLiQ communication "flash”
This type of problem is the most "annoying”, because it is often not permanent damage. It may be that the cable is not plugged in tightly, that the plug is oxidized, or that there is occasionally poor contact inside the cable. The module itself is fine, but the communication path that reports "I'm OK” is intermittent, the system receives incomplete status messages, and the F7802 comes out.
5. Software and hardware "don't get along”
This usually happens after the hardware has been changed, e.g., modules have been replaced, drivers have been repaired, system has been changed. The hardware has changed, but the software configuration (topology, module address, parameters) forgot to synchronize the update. The system is still waiting for a "non-existent” or "incorrect” module to return the signal, naturally, never wait, the alarm becomes inevitable.
