AB Generic string communication

Contr_Conn · Nov 7, 2019

The reason that many samples mentioned EWEB is because it was the first module that supported Sockets. It was the only module for many years until Sockets were introduced in EN2T and 5370 complactlogix platforms. While there is a small difference in implementations, most of sample code applications use workarounds to make these differences transparent for users.

Jeev · Nov 7, 2019

Holmux said:
I am just trying to work true the errors, I can also be my socket simulator that is teasing me.

Use Hercules.

Holmux · Nov 9, 2019

Here are the AOI after I made a few changes:

Added the length the the write masage, but I can't see what else I am doing wrong, it just returns a general error that doesn't give me much.

Contr_Conn · Nov 9, 2019

What exact error?
Did you get the error before you made changes?
This AOI is been out for many year and we used it many times without making any changes.

Holmux · Nov 9, 2019

Well I think it has been the source length that has been giving me problems, here is what I used:

Socket Create = 12 Bytes

OpenConnectionMsg = 32 Bytes (8 + length of destination string)
Error Code= 16#0013 (Configuration data size too short)

SocketWriteMsg = = 16 Bytes + length of string
Error Code = 16#00ff, Extended error code = 16#0000_0039 (General Error)

SocketDeleteMsg = 0 Bytes
SocketReadMsg = 8 Bytes

Contr_Conn · Nov 9, 2019

https://literature.rockwellautomation.com/idc/groups/literature/documents/at/enet-at002_-en-p.pdf
Page 49 has explains both errors

Error 13 means that your source data calculations are incorrect and UDT has less bytes that you are sending.
If you are using the AOI, it does source length calculations correctly.

Error 39 is related to the instance number that must be copied from Create message. Without seen your code I cant say what you are doing wrong.
AOI does it correctly.

So why you are not using AOI?

Holmux · Nov 9, 2019

That is what I am trying to do.

I this copy of the AOI, the only thing I have done is is adding a rung to copy ind my test string.

And change the addressing to the Ethernet port of the CPU and the IP for the port.

PC Socket server: 192.168.0.157, Port 20001

PLC 192.168.0.81

Contr_Conn · Nov 9, 2019

Try unmodified code first

Holmux · Nov 9, 2019

Had the same thought, just went back to the starting point

Holmux · Nov 9, 2019

Would you know what version of Logix 5000, the AOI was programmed in ?

Holmux · Nov 9, 2019

The PC I am using at the moment only have version 31 installed.

So my theory is that somethings get lost in translation, I will try installing version 16.4 and change the addressing for the Ethernet port before translating into version 31

Contr_Conn · Nov 9, 2019

If you open L5X files then you can see that V2 was provided in v16.04 and V3 in V28.
I never used V3, but V2 should be working just fine in all versions

Jeev · Nov 10, 2019

I used this AOI in V30 just a few days ago. Did you copy and past the code or import it? If you copy/pasted it, all the values will be initialised, including the MSG structures and tags, so nothing will work properly. If you import the AOI, the following is all you will need:

1) SKT_MSG_Client_Create.Path is $01$00
2) SKT_DATA_Client.Create_Source.Addr.Port is 20001
3) SKT_DATA_Client.Connect_Source.DestAddr is 192.168.0.157?port=20001
4) Set your Client_Data.Timeout in the AOI Configuration Dialog(e.g. 20ms)
5) Enable the client
6) Write the data

Be careful which program you use to check the comms. I have had mixed results with different programs, and Hercules works well. See how you go

Contr_Conn · Nov 10, 2019

I assume that OP read the instructions.
The description in this technote clearly states that you must use Rung Export/Import to preserve Message configurations and other settings. Copy/Paste will not work.

Contr_Conn · Nov 11, 2019

I can only say that ACD file that you have attached in post #22 above has nothing to do with sample code that you should be using from Technote 50122.

AB Generic string communication

Contr_Conn

Member

Jeev

Member

Holmux

Lifetime Supporting Member

Contr_Conn

Member

Holmux

Lifetime Supporting Member

Contr_Conn

Member

Holmux

Lifetime Supporting Member

Contr_Conn

Member

Holmux

Lifetime Supporting Member

Holmux

Lifetime Supporting Member

Holmux

Lifetime Supporting Member

Contr_Conn

Member

Jeev

Member

Contr_Conn

Member

Contr_Conn

Member

Similar Topics