Siemens S7 TCP IP Comunication

[antoine]

Dear colleagues,

I am working on a good old Siemens S7 (315-2DP), I installed an ethernet board CP343-1.

My (old) s7 software is V5.5 + SP1

I added Simatic NET PC Software, edition 2008 + SP2.
This is the first surprise, I see no difference in the NetPro window.

I found a beautiful manual on the Siemens Web site:

Configuring a TCP connection via Ethernet (TCP native) between a SIMATIC S7 and a PC with Socket Interface

[FONT=Arial, Helvetica, sans-serif]They are big differences between what they show and what I have on my console:[/FONT]
[FONT=Arial, Helvetica, sans-serif]
[/FONT]
[FONT=Arial, Helvetica, sans-serif]Their ID is "0001 A050"[/FONT]
[FONT=Arial, Helvetica, sans-serif]My ID is "00D6 0006"[/FONT]
[FONT=Arial, Helvetica, sans-serif]D6 = 214 in decimal, very different with their 0001 !?[/FONT]
[FONT=Arial, Helvetica, sans-serif]
[/FONT]
[FONT=Arial, Helvetica, sans-serif]The LADDR input of the "AG_RECV" function is called "Module adress in hardware configuration"[/FONT]
[FONT=Arial, Helvetica, sans-serif]In their example they have "W#16#100"[/FONT]
[FONT=Arial, Helvetica, sans-serif]Where does that come from ???[/FONT]




IP adress, OK I can put my adress 192.168.0.200
PORT: ??? I have nowhere to type it in ???


Option "Send / Receive"
I have nowhere to type it in ???




And of course all the trials I have done put the processor in STOP, bad situation ...


I can give you more infos or screencopys, but let's go back to basics, are my software versions OK, can this have a bad influence on the configuration ?


Thanks in advance,


Antoine

 

[L D[AR2P#0.0]]

The LADDR is in hex, but it is shown in decimal in the h/w config:

W#16#100 = 256

 

[L D[AR2P#0.0]]

Are you following this doc?

https://support.industry.siemens.co...and-a-pc-with-socket-interface?dti=0&lc=en-WW

 

[antoine]

Yes, exactly !

 

[mk42]

You enter the port and send/receive in different tabs of the TCP connection properties window.

 

[L D[AR2P#0.0]]

e.g.

 

[cardosocea]

I always found that the information required to set this up in the code is in the "General Information" tab of the window L D[AR2,P#0.0] shows on post 6.

If I remember correctly, the manuals indicated as such too, but it's been a while since I played with it.

 

[Bratt]

I added Simatic NET PC Software, edition 2008 + SP2.

This is the first surprise, I see no difference in the NetPro window.

This software is not needed for what you are trying to accomplish! Regular Step7 is enough

 

[antoine]

You're right Bratt, it's completely unneeded, I'll remove it !

For the others very good suggestions I will try that when I will be back on site, I will let you know...

 

[antoine]

Dear all,

After a few days, it works !
The first problem was in the istallation of the Ethernet card, I selected randomly the version.

But it is really needed, it is written on the front face of the board, not only on the side (not visible when the board is in the PLC rack)

The config adviced by L D[AR2,P#0.0] is very important but these windows are only available when you create it, then no more accessible (?!)

Finally, the length of the message was difficult to find, I used another receiver to capture it, it has 9 bytes (9*8bits) more than the original table sent.

The main problem is that when you change the length in the S7, you need to reset the sender, else you are in a strange situation like a part of the end the previous message begins the new one ...

So when I reseted the sender for my last trials, I found it !

Thanks and good luck to the others Siemens Ethernet players

Antoine

 

[Bratt]

The config adviced by L D[AR2,P#0.0] is very important but these windows are only available when you create it, then no more accessible (?!)

Double click the connection in Netpro to access the configuration again.

The main problem is that when you change the length in the S7, you need to reset the sender,

I don't think you understand the basis of TCP/IP. The protocol is stream based there is no such thing as lenght! Thats why Siemens use IsoOnTcp.

 

[Bratt]

Read this FAQ. It contains a pretty good explanation on why it does not work as you expect it to do.

When data is transferred with the TCP, the transfer is made in the form of a data stream. In this case no information is given about the length nor about the beginning and end and so the recipient cannot tell where one message ends in the data stream and where the next begins.