PAS · EM133-XM memory and interval logging

Plan memory partitions and retained history

Written lesson · recording pending

Plan retained history from the allocation reported for the selected meter. Total memory, free memory, record size and the number of allocated records describe different things. Before applying any partition change, complete the Upload and verify your logs lesson and keep its checked archive.

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

Before you start

Read the current allocation

Memory is allocated to log files. The record limit determines how many records a file can hold; the recording rate determines how quickly those slots are used. Additional XM data-log entries must be checked on the selected unit.

First inspect Data Log 1, then 2, then 3 in Data Recorder. Each file has its own parameter list. Return to Log Memory to connect those contents with each file’s allocation: parameters describe the columns in one record; Number of Records describes how many timestamped records the file can retain.

  1. Open Log Memory

    Open MeterSetup > Memory/Log and select Log Memory. For a connected check, receive the current settings from the intended meter before treating the displayed values as live.

    Keep PAS maximised with the full Site Tree and clock visible. If the meter branch is collapsed, expand its + control so the selected site remains easy to identify; use the menu route first.

    Source 1 · Source 2

  2. Record the starting state

    Note Total and Free memory, each allocated file, its type, number of records, number of parameters and reported record size. Preserve the starting configuration with the archive.

    Source 1 · Source 3

  3. Separate file purposes

    Keep Event Log history, conventional interval data and the daily Billing/TOU profile distinct. The daily profile is not a substitute for a conventional interval log.

    Source 1 · Source 2

Full PAS window showing the offline saved-site memory allocation 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

Separate data points from stored records

The EM133-XM datasheet specifies interval recording for up to 16 user-selected parameters or channels. These are the values stored together in a record, not 16 separate records each time the logger runs. Check the selected file’s allocated parameter count and available PAS rows before editing.

For example, a record containing voltage, current and active power contains three data points at one recording time. At one record every 15 minutes, it uses 96 record slots per day, not 288. Adding fields can increase the record size and the memory needed for that allocation.

Older EM13x and unified-protocol tables show nine parameters. Use the XM-specific specification and confirm the actual model, firmware and allocation; do not copy the older limit or a memory-size formula across versions.

Source 5 · Source 2 · Source 1

Decide what happens when the file fills

The manufacturer's file type controls whether recording overwrites old data or stops at capacity. Choose it deliberately and plan uploads around that behaviour.

FIFO means first in, first out: in a circular or wrap-around file, the oldest record is replaced as new records arrive after capacity is reached. This explanation applies to wrap-around recording. A non-wrap file stops when full. Clearing a file or changing its partition is a separate operation, not normal FIFO turnover.

File typeWhen the allocated file fillsOperational consequence
Wrap-aroundNew records replace the oldest records.Retrieve records before the required history is overwritten.
Non-wrapRecording stops until the file is cleared.Monitor remaining capacity and archive before an authorised clear.

Source 1 · Source 2

Estimate retention from record slots

Teaching example: assume one record at each scheduled interval, no additional event-triggered records and a constant interval. Records per day = 1440 ÷ interval in minutes. Retained days = allocated record slots ÷ records per day.

The example below assumes 1440 allocated record slots. It is not a measured capacity or factory default for the connected meter. Use its actual allocation for a site calculation.

For the hourly and daily examples, assume one conventional record per hour or day. A Billing/TOU daily profile has a different multi-section structure, so do not use this table to infer its byte allocation. The Event Log is event-driven: its retention depends on the rate of recorded events.

Calculate each file separately. Use PAS’s reported record size and allocated record count; there is no universal conversion from a headline memory size in MB to retained days. Additional event-triggered records reduce the simple periodic estimate.

Illustrative intervalEstimated records per dayEstimated retention with 1440 slots
5 minutes2885 days
15 minutes9615 days
30 minutes4830 days
1 hour2460 days
1 day11440 days

Source 1 · Source 2

Configure the file and its recorded contents

Treat deletion, clearing and partition changes as potentially destructive. Do not proceed until the required archive has been reopened and verified. Use a disposable offline copy to practise the dialog before an authorised live change.

  1. Open the intended file partition

    In Log Memory, double-click the intended file. Inspect File Type, Number of Records and Number of Parameters. Use the displayed record size and available capacity when planning the allocation.

    Source 1 · Source 2

  2. Review any affected history

    Read the exact warning and affected-file list before accepting a change. Delete removes a partition; a log-clear command removes retained records from its selected target. Do not add a Clear All Log Files operation unless it is independently required and authorised.

    Source 1 · Source 4 · Source 3

  3. Choose the recorded parameters

    Select the file row and Setup Recorder, or open the Data Recorder tab and choose the corresponding log. Configure the fields within the allocated parameter count and give the log a clear name.

    Source 1

  4. Save, send and read back deliberately

    Saving a local setup and sending it to the meter are separate steps. For an authorised live change, send only the intended setup, receive it again and compare the allocation and recorder contents with the plan.

    Source 1 · Source 3

  5. Check recording resumes as intended

    After the appropriate recording trigger, upload new records and verify their timestamps, fields and units. Check relevant Event Log entries. Keep the pre-change archive separate from the new configuration's records.

    Source 1 · Source 3

Source 1 · Source 2 · Source 3 · Source 4

Pro tips after the menu workflow

At the same record capacity, a shorter logging interval retains less time. Extra setpoints recording to the same file also consume record slots and reduce the simple periodic estimate.

Choose only the parameters needed for the task, then check the reported record size and capacity again. Do not rely on a generic memory-size headline to promise a fixed number of days.

Schedule uploads comfortably inside the verified retention window and check successful archive results. A configured schedule alone is not evidence that an upload ran.

Source 1 · Source 2 · Source 3

Limits and checks

Check your understanding

Does selecting wrap-around preserve all old records indefinitely?

Show answer

No. When the allocated file fills, new records replace the oldest ones. Upload before the required history is overwritten.

Source 1 · Source 2

Can the base EM13x manual's memory size be used as the XM meter's confirmed capacity?

Show answer

No. Identify the variant and read its current allocation. The XM documentation contains additional data-log entries.

Source 1 · Source 2

In the illustrative exercise, what happens when the interval changes from fifteen minutes to five minutes without changing record capacity?

Show answer

Records are used three times as quickly, so estimated retained time becomes one third. This assumes only one periodic record per interval.

Source 1 · Source 2

Does one record with 16 selected values consume 16 record slots?

Show answer

No. The values are fields within one record. More fields can increase its size in bytes, while the recording rate determines how quickly record slots are used.

Source 5 · Source 1

Does FIFO describe a non-wrap file or a partition change?

Show answer

No. FIFO describes oldest-record replacement during wrap-around recording. Non-wrap stops when full; clearing and repartitioning are separate operations requiring a checked archive.

Source 2 · Source 1

Sources

Revision and review details
RevisionChange and reasonReview / supersedes
20261108-draft-v1
8 November 2026
Added partition planning, full-file behaviour and conditional retention exercises.

Teach allocation and backup consequences without applying base-model factory figures to XM.

Manufacturer source review complete; live partition change and recording release 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