Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

New KTP400 not communicating to 1212 cpu

Created by: nepiter at: 11/1/2024 10:54 AM (2 Replies)

Rating (0)

Thanks 0

3 Entries

11/1/2024 10:54 AM	Rate (0)
nepiter Regular Member Joined: 9/23/2011 Last visit: 7/23/2025 Posts: 6 Rating: (0)	Hi, I have a problem, that i've never come across.. I am replacing the KTP400 panel, because it has small scratch on the screen though it's working fully. New KTP400 arrived, and I did connect ethernet and power to panel. I did set IP address manually from the panel, as usually. Then I did download Tia Wincc project to the panel. Everything ok so far. But when the project is started at the panel, it is not communicating with CPU. CPU buffer says: System initiated session termination (Security information: system initiated session termination) What I have done so far to get communication: I have upgraded panel image I have upgraded CPU firmware I have deleted certificate from CPU, and I did generate new one with this date (Before that, I did check the time from the panel and from the CPU) I have recovered panel software with USB-media, just to make sure that I haven't messed anything up. Funny thing is that whenever I connect the old panel, it works like a charm.. But not the new one.. With the old panel, CPU diagnostic buffer is just quiet, everything OK. No idea how to proceed. Any ideas what to do?

Suggestion To thank Quote Answer

11/1/2024 11:58 AM	Rate (0)
nepiter Regular Member Joined: 9/23/2011 Last visit: 7/23/2025 Posts: 6 Rating: (0)	Two days struggle, and now I've found temporarily solution. I did tick the parameter "Only allow secure PG/PC and HMI communication" OFF from the CPU parameters. I assume that the problem is with the certificate.. But what to do? I have already created new certificate (PLC communication certificate -> Add new -> created one with date from 1970 etc. -> Then selected new connection mechanism with a new certificate. But do I need to export this certificate, and copy to HMI with USB.. I doubt it.. I believe that the certificate should be transferred when downloading. But if someone knows or has some experience, I'd love to hear. ( Btw, recovering/restoring HMI with USB is a bit tricky thing. The Panel seem to be very picky with the usb media. Kingston, maxell, sandisk, verbatim, unknown brand, or any version of these, or gen 1 or 2, did not work with recovering.. I had over 14 usb sticks on the table last night, and last one worked: Corsair 1 gen, 1gb stick. ) Attachment Not the correct solution but works.JPG (170 Downloads)
	Last edited by: nepiter at: 11/01/2024 11:59:02
Suggestion To thank Quote Answer

11/7/2024 8:57 AM	Rate (0)
Murof Platinum Expert Joined: 8/3/2009 Last visit: 9/12/2025 Posts: 16409 Rating: (1935)	Hello nepiter you do not have listed which FW Version your PLC has and which Image Versino your Panel. It s because only newer HMI Image Versios do work with the Secure HMI communication. for example: https://support.industry.siemens.com/cs/de/en/view/109820712 also you should care about the Date/time of your Panel. The Basic Panels do not have a retentive Clock, so it will only synch if your establish a connection to the PLC... but this will not work if the panel time is out of the validity area of the certificate. So a NTP Server connection would be the best solution in this situation. Also you should not make a certificate with startdate 1970... Use realistic timeranges You do not have to transfer the certificate manually, it will be sent by project transfer from TIA Portal. you do not have to care about it Bye Murof
	If this Information really helps, you could use the Rate function
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on