Post Go back to editing

Overcurrent indication on IRQ1 pin

Thread Summary

The user encountered a 22.2ms delay in overcurrent detection using the ADE9000, which is expected due to the RMS half-cycle updates. The solution was to read the IPEAK register at zero-crosses for faster detection, as the ADE9000 does not have an IRQ for peak current. This method successfully detected overcurrent events within a half cycle.
AI Generated Content
Category: Datasheet/Specs
Product Number: ADE9000

Hi! I was evaluating some of the ADE9000 specs and tried to implement a simple Overcurrent detection.

Setup was a three Phase 220Vrms/60Hz supply and 3 lamps as a load, consuming roughly 30mA on each phase.

Measurements for Current and voltage were perfect and sequence detection worked flawlessly but when I tried to use the Overcurrent indication I got confused with some of the timings between the event and the actual indication on pin IRQ1. This is what I got from a first attempt.

 

The cyan and magenta channels can be ignored, they are the voltage sinewaves for A and B phases. Green one though is a current measurement taken from a load passing through the CT on phase C. It starts off and when I press a switch it turns on on a scale that its suppoused to trigger the overcurrent interrupt.

Interrupt does trigger (obscured by the green cursor marker but its a falling edge on the yellow channel) but what got me confused was the 22,20mS time for it to be noticed by the ADE9000.

Datasheet says this indication takes into account the RMS½ measurements and also reference manual UG-1098 says these measurements  are "[...] done over one line cycle, updated every half cycle."

Am I right to think that for a 60Hz signal this indication can only happen at about 25mS(16,67ms of one cycle + 8,33mS of a half cycle)?

I ask because I  was hoping to detect this on half a cycle. If remember right another meter from AD (ADE7953) used peak measurements for this and it was able to detect these surges and overcurrents super fast. Not sure if ADE9000 has the same feature.

  • I think you are correct as for the timing worse case. I think it will depend on when the transition happens and where the half-cycle rms updates. teh one cycle RMS is teh average of 2 half cycles. 3 cycles the average is now high enough to trigger the over current event. 

    The IPEAK register may be what you need. Sync the reading of Ipeak to zero-crosses. 

    There is no IRQ associated to this so you would need to read every zerocross to see if the peakval is over your threshold. 

    RMS to IPCF value = IRMS / RMS conversion constant * 1.414.  

    Ipeak = IPCF/2^5

    Calculate IPeak with your overcurrent value using above.

    You would read IPEAK at the zero-crosses this will indicate the highest Ipeak and which phase had this peak over the half cycle. 

    If Ipeak is above this value when you read. This is an over current event over a half cycle. 

    Dave

  • Thank you, Dave!

    It worked!

    I'm reading the IPEAK register at every zero cross on each phase now, this indeed allows for a super fast surge detection.

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.