Ask our Experts
Didn't find what you are looking for? Ask our experts!
New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).
Schneider Electric support forum about Power Meters (ION, PowerTag, PowerLogic) and Power Quality from design, implementation to troubleshooting and more.
Search in
Please select a country to continue with beta search.
Link copied. Please paste this link to share this article on your social media post.
Hi,
I captured CSV waveform data from the HDPM6000 Head Unit and the HDPM6000R retrofit unit
(with voltage and current at 60 Hz).
I counted a total of 2048 samples in each waveform.
The data appears to be formatted as 128 samples per cycle over 16 cycles. Is this correct?
Is the same format used in a 50 Hz environment?
Also, can the waveform format be changed?
For example, 64 samples × 32 cycles.
I would like to know the waveform trigger point used by the HDPM6000.
Thank you,
Okada
Link copied. Please paste this link to share this article on your social media post.
Hi @T.Okada
Based on Table 3.1 – Waveform Capture Specifications in the HDPM6000 Installation Guide:
HDPM6000 uses a fixed sampling frequency of 8 kHz means sample interval = 125 µs for its waveform captures, regardless of the line frequency.
For 60 Hz: each cycle is 1/60 ≈ 16.66 ms therefore each cycle includes (16.66 ms)/(125 µs) ≈ 133.33 samples
For 50 Hz: each cycle is 1/50 = 20 ms therefore each cycle includes (20 ms)/(125 µs) = 160 samples
The HDPM6000 waveform capture uses a fixed buffer length of total 2048 samples per waveform, regardless of frequency or module type.
At 60 Hz, 2048 samples at 133.33 samples/cycle equals 15.36 cycles. -> sampling × cycles = 133.33 × 15.36
At 50 Hz, 2048 samples at 160 samples/cycle equals 12.8 cycles. -> sampling × cycles = 160 × 12.8
The waveform capture format of is a fixed and cannot be changed.
Trigger is event‑based, with 2/3 pre‑event, and waveforms are captured when:
Voltage swell or sag crosses an RMS threshold
Overcurrent or tripped breaker conditions occur
A manual “Force Capture” is issued
Best Regards,
-Mehran
L3 Expert Advanced metering
Link copied. Please paste this link to share this article on your social media post.
Hi @T.Okada
Based on Table 3.1 – Waveform Capture Specifications in the HDPM6000 Installation Guide:
HDPM6000 uses a fixed sampling frequency of 8 kHz means sample interval = 125 µs for its waveform captures, regardless of the line frequency.
For 60 Hz: each cycle is 1/60 ≈ 16.66 ms therefore each cycle includes (16.66 ms)/(125 µs) ≈ 133.33 samples
For 50 Hz: each cycle is 1/50 = 20 ms therefore each cycle includes (20 ms)/(125 µs) = 160 samples
The HDPM6000 waveform capture uses a fixed buffer length of total 2048 samples per waveform, regardless of frequency or module type.
At 60 Hz, 2048 samples at 133.33 samples/cycle equals 15.36 cycles. -> sampling × cycles = 133.33 × 15.36
At 50 Hz, 2048 samples at 160 samples/cycle equals 12.8 cycles. -> sampling × cycles = 160 × 12.8
The waveform capture format of is a fixed and cannot be changed.
Trigger is event‑based, with 2/3 pre‑event, and waveforms are captured when:
Voltage swell or sag crosses an RMS threshold
Overcurrent or tripped breaker conditions occur
A manual “Force Capture” is issued
Best Regards,
-Mehran
L3 Expert Advanced metering
Link copied. Please paste this link to share this article on your social media post.
Thank you for your prompt reply.
I now understand the HDPM6000’s waveform format, and I have a few additional questions:
・How many waveforms can the HDPM6000 store?
・Is the number of waveforms limited only by the capacity of the 64GB microSD card?
・Does the HDPM6000 have onboard storage in addition to the microSD card,
or are all waveform and log data saved to the 64GB microSD card?
・Could you also let me know the size limits for the various types of data?
・Do these limits differ depending on the data type?
Regards,
Okada
Link copied. Please paste this link to share this article on your social media post.
Hi @T.Okada
You're welcome and thank you for your patience while I waited for confirmation from the hardware team.
Please see my comments below:
・How many waveforms can the HDPM6000 store?
- The meter supports a maximum of 1,024 waveform entries. Once this limit is reached, waveform storage rolls over, and the oldest entries are overwritten.
・Is the number of waveforms limited only by the capacity of the 64GB microSD card?
- No, the 1024 entries are fixed and are independent of the SD card size, the connected module type, and the associated channels.
・Does the HDPM6000 have onboard storage in addition to the microSD card, or are all waveform and log data saved to the 64GB microSD card?
- All waveform captures, data logs and records are stored exclusively on the microSD card. The HDPM6000 internal onboard memory (RAM/flash) is used only for real‑time processing, temporary buffering, and Energy accumulation calculation.
・Could you also let me know the size limits for the various types of data?
- As for data logging, the meter can store a maximum of 120 (or 121) registers in INT16 format, or 60 registers in INT32 format, across 20 available logs, with a maximum of 65,535 log entries, which means:
20 logs x 65535 entries for each x (120 16-bit registers + timestamp)
As for waveform data, the meter can store a maximum of 1,024 waveforms. The file size of each waveform file depends on the number of channels in the connected branch module. For example, for one S24 module, a single waveform file is approximately 400 kB, resulting in a total storage requirement of 1,024 × 400 kB.
・Do these limits differ depending on the data type?
- As mentioned above, it is limited to the fixed number of entries.
Best Regards,
-Mehran
L3 Expert Advanced metering
Link copied. Please paste this link to share this article on your social media post.
Thank you for your kind reply!
Your detailed explanation, along with the image capture, helped deepen my understanding of the HDPM6000’s logging and its capacity limitations.
Regards,
Okada
You’ve reached the end of your document
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.