How to communicate between Mitsubishi Q06H PLC and GCM Communication Module via Modbus registers.

Question:

Hey everyone, I'm new to PLC programming and currently working with a Mitsubishi Q06H PLC that needs to communicate with an Electronic module (specifically the GCM-Communication Module) via Ethernet. I need assistance with reading/writing data between the PLC and the Electronic Module using Modbus registers such as 40040 and 40041. I have provided a link to the Communication module manual for reference: https://www.graco.com/content/dam/graco/tech_documents/manuals/312/312785/312785EN-E.pdf (refer to page 28). I appreciate any comments or help you can provide on this matter. Thank you.

Top Replies

Welcome, Cu Do, to the forum! I have some mixed news for you. On a positive note, it is technically feasible to establish communication between a Mitsubitshi Q06H and a GCM-Communication Module via Ethernet. However, the downside is that some extra effort will be required on your end. The Mitsubitshi Q06H does not inherently support the same protocol as the GCM-Communication Module. Although they both utilize Ethernet and share layers 1 to 4 of the ISO/OSI 7-Layer model (Physical L1, Data Link L2, Network L3/IP, and Transport L4/TCP), they differ at the Application layer. The GCM-Communication Module functions as a Modbus TCP server, making its data accessible on a Modbus database as per the Modbus specification and GCM's requirements. Unfortunately, the Q06H is not equipped to comprehend Modbus TCP by default. As a result, you will need a program that enables the Q06H to act as a Modbus TCP "Client" to communicate with the GCM's Modbus TCP "server." The following web page provides a detailed explanation of this process: https://www.fasupportme.com/portal/...on-build-in-ethernet-port-in-iq-f-and-iq-r-en. While the article pertains to the iQ-R series, adjustments will be necessary for the GxWorks2 version compatible with the Q06H. Regrettably, there is no specific article available for configuring the Q06H as a Modbus TCP client. However, diligent searching may yield a helpful YouTube tutorial on this subject. Alternatively, you can opt for a dedicated Modbus TCP master, though this will come at a cost and require a PLC slot. For further information on MODBUS/TCP Network integration with Mitsubishi Electric Americas, please visit their official website.

While the Q06H is compatible with the QJ71E71-100 module, it is not specifically designed for Modbus communication. There is a -MB version available with the necessary protocol. Despite not being able to locate a specific YouTube video, it is possible to use the E71-100 module for Modbus communication. However, it may require writing your own CRC and control. I once encountered a problem when the wrong 232 adapter was ordered for an FX system, which should have been the 232-MB version. In this case, I had to write my own solution.

Hi everyone, I am new to programming PLCs and currently working with a Mitsubithi Q06H PLC that communicates with an Electronic module (GCM-Communication Module) via Ethernet. I am looking for guidance on how to read and write data between the PLC and Electronic Module using Modbus registers such as 40040, 40041, and so on. You can access the manual for the Communication module here: [Link]. I appreciate any comments or assistance on this issue. Additionally, if you are using the QJ71E71-100 module for this PLC, I can provide a sample program for both the PLC and HMI (GOT 2000 series) to help you better understand the process.

Rajesh mentioned that the PLC QJ71E71-100 module is specifically compatible with this particular project. If assistance is needed, a sample program for both the PLC and HMI (GOT 2000 series) can be provided for better comprehension. I am currently utilizing the Intel module QJ71E71-100. Would you be able to send a project example for my educational purposes? Thank you.

Greetings Cu Do and welcome to the forum! I have some news for you - both good and not so good. The exciting part is that it's "technically feasible" to establish communication between the Mitsubitshi Q06H and GCM-Communication Module via Ethernet. However, the downside is that you'll need to put in some effort as the Mitsubitshi Q06H doesn't naturally support the same protocol as the GCM-Communication Module. Both devices operate on Ethernet, meaning they share layers 1 through 4 of the ISO/OSI 7-Layer model (Physical L1, Data Link L2, Network L3/IP, and Transport L4/TCP). However, they differ at the Application layer. The GCM-Communication Module supports Modbus TCP server, making its data accessible on a Modbus database as per the Modbus and GCM specifications. Unfortunately, the Q06H doesn't have built-in support for Modbus TCP, so you'll need a program to enable it to operate as a Modbus TCP "Client" to communicate with the GCM's Modbus TCP "server." While I haven't personally undertaken this task, I recommend visiting https://www.fasupportme.com/portal/...on-build-in-ethernet-port-in-iq-f-and-iq-r-en for guidance. Please note that the article is tailored for the iQ-R series, so adjustments will be needed for the GxWorks2 version compatible with the Q06H. If you're unable to find a specific article for the Q06H as a Modbus TCP client, consider searching for informative YouTube videos. Alternatively, there is a dedicated Modbus TCP master available for purchase, which will require a PLC slot. For more information on MODBUS/TCP Network solutions from Mitsubishi Electric Americas, click here. Thank you for your informative explanation!

Hello, welcome to the world of PLC programming! The Modbus registers you're referring to (like 40040 and 40041) are typically associated with Input/Output data. In the Q Series PLC, you might need to use the predefined sequences from the communication module's manual to successfully read/write data. It's also essential to establish the correct connection settings between your PLC and the GCM-Communication Module. I suggest you start checking the connection settings (Network Settings or Ethernet parameters) and make sure that everything aligns as per the manual directions. Also, include any error messages if you're encountering any, they can be quite insightful for troubleshooting.

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: FAQs:

Answer: 1. How can I establish communication between a Mitsubishi Q06H PLC and a GCM-Communication Module using Modbus registers? - To establish communication between the PLC and the Communication Module using Modbus registers, you can refer to the manual provided on page 28 for detailed instructions. Ensure to configure the communication settings and address the Modbus registers correctly for reading/writing data.

FAQ: 2. What are some key considerations when working with Modbus registers 40040 and 40041 for communication?

Answer: - When working with Modbus registers 40040 and 40041, ensure that you understand the data format expected by the Communication Module and PLC. Verify the data types, addressing scheme, and communication protocol to ensure successful data exchange between the devices.

FAQ: 3. How can I troubleshoot communication issues between the Mitsubishi Q06H PLC and the GCM-Communication Module?

Answer: - If you encounter communication issues, check the configuration settings on both devices to ensure they match. Verify the network connectivity, IP addresses, and communication parameters. Additionally, monitor communication using diagnostic tools to identify any errors or inconsistencies.

FAQ: 4. Are there any specific programming tips or best practices for implementing Modbus communication between the PLC and the Communication Module?

Answer: - When programming the PLC for Modbus communication, follow the guidelines provided in the manual and ensure proper handling of data registers, error checking, and exception handling. Implement robust error recovery mechanisms to handle communication failures and optimize data exchange efficiency.

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  â†’