Can an IEC 60870 device respond with the wrong Common Address?

Yes. The link or TCP session can be alive while the ASDU Common Address belongs to another station or does not match the test profile.

How do I prove CA mismatch?

Compare the decoded ASDU Common Address in the RX frame with the expected project profile and include the raw frame in the evidence report.

Troubleshooting

IEC 60870 Common Address mismatch: the device answers, but the ASDU belongs somewhere else.

CA mismatch is one of the most confusing field symptoms: the physical link or IEC-104 TCP session can look healthy, but application data does not match the expected station. ARIEC60870 keeps the raw TX/RX frame visible and explains the decoded CA so the issue is easier to prove.

Download ARIEC60870 Back to troubleshooting

Why it happens

The transport can be correct while the ASDU address is wrong.

IEC 101 and IEC 104 separate link/session reachability from application addressing. A device can accept communication while sending an ASDU Common Address that does not match the engineering profile, RTU station, bay controller, or test setup.

ProblemRX frame shows CA=2 while the setup expects CA=1.

ProofSelected-frame interpretation shows direction, Type ID, COT, CA, and raw frame evidence.

Next stepVerify project profile, device CA, endpoint selection, gateway mapping, and ARIEC60870 setup.

How ARIEC60870 helps

Raw frame → decoded CA → Smart Finding → PDF evidence.

Frame interpreterShows the raw TX/RX frame and the decoded ASDU Common Address in readable form.

Smart FindingsHighlights likely CA mismatch instead of leaving the engineer with a vague communication error.

Evidence reportPackages the frame, finding, and next step into the PDF report for FAT, SAT, commissioning, troubleshooting, homologation, or handover.

Follow the evidence path.

CA mismatch often appears together with GI gaps, unknown IOA, or command confirmation problems.

GI incomplete ACTCON missing PDF evidence report