PAS · EM133-XM data and event logs

Data Log 16: understand the daily Billing/TOU profile

Written lesson · recording pending

Data Log 16 serves a different purpose from the conventional recorders: it holds the daily Billing/TOU profile. Its structure follows the enabled billing energy and maximum-demand profiles, rather than an arbitrary list of ordinary snapshot fields.

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

Before you start

Recognise a daily register profile

The unified guide states that new profile records are added automatically every day at midnight. The file has sections for configured energy and maximum-demand registers; each section can include summary and tariff readings.

A daily record is not a five-minute interval profile. The documented fields are register readings. Do not label them daily consumption merely because they were saved daily; establish the reading's meaning, reset behaviour and any required calculation first.

Source 1 · Source 3

Configure the billing sources and profile flags first

The register/profile setup determines which sections exist. Complete it before allocating the daily-profile file, because memory requirements depend on the selected profiles and tariffs.

  1. Inspect Billing/TOU Registers

    Open MeterSetup > Energy/TOU and select Billing/TOU Registers. Review the Source Input and intended register, measurement units and any applicable multiplier. Use actual XM options rather than a base-model register-count assumption.

    Source 2 · Source 1

  2. Read the profile flags

    Inspect TOU, Use Profile, Dmd Profile and Sum Profile. Confirm which energy registers, maximum-demand profiles and summary totals are intended. A source that is not configured, or a profile that is not enabled, need not create a downloadable section.

    Source 2 · Source 1

  3. Review the tariff schedule

    Inspect TOU Daily Profiles and TOU Calendar for the intended day types and seasonal/exception schedule. A tariff label in a report must be interpreted using this configuration.

    Source 2

Source 2 · Source 1

Inspect the daily file's allocation

Open MeterSetup > Memory/Log > Log Memory and inspect Data Log 16. Its file type should correspond to the intended TOU Daily Profile use; verify actual settings before describing it as active.

The family procedure selects the number of season tariffs and includes an additional summary parameter when summary totals are recorded. The sections arise from the Billing/TOU profile configuration. Maximum-demand profiles add to the allocation.

Use the actual reported section, parameter and record sizes for memory planning. Older source tables contain inconsistent XM section limits; this lesson gives no universal maximum or factory retention guarantee.

Source 2 · Source 1 · Source 4

Read sections and tariff columns correctly

The Data Log 16 setup view can show the first section's parameter list. That view alone does not prove that every enabled register and demand section has been inspected.

In the uploaded archive, identify the register/channel and whether its section represents energy or maximum demand. Read the summary and individual tariff fields with their actual units. Compare corresponding dates and sections, not unrelated rows.

ItemMeaning to confirm
Energy sectionWhich billing source and energy register it represents.
Demand sectionWhich enabled daily maximum-demand profile it represents.
Summary/total fieldThe total register reading, when included.
Tariff fieldsThe readings for the configured tariff registers.
TimestampThe meter's daily recording time and configured time reference.
Full PAS saved-site Data Log 16 recorder fields
Offline saved-site example; no current meter readback or configuration change. Open full-size image in a new tab

Source 1 · Source 5

Upload every required section and verify the clock

Use Logs > Upload Logs > Select Logs to include the daily Billing/TOU profile. Review the requested date range, then reopen the archive and verify the required register/profile sections and their time coverage.

Check the meter's Local Settings and the application's intended time reference before interpreting midnight records or synchronising the RTC. Do not change the clock simply to manufacture a daily record for training.

No row immediately after setup may simply mean that the next daily boundary has not occurred. Verify enabled profiles, file allocation, clock and upload selection before diagnosing missing data; do not clear the file as the first test.

Source 5 · Source 1 · Source 6

Limits and checks

Check your understanding

Is Data Log 16 a conventional five-minute snapshot log?

Show answer

No. It is the daily Billing/TOU profile, updated automatically at midnight according to the manufacturer guide.

Source 1

What should be configured before allocating this profile file?

Show answer

The billing sources, enabled energy/demand/summary profiles and tariff schedule, because they determine its structure.

Source 2 · Source 1

Does a midnight energy reading automatically equal that day's consumption?

Show answer

No. Confirm register semantics and reset history before any subtraction or daily-use calculation.

Source 1

Does the first section shown in setup prove every billing profile was archived?

Show answer

No. Verify all required enabled sections in the saved archive.

Source 1 · Source 5

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