TCP Socket Communication with A-B's between Logix Controllers

Finnbliss

Member
Join Date
Jul 2021
Location
Roskilde
Posts
3
Silly question:
I would like to know if anyone has done TCP Socket communication between Logix controllers?
I do know it works fine from any Control or Compact Logix controller to a high level programmed application residing in a computer.

Now, I would like to do the same between Logix controllers.
As an example between a ControlLogix and a CompactLogix.

There is a reason not to use Ethernet IP in this case.
Anyone that has done this before?
Pls feel free to comment.
 
We used it to test Modbus AOIs that are Sockets based. One PLC was running Client, another Server.

But not using a native Ethernet/IP is like inventing a bicycle with square wheels - your sockets comms will be much slower, less reliable and use all processor resources to parse the data that is normally done in firmware
 
Problem solved...

Hi, got the problem solved as questioned by me.
I know very well the entertainment using squared wheels. ;)
But this was a customer request.


They wanted to use the same standard as they use with Siemens S7.

Of course in the same way with Rockwell controllers. :p.

I made the socket communication working and built AOIs' for TCP read and write to protect the code from third party itchy fingers messing it up.


Did all this by using an 1756-EN3TR module for ControlLogix and communicated directly to the CompactLogix built in Ethernet port.

The code functions just fine without any noticeable delays.
I based it all on the code that exists in RA's knowledge base with an EWEB module and the app attached.

Took me two days to figure it all out.
 
I think the delays i ran into is "Where is the start and end of that message? If there all variable length messages, then your stuck processing the message byte at a time to decide start, type of message, content, end. So to speed it up just bring a big chuck of the messages at the read buffer and do the processing internal of "start, type of message, content, end".

That is my only suggestion.
Plus i thought RA does give an AOI of the interface.
 
Jim3846

No need to execute messages byte by byte.
The write socket has a standard connection size of 472 bytes.
Large connection size is 3972 bytes.
Depends how we configure the MSG instruction.


If this is not enough, we can use multiple sockets. :)

Saw that RA have AOIs' but I prefer my own with extended fault handling etc. I'm kind of old fashioned and do know what I have built. Hehehe.

Anyway, this was a good lesson for all TCP socket communication, no matter what is on the other end of a controller from RA.
Like other controllers, bar code readers, printers etc..
 
Hello Finnbliss,
May I know how to configure MSG instruction to increase the socket size?
My current socket size(4650) is bigger than the the Max size(3972), may I know is it possible to increase the socket size?
 

Similar Topics

Hi all I'm new to Allen Brabley Plc's, but hope that some of you are able to help on this issue. Hardware: Allen Bradley Micro850 cpu Software...
Replies
0
Views
2,192
Hi all, I have two questions I am hoping someone might have some information on. 1. I remembered reading somewhere on this forum that you could...
Replies
5
Views
157
Hello, I'm trying to setup a TCP connection from a Compactlogix 5069-L306ER to a TDI checkweigher to receive real-time weight data of the...
Replies
6
Views
280
I would like to communication with application installation in my printer server via TCP port 5450. i.e ., 71.16.40.200:5450 . How can i write...
Replies
1
Views
362
I'm trying to set up a TCP Socket connection between a CompactLogix 1769-L16 and a printer that can receive external data through a TCP socket. I...
Replies
7
Views
3,294
Back
Top Bottom