PAS · EM133-XM data and event logs

Event Log: read the meter's operational history

Written lesson · recording pending

The Event Log helps reconstruct what the meter reported about configuration changes, resets and diagnostics. It is a chronological record to interpret with configuration and measurement evidence, not a substitute for the conventional data logs.

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

Before you start

Read an event as time, cause and effect

The family manual describes time-tagged configuration, reset and diagnostic events, shown one event per row. The XM protocol record includes time, event number, source/cause, effect and a triggered-value field.

Examples in the protocol dictionary include setup changed, RTC set, log file cleared, power down and power up. The presence of a named event is evidence of that recorded condition; it does not by itself prove the root cause of every nearby measurement change.

Source 1 · Source 2

Upload and open the event history

Use a clearly named history database, separate from the site configuration file. Preserve the unfiltered archive for investigation.

  1. Select the intended meter and date range

    With communication verified, choose the intended site, enable online operation and open Logs > Upload Logs. Select the destination database and use Select Logs to include Event Log. Review From and To filters.

    Source 3

  2. Open the saved event table

    Use File > Open, select Access Database (*.mdb), choose the archive and the Event Log table, then Open. Confirm the first and last timestamps and representative event rows.

    Source 3 · Source 4

  3. Record the context

    Keep the relevant configuration, clock reference and related data-log time range with the archive. Note missing ranges or upload errors before drawing a conclusion.

    Source 1 · Source 2 · Source 3

Source 3 · Source 4

Use filters and sorting without losing evidence

A filter narrows what PAS displays; it does not erase the rows in the database. Sorting changes their display order. These controls are useful for reviewing a focused question while retaining the original archive.

  1. Filter by event cause

    In the Event Log report, right-click and select Filter, or use the Filter button. Select the causes relevant to the investigation and confirm. State when a filtered subset is being shown.

    Source 4

  2. Choose a clear order

    Right-click the report and choose Sort, or use the Sort button. Choose the required order and confirm. Use the timestamp and event details, not screen position alone, to reconstruct a sequence.

    Source 4

  3. Restore the broad view

    Remove the narrowing filter when checking completeness. A filtered screen with no rows is not proof that the meter recorded no events.

    Source 4

Source 4 · Source 1

Use the Event Log to check a maintenance sequence

ILLUSTRATIVE review: after an authorised RTC synchronisation or setup change, upload the Event Log and inspect the relevant recorded event and surrounding rows. Compare this with the performed action and current readback.

The protocol lists RTC set and setup changed effects, but the lesson must not claim a specific event appeared until the actual archive is inspected. A setup-changed event does not establish that every intended value is correct; receive the relevant settings and compare them.

Clock changes can affect how nearby timestamps are interpreted. Preserve the intended time reference and the maintenance record instead of assuming local PC time is always the correct reference.

Source 2 · Source 1 · Source 3

Preserve history and recognise the limits

The Event Log has its own allocation and file behaviour. Wrap-around can replace the oldest records; non-wrap can stop recording when full. Review actual capacity and upload before required history is lost.

Clear Event Log, clear a data log and reset energy/demand counters are different operations. Upload and verify the required history first; do not clear the Event Log as a routine communication test.

Generic PAS documentation describes links to related waveform or data records on supported devices. That software feature does not establish an EM133-XM historical waveform recorder or guarantee that every event has a linked record. Use the actual model capabilities and archived data.

Full PAS memory allocation with the Event Log row selected; not an Event Log report
Offline saved-site memory allocation with the Event Log row selected; this is not an Event Log report. No current meter readback or configuration change. Open full-size image in a new tab

Source 5 · Source 6 · Source 4 · Source 1

Limits and checks

Check your understanding

Does filtering delete events from the archive?

Show answer

No. PAS temporarily hides rows that do not match the filter.

Source 4

Does an RTC set event prove all required logging timestamps are correct?

Show answer

No. Inspect the clock reference, relevant settings and the resulting data records as well.

Source 2 · Source 1

Does an empty filtered view prove the Event Log is empty?

Show answer

No. Remove the filter and check the selected table and requested date range.

Source 4 · Source 3

May the Event Log be cleared before the required archive can be reopened?

Show answer

No. Verify the required off-meter history before destructive work.

Source 3 · Source 6

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