If this video is helpful, please like, share and subscribe to my channel! Thank you. MICRO850 2080-LC50-24QWB Modbus TCP Server PLC IP: 192.168.0.90 Subnet Mask: 255.255.255.0
@babu: Modbus TCP Client is what you should look for instead for your micro850. First, you also need to know your drive IP address and Modbus mapping in order to configure it in the micro850 PLC program. Just think like if you (as a PLC) are looking for someone (any drive. VFC or Modbus TCP Server devices), you (as a PLC) will need to know the city (IP address) and the home address (Modbus mapping) of that person (any Modbus TCP Server devices). Modbus mapping should be like 40001.0 bit to start/stop the VFD, 40001.1 bit for VFD running status feedback to the PLC, 40002 AND 40003 REAL/FLOAT for analog output from 0.0 to 100.0% to VFD and so on. Hopefully my example is simple and make the most sense to you. Second, just follow the below 2 videos to configure your micro 850 as Modbus TCP Client. Thank you for subscribing to my channel. Should you have any more questions please let me know. If my answers and the recommended videos are helpful to you, please let me know by giving my comment a like. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-F0R90ZiI1Mg.html ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-lDZ9KA5DGXc.html
@Jim H: Yes, it is the terminology. For Modbus RTU, it’s slave and master. For Modbus TCP, it’s Server and client. Slave and Server are the same. Master and client are the same. If you are looking for Modbus TCP client, the below video might be helpful. Thank you for subscribing to my channel. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-F0R90ZiI1Mg.html
@babu: See the above comment. Thank you. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-F0R90ZiI1Mg.html ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-lDZ9KA5DGXc.html
