The is no tool to simply click a button and convert the code. But we already transferred several projects successfully. In my opinion the rule is:
If only codesys standard libraries were used on the "old" MLC system then it can be run on a ctrlX CORE nearly without changes.
When using MLC specific libraries like RIL_Commontypes and so on, most of them were already transferred to the ctrlX ecosystem and you simply have to change them to the CXA_... version (or only change the placeholders)
When using very firmware specific functions like winder and so on we are actually working on this topic.
The main difference is the fieldbus and firmware functions. Like e.g. there are no direct variables available. But on the other side there are also PLC-Open standard function blocks (CXA_PLCOPEN) for motion commands available like they have been before. And also read and write parameter function blocks that now use the EtherCat instead of the Sercos.
State machine like from the GAT compact are also portable/adaptable. I did that already two years ago.
For further suggestions it would be necessary to know which direct firmware functions and other interface customer is using.
From the start you have to get the project moves from MLC to Corr device - after that compile and check errors.
But - I can't just open the MLC project and set the target. And I can't just export and import, because it is wrong level.
I try export/import PLCopenXML on CtrlX, but is not support on MLC
Is there some one that could explane just have to get started?
PLC Open Export/Import is not the best solution, because CoDeSys visu can't be exported and some CoDeSys code is changed by PLC Open Export. There is a better way. Please see article: