However, if faulty EtherCAT cables were the issue, why wouldn't the error occur during normal operation? Why would bad cables only cause problems during a hard shutdown? I don't have the answer to this question. One last question: When you encountered this behavior, did you see a similar error in your logs? i.e, an "AccessViolation" exception in the EtherCAT Task Yes. It was the exeption you can see in attached file.
I think that the .err file is the .app file renamed by Codesys, so it is compiled. We met this behaviour one time, it was because the runtime goes in exception due to bad Ethercat cables.
Hi, Runtime goes in exception before the shutdown ? Do you have a .err file which is created ? (located in the folder of the .app and .crc)
IDK why you lost values but about the limit, when you compile, you should have the information about the memory remaining.
When you compile, you should have the information about the memory remaining.
Thank you for your answer. Finally I don't confirm that it used to work before. It seems that the IO-link Package is needed is you want to configure the network, but you don't need it if you use generic IO-link devices.
Hello, I'm using th IDE Combivis studio 6 (codesys based) and I get an error message when I use IO-link. "The license is missing or invalid. The API is running in demo mode." However the package Manager indicates that no licence is required. It used to work, it seems that the free package has become a paying one. Can Codeys confirm this? BR
https://forge.codesys.com/forge/talk/Engineering/thread/1203efe4d8/