PAS · EM133-XM data and event logs

Data Log 3: reserve a recorder for a defined question

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 3 is another separately configured conventional XM file. Use it to answer a defined measurement-history question rather than duplicating an existing file without understanding the additional memory use.

Australian narrated walkthrough with written guidance.

Before you start

Start with the question

The XM file and parameter tables include Data Log 3 separately from Data Logs 1 and 2. Conventional files can hold selected supported measured parameters and can be triggered through the setpoint system.

ILLUSTRATIVE use: a dedicated file could retain selected operating quantities for a particular investigation or a separate periodic cadence. Calling it a diagnostic log describes your chosen use, not a fixed factory function.

Source 1 · Source 2

Keep the field selection focused

More columns are not automatically a better investigation. Select the quantities that answer the question and retain their meaning and units.

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. Inspect Log No. 3

    Open MeterSetup > Memory/Log > Data Recorder and choose Log No. 3. Read the current name and parameter rows before making a proposed change.

    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. Describe the intended record

    List the question, selected quantities, units and intended trigger in the plan. Distinguish measured power, demand values and cumulative energy rather than mixing their interpretations.

    Source 2

  3. Check allocation and overwrite behaviour

    Inspect the Data Log 3 partition in Log Memory. Check record capacity and wrap-around/non-wrap behaviour and keep a verified archive before any reallocation or clear.

    Source 4

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

Source 2 · Source 4 · Source 7

Explain conditional recording without inventing a threshold

Conventional data recording may be requested by a setpoint event as well as a time-based trigger. A conditional example can retain selected quantities when a reviewed condition operates; it is not the same as continuous high-speed waveform capture.

For an analogue trigger, the operate and release limits define the operating condition and hysteresis, with delays affecting when operation/release occurs. Thresholds and delays must come from the application; this lesson does not provide an arbitrary live alarm setting.

Do not force a relay or reset action to create a demonstration. Check the actual supported Data Log 3 destination and preserve existing control functions.

Source 1 · Source 3

Resolve the destination and test its actual behaviour

In the installed example, the offline PAS demonstration shows DATA LOG #3 in General Setup > Control/Alarm Setpoints > Action. This is the intended destination label for the reviewed Data Log 3 plan, not evidence that the connected meter is configured to use it.

The XM guide documents the file and its contents, but its older action table does not fully enumerate the additional XM destinations. No undocumented numeric action code is supplied. Check the actual installed model/PAS combination and obtain clarification if the destination is absent.

For an authorised implementation, read back the chosen trigger, limits, delays and destination. Test under a controlled, agreed condition and retrieve the resulting file. Do not assume a record will repeat continuously while a condition remains true; inspect actual timestamps and the documented setpoint transition behaviour.

Source 1 · Source 3 · Source 5 · Source 6

Count all sources of records

When several setpoints can write into one file, include them in retention planning. A simple periodic-record estimate is insufficient if additional conditional records are also generated.

Upload Data Log 3 separately, inspect timestamps and selected values, and compare with Event Log evidence where relevant. A time correlation is evidence to investigate, not proof that one event caused every observed change. Preserve the configuration and the pre-change archive with the investigation.

Source 1 · Source 4 · Source 5

Limits and checks

Check your understanding

Is Data Log 3 inherently an alarm or waveform recorder?

Show answer

No. It is a conventional configurable file; its role depends on selected fields and supported triggers.

Source 1 · Source 2

May an arbitrary threshold be used on a live installation to make a video?

Show answer

No. Use the agreed application conditions and preserve unrelated controls.

Source 3

Can periodic-only retention arithmetic ignore conditional records into the same file?

Show answer

No. Every extra recorded event uses capacity and can shorten retained history.

Source 1 · Source 4

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