PAS · EM133-XM memory and interval logging

Upload and verify your logs before changing memory

Written lesson · recording pending

Upload and check the records you need before clearing a log, deleting a partition or reorganising meter memory. Keep the configuration backup and historical-log archive as separate files with clear names. A successful upload message is the start of the archive check, not its conclusion.

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

Before you start

Save configuration and historical data separately

Upload Setups copies the meter's configuration into the selected site database. Upload Logs retrieves stored Event, Data and other selected logs into a log database. One does not replace the other.

Use dated filenames that identify their purpose, such as XM Config Before and XM Logs Before. Keep the original working site and previously verified archives available.

  1. Check the selected site

    Confirm the selected meter and destination site file. Enable Monitor > On line for the upload. Prepare a separate configuration-backup site file before accepting an overwrite prompt.

    Source 1

  2. Upload the configuration

    Select MeterSetup > Upload Setups. Read the warning and confirm that the destination is the intended backup site database. Wait for completion and retain the resulting file.

    Source 1

Source 1 · Source 2

Retrieve the required history

The archive must cover the history you intend to preserve. Do not assume that records newly retrieved since an earlier upload represent everything still retained in the meter.

  1. Choose a log database

    With the intended site selected and online, open Logs > Upload Logs. Choose a new archive database and a clear folder location.

    Source 2

  2. Select the required logs

    Choose Select Logs. Include the Event Log and each required Data Log or daily Billing/TOU profile. Check the actual allocated XM logs rather than relying on the base-model manual's shorter file list.

    Source 2 · Source 4

  3. Check the date range and upload

    Review From and To filters against the required archive period. Retrieve the required range, start the upload and wait for it to finish. Retain any error or incomplete-upload indication for investigation.

    Source 2

Source 2 · Source 4

Verify the saved file before proceeding

Recommended archive acceptance check: reopen the saved log database and examine the files themselves. An upload counter or file size alone does not demonstrate that the required records can be read.

  1. Reopen the archive

    Use PAS's log-file viewing controls to open the saved database. Confirm that each required log is present and readable.

    Source 2

  2. Inspect coverage and contents

    Check the earliest and latest timestamps, representative rows, parameter names and units. Compare the available record count and continuity with the intended archive period. Record and investigate gaps rather than treating them as a complete backup.

    Source 2 · Source 4

  3. Preserve the checked copy

    Save a second copy of the verified archive and its configuration backup. Record the selected meter, capture time, archived range and any unresolved gap in your maintenance record.

    Source 1 · Source 2

  4. Stop if verification fails

    If the upload fails, the archive cannot be reopened or the required history is missing, stop before any clear, delete or repartition command. Resolve the archive problem first.

    Source 2 · Source 3

Source 2 · Source 4 · Source 3

Choose the exact operation after the archive passes

Monitor > Reset contains separate operations for logs, energy, maximum demands and counters. Clear Event Log, Clear Data Log and Clear All Log Files have different scopes. Read the actual confirmation and affected-file list before proceeding.

Do not clear every log simply because a partition change is planned. Repartitioning can put retained data at risk, but the reviewed manuals do not establish that every partition edit clears all files or requires a separate clear-all command. The operation must be justified and authorised for that meter.

Source 3 · Source 4

Limits and checks

Check your understanding

Does Upload Setups preserve historical data logs?

Show answer

No. It saves configuration into the site database. Use Upload Logs for historical records and check the saved archive.

Source 1 · Source 2

The upload completed, but the saved database will not open. May memory be cleared?

Show answer

No. Stop before clearing or repartitioning until the required archive is readable and its coverage has been verified.

Source 2 · Source 3

Must Clear All Log Files be run before every partition edit?

Show answer

No blanket requirement is established by the reviewed sources. Preserve and verify the required logs first, then use only the authorised operation and its actual scope.

Source 3 · Source 4

Sources

Revision and review details
RevisionChange and reasonReview / supersedes
20261108-draft-v1
8 November 2026
Added the archive-before-memory procedure and separate configuration/log backup checks.

Make a verified off-meter archive the prerequisite for destructive memory work.

Manufacturer source review complete; live demonstration and release review pending.

None