Project Conversion Example: PFC200

In the following example, a PFC200 750-8217 is migrated from e!COCKPIT (firmware version 22) to CODESYS (firmware version 24).
A PFC200 750-8217 is used as an example; the example also applies to other PFC 200 devices.

  1. To export the “Local Bus I/O Mapping” shown under the device to a CSV file, go to the “DEVICE” tab and click [Export I/O mapping] on the ribbon.
  2. Exporting I/O Image
  3. Provide a filename for the export file and click [Save].
  4. Save and close the project in e!COCKPIT.
  5. Copy the project file.
  6. Change the file extension of the copy from “.ecp” to “.project.”
  7. PFC200_G2_2ETH_RS_4G.csv
    TestProjektPFC200_750-8217 – Copy.project
  8. Open the project with the new extension in the CODESYS version that matches the firmware. Version information can be found in the release notes that accompany the downloaded firmware packages.
    In this example, the project is opened in CODESYS V3.5 SP18 Patch 2. This CODESYS version is compatible with firmware version 24.
  9. Click [OK] to confirm the dialog for updating the project environment.
  10. Updating the Project Environment
  11. Confirm that the project’s saving format has been updated by clicking [Yes].
    In future, further processing of the project will only be possible in CODESYS.
  12. Updating the Saving Format
  13. The opened project is displayed in CODESYS as follows:
  14. Imported Project in CODESYS
  15. Right-click on the project name in the device tree at the top and select “Add Device” from the context menu.
  16. In the dialog, select the new target device, in this case “750-8217 PFC200.”
  17. Selecting the Target System
  18. Click [Add Device] and close the window.
  19. The device is attached to the tree:
  20. Attached Device
  21. Delete the library manager for the newly attached device.
  22. Now copy all the elements of the old device under “Application” and insert them back into the new device under “Application.”
  23. Copying Content from “Application” to New Device
  24. Now copy all the elements of the old device under “Kbus (Kbus)” and insert them back into the new device under “Kbus (Kbus).”
  25. Copying Content of “Kbus” under New Device
  26. The question marks in red circles indicate that these I/O modules still need to be updated with the latest device description.
  27. To do so, right-click on one of the I/O modules and select “Update Device ....”
  28. Updating I/O Modules
  29. Repeat the procedure for all I/O modules until all the I/O modules have been updated and no more question marks remain.
  30. Click on the I/O modules to open the “K-BUS I/O Mapping” tab on the right.
  31. The variables from the I/O images of the I/O modules appear here. After the update, the variables are initially missing. The I/O images must be imported from the CSV file.
  32. To do so, right-click on “Kbus (Kbus)” and select “Import mappings from CSV...” from the context menu.
  33. Select the CSV file you saved in e!COCKPIT and open it.
  34. The variables from the CSV file are loaded and displayed on the “K-BUS I/O Mapping” tab, similarly to how they are in e!COCKPIT.
  35. Imported Variables
  36. Since you no longer need the old device, delete the old device from the project tree.
  37. Save and close the project.
  38. Reopen the project.
  39. Update the project environment by clicking [Set All to Newest].
  40. Setting Everything to “Latest”
  41. Click [OK] to confirm.
  42. Save the project.