I noticed that the 'Recipe Manager' in the device tree disappeared, when I export and import the project via PLCopenXML.
The PLCopenXML file has not any trace of a recipe.
(With normal save and open project, the recipe manager information is retained.)
Has somebody else detected that the PLCopenXML does not include the recipe manager information?
And is there a work-around. So I can import the recipe managers information into a project. Maybe with python scripting?
With CoDeSys V3.5 Patch 4.
Regards,
Edwin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you Tim. I missed that option / work-around.
The "CoDeSys specific" import / export handles the recipe successful.
Though, when exporting, I see a warning regarding 'position': <invalid position="">. See figure.
Maybe this influences the PLCopenXML export! And is importing a recipe with PLCopenXML possible still.
Only I do not know the format that recipes are stored in, in a PLCopenXML file.
I'll do some investigation...</invalid>
Regards,
Edwin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My OEM confirmed that recipes are not stored in PLCopenXML.
The Jira database has the item: REQ-747 PlcopenXML export should also support recipe and recipe manager objects.
For now, I made a work-around with "CoDeSys specific" import / export.
Regards,
Edwin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I could not find any example for import_native. So I donate an example:
classNativeImReporter(NativeImportHandler):
  defconflict(self, name, existingObject, newguid):
    sys.stderr.write("%s%s"%("name: ", name))
  defprogress(self, name, pastedObject, exception):
    sys.stderr.write("%s%s"%("name: ", name))
  defskipped(self, name):
    sys.stderr.write("%s%s"%("name: ", name))defNativeImportFilter_All(name, guid, type, path):
  return(True)nativeImReporter=NativeImReporter()ifprojects.primary:
  projects.primary.close()proj=projects.open(name_project)app_list=proj.find(name_application, True)if(len(app_list)==1):
  NativeImportResult=app_list[0].import_native(name_recipe_export, NativeImportFilter_All, nativeImReporter)proj.save()proj.close()
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
All,
I noticed that the 'Recipe Manager' in the device tree disappeared, when I export and import the project via PLCopenXML.
The PLCopenXML file has not any trace of a recipe.
(With normal save and open project, the recipe manager information is retained.)
Has somebody else detected that the PLCopenXML does not include the recipe manager information?
And is there a work-around. So I can import the recipe managers information into a project. Maybe with python scripting?
With CoDeSys V3.5 Patch 4.
Regards,
Edwin.
Use the "CoDeSys specific" import/export. This also supports the recipe's.
Thank you Tim. I missed that option / work-around.
The "CoDeSys specific" import / export handles the recipe successful.
Though, when exporting, I see a warning regarding 'position': <invalid position="">. See figure.
Maybe this influences the PLCopenXML export! And is importing a recipe with PLCopenXML possible still.
Only I do not know the format that recipes are stored in, in a PLCopenXML file.
I'll do some investigation...</invalid>
Regards,
Edwin.
FYI.
My OEM confirmed that recipes are not stored in PLCopenXML.
The Jira database has the item: REQ-747 PlcopenXML export should also support recipe and recipe manager objects.
For now, I made a work-around with "CoDeSys specific" import / export.
Regards,
Edwin.
I could not find any example for import_native. So I donate an example: