Why this validation matters
Track specified active power and displacement angle at the rectifier while controlling the common DC link and measuring net exported power through the NPC stage.
Several different numerical or control assumptions can produce visually plausible plots. The validation must establish that the observed trend comes from the intended physical mechanism rather than mesh, solver, controller or boundary-condition artifacts.
First-pass physical and numerical checks
- State the direction convention for rectifier and NPC measured power.
- Calculate THD over a stable integer-cycle window using a defined sampling method.
- Separate rectifier power tracking accuracy from the NPC export and power losses.
- Measurement cross-check: Commanded versus measured rectifier active power and displacement angle.
- Measurement cross-check: Rectifier current THD and fundamental phase displacement.
Challenge the model under changed inputs
- Case 1: uncontrolled rectifier loading. Establish a reference case, change one physical assumption and compare the same metrics across runs.
- Case 2: PWM rectifier without NPC regeneration. Establish a reference case, change one physical assumption and compare the same metrics across runs.
- Case 3: combined rectifier–NPC active emulator. Establish a reference case, change one physical assumption and compare the same metrics across runs.
Quantities to retain for audit
- Archive commanded versus measured rectifier active power and displacement angle with units, time window, data export format and configuration identifier.
- Archive rectifier current thd and fundamental phase displacement with units, time window, data export format and configuration identifier.
- Archive upper/lower dc-link capacitor voltages and neutral-point imbalance with units, time window, data export format and configuration identifier.
- Archive npc grid-side active power and net grid import/export with units, time window, data export format and configuration identifier.
What would invalidate a comparison
A well-tracked load command does not necessarily imply net-zero grid power. Compare rectifier input, NPC export and converter losses while monitoring DC-link energy accumulation.
Do not use mismatched operating conditions or different normalization conventions to claim improved performance. Report the numerical tolerance or controller sampling time where it materially affects the result.
Reporting checklist
Record model fidelity and exclusions; name the data source for each parameter; label whether a result is simulated, measured or calculated from another quantity.
Validate repeatability before expanding parameter sweeps, and preserve a baseline output so later studies can be reproduced.
Related project watch pages
Watch the relevant simulation output first, then use this article as a technical review or experimental planning guide.
Engineering research support
For the underlying MATLAB/Simulink, COMSOL, ANSYS HFSS or power electronics model, verification of solver settings, and documented outputs, contact the MATLAB Projects Code research team. Articles describe engineering validation approaches and are not a substitute for measured validation data.
Contents are for representative purposes; actual content may vary.