Jump to content

TCP/IP Socket communication not work

Recommended Posts

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:









Edited by ExtSol
Link to comment
Share on other sites

  • MVP 2023
On 6/23/2020 at 12:59 AM, ExtSol said:

PLC IP end with 103.109

In your program it is, 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

Link to comment
Share on other sites

  • MVP 2023
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

Link to comment
Share on other sites

  • MVP 2023

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.


Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...

Important Information

This site uses cookies. By clicking I accept, you agree to their use.