(0)| 2/25/2025 7:18 AM | |
|
Joined: 7/9/2015 Last visit: 1/7/2026 Posts: 4493 Rating:
|
Hi, Perhaps this is the reason: For an HMI with firmware V17.0.0.6 to be able to establish a connection to a controller with SSL/TLS encryption, the date and time of the HMI must be within the validity period of the SSL/TLS certificate of the controller. If the date and time on the HMI are up to date, a connection to the controller should be established. In this case, the time on the control unit is not taken into account. Check this FAQ: No connection to PLC after WinCC Panel Images V17 Update 6Regards, Towome |
|
|
|
This contribution was helpful to
|
|
| 2/25/2025 8:10 AM | |
|
Joined: 1/7/2025 Last visit: 11/5/2025 Posts: 16 Rating:
|
No, the clock on the hmi is not up to date. I did not connect and check if the clock on the plc is up to date (because it is far away) but what I do know is that when the user manually sets the hmi clock to the current time, it works without any problems for a certain period of time. When the machine is turned off for 2 weeks. The hmi clock and date are corrupted. Edit : hmi version 19.0.0.0 unified basic
|
Last edited by: eem28 at: 02/25/2025 08:35:50 |
|
| 2/26/2025 6:22 AM | |
|
Joined: 9/21/2012 Last visit: 1/11/2026 Posts: 4846 Rating:
|
Set the PLC to be NTP server and the HMI to sync with that. |
Follow us on