wattbench
Diagnostic Evidence

Grid-Voltage Investigations: Build the Evidence Chain

A single high reading does not identify the cause. Separate inverter telemetry, site measurements, circuit rise and network conditions before escalating.

Sources listedReviewed July 2026Our methodology
Topic
Grid voltage and inverter trips
Applies to
Grid-connected solar
Audience
Licensed solar workers
Neutrality
Manufacturer-neutral
Key takeaways
  • Start with timestamps and patterns: one event, daily recurrence and site-wide behaviour imply different investigations.
  • Keep inverter telemetry, measurements at named points and retailer or DNSP data as separate evidence sources.
  • Do not alter grid-protection settings to mask a voltage problem; settings and escalation follow the approval and current network process.

Start a job record

Give it a job or site name. Wattbench will open the right evidence prompts.

Start job record

Start with the event pattern

Record the exact event code, inverter model, time, duration, generation, site load and weather. Note whether every inverter or phase is affected and whether the event occurs at similar times on clear days. Monitoring data can establish a pattern, but it is not automatically a calibrated electrical measurement.

Name every measurement point

A voltage reading only makes sense when its location, phase, method, time and operating condition are recorded. Measurements at the inverter terminals, main switchboard and connection point answer different questions. The AC voltage rise worksheet compares two entered readings without pretending to issue a compliance verdict.

Electrical measurements and switchboard access are licensed-worker tasks. Record instrument identification and test conditions in the evidence log. Do not send an owner to operate isolators or open equipment to collect data.

Separate the site from the network

Voltage at an inverter reflects both the incoming supply and changes across the site’s AC circuit while exporting. A structured investigation compares named points under documented conditions, checks the installation and protection arrangement, and then determines whether DNSP escalation is supported. It does not jump from an app screenshot to a network conclusion.

Keep settings changes out of diagnosis

Grid response and protection settings exist to satisfy current connection requirements. Western Power’s guidance states that existing approvals remain tied to their conditions and that changing export or generation limits can require a new application. Never widen or defeat a setting simply to keep an inverter online. Preserve settings as found, approval details and every authorised change.

Prepare an escalation pack

  • Connection approval, supply and phase details.
  • Exact inverter events and a timestamped recurrence pattern.
  • Measurements at clearly named points and conditions.
  • Relevant circuit and equipment details.
  • Monitoring exports kept distinct from instrument readings.
  • Installer assessment and the specific question for the DNSP.

The grid-overvoltage playbook provides the safe sequence for packaging that evidence.

New to the jargon? Browse the glossary.

Sources

Continue this work

Did this help you move the job forward?

Tell us what is missing
Good to know

Frequently asked

Can an inverter app prove that the grid supply is too high?
It can show a useful pattern, but it does not by itself locate the cause or replace measurements taken at named points under documented conditions.
Should an installer raise the trip threshold to stop nuisance shutdowns?
Not as a diagnostic shortcut. Protection settings must remain consistent with the approved connection and current network requirements. Preserve settings as found and follow the authorised process.