Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
How to establish Modbus TCP communication between two PLCs?
Machine Automation Forum
A forum addressing machine automation solutions for the complete machine lifecycle. Including offers like Machine Advisor, Modicon PLC/PacDrive, Lexium or Preventa. Discuss and share knowledge on offers relating to cloud-based service platforms, machine localization and monitoring, industrial operations control, motion products as well as safety function!
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Link copied. Please paste this link to share this article on your social media post.
Hello,
I have two PLCs: a TM251MESE (which is the master) and a TM221CE24R (which is the slave). On my slave I've set some values for three memory words (%MW100=13, %MW101=11 and %MW102=6). I want to see these values on my master PLC. I have followed this example.
My problem is that when PLC is RUN mode I don't get rid of that "The bus is nor running. The shown values are perhaps not actual." What I'm concerned of is the communication status. I have seen here that the red triangle (please see the attached photo) means the controller is unable to communicate with the device, but I really don't know why. I've used a software which connects to Modbus slave and I could seethe MWs values.
What should I do to see these values, through Modbus TCP, on my master PLC?
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
If you look at your capture for the M251, you have the configured settings on the left and the current settings on the right. On the right, your IP address is at the default IP 10.10.xxx.xxx . The controller typically revert to it's default address when there's an issue with the address. A possible reason could be an IP address conflict (there's already another device with the same IP address on the network). The other thing is you have to make sure that Ethernet 1 and Ethernet 2 on the M251 are on different subnet (both can't be at 192.168.44.xxx)
I didn't see your Slave configuration under the Industrial Ethernet Manager on the M251 but is it configured as Fixed IP address? Because under your M251 Ethernet port 2, the DHCP server is active (checkbox in the config tab). When this is active and you add a new generic slave, the slave is automatically added to receive an IP by DHCP instead of fixed address. You can configure that under the Industrial Ethernet Manager in the Network Manager tab.
Link copied. Please paste this link to share this article on your social media post.
If you look at your capture for the M251, you have the configured settings on the left and the current settings on the right. On the right, your IP address is at the default IP 10.10.xxx.xxx . The controller typically revert to it's default address when there's an issue with the address. A possible reason could be an IP address conflict (there's already another device with the same IP address on the network). The other thing is you have to make sure that Ethernet 1 and Ethernet 2 on the M251 are on different subnet (both can't be at 192.168.44.xxx)
I didn't see your Slave configuration under the Industrial Ethernet Manager on the M251 but is it configured as Fixed IP address? Because under your M251 Ethernet port 2, the DHCP server is active (checkbox in the config tab). When this is active and you add a new generic slave, the slave is automatically added to receive an IP by DHCP instead of fixed address. You can configure that under the Industrial Ethernet Manager in the Network Manager tab.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.