Dev.to AI 🤖 Ai 👁 0

CODESYS AI Practice — Project Sync

Environment: CODESYS V3.5 SP17 / SP22 | Windows + PowerShell 5.1 The previous post, CODESYS AI Practice — Import/Export Files, closed the “project ⇄ text ⇄ AI” loop, but it was still a code-editing-only tool. This post

CODESYS AI Practice — Project Sync

Environment: CODESYS V3.5 SP17 / SP22 | Windows + PowerShell 5.1

The previous post, CODESYS AI Practice — Import/Export Files, closed the “project ⇄ text ⇄ AI” loop, but it was still a code-editing-only tool. This post completes the picture by turning it into a tool that operates on the project itself — CRUD for project objects.

Same approach as before.

What “project sync” means here

  • Export project objects (POUs, DUTs, GVLs) to text
  • Edit text (AI)
  • Import back into the project with safety rails

The loop is the same: export → edit → import → sync.

Export, edit, import loop

Beyond code edit

Earlier import/export only rewrote existing code bodies. This version can:

  • Create new objects
  • Delete objects
  • Rename objects
  • Sync declarations with implementations

…while still treating the CODESYS project as the single source of truth.

Safety

  • Backup before write-back
  • Diff before apply
  • Save after successful import

Summary

Project sync makes the text side a full peer of the binary project: AI can change structure, not only bodies — with the same export/edit/import discipline as the earlier posts in this series.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.