Documentation authority
Know which document wins when older design notes disagree.
Current shipped status
Beta.6 product surface, closed-loop authority, timing profile, reset semantics, Transformer/AVR status, validation, and safety boundary.
Published releaseRelease status and integrity
Version, package assets, pinned engine, SHA-256, SBOM/provenance, and public claim boundaries.
Release notesBeta.6 release notes
Release-specific changes and retained capabilities for the selected public package.
P0_*, P1_*, and other milestone P* documents record engineering progression. They are useful history, not the current product-status authority.Start here
First evaluation and daily operation.
Closed-loop quick start
Run a feeder fault through TESTSET T0, relay acquisition, BO contacts, BI timing, auto-stop, frozen capture, and one-click re-arm.
Complete workflowUser guide
Feeder, process bus, Transformer Differential, AVR/MMS, evidence, troubleshooting, and safety.
Release integrityDownload and verify
Select an official beta.6 package and validate SHA-256 before evaluation.
Common questionsEngineering FAQ
Timing authority, BI semantics, reset/re-arm, transformer injection, MMS, Npcap, and limitations.
Closed-loop timing
Understand what beta.6 changed.
Authority and data flow
Separate TESTSET, virtual wiring, relay front end, protection, contacts, BI inputs, process-bus, transformer, and AVR paths.
Implementation detailMetrology-grade timing engine
1 µs clock, 10 kHz BI, causal acquisition, timing correlation, and behavioral profile details.
Evidence semanticsExternal timing and trust
Why generic BI2, operated-element pickup, relay trip request, BI1 measured trip, and process-bus trust are distinct authorities.
IED-specific guides
Feeder, transformer, and AVR workflows.
Protection engineering
Measured quantities, settings, pickup/timing, closed-loop TESTSET evidence, restraint, and re-arm.
TransformerTransformer public test
10-scenario self-test, synchronized two-sided injection, REF neutral requirements, and paired-SV evaluation.
AVR / MMSAVR IEC 61850 test guide
Virtual plant, OLTC authority, reports, controls, and the simulator-only process boundary.
Process bus and research
Investigate external data and reproduce engineering claims.
Process-bus workflow
Identity, mapping, scaling, continuity, quality, SCL binding, and trust.
Research hub
Signal processing, continuity, directional protection, related work, and validation.
Validation matrix
Stable public scenarios mapped to source and deterministic tests.
Laboratory exercises
Repeatable learning exercises for measurement, protection, trust, and evidence.
Release, governance, and safety
Review the controls around the product.
Safety and fidelity boundaries
Virtual-only authority, behavioral timing, calibration/certification non-claims, live-network constraints, and data handling.
Public-site maintenance
Canonical URLs, metadata, structured data, sitemap, version synchronization, and CI gates.
Evidence-gated roadmap
Future device-specific fidelity and research gates without turning aspirations into shipped claims.
Documentation boundary
Documentation cannot expand equipment authority.
ARVREL remains virtual-output laboratory software. Documentation, timing models, tests, reports, and research do not constitute calibration, IEC 61850 conformance, IEC 60255 type-test evidence, commissioning acceptance, or switching authority.