Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!
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 All,
I’m testing an ION meter and have encountered an issue with the waveform timestamp display under ION Setup → Data View → Waveform.
I triggered several voltage sags. The Event and Sag/Swell logs correctly show the timestamps of these occurrences. However, the Waveform section consistently displays timestamps of 1970 and 1955, which are clearly incorrect.
Wondering has anyone encountered this issue before? Is there a specific setting I should adjust to correct the waveform timestamp? Thank you
Link copied. Please paste this link to share this article on your social media post.
Hello @Stuart_Cheng
Looking at the event log, it looks like you are trying to trigger PQ events by changing setup registers. This is not a good way to generate an event. When you change a setup register, you will take the module offline then make the change then put the module back online. Doing this to sag/swell module can make the data associated with PQ events become corrupted. Changing the setup registers is not a good test method. What exactly are you trying to test? Would a manual waveform trigger achieve what you are looking for?
Regards,
Charles
Link copied. Please paste this link to share this article on your social media post.
One thing to keep in mind is that triggering waveforms when the volts mode is set to DEMO will result in waveforms that are not timestamped properly. Timestamps for waveforms while the device is in DEMO mode will always be reported as the time it was downloaded (not when it was stored).
You should also make sure that all waveforms are modified equally as they process for ION Setup to group records are not time based but all are expected to have the same number of waveforms (i.e. reprograming only 1 of the waveform recorders will only reset the stored waveforms in that 1 module which causes offset issues in the waveform viewer).
Link copied. Please paste this link to share this article on your social media post.
Hello @Stuart_Cheng
Looking at the event log, it looks like you are trying to trigger PQ events by changing setup registers. This is not a good way to generate an event. When you change a setup register, you will take the module offline then make the change then put the module back online. Doing this to sag/swell module can make the data associated with PQ events become corrupted. Changing the setup registers is not a good test method. What exactly are you trying to test? Would a manual waveform trigger achieve what you are looking for?
Regards,
Charles
Link copied. Please paste this link to share this article on your social media post.
One thing to keep in mind is that triggering waveforms when the volts mode is set to DEMO will result in waveforms that are not timestamped properly. Timestamps for waveforms while the device is in DEMO mode will always be reported as the time it was downloaded (not when it was stored).
You should also make sure that all waveforms are modified equally as they process for ION Setup to group records are not time based but all are expected to have the same number of waveforms (i.e. reprograming only 1 of the waveform recorders will only reset the stored waveforms in that 1 module which causes offset issues in the waveform viewer).
Link copied. Please paste this link to share this article on your social media post.
Hi @Charles_Murison and @Robert_Lee,
Thanks for helping me point out the issue.
I was testing some PQ functions in the office, so I used a simplified approach—running in demo mode and manually adjusting the voltage to simulate sags. That method indeed caused the issue. After your reminders, I switched to using a simulator, and everything is working fine now. Appreciate your support and guidance!
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.
Welcome to your new personalized space.
of