Skip to main content

ADS Overview

The ADS route enables communication with Beckhoff TwinCAT PLCs and systems using the ADS (Automation Device Specification) protocol. It supports automatic symbol discovery, bidirectional communication, and complex data types including arrays and structures.
ADS provides direct, high-performance access to TwinCAT variables. The AutoDiscovery feature can automatically find and expose all PLC symbols as MQTT topics.
The ADS route is on beta testing. It is planned for a future release.

Basic Syntax


AMS Net ID Basics

ADS communication requires AMS Net IDs for both local and target systems. The AMS Net ID is typically the IP address followed by .1.1.
You can find your TwinCAT system’s AMS Net ID in TwinCAT XAE under SYSTEMRoutes or by running adsInfo on the target.

Connection Configuration

ADS_CONFIG Parameters

string
required
Local AMS Net ID (format: x.x.x.x.x.x). This is typically your machine’s IP + .1.1.
string
required
Route name on local machine to reach the target PLC.
string
Local host name (optional).
string
required
Target PLC’s AMS Net ID (format: x.x.x.x.x.x).
string
required
Target PLC’s IP address.
integer
ADS port. Typically 851 for TwinCAT 3, 801 for TwinCAT 2.
string
required
Route name on target PLC to reach the local machine.
string
Username for route creation (typically Administrator).
string
Password for route creation.
integer
Connection timeout in milliseconds. Default: 5000.

Connection Example


AutoDiscovery

AutoDiscovery automatically finds all PLC symbols and exposes them as MQTT topics.

AutoDiscovery Parameters

boolean
Enable automatic symbol discovery. Default: false.
string
Base MQTT topic for discovered symbols. Default: ads/discovery.
integer
Default QoS for discovered symbols (0-2). Default: 0.
boolean
Default retain flag for discovered symbols. Default: false.
integer
Default trigger mode:
  • 0 - OnStart (read once at connection)
  • 1 - OnChange (publish on value change)
  • 2 - Cyclic (poll at interval)
Default: 2.
integer
Default polling cycle in milliseconds. Default: 1000.
string
Include patterns (comma-separated, * wildcard). Default: * (all symbols).
string
Exclude patterns (comma-separated, * wildcard).
integer
Structure expansion depth. Default: 3.
boolean
Enable parallel reading for large projects. Default: false.
integer
Batch size for parallel reading. Default: 50.

AutoDiscovery Example


TwinCAT Data Types


TAG Configuration

Symbol-Based Addressing

Index-Based Addressing

For direct memory access using index group and offset:

Array Handling

string
Array element type (required for ARRAY): BOOL, INT, REAL, STRING, STRUCT, etc.
integer
Number of elements in the array.
integer
Length of each element in bytes (for STRING/STRUCT arrays).
integer
Offset in bytes to skip before array data. Default: 0.
integer
Header bytes to skip per element. Default: 0.

Structure Handling

string
Structure field definitions in format: name:offset:type:size (comma-separated).

Event-Based Operations

For on-demand ADS operations (not polling), use the EVENT syntax. Publish a message to SOURCE_TOPIC to trigger the operation; the route executes it and publishes the result to DESTINATION_TOPIC.

Supported Operations

Query Parameters

Read Example

Read a process variable on demand:

Write Example

Write a setpoint on demand:

Complete Examples

Read PLC variables using symbol names:

Route Setup Process

To establish ADS communication, routes must be configured on both sides:

1. On TwinCAT System

  1. Open TwinCAT XAE
  2. Go to SYSTEMRoutes
  3. Add a static route:
    • Route Name: Match TARGET_ROUTE_TO_LOCAL parameter
    • AMS Net ID: Your Coreflux machine’s AMS Net ID
    • Transport Type: TCP/IP
    • Address: Your Coreflux machine’s IP

2. In Coreflux Configuration

The route automatically creates a corresponding route on the local machine using the configured parameters.
Both route names (LOCAL_ROUTE_TO_TARGET and TARGET_ROUTE_TO_LOCAL) must match the actual route names configured on each system.

Troubleshooting

  • Verify AMS Net IDs are correct on both sides
  • Check routes are properly configured in TwinCAT
  • Ensure TARGET_PORT is correct (851 for TC3, 801 for TC2)
  • Verify firewall allows ADS port (typically 48898)
  • Check TARGET_USER/PASSWORD for route creation
  • Verify symbol path matches exactly (case-sensitive)
  • Check symbol exists in PLC project
  • Ensure PLC is in RUN mode
  • Use AutoDiscovery to find correct symbol names
  • Check DISCOVERY_FILTER_INCLUDES patterns
  • Verify DISCOVERY_MAX_DEPTH is sufficient
  • For large projects, enable DISCOVERY_PARALLEL_READING
  • Check PLC project is compiled and deployed
  • Ensure WRITABLE is set to “true”
  • Verify PLC variable is not constant
  • Check value is within MIN_VALUE/MAX_VALUE
  • Verify PLC is in RUN mode
  • Increase TIMEOUT value
  • Check network connectivity
  • Verify TwinCAT runtime is running
  • Reduce DISCOVERY_BATCH_SIZE if using AutoDiscovery

Next Steps

Allen-Bradley

Connect to Rockwell Automation PLCs.

OPC UA

Cross-platform OPC UA communication.
Last modified on July 3, 2026