Your connection configuration should look something like the attachment. Consuming assembly O->T will be the hex of the assembly you want to reference for output data - I want 102 (DO Data Only) shown in the Wago web page 102 = 16#66. Producing assembly (T->O) is the assembly you require for input data - again shown in the Wago web page - I want 108 (DI Data Only) or 16#6C Then set the number of bytes as per the data in the Wago web page too (both 2 in my case)
Your connection configuration should look something like the attachment. Consuming assembly O->T will be the hex of the assembly you want to reference for output data - I want 102 (DO Data Only) shown in the Wago web page 102 = 16#66. Producing assembly (T->O) is the assembly you require for input data - again shown in the Wago web page - I want 108 (DI Data Only) or 16#6C Then set the number of bytes as per the data in the Wago web page too (both 2 in my case)
Your connection configuration should look something like this consuming assembly O->T will be the hex of the assembly you want to reference for output data - I want 102 (DO Data Only) shown in the Wago web page 102 = 16#66. Producting assembly (T->O) is the assembly you require for input data - again shown in the Wago web page - I want 108 (DI Data Only) or 16#6C Then set the number of bytes as per the data in the Wago web page too (both 2 in my case)
Make sure the number of bytes matches the values in the Ethernet/IP>Assembly Information section of the Wagos web management page (expand by clicking on the +). The EDS file will probably have defaulted to assemblies 101 and 104. If you want a different assembly there is an article that tells you how to modify but seems to be unavailable at the moment. An alternative is to modify the .eds file to change the default assemblies.
Make sure the number of bytes matches the values in the Ethernet/IP>Assembly Information section of the Wagos web management page (expand by clicking on the +). The EDS file will probably have defaulted to assemblies 101 and 104.
This file is still useful but no longer available?
I was answering your last paragraph Meanwhile, I would like to understand why the motion FB instances must still be called even after the Execute is set to FALSE, especially in view of the fact that the next instruction is programmed to abort the previous one, with BufferMode set to 'Aborting'. All these unnecessary FB calls are an unnecessary overhead on the CPU anyway. Is there any precise rule about when to cease calling the various instances? (It should precisely be the 'done' status that says...
Most FBs clock on the rising edge so if they are never called with xExecute = False then subsequent actions will not be performed.