我也没有用过

WINCC帮助这么描述的

To synchronize the standard client with its server, you only need to enter the "ccTMTimeSync.EXE" application in the startup list of the standard client. In this case, no additional synchronization may be active on the default client (e.g.: DCF77 Client Service or other 3rd Party Software, which provides the local PC time).

If an AS is used as the time master, the synchronization interval there should be set to one second.

When time synchronization is used on a PC, the user logged on to Windows must either belong to the "Power user" group or have permission to "Change the system time".

GMT or the local winter time is used for all user data and time telegrams on all devices on the system bus.

Upgrading V5 projects is only possible online if on the "Computer properties" dialog box on the "Parameters" tab "PLC clock setting" option is set to "PLC is set to the local winter time all year (WinCC V5 compatibility mode)". This option is activated by default for migrated V5 projects and deactivated for newly created V6 projects.

When using Softnet (BCE), only one Softnet module can be used for time synchronization. This applies to Softnet operation via Softnet modules (CP 1512, CP 1612) and via the normal network card.

Due to a system feature in connection with the interplay between AS417-4H and CP443-1EX11 (Industrial Ethernet), the time synchronization on the redundant System Bus is only possible as from CP443-1EX11 Firmware Version 2.3.

If the "Time synchronization via terminalbus (Slave)" function should be used, the user accounts (Windows login) of the respective partner stations must be set up on all the computers on which the users log on to the partner stations (Windows login).

Up to Version WinCC V 5.1, clock synchronization on the system bus was also supported by PROFIBUS. This function is no longer directly available since WinCC V 6.0. For questions concerning this problem, please contact Customer Support.