Quick start

Download, configure, run a session, review evidence, export PDF.

This page is the user-first walkthrough for ArSee Evidence Analyzer. It assumes an authorized lab, FAT/SAT, commissioning, or troubleshooting environment and a known IEC 60870 endpoint.

1. Choose the release channel

The latest public stable release is v3.6.16: choose installer or portable ZIP. The previous stable release was v3.6.14.

  • Verify SHA256SUMS.txt.
  • Avoid the GitHub source ZIP unless building from source.
  • Physical SICAM FAT has not been established.

2. Install or extract

Run the per-user Setup EXE or fully extract the portable ZIP and launch ArSee.

  • Portable mode does not require an installer.
  • No start batch file is needed.
  • Never run the app directly in a compressed ZIP viewer.

3. Choose protocol mode

Open Setup and choose the mode that matches the authorized target device.

  • IEC-101 serial for RTU or gateway serial checks.
  • IEC-103 serial for protection relay communication checks.
  • IEC-104 TCP/IP for TCP endpoint checks.

4. Enter approved settings

Use the project/device communication sheet. Avoid guessing settings from labels or old screenshots.

  • Serial: COM port, baud rate, parity, stop bits, link address, CA, ASDU profile.
  • TCP: server IP, TCP port, common address, ASDU profile.
  • Mapping: load an approved, user-owned JSON profile for readable names. The bundled 31-point utility sample must match the actual CA/IOA/IEC Type ID; it does not replace saved custom mapping.

5. Start and review

Start the session, then review the evidence from high-level rows down to protocol detail.

  • Operator Evidence for review-level output.
  • Value Viewer and Event Log for decoded point behavior.
  • Frame Trace and Diagnostics when the high-level evidence is not enough.

6. Export native PDF

Open Report, refresh the preview when needed, then click Export PDF.

  • The report is generated by the built-in native PDF engine.
  • Review station names, IP addresses, signal names, and project labels before sharing.
  • Store the PDF together with the approved test record when required.

Before you start

Minimum information you should have ready.

ArSee is most useful when the communication parameters are known and approved.

Serial sessionsCOM port, baud rate, data bits, parity, stop bits, link address length, link address, common address, COT length, IOA length, and timing expectations.
IEC-104 sessionsServer IP address, TCP port, common address, ASDU profile, allowed test window, firewall rule, and expected startup sequence.
Evidence namingUse a project-approved JSON mapping profile when the report should show readable signal names instead of raw addresses only.