PAS · EM133-XM data and event logs

Data Log 2: build a separate view of the same meter

Written lesson · recorded supplement

Narrated tour

Download MP4 · SRT captions · Use the video controls for captions and fullscreen; Escape returns to this lesson.

Your choice is remembered in this browser. Only available recordings can be selected. Changing version pauses the video and returns to the start. This choice applies to the lesson video, not a separate Short.

Playing version: Michael · en-AU · Australian.

Current complete Australian edition.

Available and planned versions
  • Michael · en-AU · Australian — available
  • Charlotte · en-US · American — planned; recording not available
  • Spanish narration · es · To be selected — planned; recording not available
  • US English narration · en-US · US — planned; recording not available
About this recording

Edited saved offline settings inspection. No configuration sent or accepted meter change claimed. Full recorded PAS frame, Site Tree and clock retained. No full-screen cards or manual inserts. Closing Site Tree tip uses separate edited saved-site views from a wider EM133-XM capture.

Michael (Australian) narration from ElevenLabs. Edited PAS screen recording.

Chapters

Data Log 2 is an additional conventional file documented for EM133-XM. It can carry a different selected parameter list from Data Log 1; it is not inherently a voltage log, a second meter or a second set of physical inputs.

Australian narrated walkthrough with written guidance.

Before you start

Identify the XM-specific file

The unified EM133/EM133-XM reference provides separate Data Log 2 file allocation and parameter-setup blocks and marks this additional file for XM. Use the exact model's available controls rather than the older base-family file-count table.

A separate file provides another organised history from supported measured quantities. It does not create new sensors or improve the meter's measurement accuracy.

Source 1

Inspect Data Log 2 independently

The selected log number matters. Similar-looking parameter lists can make it easy to explain or edit the wrong file.

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. Select the log

    Open MeterSetup > Memory/Log > Data Recorder and select Log No. 2. Read back the visible log number before discussing its contents.

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

    Source 2 · Source 1

  2. Review each field

    Read the current Name, Group and Parameter selections. Compare them with Data Log 1 only after noting which file is selected. Check units and the source quantity for every populated field.

    Source 2

  3. Inspect its allocation

    Return to Log Memory and inspect the Data Log 2 row: file type, record limit and reported size. Do not substitute Data Log 1's retention for this file.

    Source 4 · Source 1

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

Source 2 · Source 1 · Source 8 · Source 4

Example: keep voltage and current trends together

ILLUSTRATIVE application: Data Log 2 could hold supported phase voltage and current quantities for operating-condition trends while Data Log 1 retains an energy-focused selection.

Choose available parameter labels for the actual wiring mode and device. Phase-to-neutral and phase-to-phase voltages are not interchangeable descriptions. The example is a design choice, not a claim that these fields are already configured.

Source 1 · Source 2

Verify the recording destination before programming

Open MeterSetup > General Setup > Control/Alarm Setpoints and inspect the Action choices. In the installed example, the offline PAS demonstration shows DATA LOG #2 as a separate destination alongside DATA LOG #1 and DATA LOG #3. This identifies the available label in that saved-site view; it does not show that the meter is currently using it.

For the reviewed Data Log 2 plan, the intended logging action is DATA LOG #2. Do not copy a DATA LOG #1 action and expect it to record into Data Log 2. The older unified-guide action table lists only Data Log 1 despite its XM file setup entries, so no undocumented numeric action code is supplied here. If the required destination is absent in another installation, obtain model/firmware-specific guidance.

For an authorised change, preserve unrelated setpoints, save the reviewed plan, send only the intended settings and receive them again. Verify the destination and actual new records. Merely opening or selecting an offline action does not program the meter.

Source 1 · Source 3 · Source 5 · Source 7

Retrieve the separate history and compare fairly

Use Logs > Upload Logs > Select Logs to include Data Log 2 in the archive. Open the saved database and its matching table, then use a trend view if useful.

Compare logs over the same time range and check their individual timestamps. Different recording intervals or trigger conditions can produce different row counts; a row number is not a reliable cross-file time match. Check units, clock basis and gaps before drawing a conclusion.

Source 5 · Source 6 · Source 1

Limits and checks

Check your understanding

Does Data Log 2 always contain voltage and current?

Show answer

No. That is an illustrative use; inspect its independently configured parameter list.

Source 1 · Source 2

Can a Data Log 1 action be assumed to write into Data Log 2?

Show answer

No. Verify the actual destination supported by the selected XM/PAS combination; do not invent a protocol action code.

Source 1 · Source 3

Should row 100 in each log be assumed to be the same moment?

Show answer

No. Compare timestamps and recording conditions, not row numbers.

Source 1 · Source 5

Sources

Revision and review details
RevisionChange and reasonReview / supersedes
20261108-video-v4
8 November 2026
Revised teaching video, captions and chapter timing.

Show the menu and relevant setup screens clearly, with spoken guidance and pauses.

Final export checked before development deployment.

20261108-retention-v3

20261108-draft-v1
8 November 2026
Added a detailed model-scoped log lesson with source references and learner checks. Added a hashed original PAS frame verifying the installed action labels with an offline-only qualification.

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

20261108-retention-v3
8 November 2026
Added a Charlotte narrated mini-lesson with moving PAS navigation, captions, chapter controls and Site Tree expansion.

Connect recorder contents to memory allocation and make the steps visible.

Export decoded and visual checks recorded; final independent review accompanies the deployment record.

20261108-retention-v2