Is ARIEC60870 free?
Yes. ARIEC60870 is free and open source under Apache-2.0. There is no license key, subscription, or account requirement for trying the release package.
FAQ
Questions before using ARIEC60870.
These answers clarify the product scope, license, commercial use, operating system, supported protocols, mapping approach, and report output.
Can it be used commercially?
The source is Apache-2.0. That is a permissive license commonly used for commercial and internal engineering workflows. Users still need to follow the license terms, organization policy, and project/customer rules.
Which protocols are supported?
The app provides practical evidence-oriented workflows for IEC 60870-5-101 serial, IEC 60870-5-103 serial relay communication, and IEC 60870-5-104 TCP/IP client testing.
Is it a full SCADA master?
No. It is a focused engineering test and evidence analyzer. It is not a production SCADA system, gateway, production redundant master station, or replacement for an approved test procedure.
Does it export PDF?
Yes. The Report workspace exports a professional PDF evidence report generated directly by the built-in native PDF engine.
Does it need an installer?
No. Download the Windows ZIP, extract it, and run ARIEC60870.exe. The user release is designed as one simple Windows package.
How are signal names handled?
Protocol decode comes from traffic. Friendly project names come from user-owned JSON mapping profiles. The app does not embed a vendor-specific relay database.
Can it be used on live systems?
Only use it in authorized engineering environments and approved test windows. The tool is intended for lab, FAT/SAT, commissioning, or troubleshooting use under the project procedure.
Does it support passive sniffing?
The current public product is focused on active single-endpoint evidence workflows. Passive monitor and dual-link redundancy evidence are advanced workflows; IEC-101 Dual Link Redundancy now has a dedicated workspace and evidence path.
What should be checked before sharing a report?
Review station labels, IP addresses, communication addresses, signal names, mapping labels, and evidence details before sharing exported PDFs outside the project team.