Troubleshooting Communication Between PLCs Using TCSEGDB23F24FA Modbus Plus Proxy Module

Question:

Hello everyone, I need assistance with a module involving communication between PLCs through a Modbus plus network. The manual instructs me to use an ADDM block and a Read_Var block. I have set the address for the ADDM to 'Machine{192.168.1.5}3' to read register 40809 from another PLC connected via Node 3 through two bridges. The routing involves M340 (192.168.1.1) to Proxy (192.168.1.5), Proxy (Node 3) to Bridge A (Node 8) to Bridge B (Node 9) to the PLC on Node 3. Despite following the example in the manual with an address of 'CPU_CoPro{192.168.1.50}2', I receive an error code of 7. I have also attempted addressing the ADDM to 'Machine{192.168.1.5}8.9.3' and adjusting the routing to index 3, but the issue persists. Any insights on troubleshooting this problem would be greatly appreciated. Thank you.

Top Replies

What types of Programmable Logic Controllers (PLCs) are used in your communication systems?

The M340 device is linked via Ethernet to a proxy that communicates with a Modicon Quantum PLC using the Modbus Plus Network. The communication was successful with a Quantum Unity processor previously, so it is expected to function properly with the M340 now.

We utilize Modicon Quantum PLCs and also have bridges in our systems. Are you familiar with Proworx32 or UnityPro software for programming these devices?

Proworx Nt - Your Solution for Reliable Network and IT Services

As per davexr's comment, Proworx Nt is a top choice for programming software compatible with Quantum and Unity PLCs, as well as the M340 series. Experience the benefits of Proworx for streamlined automation tasks.

Hey there! When it comes to troubleshooting, issues with the communication through a Modbus Plus network could be arising from a number of different areas. One common one is a potential mismatch in node addresses. Cross-verify the physical switch settings of your node identifiers in your network with the ones configured in your ADDM block. The error code 7 usually points towards addressing or communication problems. Moreover, ensure your Proxy is correctly configured to communicate with Bridge A and Bridge B. Sometimes, simply restarting the PLC can also resolve such issues. Also, double-check your Gateway configuration since the routing must be clearly defined there. Hope it helps. If the problem persists, it might be useful to rope in your Modbus Plus network provider for in-depth troubleshooting support.

Hi there! It seems like you've got quite a complex setup, but albeit an interesting one! Error 7 often means that there's something going wrong in your communication pathways. One possibility you may look into is the correctness of your network addresses. Especially considering the complicated routing that you've described. Make sure that your PLCs, bridges, and proxies, are all on the correct addresses. Also, keep in mind to appropriately encapsulate your information across different parts of the network, as information can get lost during these transitions. Lastly, remember that proxy servers can sometimes add their own issues, especially if they're not properly configured.

It sounds like you might be having an addressing issue. The Error code 7 usually corresponds to the inability of the master device to locate the slave device in Modbus. Keep in mind, you need to confirm that the slave IP address and Node address are correctly specified. In addition, make sure that both M340 and the PLC on Node 3 share the same network parameters - subnet mask and default gateway. Also, you should check if there's any disruption in the Modbus plus network or if there are conflicting nodes.

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. What is the purpose of the ADDM block and Read_Var block in communication between PLCs using Modbus plus network? - The ADDM block is used to define the address of the device you want to communicate with, while the Read_Var block is used to read specific registers from that device.

FAQ: 2. How should the address be configured in the ADDM block for communication between PLCs via Modbus plus network?

Answer: - The address in the ADDM block should be set based on the device's IP address and node number, following the format 'Machine{IP_address}Node_number'.

FAQ: 3. What could be the reason for receiving error code 7 when trying to communicate between PLCs through the Modbus plus network?

Answer: - Error code 7 could indicate a communication error, possibly due to incorrect addressing, routing configuration, or network setup.

FAQ: 4. How can the routing configuration be adjusted to troubleshoot communication issues between PLCs connected via Modbus plus network?

Answer: - Ensure that the routing configuration in the network setup matches the actual path of communication between the PLCs, including the correct node numbers for each device involved.

FAQ: 5. What steps can be taken to troubleshoot and resolve communication issues when encountering errors like code 7 in Modbus plus network communication?

Answer: - Verify the addressing, routing, and network configuration settings to ensure they are accurately set up. Check for any physical connection issues or network disruptions that may be causing communication errors.

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