PAS · EM235

EM235: back up setups, inspect logs and plan waveform recording

Start with the connected meter, upload its settings, then work through the existing recording setup. See how memory capacity, stored records, selected values and trigger actions fit together before planning a change.

Lesson and video

EM235 recording

Download EM235 video

About this recording and model

Follow an online EM235 setup upload and configuration inspection using Ethernet over the local Wi-Fi network. The displayed values are this unit’s existing settings. The inspection leaves the meter configuration unchanged.

The online setup upload and existing configuration walkthrough were reviewed against the recorded screens and model-specific manuals. No new meter settings or history archive are demonstrated.

First, upload the current settings

Keep the local site file and a log archive separately. Upload Setups reads configuration from the meter into the selected PAS site database; Upload Logs retrieves recorded history.

  1. Select the intended meter

    Select the EM235 site. Enable On-line using the PAS toolbar, then right-click the site and open Properties. Check the model, connection and status. This recorded connection uses Ethernet over the local Wi-Fi network at 192.168.1.203, device address 1 and port 502. A saved connection address alone is not a successful response.

  2. Keep the existing site file

    Make a separate copy of the current site database before the upload so existing offline work can be recovered. For the EM235, some local PAS labels are not stored in the meter; a meter upload cannot recreate all PC-side metadata.

  3. Use MeterSetup > Upload Setups

    Read the overwrite warning and confirm that the selected site database is the intended destination. Upload copies meter settings to PAS. Download Setups and Send operate in the opposite direction and write settings to the meter.

  4. Wait for Upload is complete

    The recorded transfer ends with Upload is complete. Keep the resulting site file as the configuration baseline. This message does not mean that Event, Data or Waveform history has been archived.

  5. Know which values you are viewing

    PAS remains online during this recorded configuration walkthrough. The uploaded site file provides a saved baseline for later offline work. Use Receive in a setup dialog when a fresh meter read is needed, and check the selected site and view before comparing values.

PAS Getting Started BG0337 Rev.A2, printed/PDF page 10, section 3.3: Upload Setups. PRO manual BG0612 Rev.A8 pages 92–93: online retrieval and local setup files. The online connection and completion are recording observations.

Use each setup screen for a different question

Follow the menu route first. Leave the recorded setup unchanged while learning how the screens relate.

  1. General Setup: how the meter interprets inputs

    Open MeterSetup > General Setup > Basic Setup. Review wiring mode, voltage/PT settings, current/CT settings and demand settings together. This EM235 reports HACS4CH and CT primary 50 A. The displayed secondary field is not advice to connect a conventional 5 A CT to a HACS input.

  2. Log Memory: how much space is allocated

    Open MeterSetup > Memory/Log > Log Memory. Compare Max. Records with Logged Records. Check the selected file, file type, record size and parameters or channels. Max. Events is also a capacity figure, not a count of actual events captured.

  3. Data Recorder: what each record contains

    Select Data Recorder and choose the log number. The selected list defines the values stored together in a record. The same log number can have different contents on another meter or in another site file.

  4. Control/Alarm Setpoints: when and where to record

    Return to MeterSetup > General Setup > Control/Alarm Setpoints. Read the trigger, timing or threshold, delays, logical conditions and all actions. The action chooses the destination log. Allocating a file does not create its trigger.

  5. Waveform Recorder: the shape of an event capture

    Open MeterSetup > Memory/Log > Waveform Recorder. Compare sampling rate, total duration, pre-event settings and selected channels. A waveform event can occupy several file records; periodic data-log retention arithmetic does not describe waveform storage.

  6. Keep history before changing allocation

    Use Logs > Upload Logs to save the required Event, Data, Waveform and model-specific PQ history in a separate database. Reopen it and check the required dates, channels and complete events before clearing or repartitioning. The history upload and archive checks are a separate exercise.

PAS Getting Started page 10 for setup upload and pages 21–25 for log retrieval/opening. Model-specific recorder and trigger references are listed below.

Read the recorded template without treating it as a default

These are observations from the demonstration recording on 8 November 2026. Logged counts can change while a live meter continues recording; a saved site snapshot is not a current occupancy reading.

The allocation summary displays channel/section counts 9 and 8 for Waveform Logs 7 and 8. The viewed Log 7Channels selection ticks V1–V3 and I1–I3. This mismatch is unresolved; do not turn either summary count into a physical-input specification.

The displayed total-memory number is not used here as an installed-capacity claim. Its reporting meaning has not been established for this capture.

In Configure File, PAS warns that logged data will be lost. The recording selects No and leaves the allocation unchanged. A future repartitioning exercise must first upload and inspect the required history.

AreaRecorded setupWhat it means
Event Log163 logged records; capacity 2,000; 20 bytes per recordDevice/event history is separate from periodic measured values.
Data Logs 1 and 2Each has 16 parameters, 80 bytes per record, capacity 38,400 and 15,961 logged records; wrap-aroundThe capacity is not the actual number of records stored.
Data Log 1 contentsPhase voltages/currents, power, power factor and phase voltage/current THDA general measurement trend in this existing template.
Data Log 2 contentsDemand and energy values, plus I4 and InInspect actual parameter names and units; the file number alone does not specify its purpose.
Setpoint 1TIME / MINUTE INTERVAL / equals 15; actions DATA LOG #1 and DATA LOG #2One timing condition directs records to two configured lists.
Data Logs 9 and 10EN50160Compliance and EN50160Harmonics types; 24 logged records in each sampled viewThe configured file name is not proof of a compliance result.
Data Logs 15 and 16Monthly TOU profile: 7 logged records; daily TOU profile: 167Profile history has a different cadence and purpose from an interval trend.
Waveform Log 7Fixed; 32 samples/cycle; 64 maximum cycles; 3 pre-event cycles; 4,000 maximum/4,000 logged records; 1,000 maximum eventsFour file records per sample series by 32 × 64 ÷ 512; logged records do not establish 1,000 complete events.
Waveform Log 8Fixed; 128 samples/cycle; 16 maximum cycles; 3 pre-event cycles; 2,000 maximum/0 logged records; 500 maximum eventsFour file records per sample series by 128 × 16 ÷ 512.
PQ recorderDips, swells and interruptions select On Start with Waveform Log 7; transient overvoltage selects Waveform Log 8These are recording assignments, not proof that an event occurred.

EM235 recording: take 02 at 60 seconds, PAS clock 22:57:45, for Event Log and DL1/DL2 counts; take 01 at 325,580–635 seconds and memory snapshot 22:51:59 for contents, trigger and waveform/PQ settings. PRO manual pages 120–137 explains the separate roles.

Estimate retention, then check the saved history

For one record every 15 minutes, 24 × 60 ÷ 15 gives 96 records per day. This assumes that the periodic action creates exactly one record per interval and that no additional trigger adds records. It does not establish the date range or completeness of the archive.

This templateCalculationConditional capacity
EM235 Data Log 1 or 238,400 ÷ 96400 days

Calculated training example from the recorded allocated count and the stated single-trigger assumption. Inspect the actual saved timestamps and data gaps separately.

Choose the detail and time span of an event

The Australian PRO datasheet describes eight waveform recorders and seven simultaneous AC channels: V1–V3 and I1–I4. Sampling choices are 32, 64, 128 or 256 samples per cycle. The recorder holds 512 samples in a single-channel record; longer events occupy several records sharing a series number.

Increasing samples per cycle gives more points within each cycle. At the same event length and channel count, it also consumes more records. Increasing event length or the number of recorded channels adds storage as well. Choose each setting for the disturbance you need to investigate, rather than selecting every maximum.

Sampling rateCycles in one 512-sample channel recordConsequence at a fixed event length
32 samples/cycle16Lowest record use among these choices.
64 samples/cycle8Twice the records used at 32 samples/cycle.
128 samples/cycle4Four times the records used at 32 samples/cycle.
256 samples/cycle2Eight times the records used at 32 samples/cycle.

Australian PRO datasheet, August 2025, page 3; PRO manual BG0612 Rev.A8, printed/PDF pages 136–137. Cycles per record are calculated as 512 divided by sampling rate.

Include the lead-up to the event

Pre-event recording shows the waveform before the trigger. The manual’s Before Cycles range is 1–20, while Cycles per Series describes the total duration of the event record. The before portion belongs within the total; it is not extra time to add to it.

The table below gives the manual’s total-cycle ranges. It is a reference for planning, not a promise that every combination of pre-event, duration and sampling settings will be accepted by every firmware. Confirm the actual controls and readback. Use the populated controls and their units on the selected meter when relating pre-event, total and post-event fields.

Samples per cycleDocumented total cycles per series
3216–10,848
648–5,424
1284–2,712
2562–1,356

PRO manual BG0612 Rev.A8, printed/PDF page 137. The Australian datasheet page 3 also describes 20 pre-fault cycles.

Turn the event plan into a memory allocation

Use three separate quantities: records per event, events to retain, and recorded channels. The manual gives records per event = samples per cycle × cycles per event ÷ 512. Multiply that result by the number of events to obtain the record allocation. Check PAS’s accepted value if a calculation is not a whole number; do not assume a rounding rule.

The documented waveform record size is 1,072 bytes per channel. The allocation relationship is 1,072 × channels × records per event × number of events. If PAS already reports the total file size, do not multiply that displayed size by channels again.

The manual’s example uses 64 cycles at 32 samples/cycle: four records per event. Twenty such events require 80 records. With seven recorded AC channels, the illustrative allocation is 600,320 bytes. This is a planning calculation, not a measurement of available memory on the demonstration unit.

QuantityExample calculationResult
Records per event32 × 64 ÷ 5124
Record allocation for 20 events4 × 2080
Bytes for seven channels1,072 × 7 × 80600,320 bytes
Same duration at 128 samples/cycle128 × 64 ÷ 51216 records per event
20 events, seven channels at that rate1,072 × 7 × 16 × 202,401,280 bytes

PRO manual BG0612 Rev.A8, printed/PDF pages 130 and 136. The second sampling-rate comparison and byte totals are calculations using the documented relationship; the planned 20-event history is an example.

Protect the history when memory fills or changes

The PRO documentation specifies 16 GB of onboard recording memory, shared between recording files. That specification is not the same as the free capacity of one waveform log. Use the connected meter’s received allocation to plan the change; other files and existing records matter.

Wrap-around overwrites the oldest records as new ones arrive. Non-wrap stops recording when the file fills, until it is cleared. Decide whether the priority is recent rolling evidence or preserving a finite capture window, then set an upload plan that supports that choice.

File allocation is static until it is reorganised, and the manual describes defragmentation when allocation changes. This does not establish that every edit erases every log. Follow the actual affected-file warning and preserve all required history first; do not add a routine Clear All operation.

ChoiceBenefitCheck before relying on it
Wrap-aroundContinues retaining recent records.An older incident can be overwritten before upload.
Non-wrapKeeps the allocated file from overwriting itself.New incidents are missed after the file fills.
Larger allocationCan hold more records with unchanged recording settings.Check free memory and the effect on other recording files.
Repartition or deleteChanges how storage is assigned.Upload and reopen the required archive before proceeding.

PRO manual BG0612 Rev.A8, printed/PDF pages 129–130; Australian PRO datasheet, August 2025, page 3.

Make the trigger and recorder work together

Allocating a waveform file does not specify when to record it. A setpoint evaluates its conditions and performs the chosen actions. The PRO manual describes up to four conditions and four actions per control setpoint, so inspect the full row rather than only the waveform destination.

Choose a suitable available recorder and setpoint for a training exercise. The manual identifies Waveform Log 7 and Waveform Log 8 as factory PQ assignments: Log 7 serves PQ events including transients and short-duration events, while Log 8 serves harmonic events. Do not overwrite those assignments merely because their log numbers are convenient.

Keep a training action limited to the intended recorder. Do not add relay operations, energy resets, counter clearing or network cross-triggering unless they form part of a separately planned task. A future live test should use an appropriate authorised event; creating a physical electrical fault is not a training method.

When several setpoints request the same logging target at the same time, the manual describes shared logging that avoids repeated records for that instant. Do not estimate storage by multiplying identical simultaneous requests as if each must create another event.

PRO manual BG0612 Rev.A8, printed/PDF pages 120–123 and 137. Exact installed action labels and trigger behaviour remain to be captured in a live exercise.

Check the saved event before exporting it

After a live capture, use Logs > Upload Logs and reopen the saved database. Check the event time, selected channels and complete series. An online waveform view may contain only displayed data unless it has been saved. Retain the native database even when another file format is needed.

Open the saved waveform and use Channels to show the relevant inputs. Review its time axis, overlapped or separate traces, markers and zoom. The RMS, spectrum and phasor views help examine different properties of the same recording; they do not replace checking that the required channels and time span were captured.

For manual export, the PRO manual describes the Export control, selecting the source database/table, choosing a destination, filename and output format, then saving. The Australian datasheet identifies COMTRADE and PQDIF waveform export through PAS. Reopen the exported event in a compatible viewer and compare its time, channels, units and sample information with the native record.

Upload Scheduler has separate export settings for converting selected tables during upload. Schedule configuration, recorder triggering and export are different operations. This lesson explains their relationship; it does not claim that an automated export or a historical waveform conversion has been tested.

CheckpointEvidence to look for
Identity and timingCorrect EM235 site, event date/time and understood clock basis.
CaptureRequired channels and a complete event series, including the intended lead-up.
Native archiveThe database reopens and the required history is present.
ExportThe exported file reopens with matching event and channel information.
Future capacityThe allocation and wrap/stop mode support the next upload period.

PRO manual BG0612 Rev.A8, printed/PDF pages 177–180, 187–195; Australian PRO datasheet, August 2025, page 3.

Pro Tip: keep recording, upload and export rates separate

Expand the + beside the selected site, then expand Memory/Log. Select Log Memory to inspect allocation or Waveform Recorder to inspect recording choices. Widen the Site Tree until the full programming-menu names fit. This reaches the same screens as the menu route above.

A five-, fifteen- or thirty-minute data log has a predictable periodic cadence. A waveform recorder uses space when an event triggers it, according to sampling rate, event length and channels. A large memory specification alone cannot tell you how many days of waveform incidents it will retain.

Write the assumptions beside any capacity estimate: event length, sampling rate, channels, allocated records and expected event rate. Then choose an upload frequency that protects the required history. Exporting more often does not change the meter’s sampling rate or trigger condition.

Use menu navigation first and add shortcuts after the workflow is familiar. During analysis, move the cursor away from numbers, keep the full PAS context visible and compare the waveform with its related Event or PQ entry before drawing a conclusion.

Sources

Revision and review

Lesson revision 20261108-online-setups. The online setup upload and existing configuration walkthrough were reviewed against the recorded screens and model-specific manuals. No new meter settings or history archive are demonstrated.

Recording review does not constitute public release.

Back to PAS