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
Hello,
I'm currently using Codesys 3.5 SP2 and everything works fine with the importation and eportation of PLCOpen XML except with the Task Configuration.After exporting my task(Mast) I try to import it again and what I take is a new branch of Application->Task Configuration.Is it a bug?Does anyone know who to fix this problem?
Thank you very much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm Having the same issue. If I highlight PLC Logic and import it erases everything else and replaces the Task config. If I highlight the Application I get the same result. Simple manual fix is click and drag the task config onto the origional Application, and delete the second one. Easy fix but not the expected result of importing task config.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My experience with PLCOpen xml support in CoDeSys is that not ALL data is stored in the PLCOpen xml files. Exporting and importing again, MAY lose information.
I detected this with:
- recipes
- CANopen
I did not detect it with Tasks.
Maybe the selected device in the device window, then starting the import was not correct.
CoDeSys inserts / appends the items in the imported PLCOpen xml file at the selected device.
Regards,
Edwin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your answer Edwin.I tried also to import by selecting another device but then either it finds no elements or it overwrites the application by the application->task configuration branch.
In PLCOpenxml the task should normally be under instances/configurations/configuration/resource/task but in the export file of Codesys it is under addData.I tried to import an xml according to PLCOpenxml schema but it finds no elements.You said you had no problem with importing PLCOpenxml for Task Configuration,did you use another file from the one that Codesys exports?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This export/import doesn't work like it should in V3. In V2.3 works perfectly. I found another solution for my self which works 100%. I allways open 2 Codesys project and I simply copy/paste eg. tasks, visu, GVLs, POUs, from one Codesys to another, thats all.
regards,
Alex
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there!
Please help! Can some one please guide me on how to export my FBD program to a PLC open XML file"? I am using the Codesys version 2.3. When I go to project and select the export option, it only saves it as an exp file. Please how do I export to a PLC open XML file. I am very new to Codesys. Your swift response would be much appreciated. Here is the screenshot of my program. Thank you.
Short anwser: You don't. CODESYS v23 has not got that option. As far as I know it will not come either since CODESYS v23 is officialy not further developed since begin 2019.
However, you can install CODESYS v35 32 bit version (NOT the x64 edition) and then install the CODESYS v23 to v35 project converter. It can help you convert the old v23 .pro to a v35 compatible .project. After this you can make a PLCOpenXML export from it. However converting the project from v23 to v35 can be tricky and is not always straight forward since you are new to CODESYS, but I think if the project isn't too difficult you will manage eventually. You can always ask someone here politely, but then you must agree to share the source file. (Post that question in the Codesys V2.3 forum!)
Lastly, if the project is not too complex you can always COPY/PASTE the structured text FB's into a fresh v35 project. Again this is only possible with Structured Text. Plus, maybe someone else knows another "trick"?
Get the CODESYS v23 converter here; https://store.codesys.com/codesys-v23-converter.html
The CODESYS V2.3 Converter is an extension for the CODESYS V3.5 programming environment, which makes it possible to open projects created with CODESYS V2.3 (*.pro files).
Requirements
Programming System CODESYS Development System Version 3.5.15.0 (32bit) or higher
Runtime System -
Additional Requirements -
Restrictions No support for CODESYS Development System 64bit
Licensing No license required
Required Accessories -
👍
1
Last edit: aliazzz 2021-03-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all! I would appreciate if anyone can suggest or recommend to me tools that can be used to tests FBD from Codesys. If there are tools that can be interfaced with Codesys. Your quick response would be very much appreciated. Thank you
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I'm currently using Codesys 3.5 SP2 and everything works fine with the importation and eportation of PLCOpen XML except with the Task Configuration.After exporting my task(Mast) I try to import it again and what I take is a new branch of Application->Task Configuration.Is it a bug?Does anyone know who to fix this problem?
Thank you very much.
I'm Having the same issue. If I highlight PLC Logic and import it erases everything else and replaces the Task config. If I highlight the Application I get the same result. Simple manual fix is click and drag the task config onto the origional Application, and delete the second one. Easy fix but not the expected result of importing task config.
My experience with PLCOpen xml support in CoDeSys is that not ALL data is stored in the PLCOpen xml files. Exporting and importing again, MAY lose information.
I detected this with:
- recipes
- CANopen
I did not detect it with Tasks.
Maybe the selected device in the device window, then starting the import was not correct.
CoDeSys inserts / appends the items in the imported PLCOpen xml file at the selected device.
Regards,
Edwin.
Thank you for your answer Edwin.I tried also to import by selecting another device but then either it finds no elements or it overwrites the application by the application->task configuration branch.
In PLCOpenxml the task should normally be under instances/configurations/configuration/resource/task but in the export file of Codesys it is under addData.I tried to import an xml according to PLCOpenxml schema but it finds no elements.You said you had no problem with importing PLCOpenxml for Task Configuration,did you use another file from the one that Codesys exports?
I create a PLCOpen xml file with another program / script. And that works fine.
This export/import doesn't work like it should in V3. In V2.3 works perfectly. I found another solution for my self which works 100%. I allways open 2 Codesys project and I simply copy/paste eg. tasks, visu, GVLs, POUs, from one Codesys to another, thats all.
regards,
Alex
Thank you both for your answers!
Yes Alex that is also a way to do it.
Edwin is it easy to tell me which program?
It's a proprietary application / script. Sorry.
I see.Thank you!
Hi there!
Please help! Can some one please guide me on how to export my FBD program to a PLC open XML file"? I am using the Codesys version 2.3. When I go to project and select the export option, it only saves it as an exp file. Please how do I export to a PLC open XML file. I am very new to Codesys. Your swift response would be much appreciated. Here is the screenshot of my program. Thank you.
Last edit: adexis 2021-03-26
Short anwser: You don't. CODESYS v23 has not got that option. As far as I know it will not come either since CODESYS v23 is officialy not further developed since begin 2019.
However, you can install CODESYS v35 32 bit version (NOT the x64 edition) and then install the CODESYS v23 to v35 project converter. It can help you convert the old v23 .pro to a v35 compatible .project. After this you can make a PLCOpenXML export from it. However converting the project from v23 to v35 can be tricky and is not always straight forward since you are new to CODESYS, but I think if the project isn't too difficult you will manage eventually. You can always ask someone here politely, but then you must agree to share the source file. (Post that question in the Codesys V2.3 forum!)
Lastly, if the project is not too complex you can always COPY/PASTE the structured text FB's into a fresh v35 project. Again this is only possible with Structured Text. Plus, maybe someone else knows another "trick"?
So, it is not impossible, but takes some effort.
Regards
Get the 32 bit version of CODESYS v35 here;
https://store.codesys.com/codesys.html
Get the CODESYS v23 converter here;
https://store.codesys.com/codesys-v23-converter.html
The CODESYS V2.3 Converter is an extension for the CODESYS V3.5 programming environment, which makes it possible to open projects created with CODESYS V2.3 (*.pro files).
Requirements
Programming System CODESYS Development System Version 3.5.15.0 (32bit) or higher
Runtime System -
Additional Requirements -
Restrictions No support for CODESYS Development System 64bit
Licensing No license required
Required Accessories -
Last edit: aliazzz 2021-03-26
Thank you for this detailed answer. I will try and give a feedback soon. Once again, thank you very much for your help.
Hi all! I would appreciate if anyone can suggest or recommend to me tools that can be used to tests FBD from Codesys. If there are tools that can be interfaced with Codesys. Your quick response would be very much appreciated. Thank you