Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Hi I recently starting using CodeSys V3.5 SP16 Patch 1.
I wrote a .library and exported it to the PLCopen XML format.
When I manually import it back into CodeSys the folder structure in my .library gets correctly imported. But when I try to import it via a python script, I just get a flat list. The folder structure isn't imported. Also the script always makes a .project file instead of a .library file, regardless of the name I give it in my script.
My main goal is to write a Structured Text 61131 library in a way which makes it easy to port to any other PLC IDE. I think PLCopen XML is the closest to a standard? Other ideas are always welcome!
Hi I recently starting using CodeSys V3.5 SP16 Patch 1.
I wrote a .library and exported it to the PLCopen XML format.
When I manually import it back into CodeSys the folder structure in my .library gets correctly imported. But when I try to import it via a python script, I just get a flat list. The folder structure isn't imported. Also the script always makes a .project file instead of a .library file, regardless of the name I give it in my script.
My main goal is to write a Structured Text 61131 library in a way which makes it easy to port to any other PLC IDE. I think PLCopen XML is the closest to a standard? Other ideas are always welcome!