PAS · EM133-XM memory and interval logging

Set up periodic data logging with a basic setpoint

Written lesson · recording pending

A periodic logging setup needs a destination file, a list of recorded parameters and a trigger that tells the meter when to record. Teach these together: MINUTE INTERVAL supplies the timing and DATA LOG #1 supplies the logging action. The chosen interval does not by itself establish NEM metering compliance.

Source-reviewed draft; live reconfiguration and recording release pending.

Before you start

Choose what the record contains

Open MeterSetup > Memory/Log > Data Recorder and select the intended conventional log. Choose the parameter names and check their units. Confirm that the file allocation has enough parameter slots and record capacity.

Cumulative energy, instantaneous power, block demand and sliding demand answer different questions. Choose the quantity for the task rather than assuming every power-related field represents interval energy.

The XM datasheet specifies up to 16 parameters/channels for interval recording. Each logging action creates a record containing the selected values. Inspect Data Logs 1, 2 and 3 separately, then their Log Memory allocations; a longer parameter list is not a faster recording interval.

  1. Inspect the existing recorder

    Read the selected log number, name and current parameter list. Keep a copy before editing. If the change affects allocation or retained history, complete the archive-before-memory procedure first.

    Source 2 · Source 5

  2. Select the intended parameters

    Set the Group and Parameter fields within the allocated count. Preserve import/export direction and units in the lesson notes. Save the intended recorder setup locally for review.

    Source 2 · Source 4

Source 2 · Source 4 · Source 5 · Source 6

Link the interval trigger to the log action

Open MeterSetup > General Setup > Control/Alarm Setpoints. Inspect the existing logging row. The manufacturer describes Setpoint 1 as the base-model default for periodic Data Log 1 recording; the selected site's existing purpose must still be checked.

Interval choices in the manufacturer guide include 5, 15 and 30 minutes. The following values are instructional alternatives, not claims about the meter's current settings.

  1. Select the periodic trigger

    On the reviewed demonstration logging row, select MINUTE INTERVAL as Trigger. Use the interval's Operate limit field to select the intended supported minute value. Confirm the field label and available choices in the installed PAS version.

    Source 1 · Source 2 · Source 3

  2. Select the logging action

    Choose DATA LOG #1 as Action for this lesson's destination. Do not select a relay, counter or notification action as a substitute. Preserve unrelated setpoints and actions.

    Source 1 · Source 3

  3. Review the rest of the row

    Inspect Release limit and operate/release delays. The interval example is not an analogue threshold exercise: do not add arbitrary release thresholds or delays. Compare the complete row with the reviewed configuration before sending.

    Source 1 · Source 2

Instructional logging intervalTriggerOperate limitAction
5 minutesMINUTE INTERVAL5DATA LOG #1
15 minutesMINUTE INTERVAL15DATA LOG #1
30 minutesMINUTE INTERVAL30DATA LOG #1
Full PAS window showing the offline saved-site setpoint configuration dialog
Offline saved-site example; not current meter readback. No settings saved or sent. Open full-size image in a new tab

Source 1 · Source 2 · Source 3

Find the trigger, action and parameter lists

Keep the manual beside PAS. Near the end of the EM13x Installation and Operation Manual, Appendix D lists Setpoint Triggers and Actions: Table 25 begins at printed page 169 (PDF page 172), and Table 26 is at printed page 172 (PDF page 175). Use these to distinguish the condition that starts an action from the action itself.

Appendix E, Parameters for Data Monitoring and Logging, starts at printed page 173 (PDF page 176). Table 27 pairs PAS abbreviations with their meanings and groups. Find the Group first, then the Parameter; check units and whether the quantity is instantaneous, demand or accumulated energy.

Return to MeterSetup > General Setup > Control/Alarm Setpoints to inspect the trigger and destination, then MeterSetup > Memory/Log > Data Recorder to inspect recorded fields. The older family action list does not enumerate every XM destination, so compare it with the selected model’s actual PAS choices.

Source 7

Keep logging cadence separate from demand periods

Basic Setup has its own power demand period, sliding-demand block count and volt/ampere demand period. Changing MINUTE INTERVAL changes the recording cadence; it does not automatically change those calculations.

Illustrative example: recording a fifteen-minute demand value every five minutes still records that demand calculation, not a newly defined five-minute demand. Likewise, an instantaneous kW sample is not interval kWh. Use the separate NEM interval lesson to check the required energy data, time basis and application obligations.

Source 4 · Source 2 · Source 3

Verify configuration and actual records

An offline save demonstrates the intended configuration. It does not demonstrate that the meter accepted it or generated a record.

  1. Save and review the complete setup

    Save the intended recorder and setpoint configuration locally. Confirm the target site, log destination, chosen interval and expected retention before an authorised live change.

    Source 2 · Source 5

  2. Send only the intended change and read it back

    For an authorised connected demonstration, send the reviewed setup to the intended meter. Receive the settings again and verify the Trigger, interval value, Action and recorder contents. A send-success message alone is not the readback check.

    Source 2 · Source 5

  3. Wait for successive records

    Allow the chosen intervals to occur normally. Do not move the PC or meter clock to manufacture a demonstration. Use Logs > Upload Logs to retrieve the resulting records.

    Source 3 · Source 5

  4. Inspect timestamps and fields

    Open the retrieved log and compare successive timestamps, spacing, parameter names and units. Check the intended boundary alignment and note clock changes or missing records. Revisit allocation if the chosen interval reduces retained history below the requirement.

    Source 2 · Source 3 · Source 5

Source 2 · Source 3 · Source 5

Pro tips after the menu workflow

Use a clear log name so the report identifies its purpose. Keep pre-change and post-change archives distinguishable when recorder contents change.

Inspect every setpoint that can record to the destination file. Extra event-triggered records can make the file fill faster than a periodic-only retention estimate.

Teach the menu path first. Add keyboard accelerators only after they have been demonstrated in the installed PAS version.

Source 2 · Source 1 · Source 3 · Source 5

Limits and checks

Check your understanding

Which action belongs to this periodic logging example?

Show answer

DATA LOG #1. A relay or counter action is a different function and must not be substituted.

Source 1 · Source 3

Does changing MINUTE INTERVAL change the power demand calculation period?

Show answer

No. The recording trigger and the Basic Setup demand period are separate settings.

Source 4 · Source 2

What proves that the intended interval is operating?

Show answer

Read back the recorder and setpoint settings, then retrieve and inspect successive actual records for the intended timing, fields and units.

Source 2 · Source 3 · Source 5

Does a five-minute instantaneous kW sample establish five-minute interval energy?

Show answer

No. Power and energy are different quantities; select and verify the data required by the application.

Source 4 · Source 2

Sources

Revision and review details
RevisionChange and reasonReview / supersedes
20261108-draft-v1
8 November 2026
Added periodic-trigger examples and configuration/record readback checks.

Teach the recorder, interval trigger and logging action together while separating demand periods and NEM requirements.

Manufacturer source review complete; connected programming and new-record verification pending.

None

20261108-retention-v2
8 November 2026
Clarified parameters per record, per-file allocation and retention; added sequential log navigation and manual-reference guidance where relevant.

Connect the displayed recorder settings with practical memory planning.

Manufacturer-source review completed; no new footage or live changes claimed.

20261108-draft-v1