Export Jobs: Pan-42 Measurements Interface
A scheduled export of PAN-42 power meter readings - current, voltage, power, power factor, energy, reactive power, consumed active energy, and frequency - delivered to a destination you control.
Written by Shir Goldstein
Updated at May 26th, 2026
Table of Contents
A scheduled export of meter-grade readings from your PAN-42 power meters - voltage, current, active power, real power factor, reactive power, frequency, and the meter's internal energy counter - for use in downstream analytics, BI, billing, or integration systems.
What Is a Pan-42 Measurements Export?
A Pan-42 Measurements export job pulls readings from your PAN-42 power meters on a schedule and delivers them as a file (CSV) or HTTP payload (JSON) to a destination you choose. Each record is one phase channel on a PAN-42 meter, at one point in time, with the electrical readings the meter produced for that interval.
Why use it?
- Feed PAN-42 time-series readings into a BI tool, data warehouse, or analytics platform.
- Drive billing, sub-metering, or energy attribution workflows that rely on meter-grade measurements.
- Capture the fields PAN-42 meters report that standard Panoramic Power sensor exports do not include- voltage, real power factor, reactive power, consumed active energy, and frequency.
- Keep a long-term archive of meter readings outside PowerRadar.
Why PAN-42 instead of a standard sensor export?
Standard Panoramic Power sensors (PAN-10, PAN-12, PAN-14) measure current only. Voltage and power factor on those sensors come from the panel's configuration at installation - they are not measured. Energy on a standard sensor is then calculated on the bridge as current × configured voltage × configured power factor × time.
PAN-42 is a true 3-phase power meter. It measures voltage, current, active power, reactive power, and power factor directly per phase, and reports its own cumulative active energy counter - the same value displayed in TimeView. For a deeper look at what PAN-42 measures and how it compares to standard sensors, see About PAN-42 Power Meters.
A Pan-42 Measurements export is usually paired with a Catalog export. Catalog supplies the asset metadata — the sites and meters your readings reference - while Pan-42 Measurements supplies the actual readings. Most partners run both: Catalog daily, Pan-42 Measurements at the chosen frequency. See Export Jobs: Catalog Interface.
For standard Panoramic Power sensor readings, use the Measurements export type instead. For Pulse Meter readings, use the Meters Measurements export type. Each is documented in its own article: Export Jobs: Measurements Interface and Export Jobs: Pulse Meter Measurements Interface. This article covers PAN-42 power meter exports only.
Where to Find It
In the sidebar, open the Account Dashboard and click Auto-Export. The Export jobs list opens. Click Create New Export Job in the top right.
For a tour of the Export jobs list itself - the columns, the search and refresh controls, the row menu -see Export Jobs: Setup.
Configuring a Pan-42 Measurements Export Job
The New export job page has the configuration form on the left and a Data sample preview on the right. The preview shows a fixed example of the export file format - it isn't pulled from your account - and it's there to help you see the shape of the file before saving. See Sample Outputs below for what does and doesn't change the preview.
1. Job Name
Enter a descriptive name in the Job name field. The name appears in the Export jobs list and in any failure notifications, so use something you'll recognize later - for example, "Pan-42 hourly - all sites".
2. Data to Export
Open the Data to export dropdown and select Pan-42 Measurements - Meter-level readings from your PAN-42 power meters.
3. Sites for Data Export
Choose which sites the job covers:
- Toggle All sites on to include every site in the account.
- Toggle it off to pick specific sites from the dropdown.
Sites that don't have any PAN-42 meters can still be included - they contribute no rows to the export. If you select sites without PAN-42 meters and no other meters either, the export file for that run may be empty.
4. Export Frequency and Data Resolution
- Export frequency- how often the job runs. Options: Every day, Every hour, Every 15 minutes, Every 5 minutes.
- Data resolution- the granularity of each measurement record. Options: 1 min, 5 min, 15 min, 30 min, 1 hour.
The available resolution options are filtered by the frequency you select. For example, choosing Every day as the frequency will not let you pick 1 min as the resolution.
If you change Export frequency after setting Data resolution, the resolution options refresh - re-confirm your resolution choice before saving.
Note - frequency (Hz) appears only at 1-min resolution. All other Pan-42 readings are available at every resolution, but frequency (Hz) is the one field that exists only at the highest resolution. To include it in your export, choose Data resolution = 1 min - which is selectable only when Export frequency = Every 15 minutes or Every 5 minutes. At any other resolution, the frequency field is dropped from the export entirely: no key in JSON, no column in CSV.
Heads up - the Data sample preview always shows frequency (Hz), regardless of the resolution you pick. The preview panel on the right side of the New export job page loads a fixed example file that was built at 1-min resolution, so frequency (Hz) appears in every preview. The field is only included in your actual export when your Data resolution is 1 min. If you save a Pan-42 job at 5-min or 15-min resolution, the field will be absent from the files you receive even though the preview shows it.
5. Zero Pad Measurement Gaps
Tick the Zero pad measurement gaps checkbox to fill missing intervals with zero values instead of leaving them as gaps. PowerRadar produces a continuous timeline at the chosen resolution — every numeric field (power(W), energy(Wh), current(A), voltage(V), power_factor, reactive power (VAR), consumed active energy (Wh), and frequency (Hz) when present) is set to 0 for any interval where the meter didn't report. Meter IDs, names, phase, and site fields stay populated.
Use it when your downstream system expects evenly spaced records — for example, a BI tool that would otherwise misalign charts when intervals are missing. Leave it off when your downstream system handles sparse data on its own, or when you want to distinguish "meter reported zero" from "meter reported nothing".
Note: Padded rows count toward the batch size limit, and PAN-42 padding produces one padded row per phase channel per missing interval. A three-phase PAN-42 meter that is silent for an hour at 1-min resolution generates 180 padded rows (3 phases × 60 minutes), not 60. See Batch Sizes and Limits below.
This option is available for Measurements and Pan-42 Measurements jobs only. It does not apply to Catalog or Meters Measurements.
6. Data Transfer Method
Pick how the file is delivered. Three methods are available:
- JSON over HTTPS - Recommended. Sends the export as a JSON payload to a URL you control.
- CSV over SFTP - Best FTP protocol. Sends a CSV file to a secure SFTP folder hosted by Panoramic Power.
- CSV over FTPS - Older FTP protocol. Sends a CSV file over FTPS.
Each method has its own configuration fields and a How it works? panel below the cards.
For the full breakdown of each transport - including credentials, ports, firewall rules, and the SFTP vs FTPS decision - see Export Jobs: Setup and the SFTP and FTPs Server Connection Checklist.
7. Apply
Click Apply at the bottom right to save the job. Use the same button when editing an existing Pan-42 Measurements job.
Once saved, the job is active and runs automatically on the schedule you defined. To pause, re-enable, or delete a Pan-42 Measurements job later, open the three-dot menu in its row on the Export jobs list - see Export Jobs: Setup for the list controls.
Sample Outputs
The Data sample panel on the right side of the New export job page shows a fixed example file that illustrates the structure and field names of the export you're configuring. The same example is shown to every account — it does not reflect your actual sites, meters, or measurements.
The preview changes when you switch:
- Data to export - between Measurements, Catalog, Pan-42 Measurements, and Meters Measurements.
- File format - between CSV (used by CSV over SFTP and CSV over FTPS) and JSON (used by JSON over HTTPS).
Settings such as Sites, Export frequency, Data resolution, and Zero pad measurement gaps do not change the preview. To see how your real PAN-42 data will look at the chosen frequency and resolution, wait for the first scheduled run.
Field Reference
Heads up - JSON keys and CSV column headers differ for two Pan-42 fields. The standard Measurements export uses identical strings for both formats, but the Pan-42 Measurements export does not. For reactive power and consumed active energy, the JSON key uses underscores and no space before the parenthesis (
reactive_power(VAR),consumed_active_energy(Wh)), while the CSV column header uses spaces and a space before the parenthesis (reactive power (VAR),consumed active energy (Wh)). Only the frequency field is identical in both formats (frequency (Hz)). If your downstream parser handles both transports, treat the JSON keys and CSV headers as two separate strings — don't assume they match.
Two energy fields - different meanings. Every row contains two energy values, and they are not interchangeable:
energy(Wh)is an interval estimate calculated by PowerRadar at export time as active power × interval duration. Use it for a quick read of how much energy was consumed during each interval.consumed_active_energy(Wh)is the PAN-42 meter's own cumulative energy counter — a running total in watt-hours that grows over time. It is the most precise meter-grade value available and matches what TimeView displays internally.For billing and high-precision use cases, ingest
consumed_active_energy(Wh)and compute interval consumption downstream as the delta between consecutive rows for the same(device_id, phase):consumed_active_energy[t] − consumed_active_energy[t−1].
Every Pan-42 Measurements record contains the following fields.
| Field - JSON key | Field - CSV column header | Type | Description |
|---|---|---|---|
| device_id | device_id | string | Unique identifier of the PAN-42 meter. Shared across every phase channel on the same physical meter. |
| device_name | device_name | string | Display name of the PAN-42 meter. Shared across every phase channel on the same physical meter. |
| phase | phase | string | The phase channel on the meter (R, S, T). Differentiates rows that share the same device_id and measurement_time. |
| measurement_time(UTC) | measurement_time(UTC) | timestamp | Start of the measurement interval, in UTC. Always UTC — regardless of the account's display timezone. |
| resolution(minutes) | resolution(minutes) | integer | Length of the measurement interval, in minutes. Matches the Data resolution chosen for the job. |
| site_id | site_id | string | Unique identifier of the site the meter belongs to. |
| site_name | site_name | string | Display name of the site. |
| current(A) | current(A) | decimal | Average current over the interval, in amperes. |
| voltage(V) | voltage(V) | decimal | Average voltage over the interval, in volts. |
| power(W) | power(W) | decimal | Average active power over the interval, in watts. |
| power_factor | power_factor | decimal | Average power factor over the interval, between 0 and 1. Reported as an absolute value — the meter measures whether the load is inductive or capacitive, but that direction is not currently included in the export. |
| energy(Wh) | energy(Wh) | decimal | Interval energy estimate, in watt-hours. Calculated by PowerRadar at export time as active power × interval duration. For meter-grade precision, use consumed_active_energy(Wh) and compute deltas yourself. |
| reactive_power(VAR) | reactive power (VAR) | decimal | Average reactive power over the interval, in volt-amperes reactive. Reported as an absolute value — the inductive vs capacitive direction is measured by the meter but not included in the export. |
| consumed_active_energy(Wh) | consumed active energy (Wh) | decimal | The PAN-42 meter's internal cumulative active energy counter, in watt-hours. Each row holds the meter's running total at that measurement_time — values grow monotonically across consecutive rows for the same (device_id, phase). To get interval consumption, subtract the previous row's value: consumed_active_energy[t] − consumed_active_energy[t−1]. This is the same value displayed in TimeView (which performs the delta calculation internally). |
| frequency (Hz) | frequency (Hz) | decimal | Line frequency over the interval, in hertz. Present only when Data resolution = 1 min. At 1-min resolution, the field is always present in every row even when the meter did not report a frequency reading — in JSON the key is included with the value "" (empty string), and in CSV the cell is empty (no value between the surrounding commas). At any other resolution the field is omitted entirely. |
Note — Multiple rows per meter. A single PAN-42 meter produces one row per active phase channel per measurement time. A 3-phase PAN-42 meter at 15-minute resolution running over a 24-hour window produces 3 phases × 96 intervals = 288 rows for that meter alone. Plan downstream ingestion accordingly — the unique key per row is the combination of device_id, phase, and measurement_time(UTC).
Coming soon - additional PAN-42 fields. PAN-42 meters report more power-quality data than this export currently includes. Planned additions to the field set include THD (total harmonic distortion) for voltage and current, phase angle between phases, and additional meter fields. These will roll out across both this export and TimeView at the same time, so the data you see in TimeView and the data you receive in the export stay in sync.
Late Data and One Row Per Channel
PowerRadar guarantees one row per meter, per phase channel, per measurement time, per export run. The exporter looks up the most recent version of each (device_id, phase, measurement_time) combination at query time and emits only that - you will never receive two records for the same meter, phase, and timestamp in a single run.
What this means in practice:
-
No deduplication needed. You can append every row to your downstream store without checking for duplicates by
(device_id, phase, measurement_time). - No "updated record" follow-ups. PowerRadar does not re-send a previously delivered record with a corrected value.
- Late data has a 5-minute window. A reading that arrives at PowerRadar within 5 minutes after its measurement window closes is included in the next export run. Data that arrives later than that is stored in PowerRadar but is not picked up by any future export run.
If you need a measurement window that has already passed, run a Manual Export - manual exports are not bound by the 5-minute window.
Batch Sizes and Limits
Large exports are split into multiple files or transactions. The split is automatic - you don't need to configure it — but if you size downstream ingestion or storage by record count, the numbers below are the ones to plan against.
| Transport | Maximum rows per file / transaction |
|---|---|
| CSV over SFTP | 10,000 rows |
| CSV over FTPS | 10,000 rows |
| JSON over HTTPS | 2,000 measurements |
A few practical notes:
- PAN-42 row counts grow per phase. Every active phase channel produces its own row per measurement time. A site with five 3-phase PAN-42 meters at 1-min resolution generates 5 meters × 3 phases × 60 minutes = 900 rows per hour, before any padding. Size your batch expectations accordingly.
- Zero Pad Gaps rows count toward the limit. A job with 8,000 real measurements and 3,000 padded rows totals 11,000 rows, which exceeds the 10,000-row file limit and will be delivered as two files.
- JSON over HTTPS retries. Each HTTP transaction must return HTTP 200 OK on its own. Failed transactions are retried in the next scheduled run for up to one week.
- Configure your endpoint for at least 1 MB payload size if you receive Pan-42 Measurements over HTTPS.