I’m trying to integrate a custom PLC into CODESYS so that it appears under the Device section. From what I understand, this requires a .devdesc.xml device descriptor file.
I attempted to create the XML manually, but whenever I try to install it in order to generate a .package file, CODESYS crashes.
CODESYS version: 3.5.21.20
Target PLC: Linux ARM64–based
My questions are:
Is there an official or easier way to generate a valid .devdesc.xml file for a custom PLC?
Are there tools, templates, or examples that can help ensure the XML is structured correctly and won’t cause crashes?
For Linux ARM64 targets specifically, is there a recommended starting point (e.g., modifying an existing device descriptor)?
Any guidance or best practices for creating and packaging custom device descriptors would be greatly appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are a vendor of controllers and want to have your own CODESYS Runtime on your device, then you need to contact the CODESYS Sales team and ask for the runtime Toolkit. For resellers of CODESYS devices, this can be interesting.
If it is only for a few devices, then why not just take the standard runtime?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I’m trying to integrate a custom PLC into CODESYS so that it appears under the Device section. From what I understand, this requires a .devdesc.xml device descriptor file.
I attempted to create the XML manually, but whenever I try to install it in order to generate a .package file, CODESYS crashes.
CODESYS version: 3.5.21.20
Target PLC: Linux ARM64–based
My questions are:
Is there an official or easier way to generate a valid .devdesc.xml file for a custom PLC?
Are there tools, templates, or examples that can help ensure the XML is structured correctly and won’t cause crashes?
For Linux ARM64 targets specifically, is there a recommended starting point (e.g., modifying an existing device descriptor)?
Any guidance or best practices for creating and packaging custom device descriptors would be greatly appreciated.
If you are a vendor of controllers and want to have your own CODESYS Runtime on your device, then you need to contact the CODESYS Sales team and ask for the runtime Toolkit. For resellers of CODESYS devices, this can be interesting.
If it is only for a few devices, then why not just take the standard runtime?