What is the current public version?
v0.1.0-beta.6 for Windows 10/11 x64. GitHub Releases is the package source of truth.
Engineering FAQ · beta.6
These answers distinguish the shipped behavioral model from calibration, certification, manufacturer-specific hardware, and operational authority.
Current release
v0.1.0-beta.6 for Windows 10/11 x64. GitHub Releases is the package source of truth.
CURRENT_STATUS.md. Historical P* files are retained as milestone records and may describe older behavior.
No. Relay outputs, OLTC actions, and process controls are virtual only. There is no physical trip, operational GOOSE, OLTC motor, switching, or primary-equipment authority.
Yes, as a laboratory model for the virtual AVR/OLTC process. Browse/read, reports, and modeled SBO/SBOw controls exist, but accepted commands terminate inside the simulator.
Closed-loop feeder testing
The accepted wired TESTSET BI1 edge. Internal relay TripLatched may request BO1 but is never read directly as the TESTSET result or trip auto-stop authority.
The relay may still trip internally, but the TESTSET must report no external trip time and must not trip-auto-stop. This is a deliberate regression invariant.
BI2 is the wired generic ANY PICKUP input. It does not necessarily represent the pickup of the element that ultimately trips.
Another enabled element—such as an earth/time-overcurrent function—may pick up first and drive generic BO2. Operated-element P→T is correlated separately.
The TESTSET metrology clock is integer microseconds with 1 µs resolution. BI samples at 10 kHz / 100 µs. Relay acquisition/protection advances at 4 kHz / 250 µs.
No. The CMC-style profile is a behavioral modeling choice informed by relay-test-set concepts. ARVREL is not calibrated commercial test equipment and does not claim manufacturer equivalence.
Instantaneous signed terminal samples, then modeled clipping, 16-bit-equivalent quantization, 1.5 ms input/filter delay, and a causal one-cycle rolling DFT. Source-side phasors are not substituted for relay ADC input in the closed-loop path.
Definite timing starts at the first observed pickup frame. When 60 ms is exactly representable on the 250 µs relay grid, the operated-element record is exactly 60.000 ms.
Auto-stop, capture, and reset
Configured setpoints are retained for repeatability. The actual output state is explicitly OUTPUT OFF · FROZEN CAPTURE.
Not necessarily. The capture can belong to a later causal relay-processing frame. Evidence schema 9 records the relationship instead of conflating the two instants.
Once. Beta.6 uses one deterministic reset transaction that drains stale causal acquisition, clears relay state once, releases contacts/BI inputs, and shows READY TO RE-ARM only after the full postcondition.
No. Completed TESTSET timing and frozen trip/event evidence are intentionally preserved.
No. Source and relay are separate equipment authorities. If the source remains energized, protection may legitimately reassert after reset.
The transaction is bounded by a modeled 100 ms settle timeout and should expose diagnostic state. Repeated clicking should not be used to hide the underlying condition.
Transformer Differential
Yes. Run the deterministic 10-scenario self-test and synchronized internal HV/LV/neutral secondary injection first.
PASS · 10/10 · transformer-public-beta-v1.
No. It drives the existing transformer protection runtime so the UI does not duplicate 87T/REF logic.
No. Independent neutral/NGR current evidence is explicit. Calculated phase residual is not silently promoted to a neutral-CT input for REF authority.
For the external paired-SV live/replay transformer path. Internal two-sided injection is a separate no-external-stream workflow.
H2/H5 security plus context-gated external-fault/CT-saturation behavior within the documented generic model.
IEC 61850 and live capture
Only for live Sampled Values capture. Internal workflows and PCAP/PCAPNG replay do not require Npcap.
Complete windows, decode health, mapping/scaling provenance, freshness, smpCnt continuity, quality, SCL identity, svID, dataset, confRev, and source context.
Yes. Diagnostic visibility is separate from AllowsMeasurement, AllowsPickup, and AllowsTrip.
Not without explicit authorization and an approved test method. The public guidance is to use an isolated laboratory network.
Fidelity and certification
No. Timing and source behavior are deterministic software models without traceable calibration or instrument uncertainty claims.
No. The default relay profile is generic. Exact anti-alias filters, ADC topology, burdens, channel skew, electrical BI thresholds, proprietary fast paths, and manufacturer uncertainty are not claimed.
No formal conformance certification is claimed.
No. Deterministic regression tests validate software behavior only.
Responsible use
Do not publish proprietary captures, SCL files, credentials, IP plans, protected infrastructure information, or employer-confidential material. Do not use ARVREL as the sole basis for operational protection settings, commissioning acceptance, or switching decisions.