Before opening a GX Developer project in GX Works2: format, CPU and compilation checks

When receiving an old machine's PLC project, first determine whether it is an editable project, exported text or only data read from the equipment. Each provides different information. This article covers opening and checking GX Developer projects in GX Works2, not forcing outputs, making online changes or bypassing safety logic on site.

Software scope and import limits

According to §4.7 of the GX Works2 Version 1 common manual SH-080779ENG-AT, a GX Developer project can be accessed through “Open Other Project” and opens as a Simple project. Other-format projects containing labels require a complete rebuild after opening before online operations can continue. For CPU types unsupported by GX Works2, the manual directs use of GX Developer. Check support for the exact CPU, not merely the brand.

Retain the original project before conversion

Copy the complete project directory, preserving file names and directory structure, and record the receipt date and provider. Save the opened version to a separate folder so the new software cannot overwrite the only original through automatic saving. Note whether dependent module information and comment files are complete; missing material is not a basis for guessing the original design.

Also record the exact on-site CPU and module models, the CPU type shown in the project and software version. Preserve model suffixes. If the connection target is uncertain, perform offline checks first rather than trying machines one by one to find it.

Checks after the project opens

1. Check that program lists, parameters, labels and comments match the original project structure, and record import messages.
2. Save compilation errors and warnings separately and resolve them using the original design and relevant programming manual. Do not simply delete offending program sections to obtain a successful build.
3. Sample-check the completeness of start/stop, interlock and abnormal-condition logic. Functional confirmation requires involvement of the machine builder or maintenance lead.
4. Retain the converted project, compilation records and change list so the next person can distinguish conversion-only content from manual modifications.

Successful compilation is not the only delivery criterion

A successful offline build establishes conformity with relevant software checks, not correct site wiring, machine actions or production conditions. Before writing to equipment, there must also be recoverable original data, a defined stoppage window and a validation plan. The work order should identify who confirms the target PLC, approves changes and takes responsibility for restart.

GX Works3 has specific historical-version restrictions for SFC projects; see version checks before SFC migration. The older GX Works2 questions and answers (Chinese) concern early operating systems: interpret their environment descriptions in that version context, not as a replacement for actual compatibility checks.

Reference: GX Works2 Version 1 Operating Manual (Common), SH-080779ENG-AT, §4.7 and §4.7.1, printed pages 4-53 to 4-56. This text explains scope and suggests ways to organize site records. Follow the documentation for the actual system and machine builder for specific operations.