Hello everyone! I am facing a challenge with connecting my 2 Mitsubishi Q series PLCs, each with a built-in IP address of 192.168.3.xx, to our SCADA system using Ethernet modules QJ71E71-100 with IP addresses of 192.168.4.xx. Despite my efforts, I am unable to ping these modules from our current router, which has the address 192.168.50.xx. On the other hand, we have successfully connected Siemens S7-300 and S7-400 PLCs to a router with the address 10.133.120.xxx in the past. Unlike the Siemens PLCs, the QJ71E71-100 modules do not have settings to set the gateway for router connectivity. I need to find a solution to connect these Ethernet modules to the 192.168.50.xx router to enable communication with Kepware. Previously, the Siemens PLCs were configured with the help of the OEM company to work seamlessly with the router. How can I achieve the same level of connectivity for the Mitsubishi PLCs? Any advice would be greatly appreciated. Thank you.
Insufficient information is available in Post #1 to address the question effectively. To simplify, a hand-drawn sketch depicting the different LANs and their connections, labeled with network addresses like 192.168.50.0/24 (not variations like 192.168.50.xx), along with routers and devices labeled with their IP addresses, could be helpful. If the Mitsubishi PLCs are connected to the 192.168.50.xx side of the router, it is necessary to change the IP addresses on each Mitsubishi PLC from 192.168.3.xx or 192.168.4.xx to 192.169.50.xx. If the Mitsubishi PLCs are not on the 192.168.50.xx side of the router, devices on that side must be configured to use the router as the gateway to the respective LAN, and all routers in between should be aware of routes to LANs like 192.168.3.xx (192.168.3.0/24?) and 192.168.4.xx (192.168.4.0/24). Despite the limitations of the provided information, this response aims to offer the best possible guidance.
Utilize UDP for the Kepware as there have been ongoing issues with using TCPIP, unless it has been recently updated.
In response to a query posed by user drbitboy, it appears that additional information is required to accurately address the question at hand. One suggestion to simplify the process would be to provide a hand-drawn sketch detailing the various LANs and their connections, with network addresses (e.g. 192.168.50.0/24) and IP addresses for routers and devices clearly labeled. If the Mitsubishi PLCs are connected to the 192.168.50.xx side of the router, it will be necessary to change at least one IP address on each PLC to 192.168.50.xx. If the PLCs are not on the 192.168.50.xx side of the router, configuration adjustments will be needed for devices on that side to utilize the router as the gateway. Additionally, all routers involved must have knowledge of the routes to LANs 192.168.3.xx and 192.168.4.xx. In a separate context, a user expressed encountering issues while working with a Mitsubishi PLC Q series for the first time. Upon uploading the PLC program to their PC, they noticed only one GD2 file compared to the multiple XML files from previous backups. The user is uncertain if this discrepancy indicates a problem with their GX Works2 software.
To ensure proper network connectivity, the first step is to establish the subnet configuration for the plant's requirements. For two IPs to communicate, they must be within the same subnet or have a gateway managing traffic between multiple subnets. A recommended approach is to assign all IPs to the same subnet; for instance, utilizing the 192.168.1.x range with the standard network mask 255.255.255.0 (/24). For a larger network requiring 500 IPs, a subnet mask of 255.255.254.0 (/23) can be utilized. Opting for a more restrictive subnet mask is advisable for improved network performance. Additionally, ensure all network cables are routed from the same switch rack for an efficient physical connection.
If the original programmer coded in GXWorks2 and used Function Block Diagram (FBD) or Ladder Diagram (LAD), the program is likely structured. However, without the source file or if the symbolic information wasn't downloaded to the PLC, the ladder program may appear messy with numerous jumps to routines and lacking comments. Additionally, if a simple single file project was selected during upload, there may be differences such as missing comments or symbols. It is crucial to have a copy of the source file when working with Mitsi and GXWorks to maintain the program's format, especially if the symbolic file was downloaded to the PLC as it affects the FBD format and structure.
It appears to be a subnet conflict issue. Your Mitsubishi PLCs and Ethernet modules are on the 192.168.3.xx and 192.168.4.xx subnets respectively, yet your router is on 192.168.50.xx subnet. While the Siemens PLCs are on 10.133.120.xx which is a completely different network, and probably the default gateway was set to resolve route conflicts. For the Mitsubishi case, you might need to change the IP addresses of your PLCs and modules so they align with your 192.168.50.xx subnet, or introduce an intermediary routing device to resolve the subnet conflict, since it seems the QJ71E71-100 modules lack a default gateway setting. Make sure to consult with a networking professional to evaluate the best solution in your environment.
It seems like your issue might be related to the differing subnets of your Mitsubishi PLCs and your router. Since the QJ71E71-100 modules do not have a gateway setting, they can't reach networks outside their subnet (192.168.3.xx). One possible solution could be to align your PLC IP addresses with the 192.168.50.xx range of your router or use a multi-homed PC acting as a bridge between your different subnets. This computer will have direct connections to all your networks (192.168.3.xx, 192.168.4.xx, and 192.168.50.xx), acting as a liaison to facilitate communication. Of course, keep security considerations in mind when implementing this solution.
Looking at your problem, it seems like an IP addressing and subnetting issue. Since the Mitsubishi PLCs and the Ethernet modules have IPs in the 192.168.3.xx and 192.168.4.xx ranges respectively, they're on different subnets than your router, which is on the 192.168.50.xx subnet. You may want to reconsider your addressing scheme so that all devices are in the same subnet. Alternatively, you could potentially introduce a layer-3 switch or router that can route the traffic between the subnets. Remember to ensure that each device's subnet mask is correctly configured alongside their IP address.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: To troubleshoot connectivity issues, you can start by checking the network settings on both the PLCs and the Ethernet modules to ensure they are on the same subnet. You may also need to verify the routing configuration on the network to allow communication between devices on different IP address ranges.
Answer: Answer: Yes, it is possible to connect devices with different IP address ranges by configuring proper routing and subnet settings. Ensure that the gateway settings are correctly configured on the devices to enable communication with devices on different subnets.
Answer: Answer: Mitsubishi Q series PLCs with QJ71E71-100 Ethernet modules do not have built-in settings to configure the gateway for router connectivity. In such cases, you may need to configure the routing tables on the network infrastructure to facilitate communication between devices on different subnets. Consulting the user manual or contacting Mitsubishi support for guidance on advanced networking configurations is recommended.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.