Troubleshooting Errors Converting Mitsubishi Q Series PLC Program from GX IEC Developer 7.04 with GX Works 2

Question:

Hello everyone, I am currently working on a Mitsubishi Q series PLC that was programmed using Mistubishi's GX IEC Developer v7.04. Despite searching online, I have been unable to locate a copy of GX IEC Developer. I have turned to using GX Works 2 to convert the file since IEC developer is no longer supported. However, I have encountered various errors during the compilation of the converted file, prompting me to continue my search for the old IEC developer software. Any guidance on this matter would be greatly appreciated. Thank you for your help.

Top Replies

It is important to have the source file available for code conversion in GXDeveloper. Without it, the code may convert to ladder format, which can cause issues. The GXIEC system was designed to be compatible with older systems and display graphical representations, using temporary memories as placeholders. If the original source file is not available, complications may arise during the conversion process. For instance, errors may occur if function blocks have the same name for parameters as symbolic variables. While there is an option in the compiler settings to allow the use of the same symbolic name, it is recommended to rename either the symbol or the function block variables. Originally developed by a contractor for Mitsubishi, GXIEC is no longer available and I have it stored on an old PC without the original CD. It is advisable to upload the memory "Main" from the PLC to prevent data loss due to battery issues.

Parky mentioned the importance of having the source file for code conversion. If the source file is not available, the code will likely be converted to ladder format in GXDeveloper. There may be issues if the original source file is missing, as GXIEC was specifically designed to make older systems compatible and display graphical representations of the code using temporary placeholders like M9000 and D9000. Converting the code can also be challenging if the user created function blocks with the same names for parameters and symbolic variables. It is recommended to check the compiler settings for options to handle this issue. GXIEC, originally created by a Mitsubishi contractor, appears to no longer be available. Uploading the memory "Main" from the PLC is advised to prevent loss of data due to battery failure. Thank you, Parky, for sharing this insightful information.

When converting files from one programming software to another, issues may arise if the initial programmer used custom libraries that are inaccessible. In such cases, exporting the libraries in GXIEC and then importing them into GXWorks is necessary. If working with IEC version 7.xx, attempting the conversion and obtaining a PDF printout is possible, but factors like password protection may impact the process.

Parky mentioned that there may be issues with the conversion process if the original programmer used their own libraries and protected them. In such cases, these libraries will not be automatically integrated into the new GX Works project and would need to be exported from GXIEC and re-imported into GX Works. If the files are password protected, conversion may also be affected. The client provided me with a code copy, but I can only see a file with a ".PRO" extension when attempting to convert it in GX Works 2 using the "Other File Option". As mentioned by Parky, the error messages relating to the libraries not being converted are indeed appearing. I will review the code again and make necessary adjustments. Thank you for your guidance, Parky!

In order to export the libraries, you will likely require GXIEC. This tool displays the code in a visually informative way, where functions from the libraries are depicted as a box with a cross inside. However, there are peculiarities to be aware of when attempting to convert projects. If a project is password-protected in a "view only" mode, a password will be prompted for editing access. On the other hand, if the entire project is protected, it cannot be converted. Imported libraries will appear as read-only, though there may be ways to open them through some experimentation. It's important to have the necessary files, with softctrl.pro being the key file that GXWorks uses for project conversion in the project directory.

Hey there, I understand how frustrating these compatibility issues can be. You might not be able to get your hands on GX IEC Developer as Mitsubishi has discontinued it and fully transitioned to GX Works series. However, you could check if you've installed the appropriate plugins in GX Works 2 that support the previous formats and ensure you're using the right version. Also, have a look at the error messages during the compilation, they could provide an insight into what's causing the issue. Cheers!

Hey! I’ve been in a similar boat trying to get those older Mitsubishi PLC programs up and running. It can be tough finding legacy software like GX IEC Developer now that it's unsupported. Have you tried reaching out to Mitsubishi support or checking any user forums dedicated to Mitsubishi products? Sometimes, users share files or troubleshooting tips that could save you a lot of time. Also, while GX Works 2 can be a bit tricky for conversions, double-checking the settings or doing a clean import might help reduce the errors. Good luck!

Hey! I totally understand your struggle; finding legacy software can be such a hassle. Have you checked any Mitsubishi user groups or forums? Sometimes other engineers might have old installers or can share their experiences with similar issues. Another option might be reaching out to Mitsubishi support directly—they might have access to older versions of their software or can suggest a workaround for the errors you're seeing in GX Works 2. Good luck!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. Question: What are the common errors encountered when converting a Mitsubishi Q Series PLC program from GX IEC Developer 7.04 to GX Works 2?

Answer: Answer: Common errors include compilation errors, compatibility issues, and missing functions due to differences between the two software programs.

FAQ: 2. Question: Is there a way to resolve errors encountered during the conversion process from GX IEC Developer to GX Works 2?

Answer: Answer: One approach is to troubleshoot each error individually, check for compatibility settings, and consider seeking assistance from Mitsubishi support or online forums.

FAQ: 3. Question: Why is it challenging to find a copy of GX IEC Developer v7.04 and what are the alternatives?

Answer: Answer: GX IEC Developer v7.04 is no longer supported by Mitsubishi, making it difficult to find official copies. As an alternative, users can transition to GX Works 2 or explore other compatible programming software options.

FAQ: 4. Question: What resources are available for guidance on converting PLC programs between different Mitsubishi software versions?

Answer: Answer: Users can refer to Mitsubishi's official documentation, community forums, and online tutorials for assistance with converting PLC programs and troubleshooting errors between different software versions.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’