Skip to content

README.md

Latest commit

 

History

History
85 lines (57 loc) · 9.35 KB

README.md

File metadata and controls

85 lines (57 loc) · 9.35 KB
Raw

ArSee · Open-Source IEC 60870-5-101/103/104 Protocol Tester & Analyzer

CI Pages Apache-2.0 Windows x64

ArSee is the public product name. Existing source namespaces, executable names and published asset filenames retain ARIEC60870 for compatibility. A coordinated rename to masarray/arsee is planned; the existing Pages URL stays canonical until cutover.

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

Download for Windows x64

Release channel Version Official downloads Purpose
Latest public stable v3.6.10 Windows installer · Portable ZIP Event → Original Frame forensic evidence, 31 bay-aware IEC-101/104 signal labels, bounded 1200-bps FT1.2 reception and tested Windows updater
Previous stable v3.6.9 Stable release page Introduced operator-approved installed Windows self-updater

ArSee is the application branding; compatibility installer/ZIP filenames retain ARIEC60870.

v3.6.10 is the latest stable software release, not physical IEC/SCADA conformance certification. Verify the SHA-256 checksum before running currently unsigned binaries. The release page includes SPDX SBOM; exact-source Windows package workflow records full tests, WPF acceptance and provenance.

GitHub's /releases/latest resolves to the newest non-prerelease publication. The version-pinned links above point to the complete public assets. Draft engine PR #145 is not included.

Illustrative ArSee protocol evidence workspace

Illustrative product media. The v3.6.10 package workflow validates the release executable and real-WPF evidence; physical RTU FAT remains separate.

Supported engineering workflows

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

What's improved in stable v3.6.10

  • 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, 1,032 passing xUnit tests and real-WPF acceptance on the exact source commit.

Read v3.6.10 release notes and package / provenance results. 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.

Five-minute first run

  1. Download the v3.6.10 installer or portable ZIP and verify checksums; fully extract the ZIP, then launch ARIEC60870.exe directly (do not run it inside the compressed archive).
  2. 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.
  3. Connect only to an authorized simulator or isolated test endpoint. Do not guess RTS/DTR states or reset a live outstation.
  4. Compare original TX/RX frame evidence with the interpretation in Raw Frames, Values, Events and GI/Controls as available.
  5. 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.

Scope and safety boundaries

  • Full IEC-101 SICAM A8000 physical interoperability is not certified. Draft PR #145 shared transaction/FCB and dual-link hardening is excluded from v3.6.10; COM recovery, GI/SBO evidence and 1,200-bps SOE FIFO still need physical FAT. Simulated CI is not a wired RTU pass.
  • 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.

Build, inspect and contribute

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.