Skip to content

ARVREL v0.1.0-beta.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Aug 23:13
3576a5f

ARVREL v0.1.0-beta.1

ARVREL is a vendor-neutral Windows virtual protection relay laboratory for IEC 61850 Sampled Values engineering, education, process-bus troubleshooting, and protection-algorithm research.

This is a public beta technical preview, not a certified protection IED.

Highlights

  • live Npcap IEC 61850 Sampled Values capture;
  • PCAP and PCAPNG replay;
  • SCL-assisted stream binding, mapping, scaling, APPID, VLAN, svID, datSet, confRev, quality, freshness, and smpCnt trust checks;
  • 4I+4V one-cycle RMS phasors, symmetrical components, residual quantities, waveform and phasor instruments;
  • 50P-1, 51P, 50N, 51N, 67P, 67N, 27, 59, and 59N virtual protection elements;
  • practitioner settings and read-only active algorithm source;
  • research shadow workspace with deterministic policy validation;
  • relay LCD, pickup/trip annunciation, latched trip causes, event trace, settings identity, and evidence export;
  • remembered SCL file and Npcap adapter;
  • coherent waveform/phasor hold during SMV discontinuity recovery;
  • transport pacing hardening for ARSVIN/ARIEC61850 loopback publishing.

Release hardening

This beta includes targeted fixes for public distribution:

  • WPF LED animation reentrancy and potential UI stack overflow;
  • authoritative red operated phase/earth lenses;
  • engine-owned pickup/trip timestamp, quantity, unit, element, and phase/earth cause evidence;
  • per-element pickup timing to prevent cross-element evidence mixing;
  • operated feeder element precedence over legacy pickup labels;
  • explicit decoded IN/3I0 and VN/3V0 phasor preference with phase-sum fallback;
  • deterministic 67P phase cause attribution;
  • duplicate/out-of-order SMV telemetry without admitting rejected samples;
  • culture-invariant settings fingerprints and malformed-enum rejection;
  • immutable research shadow staging by settings fingerprint and source hash;
  • persistent crash logs under %LOCALAPPDATA%\ARVREL\logs.

Packages

Official release assets are expected to include:

  • ARVREL-Setup-v0.1.0-beta.1-win-x64.exe — per-user Windows installer;
  • ARVREL-v0.1.0-beta.1-win-x64-portable.zip — self-contained portable build;
  • SHA256SUMS.txt;
  • NuGet dependency report;
  • CycloneDX SBOM when generated by the release workflow.

The executable packages include the compiled ARIEC61850 dependency. Source-development builds still use the sibling repository layout.

Requirements

  • Windows 10 or Windows 11 x64;
  • Npcap for live capture;
  • authorized, isolated laboratory network for process-bus testing;
  • SCL file for trusted SCL-bound stream operation.

Npcap is not silently installed or relicensed by ARVREL.

Safety boundary

The public beta is virtual-output only. It does not provide:

  • physical relay contacts;
  • operational GOOSE trip;
  • MMS control;
  • switching authority;
  • IEC 61850 conformance certification;
  • IEC 60255 type-test, calibration, or protection-grade real-time guarantees.

Do not use ARVREL as the sole basis for operational protection settings, commissioning acceptance, or switching decisions.

Licensing

ARVREL source is available under GPL-3.0-or-later. An alternative commercial license may be negotiated for proprietary redistribution, OEM integration, contractual support, or other non-GPL terms. See COMMERCIAL-LICENSING.md.

Third-party components retain their own licenses.

Known beta limitations

  • unsigned community binaries may trigger Windows reputation warnings;
  • live performance depends on Windows scheduling, Npcap, adapter drivers, publisher behaviour, and host load;
  • the beta is not a hard real-time platform;
  • 46, 47, 49, 81U/O, 32, 37, 50BF, 79, 25, 86, 74TCS, and 60 are not implemented;
  • negative-sequence and memory polarization for 67N remain deferred;
  • broad clean-machine and multi-adapter field validation continues during the beta period.

Reporting

Use GitHub issues for reproducible non-sensitive defects. Use the private security-advisory workflow for vulnerabilities. Never publish proprietary substation captures or SCL files.