So currently the green circle appears left to the Modbus_TCP_Slave. But it turns into a red tri- angle after a while. When I do a rightklick on the Slave and choose diagnosis then it works for about 2 minutes until the red tri- angle appears again.
So currently the green circle appears left to the Modbus_TCP_Slave. But it turns into a red tri- angle after a while. When I do a rightklick on the Slave and choose diagnosis then it works for about 2 minutes until the red tri- angle appears again.
Thank you very much for the answer today. After today I know that I always have to connect the slave device to a master device. And thanks a lot for the information about the Unit- ID. That was certainly important. I also found a list on wikipedia regarding the standard ports for the different protocols. You can see the link in the following. Without a master its not possible to specify the port or Unit-ID and other relevant aspects of the slave device. https://de.wikipedia.org/wiki/Liste_der_standardisierten_Ports...
Thank you for your answer. I watched a video where someone was able to connect the Soft PLC to the TOP OPC UA Server without a master. I will send the link in the following. But I will try to implement your advice. Because when I dont use a master Im not able to give a Unit-ID to the slave device and also not an IP Adress. https://www.youtube.com/watch?v=cOr08a8JuMY&t=18s
Hello together, Im currently working on a Project in Codesys using the integrated Soft PLC. I want to connect the Soft PLC to the TOP OPC UA- Server. The variables that I used in the Codesys program are already visible in the "Adress Space" in the UA Expert- Client that I use. And when I change the value of a variable in the UA Expert- Client then this change is also visible in the Codesys programm and vice-versa. When I click on "Log in" and then "Run" in Codesys, the "Modbus_TCP Slave Device" on...