After the fix, the automatic voltage regulator response matches its approved baseline and the power system stabilizer is validated against that response. Use a condition-based maintenance program tied to manufacturer instructions and plant or utility requirements; IEEE Std 421.2-1990 provides guidance for identifying, testing, and evaluating excitation-control dynamics, but it does not define a periodic in-service test interval.
Maintenance Basis and Prerequisites
Before anything else, confirm which documents govern the installed excitation system. A calendar interval without equipment-specific limits, acceptance criteria, and operating conditions does not establish a valid test program.
- Retrieve the current manufacturer manual for the installed
AVRandPSS. Obtain replacement documentation through the manufacturer’s official support channel if the plant copy is missing. - Identify every manufacturer-prescribed inspection, functional test, tuning activity, and maintenance interval.
- Check plant procedures and applicable utility or grid requirements for additional test events or reporting obligations.
- Use
IEEE Std 421.2-1990, IEEE Guide for Identification, Testing, and Evaluation of the Dynamic Performance of Excitation Control Systems, to structure dynamic-performance evaluation—not to invent a calendar interval it does not specify. - Collect the approved settings, prior response records, study model, and last test report. Mark any undocumented setting as unresolved before testing.
| Basis | What it controls | Required confirmation |
|---|---|---|
| Manufacturer manual | Equipment-specific maintenance and tuning | Instructions match the installed equipment and configuration |
| Plant or utility program | Test triggers, approvals, records, and reporting | Current procedure and responsible engineering authority identified |
IEEE Std 421.2-1990 |
Dynamic-performance test and evaluation framework | Applicable test method selected without assigning an unsupported interval |
Do not move on until the governing documents, present settings, and last accepted baseline are under change control.
Test Scope and Acceptance Criteria
Define the test boundary before applying any disturbance. “Testing the AVR” can mean checking static regulation, dynamic response, limiters, signal paths, or the complete excitation-control loop. Those tests require different operating conditions and measurements.
- State whether the work is a maintenance check, investigation, post-modification test, or tuning activity.
- List the signals to record, including the controlled voltage, regulator output, generator response,
PSSinput and output where accessible, and any limiter or mode indication relevant to the procedure. - Record the generator operating condition and system configuration so the result can be compared with the baseline or study case.
- Define acceptance criteria from the manufacturer procedure, approved study, or plant engineering specification. Do not create settling-time, overshoot, gain, or damping limits from judgment during the test.
- Identify what changed since the last accepted test: regulator settings, excitation hardware, sensing circuits, software configuration, generator work, or the represented power-system model.
The PSS acts through the excitation system, so its effective phase and gain depend on the response of the regulator and connected plant. That coupling makes an AVR response change a direct trigger for reassessing PSS tuning. Do not move on until the recorded signals, operating case, disturbance method, and pass criteria are approved.
AVR Dynamic-Response Test
Apply the manufacturer-approved method for the installed regulator. The test input and plant condition must come from the approved procedure; using an arbitrary disturbance can activate limits or produce a response that cannot be compared with the baseline.
- Verify the active control mode and confirm that the loaded settings match the controlled copy.
- Check voltage-sensing and excitation feedback signals for plausible values before introducing a test input.
- Start synchronized recording of the selected input, controlled quantity, regulator output, generator response, and status indications.
- Apply the prescribed input and capture the full response without changing tuning during the run.
- Check for unexpected limiter action, saturation, discontinuities, sustained oscillation, or a response shape that differs from the accepted record.
- Repeat the test under the same documented conditions when repeatability is part of the acceptance procedure.
A changed waveform does not automatically justify tuning. First separate an actual control-response change from different loading, network configuration, signal scaling, active limits, or data-acquisition setup. Do not move on until the AVR result either meets the approved baseline or has a documented deviation requiring engineering action.
Concurrent PSS Performance Test
Test the PSS whenever the AVR is tested. A regulator-only pass does not prove damping performance because the stabilizer’s output passes through the excitation-control path that was just evaluated.
- Confirm the intended
PSSenable state, input-signal validity, output path, and any active blocking or limiting indication. - Verify that the software or stability-study model represents the settings and configuration present in the equipment.
- Run the approved stabilizer-performance test or engineering study across the required operating cases.
- Compare the measured response with the study objective and accepted record. Evaluate damping behavior, repeatability, and interaction with the regulator rather than judging only whether the stabilizer reports “enabled.”
- If the regulator response changed, stop release of the existing
PSStuning until the tuning study and field verification are completed.
Linearized power-system models can support parameter selection and stability evaluation, but the model must match the field configuration. Do not move on until the PSS signal chain is functional and its performance is acceptable with the tested AVR response.
Retuning Decision and Recurring Pitfalls
| Observed condition | Required action | Proof before release |
|---|---|---|
AVR response matches the accepted baseline |
Evaluate PSS performance without automatically changing parameters |
Coupled test meets approved criteria |
AVR response changed |
Reassess and, where required by the study, retune the PSS
|
Updated study and field result agree |
PSS response is poor while AVR is unchanged |
Check enable logic, signal scaling, configuration, limits, and model alignment before tuning | Fault corrected or revised tuning validated |
| Only a software study has been completed | Perform the approved field verification | Recorded plant response matches the accepted model objective |
| No reliable baseline exists | Create a controlled baseline using the approved test method | Settings, operating case, traces, and acceptance decision archived |
Recurring errors include treating IEEE Std 421.2-1990 as a maintenance-frequency mandate, testing the regulator without the stabilizer, retuning before checking signal integrity, and comparing tests performed under different plant conditions. Do not move on until the cause of every deviation is assigned to configuration, instrumentation, operating condition, equipment response, or tuning.
End-to-End Verification and Release
- Load the approved final
AVRandPSSsettings and independently compare them with the controlled record. - Restore the intended operating modes, signal paths, limits, and enable conditions specified by the plant procedure.
- Repeat the approved coupled-response test with synchronized recording.
- Confirm that the regulator response meets its acceptance criteria and that the stabilizer produces the required damping behavior without unexpected blocking, limiting, or oscillation.
- Archive settings, model revision, operating condition, raw traces, evaluated results, deviations, approvals, and the event that will trigger the next test.
Release the system only after the final coupled AVR/PSS response is repeatable and matches the approved acceptance record.
FAQ
What happens if the AVR response changes but the PSS is not retuned?
The stabilizer continues acting through a different excitation-system response, so its existing tuning may no longer deliver the intended damping. Reassess the model, retune where the study requires it, and repeat the coupled field test.
What happens if IEEE Std 421.2-1990 is used as the test interval?
IEEE Std 421.2-1990 guides dynamic-performance identification, testing, and evaluation but does not state a periodic in-service AVR interval. Set the maintenance trigger from the manufacturer manual, plant program, applicable utility requirements, and equipment or configuration changes.
What happens if the stability study passes but the field test does not?
Check model-to-plant settings, signal scaling, operating condition, active limits, and network configuration. Correct the mismatch, repeat the approved test, and accept the work only when the final recorded AVR/PSS response meets the controlled criteria.