Hello all,

I'm working on the integration of a new TP900 panel in a Simatic manager project. Because the TP900 is not configurable in Simatic Manager I will need to use TIA Portal with a device proxy. I have followed the device proxy configuration manual (Entry ID: 73502293) and have checked my work several times now. Unfortunately I'm still unable to get a connection going between the CPU and the HMI.

Project info;

• CPU 315-2 PN/DP V3.1 (IP = xxx.xxx.xxx.10, both in TIA and Simatic)
• TP900 Comfort V15.1.0.0 (IP = xxx.xxx.xxx.90), only configured in TIA
• PC IP = xxx.xxx.xxx.247
• TIA V15.1 Update 7
• Simatic manager V5.6 SP2
• In TIA; added device proxy and synchronized it as per the manual
• No error LED's on any of the modules
• Connection directly over 1 meter ethernet cable (prefab)
• When checking accessible devices in TIA, both the CPU and the HMI are detectable on the correct addresses
• HMI tags are referencing the device_proxy data
• Runtime on the HMI closes after a few seconds (this seems to stop when I delete a big chunk of the blocks in the CPU - this is a test project so for now it's not a problem - but still no connection)
• No network conflict possible due to direct connection
• In NetPro in Simatic the CPU is connected to ethernet
• I'm checking the connection with 2 always true booleans (1 merker and 1 bool from a DB) from CPU

Any help would be appreciated!

Thanks in advance

FIXXED!

For people facing the same very specific problem;

The problem was caused due to a wrong configuration of the HMI in TIA. In the runtime settings, the project ID was set to 1 which was causing the runtime to be terminated. I found this after enabling all the different alarm types in the alarm buffer properties (system alarms etc) and noticing a "Incorrect project ID" alarm after which the runtime was terminated.

After setting the project ID to 0, the connection was made and the runtime worked correctly. 

The manual mentioned above is very straight forward and easy to follow. If a problem comes up and the Simatic project is an existing project, the problem is probably somewhere in TIA configuration. Make sure to enable all the alarm options in the WinCC alarm windows. This really helped me find the cause pretty quickly. Also - GSD files of the HMI or any changes in the Simatic project aren't nescesarry for a correct configuration. 

Thanks for your response. 

That's a bad explaination on my part. I didn't configure the CPU in TIA. Only the proxy. The IP is set in both TIA and Simatic.