PAS · EM133-XM data and event logs
Choose the right EM133-XM log
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
Actual moving PAS saved offline-site inspection, plus separately labelled historical live configuration/log uploads recorded on 7 November 2026. No new configuration write, memory clearing, or Event Log report demonstration. The portrait Short retains full PAS above a same-time detail view.
Michael (Australian) narration from ElevenLabs. Edited PAS screen recording.
Chapters
Feature Short
Download MP4 · SRT captions · Use the video controls for captions and fullscreen; Escape returns to this lesson.
About this recording
Actual moving PAS saved offline-site inspection, plus separately labelled historical live configuration/log uploads recorded on 7 November 2026. No new configuration write, memory clearing, or Event Log report demonstration. The portrait Short retains full PAS above a same-time detail view.
Michael (Australian) narration from ElevenLabs. Edited PAS screen recording.
The EM133-XM provides different records for different questions. Start with the question you need the history to answer, then inspect the file's configuration and uploaded contents.
Australian narrated walkthrough with written guidance.
Before you start
- Use the intended EM133-XM site and verify its model, connection and firmware before treating settings as live.
- Complete the existing Upload and verify your logs before changing memory lesson before any operation that can alter or remove retained records. Upload Setups and Upload Logs preserve different information.
Compare the files before choosing a report
The XM-specific file table lists Data Logs 1, 2 and 3 alongside the Event Log and Data Log 16. The number in a log name identifies a destination; it does not define an application's measurement purpose.
| File | What it records | What to inspect |
|---|---|---|
| Data Log 1 | Selected measured parameters when its configured trigger records them. | Parameter list, units, trigger, action and retention. |
| Data Log 2 | A separately configurable conventional parameter file on XM. | Its own parameter list and actual trigger destination. |
| Data Log 3 | Another separately configurable conventional parameter file on XM. | Its own purpose, trigger and record capacity. |
| Data Log 16 | Daily Billing/TOU energy and maximum-demand profile sections, as enabled. | Billing sources, profile flags, tariffs, clock and available sections. |
| Event Log | Time-tagged configuration changes, resets and device diagnostics. | Time, cause/source, effect and the surrounding sequence. |
Separate contents, trigger and allocation
A conventional recorder has three separate design decisions: which quantities appear in each record, when the recording action occurs, and how much history its allocation can retain.
Changing a file name or selecting a log in PAS does not start recording. An allocated but untriggered file can remain empty. A working trigger with the wrong destination can place records in a different file.
The XM datasheet specifies up to 16 parameters/channels for interval recording. Think of those as columns within each timestamped record. Retained days depend on each file’s record capacity and how often records are added, including any event-triggered additions. Confirm the actual allocation before estimating retention.
Follow the PAS menu route
Use the menu workflow first. Keep PAS maximised, the full Site Tree and clock visible, and expand the selected site with + where needed. Read the selected log number aloud before each comparison; move the cursor beside the fields when pausing to explain them.
Compare Data Logs 1, 2 and 3
Open MeterSetup > Memory/Log > Data Recorder. Select Log No. 1 and read its name and populated Group/Parameter rows. Change to Log No. 2, then Log No. 3, pausing to show the selected number and each file’s contents. A saved offline site is a configuration example, not current meter readback.
Connect contents to memory allocation
Select Log Memory. Locate the corresponding Data Log 1, 2 and 3 rows and compare file type, Number of Records, parameter count and reported size. Inspect the partition properties without applying changes. The number of values in a record and the number of records retained are different settings.
Open historical records
Use Logs > Upload Logs for a connected upload. To inspect a saved archive, use File > Open, select Access Database (*.mdb), choose the database and the intended table, then Open.
Find the trigger, action and parameter lists
Keep the manual beside PAS. Near the end of the EM13x Installation and Operation Manual, Appendix D lists Setpoint Triggers and Actions: Table 25 begins at printed page 169 (PDF page 172), and Table 26 is at printed page 172 (PDF page 175). Use these to distinguish the condition that starts an action from the action itself.
Appendix E, Parameters for Data Monitoring and Logging, starts at printed page 173 (PDF page 176). Table 27 pairs PAS abbreviations with their meanings and groups. Find the Group first, then the Parameter; check units and whether the quantity is instantaneous, demand or accumulated energy.
Return to MeterSetup > General Setup > Control/Alarm Setpoints to inspect the trigger and destination, then MeterSetup > Memory/Log > Data Recorder to inspect recorded fields. The older family action list does not enumerate every XM destination, so compare it with the selected model’s actual PAS choices.
Give separate files a clear application purpose
ILLUSTRATIVE design: one conventional file could hold energy-related quantities, another voltage/current trends and another a condition-focused set of parameters. These are teaching examples, not factory-assigned roles or claims about the current demo setup.
Separate files can keep different parameter selections and recording needs understandable. They still share the meter's finite memory, so calculate retention for every active file and include any additional event-triggered records.
Treat the archive as the evidence
Record settings explain what was intended. Uploaded rows show what was retained. Check both before concluding that a logging arrangement works.
Verify each required file, time range, field names, units and continuity. A daily profile does not replace a short-interval log; an Event Log does not replace measured-value history. Preserve all required records before clearing or repartitioning.
Limits and checks
- The written procedure is not evidence that a live setting was changed or that new records were generated. Check the selected device, firmware and current readback.
- Older generic tables omit some XM file/action entries. Use XM-specific setup evidence and the actual installed controls; do not invent raw protocol codes.
Check your understanding
Are Data Logs 1, 2 and 3 permanently assigned to energy, voltage and alarms?
Does an allocated log prove that records are being generated?
Which file helps investigate configuration changes?
Show answer
The Event Log provides time-tagged configuration/reset/diagnostic history; compare it with relevant data logs where needed.
Sources
- Source 1. EM133 / EM133-XM Modbus Reference — log organisation and XM files (opens in a new tab)
BG0640 Rev. A1, printed/PDF pages 14–16 and 63–64
The file-setup table explicitly includes XM Data Logs 2 and 3; older generic file-ID/action tables are incomplete for these files.
- Source 2. EM13x Installation and Operation Manual — data recorder (opens in a new tab)
Printed pages 122–124 / PDF pages 125–127, section 5.5.3–5.5.4
General recorder procedure and documented base-family defaults; not evidence of the selected XM site's current settings or universal capacity.
- Source 3. EM133 / EM133-XM Modbus Reference — daily profile contents (opens in a new tab)
Printed/PDF page 15 and pages 74–75, Billing/TOU Daily Profile Data Log
Daily midnight recording; enabled energy and demand sections contain summary/tariff register readings. Do not infer daily-consumption subtraction/reset rules or a universal maximum section count.
- Source 4. EM13x Installation and Operation Manual — Event Log (opens in a new tab)
Printed page 121 / PDF page 124 and printed page 156 / PDF page 159
Model and firmware limits remain applicable.
- Source 5. PAS Getting Started — upload and open log files (opens in a new tab)
BG0337 Rev. A2, printed/PDF pages 21–22 and 25; configuration upload page 10
Model and firmware limits remain applicable.
- Source 6. EM13x Installation and Operation Manual — memory allocation (opens in a new tab)
Printed pages 119–121 / PDF pages 122–124, section 5.5
Model and firmware limits remain applicable.
- Source 7. EM133-XM datasheet — interval recording capacity (opens in a new tab)
TBV1.1, PDF page 2, Event and Interval Data Recording
XM-specific datasheet lists up to 16 parameters/channels. Older family and unified-protocol tables list nine; confirm the selected model, firmware and PAS allocation before changing a file.
- Source 8. EM13x manual — setpoint and recording reference lists (opens in a new tab)
BG0491 Rev. A15, Appendix D printed169–172/PDF172–175, Tables25–26; Appendix E starts printed173/PDF176, Table27
Use family tables to interpret PAS abbreviations. The older action table lists Data Log1; additional XM destinations must be checked in the selected XM setup.
Revision and review details
| Revision | Change and reason | Review / 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-v2 |
| 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 |
| 20261108-draft-v2 8 November 2026 | Added the narrated log tour, revised portrait Short, captions and measured chapter navigation. Connect the source-checked lessons to actual saved-site PAS views and reusable feature content. | Independent technical/documentary checks passed for the selected media; Gemini feedback adjudicated. Human editorial acceptance remains pending. 20261108-draft-v1 |
| 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-v2 |