ExtSol Posted June 22, 2020 Report Share Posted June 22, 2020 (edited) Dear Support, The connecting is working. I have no idea why can't i receive the message from PLC when pressing te F2 key. PC IP end with 103.5 PLC IP end with 103.109 PLC type: Vision280 Have you any idea? Best regards: ExtSol Edited June 22, 2020 by ExtSol Quote Link to comment Share on other sites More sharing options...
MVP 2021 Flex727 Posted June 22, 2020 MVP 2021 Report Share Posted June 22, 2020 The first thing I would do is change the contacts for 'F1' & 'F2' (SB 58 & 59) to Positive Transition contacts. Quote Link to comment Share on other sites More sharing options...
ExtSol Posted June 23, 2020 Author Report Share Posted June 23, 2020 Quote The first thing I would do is change the contacts for 'F1' & 'F2' (SB 58 & 59) to Positive Transition contacts. Not helped. Have you another idea? Quote Link to comment Share on other sites More sharing options...
MVP 2021 Flex727 Posted June 23, 2020 MVP 2021 Report Share Posted June 23, 2020 Post your program and we'll have a look. Quote Link to comment Share on other sites More sharing options...
ExtSol Posted June 23, 2020 Author Report Share Posted June 23, 2020 Here is the program. Thank you test3.vlp Quote Link to comment Share on other sites More sharing options...
ExtSol Posted June 23, 2020 Author Report Share Posted June 23, 2020 Here is the version and image from device. Quote Link to comment Share on other sites More sharing options...
MVP 2021 Ausman Posted June 24, 2020 MVP 2021 Report Share Posted June 24, 2020 You are showing serial comms, yet are talking TCP/IP. cheers, Aus Quote Link to comment Share on other sites More sharing options...
ExtSol Posted June 25, 2020 Author Report Share Posted June 25, 2020 Ausman, i used serial com to program the device, so i not show serial com, i want to show model and version information. Program over TCP/IP is working well, but communicate with PC not work. Quote Link to comment Share on other sites More sharing options...
MVP 2021 Ausman Posted June 25, 2020 MVP 2021 Report Share Posted June 25, 2020 On 6/23/2020 at 12:59 AM, ExtSol said: PLC IP end with 103.109 In your program it is 10.180.103.139, and the connection attempts show this. But I don't think this is the issue. There might be a bit of client/master confusion going on. What happens if you switch these around a little in testing, at both ends, to try all possible variations? cheers, Aus Quote Link to comment Share on other sites More sharing options...
AlexUT Posted June 25, 2020 Report Share Posted June 25, 2020 EctSol, Please make initialization of all 4 sockets in Ladder. This is a good practice. And set SB 168. Quote Link to comment Share on other sites More sharing options...
MVP 2021 Ausman Posted June 25, 2020 MVP 2021 Report Share Posted June 25, 2020 9 hours ago, AlexUT said: This is a good practice. Alex, can you please explain why? Just curious. Also, good call on 168, I missed that. I've said it before, why isn't this a default setting in Visilogic? It seems pointless to not have it on. If you're doing ethernet, it's necessary. If you aren't, it won't affect anything. cheers, Aus Quote Link to comment Share on other sites More sharing options...
MVP 2021 Joe Tauser Posted June 26, 2020 MVP 2021 Report Share Posted June 26, 2020 Use a different socket and a different port. Socket 1:20256 is the default programming access and the V280 may be stomping on it. Try Socket 2:20257. Is your terminal program expecting a CRLF (0D0A) ETX at the end of the string transmission? Did you try adding a TCP/IP Scan block to your program and sending data back down? Joe T. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.