Hi to everyone,
I am supporting a customer who is using a 3rd party EtherCAT IO device with ctrlX core. We have encountered probelms while importing the IOs in the PLC project.
PLC and ctrlx main release 1.12
He followed the "Wago HOW-TO" here there are the main step done:
Importing the XML, scan and add the right modules manually and then download
The data is then present in the datalayer, is possible to force the Outputs and read the inputs "manually".
Following the Wago guide again the procedure got stuck here:
Clicking the apply change button there is no possibility to import the IOs.
Is there some step missing, some error or in case some "workaround"? to avoid the problem?
Solved! Go to Solution.
We will check this.
Because it cannot be seen in the first screenshots, are you sure to be connected on the same ctrlX CORE? Not a virtual one or so.
I have made them a little bigger.
Yes, he is sure. Now in the screenshot it is possible to see the "ctrlX core",
which version do you use?
there was an issue, that sometimes the last EtherCAT device could not be found. Please add another module in the IO configuration, even if it is not available, and check the behavior.
This bug was solved by RM21.11.2, provided end of January 2022. If you don't succeed, please send the EtherCAT ESI file of the Wago to us!
You could also try following workaround:
In ctrlX IO Engineering add the menu for exporting EtherCat configuration:
Go to "Tools" -> "Customize" there in the tab "Menu" mark an separator and click "Add Command...". In the category "Devices" choose command "Saving EtherCat configuration...".
Now by right clicking on the EtherCat master you will find that command:
Afterwards import the created .xml file to the PLC project by right clicking on the "DataLayer_Realtime" node and choose "Edit" -> "Offline from file...":
Really thanks for the fast support. I have already sent anyting to the customer who is going to try what is highlighted and also provide all the needed info.
Here there is the ECAT ESI.
I have just tried your suggestion but there no way to import it neither with the "manual workaround".
Besides using the "NRT" Datalayer codesys library is working but the customer needs a more fast way to write/read IOs: Some inputs are connected to a photocell and some relatively fast input.
Thx for your feedback!👍