PAS · EM133-XM data and event logs
Data Log 2: build a separate view of the same meter
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
- 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.
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.
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.
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.
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.
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.

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.
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.
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.
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.
- The captured action label is verified only for PAS 1.5.8.9 with the offline saved XM site. Live acceptance, configured triggers and generated records still require device readback. The old protocol action-table omission remains unresolved; no raw action code is inferred.
Check your understanding
Does Data Log 2 always contain voltage and current?
Can a Data Log 1 action be assumed to write into Data Log 2?
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. EM13x Installation and Operation Manual — setpoints (opens in a new tab)
Printed pages 106–108 / PDF pages 109–111; interval/action tables printed 171–172 / PDF 174–175
Trigger, operate/release and action semantics; exact XM destination choices must be checked in the installed PAS version.
- Source 4. 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 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 — data trend (opens in a new tab)
Printed page 157 / PDF page 160, section 9.4
Model and firmware limits remain applicable.
- Source 7. PAS 1.5.8.9 – offline XM action choices (opens in a new tab)
Full-window frame from XM-log-tour01.mp4 at 00:03:55; PAS clock 8 November 2026, 08:10:18
Shows DATA LOG #1, DATA LOG #2, DATA LOG #3 and EVENT LOG in this installed PAS offline saved-site action list. It does not establish current meter settings, active actions or universal firmware support.
- Source 8. 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.
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-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 |