Maintaining time synchronization on the DeltaV PK controller’s network is required. This requires the communication between a time master and a time slave. The time synchronization protocol used for the Standalone DeltaV PK controller is NTP (Network Time Protocol).
The Standalone DeltaV PK controller is, by default, the NTP Time Master for its respective project SKID. All associated DeltaV nodes (operator workstation, CIOC’s/WIOC’s/SZ) sync with the Standalone DeltaV PK controller automatically.
You can set the controller's time in the PK Controller Administration application to prevent any drift that may happen.
Each Standalone DeltaV PK controller and its associated nodes rely on a request-response method for time synchronization. For each node in the project, NTP has the IP address of the PK controller configured as a time master. The other nodes query the PK's IP address explicitly. This prevents the associated nodes from obtaining time from any other PK controller on the same network. This also means that, for each project skid, all nodes within the project effectively operate as a time island and do not synchronize at all across projects (that is, across PK controllers).
To use a GPS time server for your project, use the appropriate IP addressing (as outlined in Books Online); and, connect the GPS and PK to the appropriate network. The nodes automatically synchronize with the GPS.
The Engineering Station has NTP installed on it. Engineering Stations that are not permanently attached to the PK controller must be in time sync with the PK controller before connecting to it. Set the Engineering Station's time to match the controller's time using normal Windows date and time settings.