Santiago PB

Hi flex, thanks for your answer. I attach again the file with socket 3 configured on both options. We test it with modbus slave and with the IO LINK master and nothing happens. It does not receive any information. If you can review to see where could be the problem, I really appreciate it- socket 3 puerto 20257.vlp

Hi Flex, thanks for answer. I also work with Luis and Facundo who have made some questions. This is the situation> The program Luis posted if we use the socket 3 for Modbus configuration, when we open the configuration socket option into that block, Socket 3 indicates "socket 3 Deafaulkt TCP(20257) Slave as you can see if we put that option, socket 3 / it should work as salve, and we need to be master. Same situation for socket 2, it appears to be set as slave at the end of the sentence. Sockets 0 and 1 we understand it is not useful for our application. Note that we at the TCP/IP Socket init block, we already at option "cliente/Server" we already set it as Client/Master. Is it ok for you? Is this configuration enough or correct? Which socket should we use, if we see that this options do not set it as Master? About Modbus IP read holding register Can you see why it has not answer if the slave is ok and available at the network? (we tested the IO Link master device (as slave confirmed) communication with modbus poll and works fine). We really appreciate your answer and time. Regards Santiago.