PAS · EM133-XM data and event logs

Data Log 1: inspect the main periodic recorder

Written lesson · recording pending

Data Log 1 is a conventional recorder. The family manual describes an energy-and-demand periodic default, but the selected site's current configuration is the authority for what it actually records.

Manufacturer source review complete; demonstration-specific verification and editorial acceptance pending.

Voice samples — audio only

Listen to the proposed delivery. The revised screen recording is pending; these samples do not replace the lesson video.

Charlotte · en-US · American

Voice sample for the revised Data Log 1 lesson. The new allocation-screen demonstration is not yet complete.

Download audio sample

Read sample transcript

Start with Data Log one. The parameter list tells you what goes into each record. On the X M, you can select up to sixteen values. Now look at Log Memory and select Data Log one again. Number of Parameters is the width of the record. Number of Records is how many snapshots the file can keep. Those are two different limits. Before changing the allocation, upload your logs and open the saved file to check that the history is there.

Before you start

Understand the documented default without assuming it is current

The EM13x manual describes fifteen-minute periodic Data Log 1 recording using a clock-linked Setpoint 1. Its example includes import/export energy, sliding demand and voltage-demand quantities.

The same manual permits changing both the recorded parameters and update rate. A site previously configured for another task may differ completely. Read the actual setup before describing the demonstration.

Source 2

Read the parameter list and units

The Data Recorder tab defines the contents; the memory partition defines the permitted allocation. A report name helps identify the purpose but does not change the underlying measurement.

The XM datasheet allows up to 16 parameters/channels for interval recording. Check this file’s allocated parameter count and selected rows. Those values share one record; the file’s Number of Records and recording cadence determine how much history can be retained. After inspecting the fields, return to Log Memory and read this file’s allocation.

  1. Choose the correct recorder

    Open MeterSetup > Memory/Log > Data Recorder and select Log No. 1. Read the Name and each populated Group/Parameter row.

    Keep the Site Tree visible and expand the selected site with + if needed; confirm the site and log number before proceeding.

    Source 2

  2. Distinguish measurement meanings

    Identify whether each selected value is cumulative energy, instantaneous power or a demand value. Record its units and import/export direction. Do not call every energy-related column interval consumption.

    Source 2

  3. Check capacity before editing

    Inspect the corresponding Log Memory allocation. Stay within the supported parameter count for the exact unit and archive retained history before an allocation change.

    Source 6 · Source 1

Full PAS saved-site Data Log 1 recorder fields
Offline saved-site example; no current meter readback or configuration change. Open full-size image in a new tab

Source 2 · Source 6 · Source 7

Trace the clock trigger to its destination

Open MeterSetup > General Setup > Control/Alarm Setpoints. Inspect the existing row rather than overwriting Setpoint 1 because it appears in the factory example.

For the periodic lesson, MINUTE INTERVAL supplies the cadence and DATA LOG #1 identifies the destination. A trigger field alone is incomplete without the action. Review the full row, including delays and any existing application purpose.

InspectionQuestion to answer
Trigger and intervalWhen should a record be requested?
ActionDoes the action target Data Log 1?
Other setpointsCan another row also record to the same file?
Readback and new recordsDid the meter retain the intended setup and produce the expected timestamps?

Source 3 · Source 2

Upload the file and compare table with trend

A table makes individual timestamps and values explicit. A trend helps reveal changes across the selected time range. Neither view corrects a wrong quantity or missing records.

  1. Retrieve the required history

    Select the intended online site, choose Logs > Upload Logs, select the archive database and use Select Logs to include Data Log 1. Review From and To filters and allow the upload to complete.

    Source 4

  2. Open the actual table

    Use File > Open, choose Access Database (*.mdb), select the saved archive and the relevant data-log table. Confirm its field names and first/last timestamps.

    Source 4

  3. Review a trend

    Use the Data Trend button in the data-log view. Select the intended Time Range and compare the graph with the underlying rows so that sparse or missing points are not mistaken for continuous measurement.

    Source 5

Source 4 · Source 5

Verify the useful result and preserve context

Check consecutive timestamps, expected spacing, units, field names and any gaps. Retain the configuration used for the archive so later viewers can identify the quantities.

Engineering example: a cumulative energy difference may support an energy-use calculation only when units/scaling, time boundaries, resets and rollover have been handled. A periodic instantaneous kW sample is not itself interval kWh. NEM data requirements are covered separately in the interval-selection lesson.

Source 2 · Source 1 · Source 4

Limits and checks

Check your understanding

Is the manual's fifteen-minute default proof of the current site setting?

Show answer

No. Receive/read the intended meter's configuration and inspect the uploaded records.

Source 2 · Source 4

Does selecting MINUTE INTERVAL alone define the recorder?

Show answer

No. Check the destination action and the recorder's parameter list as well.

Source 3 · Source 2

Does a trend replace timestamp and unit checks?

Show answer

No. Compare its underlying rows and the selected time range.

Source 5 · Source 4

Sources

Revision and review details
RevisionChange and reasonReview / supersedes
20261108-draft-v1
8 November 2026
Added a detailed model-scoped log lesson with source references and learner checks.

Explain each log's purpose, PAS controls and interpretation without assigning invented factory roles.

Manufacturer source review complete; independent 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