ArSee is the public product name. Existing source namespaces, executable names and published asset filenames retain ARIEC60870 for compatibility. The GitHub repository has been renamed to masarray/arsee, and the canonical Pages website is masarray.github.io/arsee. Older repository URLs redirect; old GitHub Pages project URLs do not.
From raw IEC 60870 traffic to inspectable engineering evidence.
ArSee is a free, Apache-2.0 open-source Windows protocol tester and evidence analyzer for IEC 60870-5-101, IEC 60870-5-103, and IEC 60870-5-104. Inspect original TX/RX frames, supported protocol interpretations, Values, Events, diagnostics, and native PDF evidence for authorized FAT/SAT, commissioning support, research and troubleshooting.
Product website · Download guide · Quick Start · Field Wiki
| Release channel | Version | Official downloads | Purpose |
|---|---|---|---|
| Latest public stable | v3.6.15 | Windows installer · Portable ZIP | Immediately visible analog Scaling tab, Factor/TwoPoint and X0/X100/Y0/Y100 |
| Previous stable | v3.6.14 | Stable release page | 31-point mapping, safe sync, IEC-101/104 engineering scaling |
ArSee is the public product name; compatibility installer/ZIP names retain ARIEC60870.
Published stable v3.6.15 (17 November 2026): PR #245 resolves the operator-reported hidden Scaling mode in Signal List Editor. For measured IEC-101/104 analogs, the compact Engineering Scaling tab now opens automatically; Factor/TwoPoint and all X0/X100/Y0/Y100 endpoint fields are visible in a 1360×820 window. Commands and metadata have their own tab; CA, IOA, Type and Name remain frozen during horizontal scrolling. The actual packaged GUI executable is checked by real WPF viewport acceptance and native Windows updater FAT. Raw TI11 Q counts are not assumed to be MVar.
v3.6.15 remains an unsigned software release, not IEC/SCADA field conformance certification. Verify SHA-256, read release notes, and use the approved gateway scale before labelling TI11 Q as MVar. External RTU FAT is separate.
Illustrative product media. The v3.6.15 package workflow history validates the release executable and real-WPF evidence; physical RTU FAT remains separate.
IEC-101/104 measurements may be transmitted as normalized TI9/10/21/34, signed scaled TI11/12/35, or IEEE float TI13/14/36. Enter authorized RTU engineering scaling using Factor or TwoPoint X0/X100/Y0/Y100 on the selected signal. The display projection does not rewrite original HEX, IOA, timestamps or quality; TI13 identity is appropriate if the gateway already sends MW. For the bundled 31-point CA105 reference, the operator-mapped TI11 Q ranges now use TwoPoint: Feeder/Diri Sendiri IOA790447 ±2078 MVar, Kopel/Lab SOGI 3 IOA790439 ±260 MVar, and Trafo/Lab SOGI 4 IOA790443 ±260 MVar, with decoded signed SVA X=-32768..32767. These are operator-provided display ranges awaiting physical RTU/SCADA FAT, not universal values. Existing user Signal Lists are kept; Signal List → Sync 31 I/O → Save As can apply them to exact-match legacy identity rows only without overwriting custom calibrations. POAQ feedback remains 0–1200; POOP command remains 0–1000. In v3.6.15, measured analog points open Engineering Scaling immediately and place X0/X100/Y0/Y100 above the fold. See the scaling guide.
| Area | What you can inspect |
|---|---|
| IEC-101 active serial (unbalanced) | Serial link and Class 1/2 polling, GI and selected command protocol evidence |
| IEC-101 dual-link A/B | Independent active/standby link states and redundancy trial diagnostics, not certified production redundancy |
| IEC-101 passive | Receive-only evidence interpretation from configured capture connections; electrical isolation depends on hardware |
| IEC-103 active serial | Relay protocol exchanges and supported event/value interpretation |
| IEC-104 TCP/IP | TCP session, APCI and ASDU data, STARTDT/TESTFR and transaction evidence |
| Engineer workstation | Raw Frames, Values, Events, GI/Controls where available, selected-frame inspector and contextual Smart Findings |
| Reporting | Native PDF evidence export with source frame references |
-
IEC-101 single/A/B link reliability: one bounded physical COM transaction/FCB authority, delayed-response quarantine and independent reconnect/backoff without blind command replay (#219–#225).
-
Truthful GI/SBO/IEC-104: command epoch/feedback correlation, source-bound GI ACTCON/ACTTERM, and IEC-104 TCP association validation (#226–#230).
-
SOE and mapping: per-object spontaneous accounting, bounded evidence FIFO and source-qualified mapped names in live/offline traces (#229).
-
Consistent engineering signal names: IOA profile names now align across Values, Events, Frame Trace, History search and CSV, and offline captures (PR #210); ambiguous/unmapped points remain unguessed.
-
IEC-101 service-matched replies: delayed FC11 status cannot complete another request; E5 cannot verify first link identity or FC9; unsupported A2 is rejected, and busy DFC prevents A/B standby promotion. See PR #208.
-
Event Journal → Original Frame: context-aware live-follow, historical paging and navigation to captured TX/RX frames. Missing original TX is reported as incomplete evidence rather than invented.
-
Bay-aware SCADA labels: the bundled 31-point utility I/O example distinguishes FEEDER, KOPEL, TRAFO CB/Local-Remote, relevant commands, busbar voltage and RTU alarms. Invalid CA/IOA/IEC Type ID families fail closed; existing user-owned profiles are not automatically overwritten.
-
IEC-101 at 1,200 bps: bounded baud-aware FT1.2 frame completion after a physical start, persistent RX framing across polls per COM epoch, and regression tests for incomplete telegrams and ambiguous E5. This does not prove physical RTU interoperability.
-
Windows upgrade assurance: operator-approved updates for the installed edition (portable ZIP does not self-replace), qualified by native Windows updater FAT, full xUnit regressions and real-WPF acceptance on the exact source commit.
Read v3.6.13 release notes and package / provenance workflow. The shared IEC-101 transaction core draft #145 remains unmerged. FIELD FAT PENDING: physical SICAM A8000 1,200-bps SOE 60/500/2,000 batches, GI/SBO lifecycle, COM recovery and A/B failover.
An acknowledged frame or GI termination is not proof that every configured point was received or that a physical control operated.
- Download the v3.6.15 installer or portable ZIP and verify checksums; fully extract the ZIP, then launch
ARIEC60870.exedirectly (do not run it inside the compressed archive). - In Setup, choose IEC-101 serial, IEC-101 passive, IEC-103 serial or IEC-104 TCP and enter the project-approved COM/TCP, serial handshake, link and ASDU address settings.
- Connect only to an authorized simulator or isolated test endpoint. Do not guess RTS/DTR states or reset a live outstation.
- Compare original TX/RX frame evidence with the interpretation in Raw Frames, Values, Events and GI/Controls as available.
- Export native PDF evidence, then sanitize topology, project and customer identifiers before sharing.
Further documentation: User Guide · Quick Start · Testing Strategy · IEC-101 A/B field checklist · Release notes.
- Full IEC-101 SICAM A8000 physical interoperability is not certified. Independently reviewed link/transaction/COM/GI/SBO changes #219–#230 are included in v3.6.13; draft PR #145 remains unmerged. Physical COM recovery, GI/SBO feedback and 1,200-bps SOE FIFO need field FAT.
- IEC-101 balanced mode, universal multi-vendor interoperability, industrial FIFO/SOE endurance, and electrically isolated 2/4-port capture are not certified.
- HOLD pins the visible trace viewport while acquisition continues; it does not itself guarantee durable archival recording.
- ArSee is not a production SCADA master, gateway, safety device or accredited IEC conformance test suite. Use active functions on approved isolated benches only.
The WPF UI, IEC protocol components and typed evidence engine live under src/; six test projects and site hygiene checks live in tests/. The English/Indonesian public landing site is maintained in site/, with a generated fallback mirror in docs/.
The CI workflow covers Release build, protocol regression and Windows WPF acceptance. The Package workflow verifies the actual published executable and builds ZIP, installer, checksums, SBOM and provenance. These are software checks, not physical FAT.
Read Contributing, Security, Support, Code of Conduct, Changelog, License and Third-party notices. Apache-2.0 permits commercial use under its terms; ARIEC60870 requires no subscription or activation key.
For issues, send a reproducible report with sanitized TX/RX HEX, version, OS, protocol profile and steps. Never publish sensitive captures, credentials or private substation topology.