sandreou Posted August 18, 2020 Report Share Posted August 18, 2020 I am trying to connect to a V280 over ethernet but i get TCP fail window from the pc (windows 10) i can ping the ip that i configured in V280. If i disconect the V280 i cannot ping it so i guess the ethernet cable to the plc and my configuarion is ok. I get the same message either with Visilogic or Remote operator This is the first time i experience this problem and this procedure is the same i follow for many years. Is the first time i try it on win10 Please advice Link to comment Share on other sites More sharing options...
MVP 2023 Flex727 Posted August 18, 2020 MVP 2023 Report Share Posted August 18, 2020 I presume this is an internal network (i.e. you're not trying to connect over the internet)? If so, your PC needs to be on the same subnet, meaning your PC IP address needs to be 192.168.10.xxx. Also, why do you have all those SB 1 contacts in front of the subroutine calls? They aren't hurting anything, but they are totally unnecessary. Link to comment Share on other sites More sharing options...
sandreou Posted August 18, 2020 Author Report Share Posted August 18, 2020 Thank you for your feedback Yes is over intranet and the pc is on the same subnet , with IP 192.168.10.206 and as i told in my previous post i can ping the 192.168.10.150 from the pc Link to comment Share on other sites More sharing options...
MVP 2023 Flex727 Posted August 18, 2020 MVP 2023 Report Share Posted August 18, 2020 Go into INFO Mode and confirm Socket 1 is set to: Port: 20256 TCP Slave Protocol type: Pcom Link to comment Share on other sites More sharing options...
AlexUT Posted August 18, 2020 Report Share Posted August 18, 2020 Hi, Set SB 168 as follows: Make Init for all 4 sockets to default port numbers. *Check in INFO mode sockets settings and port numbers. B.R. Link to comment Share on other sites More sharing options...
sandreou Posted August 18, 2020 Author Report Share Posted August 18, 2020 thanks for your support please be more specific how i get into INFO mode? Link to comment Share on other sites More sharing options...
MVP 2023 Flex727 Posted August 18, 2020 MVP 2023 Report Share Posted August 18, 2020 From the Help file: Quote Entering Information Mode To enter Information mode: -Non-touchscreen models: press the <i> key on the Vision’s keyboard. -Touchscreen models: touch the screen in an area that is not occupied by a Keypad Entry variable or other screen object that has been assigned a Touch Property. Maintain contact for several seconds The controller enters Information Mode and requests a password. Enter your password. The default password is 1111. From there, go to Ethernet, then Socket Parameters. Link to comment Share on other sites More sharing options...
MVP 2023 Ausman Posted August 18, 2020 MVP 2023 Report Share Posted August 18, 2020 11 hours ago, sandreou said: This is the first time i experience this problem and this procedure is the same i follow for many years. Is the first time i try it on win10 Do you mean that you used to use the same procedure with Visilogic on an earlier version of Windows? Like 7 or 8? If so, have you upgraded to a new PC that has W10 as supplied, or just upgraded your O/S to W10 on the same PC? Or are you trying Visilogic for the first time after doing similar things with other devices? If you are essentially working on a new install of Visilogic, did you install using right click run as admin, and also ensured the visilogic.exe is set to run as administrator as well? These questions are very relevant to further suggestions. As for SB168 mentioned by Alex, you are activating it incorrectly. You do not do the coil after the card init like you have shown, so remove it. In Visilogic go to the operand list at the bottom and in System Bits scroll to SB168. The "Power Plug" at the top of one of the columns is whether the bit is turned on or off at power up. If you click the relevant box of the table, you'll get a selector dropdown appear. Choose SET, which will then show as a 1. After doing a compile/ save, if you then search for SB168 by doing a right click anywhere in the relevant operand row, and then select "Find SB168", the program will show that it doesn't appear. It doesn't need to be anywhere, as the system knows it is on via the power-up setting. Turning it on: Searching should show: cheers, Aus Link to comment Share on other sites More sharing options...
sandreou Posted August 19, 2020 Author Report Share Posted August 19, 2020 Thank you for your replies please see attached the configurations of the sockets When i change socket 1 to TCP/Client and then i press ESC >ESC>ESC to go back to the user software and i enter back info mode is again set to TCP/Server I guess TCP Slave= TCP/Client Also where i set Protocol Type: Pcom Please advice Link to comment Share on other sites More sharing options...
MVP 2023 Flex727 Posted August 19, 2020 MVP 2023 Report Share Posted August 19, 2020 41 minutes ago, sandreou said: I guess TCP Slave= TCP/Client Yes, it needs to be set to TCP/Client in order for you to communicate from VisiLogic (at least to my knowledge). 41 minutes ago, sandreou said: Also where i set Protocol Type: Pcom I was thinking about the Enhanced Vision models that offer that option. Do you have the program file that is in the PLC? Are you initializing Socket 1 in the program? If all else fails, you may need to connect with serial comms in order to further troubleshoot. Link to comment Share on other sites More sharing options...
AlexUT Posted August 19, 2020 Report Share Posted August 19, 2020 To be able establish connection from PC to PLC: 1. It is recommended to initialize all 4 sockets to default values, as in Help. 2. PLC Socket 1 TCP/Sever(Slave) Port 20256. 3. Connect from VisiLogic to PLC IP Port 20256. When online, or download, port status should be "Connected" and PCOM. Link to comment Share on other sites More sharing options...
MVP 2023 Flex727 Posted August 19, 2020 MVP 2023 Report Share Posted August 19, 2020 2 hours ago, Flex727 said: it needs to be set to TCP/Client Oops, it need to be TCP/Server. Why can't we just stick to Master/Slave? Link to comment Share on other sites More sharing options...
sandreou Posted August 20, 2020 Author Report Share Posted August 20, 2020 So AlexUT based on the pictures i sent sockets are correct Also its a new pc windows 10 and i run the applications as administrator. I dont understand what is wrong Link to comment Share on other sites More sharing options...
MVP 2023 Ausman Posted August 20, 2020 MVP 2023 Report Share Posted August 20, 2020 sandreou, please answer my other questions, they are relevant. cheers, Aus Link to comment Share on other sites More sharing options...
sandreou Posted August 20, 2020 Author Report Share Posted August 20, 2020 "Do you mean that you used to use the same procedure with Visilogic on an earlier version of Windows? Like 7 or 8? If so, have you upgraded to a new PC that has W10 as supplied, or just upgraded your O/S to W10 on the same PC? Or are you trying Visilogic for the first time after doing similar things with other devices?" This is the first time i installed it on a new pc with windows 10. Also is the first experience of visiologic with windows10 "If you are essentially working on a new install of Visilogic, did you install using right click run as admin, and also ensured the visilogic.exe is set to run as administrator as well?" I run it as administraotr but during installation i did not install it as administrator but i didnt get any error These questions are very relevant to further suggestions. "As for SB168 mentioned by Alex, you are activating it incorrectly. You do not do the coil after the card init like you have shown, so remove it. In Visilogic go to the operand list at the bottom and in System Bits scroll to SB168. The "Power Plug" at the top of one of the columns is whether the bit is turned on or off at power up. If you click the relevant box of the table, you'll get a selector dropdown appear. Choose SET, which will then show as a 1. After doing a compile/ save, if you then search for SB168 by doing a right click anywhere in the relevant operand row, and then select "Find SB168", the program will show that it doesn't appear. It doesn't need to be anywhere, as the system knows it is on via the power-up setting." Because i cannot connect remotely i have to change that locally and i need to schedule a visit because is far away from me the PLC.But I guess this has nothing to do with the problem because this is the same configuration i used on ll of other applications i did without any problem Link to comment Share on other sites More sharing options...
MVP 2023 Flex727 Posted August 20, 2020 MVP 2023 Report Share Posted August 20, 2020 1 hour ago, sandreou said: Because i cannot connect remotely i have to change that locally and i need to schedule a visit because is far away from me the PLC. Wait, you're trying to connect to IP address 192.168.10.206 over the internet? Above you said it was intranet. You CANNOT connect directly to a device with an IP in the private address space over the internet. You have to have a public IP address to connect to and have the router port forward to the 192.168 address. Link to comment Share on other sites More sharing options...
MVP 2023 Ausman Posted August 20, 2020 MVP 2023 Report Share Posted August 20, 2020 6 hours ago, sandreou said: Also is the first experience of visiologic with windows10 Does this mean you have never experienced it at all until trying it on W10? Or have you used it successfully on other Windows versions? Your statement "this is the same configuration i used on all of other applications" implies this. But maybe you are meaning you have used the same configuration in totally different PLC programs. In essence I am asking did you have Visilogic running OK on previous versions of Windows? If you did, can you go back to those versions easily to use what worked then? The reason I am focussing on possible prior usage is that W10 has all sorts of restrictions on network behaviour that sometimes have to be adjusted to suit. Also some A/V programs need adjustment as well. 6 hours ago, sandreou said: i did not install it as administrator but i didnt get any error You don't get any errors during the installation process, you can get errors during that actual use of the program. Re Flex's questions, they might just be you having translation issues? Intranet = local network connections. Internet = the big wide world. If you connected to the PLC ok before just using your local network....your "Intranet".....then it won't connect using the same settings if you try to connect via the Internet. cheers, Aus Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now