Open a GX Developer project (GPJ) and print it (Beta)

Zip a GX Developer project folder (Gppw.gpj with its Resource folder) and get the ladder drawn with comments, the instruction list and the comments in Excel.

Opens: GXW, GX3, GPJ, WPG, CSV, ZIP
Saves: PDF, HTML, TXT, CSV, XLSX, ST

Open project

MELSEC project
Choose a file… or drop it here
.gxw, .gx3, .zip, .wpg, .csv · up to 200 MB
    Replace file

    A GX Works2 project (.gxw), a GX Works3 project (.gx3), a GX Developer project folder as a .zip (the folder with Gppw.gpj and the Resource folder), a single GX Developer program file (.wpg), or a GX Works2 / GX Developer instruction list export (.csv).

    More inputs
    Second version to compare (optional) (optional)
    Choose a file… or drop it here
    .gxw, .gx3, .zip, .wpg, .csv · up to 200 MB
      Replace file

      Another version of the same project (any of the kinds above). You get a report of added, removed and changed programs, ladder blocks, lines of structured text, device comments, labels and settings, from the first project to this one.

      Options
      Page size of the printout
      More options

      What the ladder printout and viewer show under each device: its device comment, the alias a GX Developer project gives it, or nothing for a shorter printout.

      Your files are deleted after processing.

      Open a GX Developer project and print it

      GX Developer, the MELSOFT programming software before GX Works2, does not save a project as one file. It writes a folder: Gppw.gpj holds the CPU type and the project comment, and the Resource folder holds the programs (.wpg), the device comments (.wcd) and the parameters (.wpa). Many FX projects passed around today are still in this form.

      How to upload it

      1. Find the project folder: the one with Gppw.gpj in it.
      2. Zip the whole folder, including Resource and everything below it (right-click, Send to, Compressed folder on Windows).
      3. Upload the .zip.

      If you only have a single program file, upload the .wpg on its own. It is drawn the same way, but without device comments and parameters, which live in other files of the folder. An instruction list exported to .csv by GX Developer or GX Works2 is read too.

      What comes out

      • Ladder with step numbers, the statements written above blocks, the notes on instructions and the device comment under every contact, coil and operand. Step ladder programs (STL and RET) are drawn as ladder with each STL step where it was written.
      • Device comments from COMMENT.wcd, and the program comments that some projects keep next to it, as tables in the printout, in CSV and in Excel.
      • Aliases: GX Developer can give each device a short alias next to its comment. Choose "Aliases (GX Developer)" under the advanced options to print those under the devices instead.
      • Parameters: memory capacity, comment capacity and the latched device ranges.
      • Project comment from Gppw.gpj, shown in the project summary.

      Old PCs, old code pages

      GX Developer stores comments in the code page of the PC that wrote them: Shift-JIS on a Japanese Windows, GBK on a Chinese one, Windows-1251 on a Russian one, and so on. The project does not say which, so the tool works it out from the texts themselves. Projects with Chinese, Russian and Portuguese comments were part of the testing.

      Series

      The GX Developer projects used for testing were for FX0(S), FX1S, FX1N, FX2N(C) and FX3U(C) controllers, over 120 of them. Projects for other CPUs, including the Q and A series, are read with the same instruction tables as GX Works2 projects, but none was available to test with, so compare the first printout with the project.

      Downloads

      A PDF printout (A4 or Letter), the offline HTML viewer, the instruction list as text and as CSV files GX Works2 can import, and the device comments and cross reference as CSV and Excel.

      More about what this tool reads and writes: Mitsubishi PLC Project Viewer (GX Works2, GX Works3, GX Developer).