06-15-2011 03:10 PM
This unit must be in parallel with another source to get a reverse power trip? Or the load has a very high inertia?
Reverse power is not necessarily an engine problem, so it does not need to shutdown the engine.
I agree with the others...try fuel quality, combustion air, it could be something besides the controls. Or maybe the other unit is going high, either Hz or V.
Does it drop the load first (low Hz?) before it gets the reverse power or does it reverse power and than drops the load?
The AVR output going high should cause an overexcitation or overvoltage alarm, not a reverse power.
If the AVR goes low, then it could result in a reverse power trip, but it should first trip on underexcitation or undervoltage.
Did this start suddenly or with some other event, like a PM service or something?
06-17-2011 02:00 AM
please check the following:
1. connection on the breaker relay or shunt trip.
2. reverse power relay maybe trigger once unit on load and open the breaker.
3. controller setting, check for accuracy or reverse power setting
06-24-2011 08:15 AM
Been on leave but the guys have fixed the problem while I was off, it appears that the battery voltage was dropping as the engine loaded up, this being the DSLC load control DC supply it affected the PWM output load signal??? Strange but it now appears to be working fine.
Thanks for all the advice.
06-27-2011 06:20 PM
If you have an emcp 2 control, I would monitor the k1 [electronic governor] relay or the k7 [fuel control relay]. the symptom you describe is consistent with the ignition power being interrupted to the engine ecm. sort of like turning the key switch in a vehicle off then back on.
06-28-2011 08:40 PM
Yes, that will do it, but you should have been getting a loss of throttle sensor fault in the ECM. IF the DSLC PWM output fails the ECM will drop the rpm to the programmed idle setting. But like I said, there should have been a fault code everytime it happened. Can't remember the fault code off the top of my head, but if you have an EMCP II it is likely a logged fault unless someone cleared it.