PAS · PM296
PM296: 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
PM296 recording
About this recording and model
Follow an online PM296 setup upload and configuration inspection using COM9 over RS-485. 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.
Select the intended meter
Select the PM296 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 COM9, device address 96, 19,200 baud and Modbus RTU. A saved connection address alone is not a successful response.
Keep the existing site file
Make a separate copy of the current site database before the upload so existing offline work can be recovered. Keep a dated backup that identifies the intended meter.
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.
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.
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. 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.
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. The PM296 example shows CT primary 500 A and wiring mode 4LN3; these are existing settings, not a new configuration sent by this lesson.
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.
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.
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.
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.
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 memory screen displays 1,029,856 total bytes and 17,856 free bytes for this snapshot. Data Log 1 occupies 1,012,000 bytes: 23,000 records × 44 bytes. These screen values do not define the memory fitted to every PM296.
| Area | Recorded setup | What it means |
|---|---|---|
| Data Log 1 | Wrap-around; 23,000 maximum records; 17 logged records; 44 bytes per record; 9 parameters | Capacity and records already stored are separate. |
| Selected parameters | V1, V2, V3, I1, I2, I3, total kW, total kvar, total kVA | The selected values share one record. |
| Setpoint 1 | Minute conditions 0, 15, 30, 45 joined with OR; Data Log action targets 1 | Check the logic and destination together. |
| Event Log, Data Logs 2–16, Waveform Logs 1–2 | Shown Free in this setup | Unallocated files do not establish absence of the model capability. |
| Waveform Recorder | Blank rows in this template | The model-specific guide defines two historical waveform logs; generic blank rows do not add recorders. |
| Programmable Min/Max Log | Only the first selection is populated in this view | Inspect this separately from the periodic Data Recorder. |
Recorded PM296 memory screen, PAS clock 08/11/26 23:05:24; current-template take 01/take 02. PM296/RPM096 ASCII BG0291 Rev.A3 pages 8–9, 16, 24, 27 and 54–56 distinguish partitions, record contents, Min/Max setup and logged counters.
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 template | Calculation | Conditional capacity |
|---|---|---|
| PM296 Data Log 1 | 23,000 ÷ 96 | About 239.6 days, roughly 240 days |
Calculated training example from the recorded allocated count and the stated single-trigger assumption. Inspect the actual saved timestamps and data gaps separately.
Two waveform logs, two record formats
The PM296/RPM096 guide describes two historical waveform partitions. Each recorded waveform record contains the three phase-voltage and three phase-current channels. Both formats hold 512 samples per channel, but they spread those samples across different numbers of cycles.
The record lengths below do not set a universal maximum event duration. A longer event may require several records. Real-time waveform monitoring is also a separate operation: viewing a current waveform does not prove that a historical recorder has saved an event.
| Historical log | Sampling | Cycles per record | What to notice |
|---|---|---|---|
| Waveform Log 1 | 32 samples per cycle | 16 | A longer time span in each record, at the lower sampling rate. |
| Waveform Log 2 | 128 samples per cycle | 4 | More samples within each cycle, with a shorter time span per record. |
| Both logs | 512 samples per channel | Depends on the log | Six recorded voltage/current waveforms; use the correct log when planning memory. |
PM296/RPM096 ASCII guide BG0291 Rev.A3, printed/PDF page 69.
A record is not always a complete event
The PM296 Basic Setup description allows a compound waveform series of up to 2,560 cycles in 160 consecutive records of 16 cycles. Its total-series setting is rounded upward to a multiple of 16. This describes the 16-cycle record behaviour; do not apply the same limit or timing rules automatically to the four-cycle high-resolution log.
A zero total-series setting means automatic selection. The documented starting point is one 16-cycle record. When a voltage-disturbance trigger remains active beyond that record, recording can continue in adjacent records while the waveform remains disturbed, subject to allocated memory. Do not read zero as ‘record nothing’.
The same Basic Setup table gives a pre-event range of 1–8 cycles. Confirm which controls and units the installed PM296 firmware exposes before teaching an exact pre/post-event setup. The blank waveform setup in this recording does not establish the high-resolution log’s compound-event behaviour.
PM296/RPM096 ASCII guide BG0291 Rev.A3, printed/PDF page 12, Table 4-4 and note 3.
Size the waveform partition in records
The PM296 guide gives a waveform record size of 6,240 bytes. This is the complete waveform record; do not multiply it by six channels again. Read the available allocation on the actual meter before deciding how many records can be reserved.
For an illustrative fixed-length Log 1 exercise, a 64-cycle event uses four 16-cycle records. Keeping 20 such events needs 80 records. At 6,240 bytes per record, the waveform allocation is 499,200 bytes. This arithmetic is an example, not a statement that the demonstration meter has that amount free. It also leaves other logs to be budgeted separately.
If automatic recording allows events to grow, event lengths vary and a fixed record allocation no longer guarantees a fixed number of complete events. Review actual series lengths and archive frequently enough for the incident rate.
| Planning quantity | Example calculation | Result |
|---|---|---|
| Records per fixed-length event | 64 cycles ÷ 16 cycles per record | 4 records |
| Records for the planned history | 4 records × 20 events | 80 records |
| Waveform allocation | 80 × 6,240 bytes | 499,200 bytes |
| Remaining capacity | Read the meter and account for other files | Do not infer it from this exercise. |
Record size: PM296/RPM096 ASCII guide BG0291 Rev.A3, printed/PDF page 24, Table 4-42. Compound records: page 12. Example event count and calculation are instructional assumptions.
Choose what happens when the file fills
Wrap-around keeps accepting new records by overwriting the oldest ones. It is useful for retaining recent evidence, but an older incident can disappear before the next upload. Non-wrap stops when the partition is full; a recording gap can then continue until the file is cleared and recording can resume.
The guide’s description of circular reading is different from wrap-around storage. A read pointer can return to the first saved record without changing the file’s overwrite policy. Likewise, Restore Log returns the reading position to earlier records; it cannot recover records that were cleared or overwritten.
The PM296 guide says an existing partition must be deleted and reallocated to change its properties. Treat that as destructive work for the affected history. It does not justify saying that every partition edit clears all logs, or that Clear All Logs is always needed.
| Setting or operation | Effect | Training checkpoint |
|---|---|---|
| Wrap-around | New records replace the oldest at capacity. | Plan uploads before important incidents are overwritten. |
| Non-wrap | Recording stops when full. | Check remaining capacity and the plan for restarting recording. |
| Restore Log | Returns the read position to earlier records. | It does not undo a clear. |
| Clear or delete partition | Removes history or its allocation. | Upload, reopen and verify the archive first. |
PM296/RPM096 ASCII guide BG0291 Rev.A3, printed/PDF pages 8–9, 13 and 23.
Check the trigger and the saved result
A waveform partition can be allocated without an event ever reaching it. The trigger condition, action destination and recorder settings must agree. Inspect all actions on the selected setpoint: a training recorder action must not unintentionally operate a relay, clear a counter or reset energy.
Use an appropriate authorised test event when a live exercise is arranged. Do not create an electrical fault for a lesson. After the event, upload the log, reopen the native database and confirm event time, log number, channels and complete series length. An empty log can mean that no qualifying event occurred; it does not by itself prove that communications failed.
For analysis, use the saved waveform’s channel selection, time axis, markers and zoom. A multi-record series is easier to assess from a saved file than from individual online records. PAS supports waveform export, but a PM296 historical export still needs an actual file test before this course calls it demonstrated. Keep the native database and compare the exported event against it.
| Checkpoint | What should agree |
|---|---|
| Identity | The selected PAS site, connected model and intended waveform log. |
| Trigger | The intended condition, limits, delays and recorder-only actions. |
| Allocation | The required records fit in the selected partition without relying on unverified free memory. |
| Archive | The saved file opens and contains the required event, channels and series. |
| Export | A compatible viewer reopens the exported event with matching time, channel names, units and sample information. |
PM296/RPM096 ASCII guide BG0291 Rev.A3, pages 49–51; PAS Getting Started BG0337 Rev.A2, pages 21–24 and 32–38. Export capability: SATEC Australia PAS product page.
Pro Tip: budget events, then plan uploads
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.
Periodic data logging and waveform recording answer different questions. A five-minute data log adds records on a known cadence. A triggered waveform file grows when qualifying events occur, and a compound event can use several records. You cannot turn its capacity into a reliable number of days without stating the event rate and length assumptions.
Keep a short planning note with log number, sampling format, records per event, allocated records, wrap/stop mode and upload frequency. During analysis, park the cursor away from the values and compare the saved series with its related Event log. Learn the menu route first; add shortcuts only after the correct model and destination are familiar.
Sources
- PM296/RPM096 ASCII Communications Protocol Reference Guide — BG0291 Rev.A3
Printed/PDF pages 8–9: partitions and wrap behaviour; 12: pre-event and compound series; 13: clear versus restore; 22–24: allocation and record size; 49–51: setpoint actions; 69: historical waveform formats.
- PAS Getting Started — BG0337 Rev.A2
Printed/PDF page 10, section 3.3: Upload Setups into the selected site database. Pages 21–24: recorded-log upload; page 25: opening saved files; pages 32–38: waveform analysis.
- SATEC Australia — Power Analysis Software
Features and Easy Export: PAS waveform analysis and COMTRADE capability. This does not document a completed PM296 export test.
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.