Skip to main content

14.2 Upgrading PLC Firmware to V1.1 in Legacy Projects with BaoskyIDE V1.1

14.2 Upgrading PLC Firmware to V1.1 in Legacy Projects with BaoskyIDE V1.1​

14.2.1 Phenomenon​

  • When decompressing a V1.00 project in BaoskyIDE V1.10, the PLC device firmware version does not auto-upgrade (remains v1.00). As shown below, the firmware version is visible in the module properties under Device Configuration:
    alt text

  • Physical PLCs upgraded to firmware v1.1 maintain backward compatibility – they can run programs built for v1.0 firmware. For deployed projects, you may keep the project's PLC firmware setting at v1.0 even after upgrading the IDE and physical PLC firmware.

  • However, such projects will still operate on v1.0 firmware logic. New features and performance optimizations in v1.1 (e.g., incremental compilation acceleration) will be unavailable. For projects not yet deployed, upgrade the project's PLC firmware to v1.1 before field commissioning.

14.2.2 Solution​

Follow these steps in the legacy project:

  1. Create a new device with v1.10 CPU firmware in the project:
    alt text
  2. Select the original device → Export XML (include all: GVS, PU, UDT).
  3. Select the new device → Import XML (automatically repairs library references).
  4. Copy Tasks (excluding MainTask) from old to new device:
    • Use Shift/Ctrl for multi-selection
    • Manually add MainTask calls if used
  5. Copy I/O Mapping Tables:
    • Exclude summary views during copy
  6. Copy Watch Tables from old to new device.
  7. Manually configure new CPU settings to match originals:
    • Network port IP
    • Communication port enable states
  8. Add remote configurations (EC/PN/DP Masters):
    • Critical for multi-PN systems: Maintain identical device numbering
    • Example: If numbering starts from 102:
      a. Enable & add dummy PN port as 101
      b. Add active PN ports as 102/103
      c. Delete dummy port once confirmed
      alt text
  9. Copy all slaves under each master station (allow time for large projects).
  10. Cross-verify configurations.
  11. Perform compilation check.
  12. For tested PLCs with upgraded firmware but uncleared programs:
    • Go online with original PLC device
    • Navigate: Debug > Online Diagnostics > User Program Reset
      alt text
  13. Delete original device.
  14. Rename new device/CPU → Go online → Download.