What causes Beckhoff TwinCAT 3 (XAR/XAE) with EtherCAT fault ADS 1861?

1. Route missing or one-sided on the remote target: Check the route exists on both sides with the correct AMS NetId and IP address. 2. Firewall blocking ADS on the target: Check incoming TCP 48898 (and UDP 48899 for search, TCP 8016 for Secure ADS) are allowed on the target, as listed in ADS Basics. 3. Target or network too slow to answer within the timeout: Compare request size/rate with the timeout; trace the response time and the task exceed counter on the target.

TwinCAT ADS Error 1861 (0x745) Timeout: Causes and Fix

Beckhoff: timeout has occurred – the remote terminal is not responding in the specified ADS timeout. The route setting of the remote terminal may be configured incorrectly. The client sent the request but no answer arrived before its timeout (ADS DLL default 5000 ms; PLC blocks such as ADSREAD use TMOUT = DEFAULT_ADS_TIMEOUT).

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

On connection from XAE, an HMI or a remote PLC
Intermittently in operation when the network or target is loaded

Likely causes and checks

1Route missing or one-sided on the remote target

Points to it: Request leaves the client (no ADS 7) but the target never answers; often a new or replaced target.
Check: Check the route exists on both sides with the correct AMS NetId and IP address.

2Firewall blocking ADS on the target

Points to it: Ping works but ADS times out; Windows firewall recently enabled or changed.
Check: Check incoming TCP 48898 (and UDP 48899 for search, TCP 8016 for Secure ADS) are allowed on the target, as listed in ADS Basics.

3Target or network too slow to answer within the timeout

Points to it: Intermittent 1861 under load; large reads or many requests per cycle.
Check: Compare request size/rate with the timeout; trace the response time and the task exceed counter on the target.

Telling it apart

ADS 7 is raised locally when no route exists; 1861 means the request was sent and nothing came back in time.
ADS 6 comes back quickly from the target when the port has no server; a 1861 on the same port points to the network path or route instead.
A 1861 from ADSREAD in the PLC to another PLC can follow an exceeded TMOUT; check the TMOUT value against the network path before raising it.

Relevant parameters

Parameter	Name	Why it matters
AdsSyncSetTimeout	ADS DLL timeout	Beckhoff: standard value 5000 ms for the ADS DLL functions.
TMOUT	ADSREAD/ADSWRITE timeout input	Defaults to DEFAULT_ADS_TIMEOUT in Tc2_System.

Evidence to collect

Route lists of client and target
Firewall rules on the target
Ping/latency and network path between both sides
Time and frequency of the timeouts
Configured ADS timeout in the client (TMOUT or AdsSyncSetTimeout)

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.

Beckhoff TwinCAT 3 (XAR/XAE) with EtherCAT fault ADS 1861: Timeout, remote terminal not responding (0x745, ADSERR_CLIENT_SYNCTIMEOUT)