Metering & Power Quality
Schneider Electric support forum about Power Meters (ION, PowerTag, PowerLogic) and Power Quality from design, implementation to troubleshooting and more.
Link copied. Please paste this link to share this article on your social media post.
Hi,
Please find the attached Sag/Swell Log from ION7650 meter. My question is why only the Upstream Disturbance Waveform has been recorded, the downstream disturbance just a event log? Is the meter set to only log High Confidence Events? Is that a way to configure it records all downstream waveform as well?
Thanks,
James
Link copied. Please paste this link to share this article on your social media post.
Hi James,
There should be no correlation between the Disturbance Direction Detection result (upstream/downstream) or confidence (high/medium/low) and the logging of a waveform file. Looking at the attached screen capture, I see six different times when there were voltage waveform captures. Each of those times corresponds to an event (with the same timestamp) indicating that a Sag/Swell disturbance either started or ended. In each case, there is a second event when the disturbance starts (with the same timestamp), indicating the result of the Disturbance Direction analysis. It looks like the software happens to show the waveform records aligned on the same row with the Disturbance Direction event, but they are more accurately triggered by the Sag/Swell event (shown in the next row but with the same timestamp). I think it is just a coincidence that each of these three sag/swell events was detected as being Upstream with High confidence.
Waveform captures are triggered within the ION framework, and there is a set of waveform recorders in the default framework associated with sag/swell events. These recorders are triggered whenever the Sag/Swell module detects the start or end of a disturbance. That is why the waveforms are aligned with a sag/swell start or end event here. Those same triggers are used in the ION framework to initiate the Disturbance Direction analysis. The default ION framework meets the needs of many customers (and with this explanation maybe it is okay for you too?). But if you are interested in further customization to how waveform records are triggered, ION is certainly very configurable, and I'm sure we can help you understand your options.
I do not fully understand why there are many Disturbance Direction events that do not seem to be aligned with any Sag/Swell event. To understand this, we would need to dig a little deeper into your system. Maybe those ones are caused by Transient events, but the Transient events are filtered out of this view in software (if it's intended to be a Sag/Swell log)?
Best regards,
David
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Just moving to the Power Monitoring Hardware Community.
Link copied. Please paste this link to share this article on your social media post.
Hi James,
There should be no correlation between the Disturbance Direction Detection result (upstream/downstream) or confidence (high/medium/low) and the logging of a waveform file. Looking at the attached screen capture, I see six different times when there were voltage waveform captures. Each of those times corresponds to an event (with the same timestamp) indicating that a Sag/Swell disturbance either started or ended. In each case, there is a second event when the disturbance starts (with the same timestamp), indicating the result of the Disturbance Direction analysis. It looks like the software happens to show the waveform records aligned on the same row with the Disturbance Direction event, but they are more accurately triggered by the Sag/Swell event (shown in the next row but with the same timestamp). I think it is just a coincidence that each of these three sag/swell events was detected as being Upstream with High confidence.
Waveform captures are triggered within the ION framework, and there is a set of waveform recorders in the default framework associated with sag/swell events. These recorders are triggered whenever the Sag/Swell module detects the start or end of a disturbance. That is why the waveforms are aligned with a sag/swell start or end event here. Those same triggers are used in the ION framework to initiate the Disturbance Direction analysis. The default ION framework meets the needs of many customers (and with this explanation maybe it is okay for you too?). But if you are interested in further customization to how waveform records are triggered, ION is certainly very configurable, and I'm sure we can help you understand your options.
I do not fully understand why there are many Disturbance Direction events that do not seem to be aligned with any Sag/Swell event. To understand this, we would need to dig a little deeper into your system. Maybe those ones are caused by Transient events, but the Transient events are filtered out of this view in software (if it's intended to be a Sag/Swell log)?
Best regards,
David
Link copied. Please paste this link to share this article on your social media post.
Hi, David,
Thank you for your reply. I have attached the detailed records and the waveforms from the Site ION7650 Main Supply Meter. It seems the sag/swell Waveform has been detected and recorded every weekday at 7:26 am and 8:06 am. Is that something we can do the further investigation? Also, I have the remote access, if possible, we can schedule a time to have a quick look my settings on the ION7650 Meter.
Thanks,
Regards,
James
Link copied. Please paste this link to share this article on your social media post.
Hi James,
These are some interesting records, and it does seem that there are some PQ events that often occur at the same time of day. It is beyond my range of expertise to comment on what might be the cause, and how big a concern it is for this system. I recommend that you engage with someone from our services team who should be better equipped to help analyze these results, and to comment on the implications for this specific installation. Maybe others in the Solutions Forum have ideas to contribute? Depending on the cause, I know that we have a number of solutions from our PQ business to help mitigate PQ issues like this.
I am interested to follow this investigation, to understand the cause and the steps we recommend (if any). But unfortunately, I don't have enough experience to suggest possible causes.
Best regards,
David
Link copied. Please paste this link to share this article on your social media post.
Thank you very much for your help, David
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.