|Table of Contents|
As with all adapters, an existing https://unit040.atlassian.net/wiki/spaces/PUD/pages/280987237/Logic+Simulator#Overview is required.
Where to find the different Gateway Adapters
Where to find
To find the Beckhoff Twincat ADS adapter, go to the Inspector window of a https://unit040.atlassian.net/wiki/spaces/PUD/pages/280987237/Logic+Simulator#Overview component.
This https://unit040.atlassian.net/wiki/spaces/PUD/pages/280987237/Logic+Simulator#Overview can be added under Logic.
Only the settings between the lines refer to the Beckhoff Twincat ADS Adapter.
Select a different adapter, please see Prespective documentation for more information
Adapter Setting (TwincatADSServerSettings)
File path to the policy file
Is used as the an indicator in the XML policy file
Is the AMS NetID of the server. Adding “:[PORT]” , where the port is an integer configures the PLC port. The default port when nothing is configured is 851 (Default for TwinCat3)
How to use
Please see the https://unit040.atlassian.net/wiki/spaces/PUD/pages/280987237/Logic+Simulator#Overview documentation for further instructions on setting up your simulation.
Prespective enables you to update your Twincat project files based on the signal definitions. Setting the right Project Export Folder for you active twincat project should be enough to get the export function working for twincat 3 projects as shown in the Advanced Tutorial - Conveyor Belt
<POU of TESTOBJ_INPUTS>
You need a (virtual) Beckhoff PLC that supports ADS communication.
These are the required steps for connecting to the digital twin. Other settings that apply to you setup can be found on https://www.beckhoff.com/
BYTEARRAY STRING STRUCT
Setting up the component works as like any other prelogic component. The thing you have to take into account is how the PLC Address Path Format (or implicit naming rule) is configured. The output of this Address is the path to the variable.