General questions asked by engineers.

Yes. ARIEC60870 is 100% free and open source under Apache-2.0. You can use it for learning, academic research, internal engineering, FAT/SAT, commissioning support, troubleshooting, and commercial activities without a license key, account, subscription, or activation server.

It is made for IEC 60870 engineering evidence: checking frames, values, events, General Interrogation behavior, commands, findings, and PDF handover records.

No. It is an engineering evidence analyzer, not a production SCADA system, gateway, or permanent master station.

Yes, when the test is authorized and the project procedure allows it. The app helps prepare and review evidence, while formal acceptance remains under the approved FAT/SAT procedure.

Yes. IEC-101 workflows include serial setup, link evidence, General Interrogation review, value and event decoding, frame trace, ACD/DFC visibility, and command evidence.

Yes. IEC-103 workflows focus on protection relay communication evidence, link reset, class polling, relay events, function information, timestamps, and mapping-assisted review.

Yes. IEC-104 workflows cover TCP client evidence, STARTDT/STOPDT/TESTFR visibility, I/S/U frame behavior, sequence counters, ASDU decoding, and report output.

ACD is the Access Demand bit in the secondary link response. When it is set, the outstation is telling the master that Class 1 data is waiting.

DFC is the Data Flow Control bit. When it is set, the outstation is indicating that it cannot accept more data at that moment.

Normally no. A healthy unbalanced IEC-101 cycle uses Class 2 polling for regular traffic and drains Class 1 when ACD indicates pending high-priority data.

A common cause is Class 1 congestion: events or cyclic analog data are configured so aggressively that command confirmation has to compete with too much high-priority traffic.

Common Address identifies the ASDU station/object group, while link address belongs to the link layer. Mixing the two is a common source of silent or rejected communication.

No. Protocol data comes from traffic, while readable signal names come from user-owned JSON mapping profiles.

Yes. The Report workspace exports a native evidence PDF for review and handover.

Review station names, IP addresses, signal names, and project labels first. The report is evidence, so sensitive project data should be checked before distribution.

No. It is an engineering analyzer and learning-friendly evidence tool, not a certified IEC conformance test suite.