👁 Image
Beckhoff.TwinCAT.Ads.Server 7.0.172

Description

The package 'Beckhoff.TwinCAT.Ads.Server' contains the base framework to create your own ADS Server / virtual ADS Device.

Requirements

• .NET 10.0,, .NET 8.0 or .NET Standard 2.0 (e.g. >= .NET Framework 4.61) compatible SDK
• A TwinCAT 2.11 Build (XAE, XAR or ADS Setup) or later.

Installation

Beckhoff.TwinCAT.Ads Version 7.X

The 7.X series of this package now supports TwinCAT 2.11 and upwards locally.

Beckhoff.TwinCAT.Ads Version 6.X limitations

Because the Beckhoff.TwinCAT.Ads Version 6.X uses internal interfaces that are available only from TwinCAT 4024.10 on, an appropriate version must be installed locally. The package doesn't work with older installations. An alternativ approach for some use cases is to use the 'Beckhoff.TwinCAT.Ads.AdsRouterConsole' / 'Beckhoff.TwinCAT.TcpIpRouter' packages to establish your own router.

Systems without TwinCAT Installation

There are options to run AdsClient/AdsServer instances without having a full TwinCAT system installed on the host system.

• Use of the TwinCAT UM Runtime on supported systems
• Usage of AdsOverMqtt via a Mqtt Broker (Beckhoff.TwinCAT.Ads >= 6.2 necessary)
• Running a slim (feature reduced) .NET implemented ADS Router (formerly AdsRouterConsole). The implementation is in the 'Beckhoff.TwinCAT.Ads.TcpRouter' package

For more information please have a look at: Beckhoff GitHub RouterSamples Beckhoff GitHub DockerSamples

Version Support lifecycle

[^1]: Requirement on the Host system. No version limitation in remote system communication. [^2]: Microsoft support for .NET6/.NET7 has ended. Therefore it is recommended to update .NET Applications to Version 8.

Migrating to the latest .NET Microsoft .NET support lifecycle

First Steps

Create your customized ADS Server by deriving the TwinCAT.Ads.Server.AdsServer class. Fill the virtual handlers with your own code.

using Microsoft.Extensions.Logging;
using System;
using System.Buffers.Binary;
using System.Collections.Concurrent;
using System.Threading;
using System.Threading.Tasks;
using TwinCAT.Ads;
using TwinCAT.Ads.Server;

namespace TestServer
{
 /*
 * Extend the AdsServer class to implement your own ADS server.
 */
 public class AdsSampleServer : AdsServer
 {
 /// <summary>
 /// Fixed ADS Port (to be changed ...)
 /// </summary>
 const ushort ADS_PORT = 42;

 /// <summary>
 /// Fixed Name for the ADS Port (change this ...)
 /// </summary>
 const string ADS_PORT_NAME = "AdsSampleServer_Port42";


 /// <summary>
 /// Logger
 /// </summary>
 private ILogger _logger;

 /* Instantiate an ADS server with a fix ADS port assigned by the ADS router.
 */


 public AdsSampleServer(ILogger logger) : base(ADS_PORT, ADS_PORT_NAME)
 {
 _logger = logger;
 }

 // Override Functions to implement customized Server
 ....
 }
}

Further documentation

The actual version of the documentation is available in the Beckhoff Infosys: Beckhoff Information System

Sample Code

Demo Code for AdsServer implementations can be found here: Beckhoff GitHub ServerSamples Beckhoff GitHub RouterSamples Beckhoff GitHub DockerSamples