Beckhoff TwinCAT 3 (XAR/XAE) with EtherCAT fault ADS 6: Target port not found (0x6, ERR_TARGETPORTNOTFOUND)

Beckhoff TwinCAT 3 (XAR/XAE) with EtherCATfaultTwinCAT 3.1; ADS Basics 2.6.2, EtherCAT System Manual 6.1.0, NC Errors 2.5.1

Beckhoff: target port not found – the ADS server is not started, not reachable or not installed. The route to the target machine works (otherwise the error would be 7), but nothing is registered on the AMS port the client addressed, for example port 851 when PLC runtime 1 has no running PLC project.

Diagnose this with AI

Upload a keypad photo, the fault history or a parameter export from your Beckhoff TwinCAT 3 (XAR/XAE) with EtherCAT. InduQT compares the evidence and suggests the next useful checks.

Try Free PLC Fault Diagnostic

When it happens

Likely causes and checks

1Wrong AMS port in the client

Points to it
Client uses 801 (TwinCAT 2) or another runtime port; the target is TwinCAT 3 with PLC runtime 1 on 851.
Check
Compare the client’s port with the ADS port of the PLC project (851 = TC3 PLC runtime 1, 852 = runtime 2…).

2No PLC project running on that port

Points to it
Target in CONFIG mode, no boot project, or the PLC was not started after activation.
Check
Check the TwinCAT state (RUN/CONFIG) and that the PLC project is loaded and running on the target.

3ADS server (e.g. an optional TwinCAT function) not installed on the target

Points to it
Error only on a non-PLC port (e.g. a TF server port); the PLC port works.
Check
Check the function is installed and licensed on the target and listed in the AMS port table.

Telling it apart

Relevant parameters

ParameterNameWhy it matters
AMS portTarget ADS portTC3 PLC runtime 1 = 851, runtime 2 = 852; NC = 500; system service = 10000.

Evidence to collect

Work on fuel trains, burners, pressure vessels and electrical equipment must be done by qualified personnel following the manufacturer’s documentation and local codes. Never bypass a safety device or interlock.

Related