Relay outputs
BO contacts, trip latch, and TESTSET BI wiring are software models only. There is no physical trip contact or operational GOOSE trip authority.
Virtual-only authority
No software action leaves the simulator as primary-equipment authority.
AVR / OLTC
Tap movement and interlocks act on the simulated transformer plant. There is no physical OLTC motor command.
MMS controls
Browse/read/report/control behavior exists, but modeled commands terminate inside the virtual AVR/OLTC process and provide no switching authority.
Timing and metrology
The beta.6 timing engine is behavioral, not calibrated.
Explicit deterministic clocks
1 µs TESTSET clock resolution, 10 kHz BI sampling, and 4 kHz relay acquisition define the shipped reference model.
External virtual-I/O timing
Relay BO behavior, virtual wiring, BI sampling, deglitch/debounce, and accepted BI edges are represented causally.
Hardware calibration or uncertainty
No traceable calibration, commercial test-set accuracy class, instrument uncertainty budget, or named-device timing equivalence is claimed.
Relay fidelity
Generic numerical-relay behavior is not a manufacturer-specific internal model.
The default closed-loop relay profile models instantaneous terminal samples, signed clipping, 16-bit-equivalent quantization, 20 A RMS current full scale, 300 V RMS voltage full scale, 1.5 ms behavioral input/filter delay, 4 kHz acquisition, and a causal one-cycle rolling DFT.
Not modeled as device-specific truth: exact anti-alias transfer functions, ADC topology, channel skew, input burden, electrical binary-input voltage/current thresholds, statistical measured contact bounce, proprietary protection fast paths, and hardware-calibrated timing uncertainty.
Standards and acceptance
Do not turn software evidence into unsupported certification.
| Claim | beta.6 position |
|---|---|
| IEC 61850 conformance certification | Not claimed |
| IEC 60255 type test | Not claimed |
| Calibrated relay-test-set output/timing | Not claimed |
| Protection-grade hard-real-time platform | Not claimed |
| Commissioning acceptance instrument | Not claimed |
| Manufacturer relay clone | Not claimed |
| Virtual deterministic laboratory behavior | Implemented and regression-tested within documented scope |
Live network use
Npcap and Ethernet workflows require explicit authorization.
- Use live capture only on isolated, authorized laboratory networks.
- Install Npcap separately under the device owner's security/licensing policy.
- Do not connect ARVREL to an operational process bus without an approved test method and authorization.
- Windows scheduling, drivers, adapters, publishers, and host load can affect live capture behavior.
- Prefer deterministic internal tests and PCAP replay before adding live-network variables.
Evidence interpretation
Internal trip and external TESTSET result are intentionally different authorities.
With the virtual BO1→BI1 trip wire disconnected, the relay may trip internally while the TESTSET correctly reports no external trip. This is not a defect; it demonstrates that the TESTSET is not peeking at relay private state.
Likewise, generic BI2 ANY PICKUP may precede the eventual operated-element pickup. Timing values must be interpreted according to their evidence source.
Data handling
Keep customer and infrastructure information out of public reports.
Do not publish proprietary SCL files, customer captures, credentials, IP plans, protected infrastructure details, employer-confidential logs, or evidence you are not authorized to redistribute. Use synthetic, sanitized, or contributor-owned fixtures for public issues.
Operational prohibition
Do not use ARVREL as the sole basis for field protection or switching decisions.
ARVREL is suitable for education, controlled laboratory evaluation, source review, research, interoperability study, and FAT/SAT preparation. It is not a substitute for approved commissioning procedures, calibrated equipment, protection-setting governance, or site switching authority.