Frequently Asked Questions

• What is TwinCAT Automation Interface?

TwinCAT Automation Interface is an interface to access the configuration of TwinCAT from an external application. This enables customers to automate the configuration of TwinCAT.

• Can I create an offline TwinCAT configuration (without any attached devices)?

Yes. You can create the TwinCAT configuration offline by manually attaching (without "Scan Devices) all devices and then providing online values, e.g. addresses, later after all devices have been attached. Please see our samples page for more information. There is also an How-To sample which shows you how to provide addressing information for pre-configured I/O devices.

• Which programming and scripting languages are supported?

Every programming or scripting language that supports the COM object model is supported. Please see our system requirements page for more information.

• Which TwinCAT features are accessible via Automation Interface?

Please see our version overview page for more information about which TwinCAT features are accessible via Automation Interface.

• What if I don't find an appropriate programming method or property for a specific setting?

If you don't find an appropriate Automation Interface method or property for a specific setting, you may use the Import/Export feature of TwinCAT to read/write this setting. Please refer to our article about custom tree item parameters for more information.

• Can I automate the configuration of TwinCAT PLC?

Yes. This feature will be available with TwinCAT 3.1. Please refer to our version overview page for more information.

• Can I execute Automation Interface code on TwinCAT XAR (Runtime-only) computers?

No. To execute Automation Interface code, TwinCAT XAE (Engineering) is needed, because Automation Interface directly accesses the Visual Studio COM object to communicate with the TwinCAT configuration. However, you can use a TwinCAT XAE computer to remotely connect to a TwinCAT runtime and configure it.

• When should I use ADS and when Automation Interface?

This is a question which cannot be answered easily because it heavily depends on what you would like to achieve. TwinCAT Automation Interface has been designed primarily to help customers to automate the configuration of TwinCAT. If you want to cyclically read/write values to IOs or PLC variables, our ADS APIs are probably better suited.

• I'm a machine builder and use a TwinCAT configuration template for all machine types and only enable/disable certain I/Os. Can I also do that with Automation Interface?

Yes. There is an How-To sample which shows you exactly how to do that.

• Can I also create ADS routes or execute a Broadcast Search?

Yes. Please see our samples and How-To pages for more information.

• Do I need to modify my Automation Interface code if I switch languages in TwinCAT XAE, e.g. from English to German?

All TwinCAT XAE items that are language dependent (Devices, Boxes, Axes, Channels, ...) can either be accessed via the currently set XAE language or via their english name. For example, if the XAE language is changed from English to German, the term "Channel" will be displayed in XAE as "Kanal" but is still available under the name "Channel" via Automation Interface. To be fully compatible, we recommend building your Automation Interface code based on english terminology.