Studio 5000 Clock Sync Service Configuration Guide

Purpose
The main purpose of this guide is to show how to configure the New Studio 5000 Clock Sync Service. It
will list the differences between the New Studio 5000 Clock Sync Service and the old Logix5000 Clock
Update Tool. It will also describe what applications it should and should not be used in.

Note: At this time, the Studio 5000 Clock Sync Service should not be used as a Grand Master (GM) of
time for any CIP Sync Motion Application.
Contents
Studio 5000 Clock Sync Service Configuration Guide ................................................................................... 1
Purpose ..................................................................................................................................................... 1
Background ............................................................................................................................................... 3
Additional CIP Sync Documents ................................................................................................................ 3
Windows Operating System (OS)/ VMWare Compatibility ...................................................................... 4
WIN OS Tested and Approved .............................................................................................................. 4
WIN OS Tested and Not Approved ....................................................................................................... 4
Comparison ............................................................................................................................................... 4
Studio 5000 Clock Sync Service vs. Logix5000 Clock Update Tool ........................................................ 4
List of CIP Sync Capable Devices ............................................................................................................... 5
Applications............................................................................................................................................... 5
Applications approved .......................................................................................................................... 5
Applications not approved .................................................................................................................... 5
Architectures ............................................................................................................................................. 6
Ex1. Clock Sync Service configured as a Grandmaster (GM) ................................................................ 6
Ex2. Clock Sync Service configured as a Slave (S) ................................................................................. 6
Studio 5000 Clock Sync Service Configuration .......................................................................................... 8
Enable CIP Sync and Choosing a NIC ..................................................................................................... 8
Master/ Slave Configuration ................................................................................................................. 9
Local Clock Priority .................................................................................................................................. 10
Other Features ........................................................................................................................................ 11
Clock Sync Service Status ........................................................................................................................ 12
Ex1. Clock Sync Service Grandmaster Status ...................................................................................... 13
Ex2. Clock Sync Service Slave Status ................................................................................................... 14
Background
The Studio 5000 Clock Sync Service was designed to synchronize the Wall Clocks on Logix Controllers and
other I/O devices that have been equipped with the CIP Sync feature. Refer to the list of CIP Sync
Capable Devices below. The Studio 5000 Clock Sync Service can also be used to synchronize PC Wall
Clocks which are used as a time source for FT View Studio SE HMI tag based alarm or FT Historian event
timestamp recording.

The Studio 5000 Clock Sync Service was released as part of the v24 Studio 5000 Tools suite. The Clock
Sync Service can either be uploaded as part of the Studio 5000 V24 install or via the Studio 5000 Tools
install. Both upload mechanisms can be found on The Rockwell Automation Compatibility Downloads
Website.

http://compatibility.rockwellautomation.com/Pages/MultiProductSelector.aspx?crumb=111

Additional CIP Sync Documents

This Studio 5000 Clock Sync Service document focuses on the Clock Sync Service Tool and does not deep
dive into CIP Sync Features/ Topics. To broaden your CIP Sync understanding, please refer to these other
documents below.

 Integrated Architecture and CIP Sync Configuration: Can be found on Rockwell Automations
Literature Library. Pub IA-003B-EN-P
http://literature.rockwellautomation.com/idc/groups/literature/documents/at/ia-at003_-en-
p.pdf
 CIP Sync Troubleshooting Guide: Can be found on Rockwell Automations Knowledgebase.
KB Doc. 623577
https://rockwellautomation.custhelp.com/app/answers/detail/a_id/623577
Windows Operating System (OS)/ VMWare Compatibility
WIN OS Tested and Approved
 MS Windows 7 64bit

WIN OS Tested and Not Approved

 MS Windows XP
 MS Windows OS running in a VMWare Environment
 MS Windows 7 32bit

Comparison
Studio 5000 Clock Sync Service vs. Logix5000 Clock Update Tool
Studio 5000 Clock Sync Service:

 Synchronizes time on Logix Controllers and devices that use CIP Sync Only. (Logix 5000
v18 - v20 and Logix Designer v21 above)
 Runs as a Service on a WIN PC. You do NOT need to be logged on to the PC for the
service to run.
 Time Sync. Resolution:
o Grand Master (+/- 1 milliseconds)
 Needs to reside on the same subnet as all other CIP Sync Devices it is sending/ receiving
time to/from unless used in conjunction with a Boundary Clock Device.
 NOT designed to be a Grand Master of time for any Motion Application.
 RSLinx Classic is NOT required.
 CIP Sync Slave device limit of 256.

Logix5000 Clock Update Tool:

 Synchronizes time on PLC5, SLC, MicroLogix, and Logix Controllers with CIP Sync Not
enabled (Logix 5000 up to V20 and Logix Designer v21 above)
 Runs as an Applications on a WIN PC. You do need to be logged on to the PC to run this
application.
 Time Sync. Resolution:
o Master (+/- 500 milliseconds to 1 second)
 Does NOT need to reside on the same subnet as other devices it is sending time to.
 NOT designed to be a Grand Master of time for any Motion Application.
 RSLinx Classic is required.
 There is no physical device schedule limitation, but this does depend on the type of
devices you have in the schedule and the performance of the PC you have the Clock
Update Tool running on.
List of CIP Sync Capable Devices
Device Clock Type Capability Firmware/
Software (SW)
1756HP-TIME (GPS) module Ordinary (Hand Settable) Master/Slave Series A: v2.03.01
w. Transparent Switch and/or Pass Thru Series B: v3.001
1756-L6x/ L7x ControlLogix Controller Ordinary (Hand Settable) Master/Slave v18 - Present
1769-L1x/L2x/L3x CompactLogix Controller Ordinary (Hand Settable) Master/Slave v20 - Present
w. Transparent Switch and/or Pass Thru
Studio 5000 Clock Sync Service Ordinary (Hand Settable) Master/Slave SW: v1.00.00
1756-ENxT Ethernet Communication Boundary (Not Hand Master/Slave Series B/C: v5.008
Settable) Series D: v10.007
1756-ENxTR Ethernet Communication Boundary/ Transparent Master/Slave Series A/B: v5.008
(Not Hand Settable) and/or Pass Thru Series C: v10.007
1756-ENxF Ethernet Communication Boundary/ Transparent Master/Slave Series A/B: v5.008
(Not Hand Settable)
1756-IB16ISOE / 1756-IH16ISOE Input Ordinary (Not Hand Slave v2.010
Settable)
1756-IB16IF Fast Digital (SOE) Input Ordinary (Not Hand Slave V1.01
Settable)
1756-OB16IEF Fast Digital Output Ordinary (Not Hand Slave V2.012
Settable)
1756-OB16IEFS Fast Scheduled Digital Ordinary (Not Hand Slave V1.011
Output Settable)
1732E-IB16M12SOEDR and IB8M8SOER Ordinary/ Transparent Slave v1.008
ArmorBlock (Not Hand Settable) v1.012
1783-MSxxT Stratix 8000/ 8300, Ethernet Boundary/ Transparent Master/ Slave or v15.2(1)EY1
Switch Pass Thru
1783- BMSxx Stratix 5700, Ethernet Switch Boundary/ Transparent Master/ Slave or v15.2(1)EY1
Pass Thru
1783-ETAP, 1783-ETAP1F, 1783-ETAP2F, Transparent Pass Thru v2.002
ETAP embedded switches modules

Applications
Applications approved
 Time/ Scheduled Applications that need Logix Controller Wall Clocks synchronized to execute a
process based on time.
 Time Stamp Applications that use CIP Sync to synchronize time across multiple Logix Controllers
and I/O devices on the same network.
 Alarm and Event Time Stamp Applications that use CIP Sync to synchronize time between Logix
Controllers and PC’s running FT View Studio SE and/or FT Historian.

Applications not approved

 Motion applications that use CIP Sync to synchronize time between Logix Controller and Drives
are NOT approved.
Architectures
The Studio 5000 Clock Sync Service can be used in Star, Linier, and/or Device Level Ring (DLR) network
Architectures.

Ex1. Clock Sync Service configured as a Grandmaster (GM)

Ex2. Clock Sync Service configured as a Slave (S)

Following the CIP Sync Time Synchronization Flow:
Time Synchronization always starts at the Grandmaster of Time and is propagated thru the network via
Communications devices such as 1756-EN2T(R) and the Stratix 8000/ 5700 Managed Switch.

 The PC1 running the Studio 5000 CIP Sync Service is CIP Sync Enabled and is designated the Grand Master
(GM) of time. It is also the Real Time Source for the control system. The Real Time Source could have been
updated via an NTP Server on the network or Hand Set. Since PC1 is now synchronized with the rest of the
control system, FT View Studio SE and FT Historian will timestamp Alarm and Events at a more accurate
resolution. CIP Sync Time is passed to Remote 1756-EN2T and other CIP Sync devices on the network.
(Reference Ex1 above).
 The 1756- L7x CLX Controller is CIP Sync Enabled and is designated the Grand Master (GM) of time. It is
also the Real Time Source for the control system. The Real Time Source could have been updated via a
1756-Time (GPS) module (not shown here) or Hand Set. CIP Sync Time is passed to the Local 1756- EN2T
module and other Logix Controllers (not shown here) and 1756-SOE modules in the same chassis.
(Reference Ex2 above).
 The Local 1756- EN2T Communication module is CIP Sync Enabled and is designated a Slave (S) on the CLX
Backplane, but is the Master (M) of time on the Ethernet Network. CIP Sync Time is passed to the Remote
1756- EN2T modules and other CIP Sync devices on the network. (Reference Ex2 above).
 The Stratix 8000 or 5700 Managed Ethernet Switch is CIP Sync Enabled and is either designated a
Transparent or Boundary Clock. In most cases, it will be configured as a Transparent Clock and will pass
CIP Sync Time thru the switch with no packet propagation delays to other CIP Sync capable devices on the
network. (Reference Ex1 and/or Ex2 above).
 All Remote 1756- EN2T Communication modules are CIP Sync Enabled and are designated as Slaves (S) on
the Ethernet Network, but are Masters (M) of time on the CLX Backplanes. (Reference Ex1 and/or Ex2
above).
 The 1769- L3xERM CPX Controller is CIP Sync Enabled and is designated a Slave (S) on the Ethernet
Network. CIP Sync Time is passed from PC1 running the Studio 5000 Clock Sync Service (Reference Ex1
above) or via the 1756-EN2T module located in the Local (GM) chassis and will update the controllers Wall
Clock Time. (Reference Ex2 above).
 The Remote 1756- SOE modules are CIP Sync Enabled and are designated Slaves (S) on the CLX Backplane.
CIP Sync Time is passed from its Local 1756-EN2T module and will update the SOE’s Clock Time for
accurate Event Time Stamping purposes. (Reference Ex1 and/or Ex2 above).
 The 1734E-SOE Armor Block modules are CIP Sync Enabled and are designated Slaves (S) on the Ethernet
Network. CIP Sync Time is passed from PC1 running the Studio 5000 Clock Sync Service (Reference Ex1
above) or via the 1756-EN2T module located in the Local (GM) chassis (Reference Ex2 above) and will
update the SOE’s Clock Time for accurate Event Time Stamping purposes. These modules are outfitted
with Dual Embedded Switch Technology set for Transparent Clock Mode by default. The Transparent
Clock will pass CIP Sync Time thru the embedded switch with no packet propagation delays to other CIP
Sync capable devices on the network. (Reference Ex1 and/or Ex2 above).
 The PC2 running the Studio 5000 CIP Sync Service is CIP Sync Enabled and is designated the Slave (S) of
time. CIP Sync Time is passed from PC1 running the Studio 5000 Clock Sync Service (Reference Ex1 above)
or via the 1756-EN2T module located in the Local (GM) chassis and will update the Wall Clock Time on PC2
(Reference Ex2 above). Since this PC is now synchronized with the rest of the control system, FT View
Studio SE and FT Historian will timestamp Alarm and Events at a more accurate resolution.
Studio 5000 Clock Sync Service Configuration
Enable CIP Sync and Choosing a NIC
1. After installing the Studio 5000 Clock Sync Service, the service can launched by browsing to it in
the tool tray as seen below.

2. Navigate to the Clock Sync Configuration Tab

 Check the Enable Clock Sync Service Box
 Choose the correct NIC Interface. Note: If you do not see the correct NIC Interface
double check the PC’s connection to the network. If the PC is connected, shut down the
Clock Sync Service and reopen. You should then see the proper NIC Interface.
 Click the Apply button at the bottom of the tool anytime you make a change on the
Clock Sync Service.
Master/ Slave Configuration
The Clock Sync Service is equipped with two Operating Modes.

 Slave- Only Mode: Choose this operating mode when a different device has been chosen to be
the Grandmaster of time on the control network.
 Master/ Slave Mode: Choose this operating mode if the Clock Sync Service will be the
Grandmaster (GM) of time on the control network or might be a backup to the (GM). This is the
default setting.
 Automatically Toggle W32Time (NTP) Service: Check this box to enable automatic time updates
from an NTP Server located somewhere else on the network. Uncheck when in Slave or in Slave-
Only modes. When the Clock Sync Service is in Slave Mode, it is receiving its time from the CIP
Sync Grandmaster on the control network.
Local Clock Priority
The Clock Sync Service and any device equipped with the CIP Sync feature has two different Local Clock
Priority.

 Priority1 (Master Override): If there is ever a need to manually override what device is the
Grandmaster, this can be accomplished by entering a lower value (range 0-255), which makes
the Clock Sync Service have a higher Priority over another device. This can be used to override
Best Master Clock Arbitration over let’s say a Hand Set Logix Controller.
 Priority2 (Tie- Breaker): If there is ever a need to manually override what device is the
Grandmaster between two identical devices, this can be accomplished by entering a lower value
(range 0-255), which makes the Clock Sync Service have a higher Priority over another device.
This can be used to override Best Master Clock Arbitration over let’s say a second PC running the
Clock Sync Service.

Note: For more information pertaining to Priority1/2 concepts please refer to the CIP Sync User Manual
and/or Troubleshooting Guide specified earlier in the Additional CIP Sync Documents section above.
Other Features
Other Clock Sync Service features that maybe useful are as follows.

 Automatically start Clock Sync Service on Boot: When Checked the Clock Sync Service will
automatically start when the PC is booted up.
 Local Clock Identity: This is where a user of the Clock Sync Service can enter a unique Name and
Location of this PC. Default is the PC User Name as seen below.
 Local Clock Offset (leap seconds): Number of leap seconds calculated by the earth’s rotation.
Default is 34. This is also the default of all Logix Controllers. Note: Logix Controller (34) leap
seconds cannot be modified. In most cases, you will leave the Clock Sync Service Leak Second at
a value of 34, until the Logix Controller leap second is changed in a future firmware release.
Clock Sync Service Status
The Clock Sync Service Status tab displays what device is currently the Grandmaster (GM) of time and
compares this with the Clock Sync Service Local Clock Status.

 Clock Sync Service: Indicated the Clock Sync Service is Enabled or Disabled.
 Current Time: Indicated current time of the Clock Sync Service. This is the time you would
monitor/ compare with other CIP Sync devices on the network.
 Grandmaster Clock: Displays what device on the network is the Grandmaster (GM) of time. This
can be deciphered by examining the Grandmaster Clock Description in addition to the (GM)
Clock Identity, Accuracy, and Configuration.
 Local Clock: Displays the Studio 5000 Clock Sync Service Clock Status. This includes Sync Status,
Port State, and Clock Identity, Accuracy, and Configuration.

Note: For more information pertaining to Clock Identity, Accuracy, and Configuration concepts please
refer to the CIP Sync User Manual and/or Troubleshooting Guide specified earlier in the Additional CIP
Sync Documents section above.
Ex1. Clock Sync Service Grandmaster Status
Indicated that the Clock Sync Service is the Grandmaster (GM) of time because both the Grandmaster
Clock and Local Clock Status Information are equal.

Other indications the Clock Sync Service is the Grandmaster (GM):

 Local Clock/ Sync Status = N/A (Master)

 Port State = Master
 Offset from Master = 0ns because the Clock Sync Service is the (GM)
Ex2. Clock Sync Service Slave Status
Indicated that the Logix Controller is the Grandmaster (GM) of time because it has a more accurate clock
then the Clock Sync Service which is Slave (S). Notice the Clock Identity values are different as well.

Other indications the Clock Sync Service is a Slave (S):

 Local Clock/ Sync Status = Synchronized

 Port Status = Slave
 Offset from Master = -0.7974ms