Hi,

I have a PC ES with TIA Portal V17, WinCC Professional V17 and WinCC Runtime Professional V17. The same PC must works as an OS.

When I try to download the project, appears the message "Project download to server failed" (see attachment).

Plus, after I changed the name of the PC in the TIA Portal project I can not compile and save the project too, also if I try tho save as a new project.

I've checked FAQ "What should you watch out for when downloading from the WinCC/PCS 7 Engineering Station to the Operator Station (ES-OS download)?" but it seems all correct.

Thanks 

Now I can create the project file and launch with RT Start but I have another problem now.

My CPU 1513 communicate with 3 remote ET200SP CPU in IO Device mode, so my CPU port X2 is configured for IO Device communication and the port X1 is configured to communicate with any partner to talk with PC SCADA. In the SCADA IE port I set port X1 CPU 1513 as a partner, and S7ONLINE acces point in the HMI connection; the PC Name is the same set in the SCADA configuration and the IP is the same; PC and CPU are in the same network.

Now if I connect only X2 port I can go online with the CPU and SCADA not communicate with PLC, but when I connect the X1 port too the communication with CPU fault. In both cases SCADA seems not communicate with CPU.

Can the CPU ports communicate to SCADA and another CPUs at the same time? Wher I'am wrong?

Thanks, I'm very confused right now.

Hi,

You are writing about using X1 and X2. The cpu 1513 only has an X1 so I assume you are not talking about the cpus X2.

If you are talking about an IPC X1 and X2 then WinCC can only communicate via one netcard.

If you notice the setting of the connection in the project, it usually refers to "S7ONLINE".

In Simatic Net, you locate this under "Communication Settings" under "Access Points" where you select which netcard S7ONLINE should use.

It is the same you select in "Set PG/PC Interface" also.

So all cpus should be in same subnet or there should be a router to cpus in other subnets.

I hope this helps.

Michael

unknown user

Hi,

You are writing about using X1 and X2. The cpu 1513 only has an X1 so I assume you are not talking about the cpus X2.

If you are talking about an IPC X1 and X2 then WinCC can only communicate via one netcard.

If you notice the setting of the connection in the project, it usually refers to "S7ONLINE".

In Simatic Net, you locate this under "Communication Settings" under "Access Points" where you select which netcard S7ONLINE should use.

It is the same you select in "Set PG/PC Interface" also.

So all cpus should be in same subnet or there should be a router to cpus in other subnets.

I hope this helps.

Michael

Sorry, I mean X1_P1 port and X1_P2 port of the CPU, but after your post I assume that are the same thing; the SCADA PC is a third part PC with 2 netcard, so if I understood correctly, one netcard should use to communicate with PLC (programming with TIA ecc.) and the other netcard for communication between PLC and SCADA, I'm right? 

Of course two netcard will be on the same subnet (es. 192.168.1.xxx)

Many Thanks

Hi,

It will be the same on a non-Siemens PC as well.

But if two (more) netcards cannot be located in the same subnet.

So let's say the netcards in the pc is called X1 and X2, then you must give them addresses in different subnets, like:

X1 = 192.168.1.10 / 24

X2 = 192.168.2.10 / 24

(24 = 255.255.255.0)

If both were in the same subnet, then tcp/ip would not know which netcard to send traffic out from, at least not unless you start making some internal static routing in Windows which is a separate topic.

If you have TIA and WinCC Scada runtime installed on same PC, they can both use the same netcard for communication/programming.

Best regards

Michael

Michael K

Hi,

It will be the same on a non-Siemens PC as well.

But if two (more) netcards cannot be located in the same subnet.

So let's say the netcards in the pc is called X1 and X2, then you must give them addresses in different subnets, like:

X1 = 192.168.1.10 / 24

X2 = 192.168.2.10 / 24

(24 = 255.255.255.0)

If both were in the same subnet, then tcp/ip would not know which netcard to send traffic out from, at least not unless you start making some internal static routing in Windows which is a separate topic.

If you have TIA and WinCC Scada runtime installed on same PC, they can both use the same netcard for communication/programming.

Best regards

Michael

Still have no communication between PLC and PC also connecting directly PC to the CPU and also with simulator.

In the attachment you will find my settings on TIA Portal Project and in the SCADA PC.

Hi,

Your settings looks ok, except for the S7ONLINE. It should be the .TCPIP.1. See the attached picture.

Also, remember there is a certificate in the cpu (depending on firmware) that an prevent communication.

Make sure after a hw config change and download to cpu that you compile WinCC and download this also.

Also make sure the clock in the cpu and pc are the currect time. This is required for the certificate to work.

On the WinCC server, you can run the channel diagnose program in. It is in the Windows Start menu under Siemens Automation and is called "WinCC Channel Diagnostics".

Also, you can find logfile for the communication in the:

c:\program files (x86)\Siemens\Automation\SCADA-RT_V11\WinCC\diagnose

Best regards

Michael

Michael K

Hi,

Your settings looks ok, except for the S7ONLINE. It should be the .TCPIP.1. See the attached picture.

Also, remember there is a certificate in the cpu (depending on firmware) that an prevent communication.

Make sure after a hw config change and download to cpu that you compile WinCC and download this also.

Also make sure the clock in the cpu and pc are the currect time. This is required for the certificate to work.

On the WinCC server, you can run the channel diagnose program in. It is in the Windows Start menu under Siemens Automation and is called "WinCC Channel Diagnostics".

Also, you can find logfile for the communication in the:

c:\program files (x86)\Siemens\Automation\SCADA-RT_V11\WinCC\diagnose

Best regards

Michael

Hi, after set S7ONLINE to TCPIP.1 the problem has been fixed.

Many thanks to you all