Gei-100513 Hmi Time Synch

gGE Industrial Systems

GEI-100513

HMI Time SynchronizationFor SPEEDTRONIC Turbine Control

Document: GEI-100513 Issued: 2001-09-04

HMI Time SynchronizationFor SPEEDTRONIC Turbine Control

© 2001 General Electric Company, USA.All rights reserved.

Printed in the United States of America.

These instructions do not purport to cover all details or variations in equipment, nor to provideevery possible contingency to be met during installation, operation, and maintenance. If furtherinformation is desired or if particular problems arise that are not covered sufficiently for thepurchaser�s purpose, the matter should be referred to GE Industrial Systems, Salem, Virginia,USA.

This document contains proprietary information of General Electric Company, USA and isfurnished to its customer solely to assist that customer in the installation, testing, operation, and/ormaintenance of the equipment described. This document shall not be reproduced in whole or inpart nor shall its contents be disclosed to any third party without the written approval of GEIndustrial Systems.

Document Identification: GEI-100513, original releaseTechnical Writer/Editor: Teresa DavidsonTechnical Responsibility: Steve Smith

ARCNET is a registered trademark of Datapoint Corporation.Ethernet is a trademark of Xerox Corporation.SPEEDTRONIC is a trademark of General Electric Company, USA.Windows® are registered trademarks of Microsoft Corporation.

We welcome comments and suggestions to make this publication more useful.

Your Name Today’s Date

Your Company’s Name and Address Job Site

GE Requisition No.

Publication No.Your Job Function / How You Use This Publication

Publication Issue/Revision Date

If needed, how can we contact you?

Fax No.

Phone No.

E-mail

Address

General RatingExcellent Good Fair Poor Additional Comments

Contents � � � � _____________________________________________________________Organization � � � � _____________________________________________________________Technical Accuracy � � � � _____________________________________________________________Clarity � � � � _____________________________________________________________Completeness � � � � _____________________________________________________________Drawings / Figures � � � � _____________________________________________________________Tables � � � � _____________________________________________________________Referencing � � � � _____________________________________________________________Readability � � � � _____________________________________________________________

Specific Suggestions (Corrections, information that could be expanded on, and such.)

Page No. Comments______ ________________________________________________________________________________________ ________________________________________________________________________________________ ________________________________________________________________________________________ ________________________________________________________________________________________ ________________________________________________________________________________________ __________________________________________________________________________________

Other Comments (What you like, what could be added, how to improve, and such.) __________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)

� Superior � Comparable � Inferior � Do not know Comment ____________________________________________

Detach and fax or mail to the address noted above.

gReader CommentsGeneral Electric Company



To:GE Industrial SystemsDocumentation Design, Rm. 2911501 Roanoke Blvd.Salem, VA 24153-6492 USAFax: 1-540-387-8651 (GE Internal DC 8-278-8651)


.........................................................................Fold here and close with staple or tape ..........................................................................................

____________________________________________________________________________________

GE Industrial SystemsDocumentation Design, Rm. 2911501 Roanoke Blvd.Salem, VA 24153-6492 USA

...........................................................................................Fold here first.........................................................................................................

Placestamphere.

GEI-100513 HMI Time Synchronization Safety Symbol Legend •••• a

Safety Symbol Legend

Indicates a procedure, condition, or statement that, if notstrictly observed, could result in personal injury or death.

Indicates a procedure, condition, or statement that, if notstrictly observed, could result in damage to or destruction ofequipment.

Indicates a procedure, condition, or statement that should bestrictly followed in order to optimize these applications.

Note Indicates an essential or important procedure, condition, or statement.

b •••• Safety Symbol Legend SPEEDTRONIC Turbine Control GEI-100513

To prevent personal injury or equipment damagecaused by equipment malfunction, only adequatelytrained personnel should modify anyprogrammable machine.

The example and setup screens in this manual donot reflect the actual application configurations. Besure to follow the correct setup procedures foryour application.

GEI-100513 HMI Time Synchronization Contents •••• i

Contents

Chapter 1 Overview

Introduction ..............................................................................................................1-1System Overview......................................................................................................1-2

Ethernet Synchronization: NTP and NTP Server .............................................1-3Stagelink Synchronization: Timesync ..............................................................1-3CSF and Serial Network Synchronization: MSP_TSET ...................................1-3

How to Use This Document .....................................................................................1-4Text Conventions ..............................................................................................1-4

How to Get Help.......................................................................................................1-4Related Documents...................................................................................................1-5

Document Distribution ......................................................................................1-5

Chapter 2 Network Time Protocol with Ethernet

Introduction ..............................................................................................................2-1Product Overview.....................................................................................................2-2

NTP (Only) Operating Modes ...........................................................................2-2NTP Server (Only) Operating Mode .................................................................2-2NTP Time Acquisition Modes...........................................................................2-2NTP Configuration Utility.................................................................................2-4

NTP Configuration Screen Examples.......................................................................2-5Broadcast Client using the Standard Configuration Option ..............................2-6Unicast Client using the Standard Configuration Option ..................................2-7Broadcast Master using the Custom Configuration Option...............................2-8Broadcast and Unicast Master using the Custom Configuration Option...........2-9

NTP Server Configuration Examples .....................................................................2-11Unicast Server .................................................................................................2-11Broadcast and Unicast Server..........................................................................2-13

Operation................................................................................................................2-15Event Viewer (NTP Only)...............................................................................2-15

NTP Server Hardware Interface .............................................................................2-16Synchronization of Mark VI and EX2100 Controllers ...........................................2-17NTP Status Indicator ..............................................................................................2-19

Starting the Status Indicator ............................................................................2-19Menu Commands ............................................................................................2-20Icon Status .......................................................................................................2-20

NTP Diagnostics.....................................................................................................2-21Starting and Closing the Program....................................................................2-21Configuration ..................................................................................................2-22Data Display....................................................................................................2-22Monitoring NTP ..............................................................................................2-24Monitoring NTP Server...................................................................................2-25

ii •••• Contents SPEEDTRONIC Turbine Control GEI-100513

Contents�continued

Chapter 3 Synchronization Over Stagelink

Introduction ..............................................................................................................3-1Configuration............................................................................................................3-2

Hardware ...........................................................................................................3-2ARCNET Driver................................................................................................3-2Timesync Software (Timesync.dat file) ............................................................3-4

Timesync Operation .................................................................................................3-7Time Card Initialization.....................................................................................3-8Timesync Startup and Initialization...................................................................3-9GTS Tracking ..................................................................................................3-10Flywheel Operation .........................................................................................3-11Low Resolution Operation...............................................................................3-11

Timesync Diagnostics and Monitoring...................................................................3-12Enable or Disable Timesync............................................................................3-12Load Major Time into the Time Card..............................................................3-13Obtain Timesync Status Information...............................................................3-13Obtain Timesync Trace Information ...............................................................3-20Timesync Log File...........................................................................................3-21

Connecting the PC Time Card to a Satellite Time Source (GTS)...........................3-22Validating GTS Signal Reception ...................................................................3-22

System Configuration Issues ..................................................................................3-22Sample Topologies (Timesync only) ......................................................................3-23

Chapter 4 Mixed Network Topology Guidelines

Introduction ..............................................................................................................4-1Overview of HMI Types...........................................................................................4-2Type 1: HMIs with a Time Card Supplying Time to the Ethernet and At Least One Stagelink Network...........................................................................................4-2

Timesync Configuration....................................................................................4-3NTP Server Configuration.................................................................................4-3

Type 2: HMI Synchronized to and/or Supplying Time to Only One Network Type (Ethernet or Stagelink) ..................................................................................4-4Type 3: HMI Synchronized to Ethernet Time and Supplying Time to at Least One Stagelink Network...........................................................................................4-5

Timesync Configuration....................................................................................4-5NTP Configuration ............................................................................................4-5

Type 4: HMI Synchronized to Stagelink Time and Supplying Time to the Ethernet...................................................................................................................4-6

Timesync Configuration....................................................................................4-6NTP Configuration ............................................................................................4-6Example Topologies..........................................................................................4-7

GEI-100513 HMI Time Synchronization Contents •••• iii

Contents�continued

Chapter 5 PC Time Card Installation

Introduction ..............................................................................................................5-1Bancomm bc620AT or bc627AT Time Card ...........................................................5-2

Setting the Base I/O Address.............................................................................5-2Setting the IRQ..................................................................................................5-3Card Installation ................................................................................................5-3Connecting to the Global Time Source (GTS) ..................................................5-3Testing the Cards...............................................................................................5-4

KSI Odetics tPRO-PC Installation and Configuration............................................5-11Setting the Base I/O Address...........................................................................5-11Setting the IRQ................................................................................................5-12Card Installation ..............................................................................................5-12Connecting the Global Time Source (GTS) ....................................................5-12

Appendix A IRIG Nomenclature and Codes

Glossary

iv •••• Contents SPEEDTRONIC Turbine Control GEI-100513

Notes

GEI-100513 HMI Time Synchronization Chapter 1 Overview •••• 1-1

Chapter 1 Overview

IntroductionWhen computers and controllers communicate within the same network and acrossnetworks, their clocks should be synchronized. This helps ensure that time stampsproduced by each controller will match each other when recording any dataexchange.

This document describes system-level time synchronization for the SPEEDTRONICturbine control systems. It discusses the configuration requirements forsynchronizing time on different types of controller networks.

Chapter 1 provides an overview of time synchronization programs used withdifferent turbine controllers. Additionally, it defines document contents and product-related reference information, as follows:

Section Page

System Overview......................................................................................................1-2Ethernet Synchronization: NTP and NTP Server .............................................1-3Stagelink Synchronization: Timesync ...............................................................1-3CSF and Serial Network Synchronization: MSP_TSET ...................................1-3

How to Use This Document .....................................................................................1-4Text Conventions ..............................................................................................1-4

How to Get Help.......................................................................................................1-4Related Documents...................................................................................................1-5

Document Distribution ......................................................................................1-5

Chapter 2, Time Synchronization Over Ethernet � NTP, discusses the NTP andNTP Server programs and configuration requirements for Mark VI and EX2100controllers.

Chapter 3, Time Synchronization Over Stagelink, discusses using the Timesyncprogram and configuration requirements for Mark V and Mark V LM controllers.

Chapter 4, Mixed Network Topology Guidelines, includes configurationrequirements for systems with both Ethernet and Stagelink-based devices.

Chapter 5, PC Time Card Installation, identifies the time cards used with thedifferent turbine control systems with guidelines.

Appendix A, IRIG Nomenclature and Codes.

1-2 •••• Chapter 1 Overview SPEEDTRONIC Turbine Control GEI-100513

System OverviewTo synchronize time, a single source (pc) within the system is selected as theprimary time reference for all other system components. Other sources providebackup. The source can receive it�s time from either an internal system clock, or aCoordinated Universal Time (UTC) satellite transmission.

(Refer to the figure below.) A turbine control system generally consists of one ormore Human-Machine Interfaces (HMIs) and a collection of devices. The types ofdevices determine the communications system, as follows:

• Mark VI controllers communicate over Ethernet

• Mark V and Mark V LM controllers communicate over Stagelink

• Mark IV controllers communicate over CSF or RS-232C serial networks

The HMI acts as the focal point for the system time synchronization. At least oneHMI (multiple if redundancy is required) is configured as the time source for thesystem�s other HMIs and devices.

The time master HMI(s) can be supplied with a satellite time card to allow it to actas a high accuracy time source, or it can supply its internal time reference to theother HMIs and devices in the system to act as a low accuracy time source. Theother HMIs and devices in the system act as time clients and follow the Master timesource.

The following figure is an example of a turbine control system communicationsnetwork.

HMI Server No.1 HMI Server No. 2

Plant Data Highway (Ethernet)

Unit Data Highway (Ethernet)

Control System Freeway (CSF)or Serial Network

Stagelink (ARCNET)

Mark VTurbineControl

I/O

Mark IVTurbineControl

I/O

Mark VITurbineControl

I/O

EX2100Excitation

ControlI/O

NTP Server TimeSync Master NTP Client

NTP Client NTP Client Time Sync Client

HMI/HistorianViewer(Client)

NTP Client

Satellite Receiver

UTC (IRIG-B)


Ethernet Synchronization: NTP and NTP ServerTime synchronization between turbine system devices on the Ethernet is achievedusing the Network Time Protocol product called NTP. This product is a standalonesoftware program that can be installed on the HMI pc. It is used to synchronize thepc to other Ethernet time sources, and to allow the pc to act as a time source on theEthernet.

The NTP Server is another standalone product that can be installed on the HMI pc. Itinterfaces to a time card installed in the pc to allow it to act as a high accuracy timesource supplying UTC time references on the Ethernet.

NTP is included in the runtime code in non-pc based devices, such as the MarkVIcontroller and the EX2100 exciter, so the devices are automatically NTP-enabled.

Stagelink Synchronization: TimesyncTime synchronization between devices on Stagelink networks is achieved using theTimesync program. Timesync is installed on the HMI as part of the Turbine ControlInterface (TCI) product. The Timesync functionality is part of the runtime code forMarkV and MarkVLM controllers. One or more HMIs act as Stagelink TimeMasters, to which the other HMIs and controllers on the Stagelink networksynchronize.

CSF and Serial Network Synchronization:MSP_TSETTime synchronization between devices on CSF or RS-232C serial networks isachieved using the MSP_TSET program. MSP_TSET is installed on the HMI as partof the TCI product. The MSP_TSET functionality is part of the runtime code forMark IV controller. One HMI will act as the Time Master on the CSF network,broadcasting the time to the other devices on the network.


How to Use This DocumentThis document provides a detailed overview of the Time Synchronization programavailable for the Human-Machine Interface (HMI) computers of a system usingSPEEDTRONIC� turbine control. It includes procedures for setting up and usingthe program, plus examples of related screens.

Text ConventionsThe following symbols, formatting, and presentation conventions are used in thisdocument to assist the user.

Convention Meaning

� A procedure follows.

Numbered list Procedural steps to be followed in order (for example, 1, 2, 3).

Alphabetized list Procedural substeps (of numbered steps) to be followed inorder (for example, a, b, c).

Bulleted (• ) list Related items or procedures, but order does not matter.

� A procedure with only one step.

Boxed (�) list A checklist.

Arial Bold When describing software, indicates the actual command oroption that is chosen from a menu or dialog box.

Monospace Represents examples of screen text or words and charactersthat are typed in a text box or at the command prompt.

How to Get HelpIf help is needed beyond the instructions provided in the system documentation,contact GE as follows:

�+� indicates the internationalaccess code required whencalling from outside the USA.

GE Industrial SystemsProduct Service Engineering1501 Roanoke Blvd.Salem, VA 24153-6492 USAPhone:+ 1 888 GE4 SERV (888 434 7378, United States)

+ 1 540 378 3280 (International)Fax: + 1 540 387 8606 (All)

Note Please have the GE requisition or shop order number and the equipment serialor model number available to exactly identify the equipment when calling.


Related DocumentsIf needed for supplementary information, refer to the following turbine controlproduct documents, as applicable:

GEI-100505 Network Time Protocol (NTP)

GEI-100507 Network Time Protocol (NTP) Server

GEH-6126 HMI for SPEEDTRONIC Turbine Controls

GEH-6421 System Guide for SPEEDTRONIC Mark VI Turbine Control

Document DistributionGE Industrial Systems supplies product documents to its customers to support theequipment provided for each requisition. The contract documents define the terms ofthe document distribution.

If provided (per contract), the following documents contain requisition informationabout the drive system.

• Requisition drawings, including outlines, layouts, and elementary diagrams

• Renewal Parts listing

Note If differences exist between the general product documentation and therequisition documentation, the requisition documentation should be considered themore exact representation of your equipment or system configuration.


Notes

GEI-100513 HMI Time Synchronization Chapter 2 Time Synchronization Over Ethernet � NTP •••• 2-1

Chapter 2 Time Synchronization OverEthernet � NTP

IntroductionTwo types of Network Time Protocol (NTP) products are used to synchronizedevices over the Ethernet: NTP and NTP Server. These products are included onthe Turbine Control System CD to provide time synchronization on HMI PCs.

The Mark VI and EX2100 controllers communicate over an Ethernet.

This chapter describes the NTP options and configuration as follows:

Section Page

Product Overview.....................................................................................................2-2NTP (Only) Operating Modes ...........................................................................2-2NTP Server (Only) Operating Mode .................................................................2-2NTP Time Acquisition Modes...........................................................................2-2NTP Configuration Utility.................................................................................2-4

NTP Configuration Screen Examples.......................................................................2-5Broadcast Client using the Standard Configuration Option ..............................2-6Unicast Client using the Standard Configuration Option ..................................2-7Broadcast Master using the Custom Configuration Option...............................2-8Broadcast and Unicast Master using the Custom Configuration Option...........2-9

NTP Server Configuration Examples .....................................................................2-11Unicast Server .................................................................................................2-11Broadcast and Unicast Server..........................................................................2-13

Operation................................................................................................................2-15Event Viewer (NTP Only)...............................................................................2-15

NTP Server Hardware Interface .............................................................................2-16Synchronization of Mark VI and EX2100 Controllers ...........................................2-17NTP Status Indicator ..............................................................................................2-19

Starting the Status Indicator ............................................................................2-19Menu Commands ............................................................................................2-20Icon Status .......................................................................................................2-20

NTP Diagnostics.....................................................................................................2-21Starting and Closing the Program....................................................................2-21Configuration ..................................................................................................2-22Data Display....................................................................................................2-22Monitoring NTP ..............................................................................................2-24Monitoring NTP Server...................................................................................2-25

2-2 •••• Chapter 2 Time Synchronization Over Ethernet � NTP SPEEDTRONIC Turbine Control GEI-100513

Product OverviewNTP consists mainly of a service that runs on the pc that uses time signals fromother PCs on the Ethernet to synchronize its local clock. NTP can optionally beconfigured to serve as a time source to other PCs and devices running NTP on theEthernet. The ability to act as both a time master and a time client is sometimesreferred to as the ability to act as an NTP Peer.

�UTC� is CoordinatedUniversal Time.

NTP Server consists mainly of a service that runs on the pc that interfaces to asatellite time card installed in the pc. The time card can be connected to a satellitereceiver to allow NTP Server to supply UTC to all of the client PCs and devices inthe system. NTP Server can only get its time information from the satellite card inthe pc. It cannot adjust its time reference based on any other NTP time sources onthe Ethernet the way an NTP Peer node can.

The NTP programs offer several configuration options for operating mode and timeacquisition mode. You select these using the NTP Configuration Utility, which isincluded with the programs. Table 2-1 lists and defines the combination of availableoptions, which are described in the following sections.

NTP (Only) Operating ModesThere are two NTP-only operating modes: Client and Master.

Client mode indicates that the NTP service on the pc is only receiving time from oneor more NTP (and/or NTP Server) time sources. It is not intended to supply time toany other pc or device.

Note NTP Server by definition cannot be a client.

Master mode indicates that the NTP service on the pc is able to both supply andreceive time. Since NTP masters are assumed to be supplying time to other devices,they are always configured to use their local pc clock as a valid time source. Thisensures that if all other time sources on the Ethernet are lost, the NTP master willmaintain synchronization at least with its local clock in order to continue to supplythe NTP clients with time information.

NTP Server (Only) Operating ModeNTP Server (only) operates in Server mode. This indicates that the service issupplying time signals to others, but is not receiving NTP messages. The time sourceis a satellite reference or an internal low drift clock. An NTP Server can act as amaster, but not as a client.

NTP Time Acquisition ModesThere are two NTP time acquisition modes: Broadcast and Unicast.

Broadcast mode involves a time Master or Server node broadcasting time messagesover the Ethernet which are received by the Client nodes.

Unicast mode involves Client nodes sending a directed message (Unicast) to anEthernet Master or Server node and the Master or Server node sending a directedreply back to the Client.

Note Unicast mode is the most accurate because network delays can be preciselycalculated with compensations made. In Broadcast mode, the total network delayscan only be approximated.


Table 2-1. NTP and NTP Server Configuration Options

NTPClient

NTPMaster

NTPServer Functional Description of Configuration

� NTP only listens for broadcasts from other NTP and NTP Server sources. NTPreceives messages from any NTP time source broadcasting on the Ethernet. Itsynchronizes to the one that it considers as best*. If broadcasts are notreceived, NTP remains unsynchronized. If broadcasts stop, NTP losessynchronization.

*NTP uses the broadcast sources� stratum levels to determine the best timesource. If the levels are the same, NTP uses time delays and time sourceavailability to determine the best time source.

� To synchronize, the NTP master uses the internal pc clock and any broadcastsfrom other NTP time sources over the Ethernet. It then broadcasts timemessages once every 16 seconds. Because the NTP master uses the localclock as a time source, it does not lose synchronization if it loses its externaltime sources. If no other NTP time sources are broadcasting time, the NTPsynchronizes to its local clock and broadcast the local time at the stratum levelassigned to its local clock.

Broadcast

� NTP Server broadcasts the time over the Ethernet at a user-configurableinterval (once a minute by default).

� NTP periodically sends a directed Ethernet message to one or more PCs(running NTP or NTP Server) that it has been configured to use as timesources. NTP evaluates the time messages returned from the queried NTPmasters, then synchronizes to the best one. If it cannot establishcommunication with another NTP-enabled host, this NTP client remainsunsynchronized. If communication with an NTP-enabled host is lost, it losessynchronization.

� To synchronize, NTP uses its internal clock and optionally one or morespecified NTP sources. It then acts as a time source to any NTP node thatqueries it with a directed message. Because this NTP uses the local clock as atime source, it does not lose synchronization if it loses its external time sources.

Unicast

� NTP Server responds to directed messages requesting time information fromremote NTP nodes.

� To synchronize, NTP uses both Broadcast and Unicast time acquisition modes.The NTP listens for time messages broadcast on the Ethernet. It also sendsdirected messages to one or more selected NTP nodes. As with any clientconfiguration, synchronization will be lost if communication with all of theexternal time sources is lost.

� NTP uses both Broadcast and Unicast time acquisition modes to achieve timesynchronization. In this mode NTP will listen for any time messages broadcaston the Ethernet in addition to sending directed messages to one or moreselected NTP nodes. If it loses communication with all external time sources,this NTP uses the local clock to maintain synchronization.

BroadcastandUnicast

� NTP Server broadcasts time periodically over the Ethernet and responds toUnicast requests from other NTP nodes.


NTP Configuration UtilityThis NTP utility is locatedunder the Windows� ControlPanel.

The NTP Configuration Utility is used to either view or change the configuration ofthe NTP and NTP Server services. It provides two functions:

• Modifies the service configuration based on the user input.

• Manages the state of the services and drivers to support the specifiedconfiguration.

Refer to the NTP and NTP Server manuals for a more detailed description of theNTP Configuration Utility and the configuration issues that may arise.

Note NTP and NTP Server can be installed on the same pc and managed via theNTP Configuration Utility, however, it is better to install only the service needed perthe system architecture scheme to avoid confusion later. Refer to the NTP or NTPServer manual for more information.

�� To activate the NTP Configuration Utility

1. Click Windows Start, Settings, and Control Panel.

2. Double-click . A screen displays showing the currentNTP configuration, as illustrated below.

This screen is an indication of the pc'scurrent NTP configuration.

This screen is the first to display whenyou activate the NTP Configuration Utility.

Exit closes the utility without changingthe configuration.

Configure starts the configurationprocess, taking you to a screen tochoose the configuration mode.


NTP Configuration Screen ExamplesStandard Configuration Mode provides the simplest approach to configuring NTP.This mode hides more of the complexity of NTP configuration from the user andprovides default configuration for some of the parameters. Standard ConfigurationMode supports the simplest possible system topology in which one node isconfigured as the time master or server. All other nodes are client nodes with allnodes in the system configured for the same NTP Time Acquisition Mode.

Custom Configuration Mode provides additional configuration options. It isrequired under either of two conditions:

• When multiple time masters are needed for redundancy

• When multiple time acquisition modes are required due to network topologyissues or issues integrating into an existing system

This NTP Configuration screen lets youchoose the configuration mode. Itfollows the Configuration Utility's currentNTP configuration screen.

Information about the selections.

With this configuration mode selected,clicking the Next button displays a screenthat allows four configuration options:Client or Master and Broadcast or Unicast.

With this configuration mode selected,clicking the Next button displays screensfor selecting a more custom configuration.

The following sections provide examples of NTP configuration screens for bothstandard and custom configuration modes.


Broadcast Client using the Standard ConfigurationOptionThe following example shows the steps involved in configuring NTP for BroadcastClient mode using the standard configuration option.

�� To configure the PC as a Broadcast Client1. Select the Configure button when the Current Configuration Screen displays.

2. Select the Standard Configuration option and the Next button.

3. At the next screen (shown below), select Client and the Broadcast operationmode, then the Next button to proceed to the next screen.

This screen displays after you selectStandard Configuration mode and Nextfrom the previous NTP Configuration Utilityscreen.

It provides the simplest choices for settingNTP options.

Select to configure the PC for eitherClient or Master operating mode.

Select to configure the PC in eitherBroadcast or Unicast time acquisitionmode.

Click to proceed with configuration.

Click to return to the Configuration Modescreen.

4. On the next screen (shown below), select the Finish button to accept theconfiguration and initiate the changes.


Unicast Client Using the Standard ConfigurationOption�� To configure the pc as a Unicast Client1. Select the Configure button when the Current Configuration Screen displays.

2. At the next screen, select the Standard Configuration option the Nextbutton.

3. At the next screen (shown below), select Client and the Unicast operationmode.

4. At the next screen (shown below), enter the Host Name or IP address of thepc chosen as the Time Master.


Broadcast Master Using the Custom ConfigurationOption� To configure the PC as a Broadcast Master using the custom

configuration option1. Select the Configure button when the Current Configuration Screen is

displayed.

2. At the next screen, select the Custom Configuration option and the Nextbutton.

3. At the next screen (shown below), select Master and the Broadcast operationmode.

This screen displays after you selectCustom Configuration mode and Nextfrom the previous NTP Configuration Utilityscreen.

It provides more complex choices forsetting NTP options.

Select to configure the PC for eitherClient or Master operating mode.

Select a stratum level. The default isStratum 13. (This replaces the slider dialogin previous software versions.)

Select one to configure the PC in eitherBroadcast, Unicast, or Broadcast andUnicast time acquisition mode.

Click to return to the Configuration Mode screen. Click to proceed with configuration.

Note The default value of 13 (Secondary, Stratum 13) can be used if only one timemaster will be configured for the system.

If multiple time masters are configured, there should be only one Primary, oneSecondary, and one Tertiary master in a system. The master with the lowest stratumlevel will be used by the client nodes as long as it is available on the network. If thelowest stratum master is lost, the master with the next highest stratum level will beused, and so on.


Broadcast and Unicast Master Using the CustomConfiguration Option�� To configure the PC as a Unicast Master1. Select the Configure button when the Current Configuration Screen is

displayed.

2. At the next screen, select the Custom Configuration option and press theNext button

3. At the next screen (shown below), select Master. Secondary is selected bydefault. If there is more than one time master, they cannot have the sameselection. For example, if there are three masters, designate one as Primary,one as Secondary, and one as Tertiary.

4. Select Broadcast and Unicast operation mode.

5. At the next screen, enter the NTP time sources, or leave them all blank tosynchronize only to the pc�s local clock.

This screen displays in the NTPConfiguration Utility after you selectCustom Configuration, then Broadcastand Unicast and Master modes .

Enter the host name or IP Address of thePCs that serve as the Time Master(s) forthes PC that you are configuring.

When checked, gives additional weight tothe preferred time master.


6. At the next screen (shown below), select the Finish button.


NTP Server Configuration ExamplesThe following examples illustrate the steps involved in setting up somerepresentative NTP Server configurations. Refer to the NTP Server manual for moreexamples and more detailed configuration information.

Unicast Server1. Select the Configure button at the current configuration screen (shown below)

to bring up the NTP Server configuration screen.

This screen is an indication of the pc'scurrent NTP Server configuration.

This screen is the first to display whenyou activate the NTP Configuration Utility.

Configure starts the configurationprocess, taking you to a screen tochoose the configuration mode.

Exit closes the utility without changingthe configuration.

2. On the next screen (shown below), select the Unicast Server option. TheEnable Logging settings can be selected to provide debug information ifneeded. These settings do not affect the normal operation of NTP Server. TheInternal Time Regulation option is normally selected, which allows NTP Serverto regulate the time on the pc.


3. Edit the driver settings if necessary. This example shows the Network TimeProtocol Driver being used. Selecting the Edit button (see previous screenexample) brings up the Network Time Protocol Driver Settings dialog box,which allows the driver settings to be modified. The driver settings should beconfigured to match the hardware installed in the pc. Refer to the NTP Serverdocumentation for more detailed information and for information regardingconfiguration when the ARCNET driver is used in place of the Network TimeProtocol Driver.

4. Select the Finish button to save and activate the new configuration.


Broadcast and Unicast Server1. Select the Configure button at the current configuration screen (shown below)

to bring up the NTP Server configuration screen.

2. At the next screen (shown below), select the Unicast Server and BroadcastServer options. Adjust the desired broadcast rate if desired. The EnableLogging settings can be selected to provide debug information if needed- thesesettings do not affect the normal operation of NTP Server. The Internal TimeRegulation option is normally selected, which allows NTP Server to regulatethe time on the PC.

This example shows the Network Time Protocol Driver being used. Edit thedriver settings if necessary by selecting the Edit button. This brings up theNetwork Time Protocol Driver Settings dialog box, which allows the driversettings to be modified.


Select to save and activatea new configuration.

This NTP Server screen displays in theNTP Configuration Utility after you selectConfigure.

Settings should match the hardwareinstalled in the PC.

Select to edit driver settings, if necessary. Thisdisplays a dialog box for changing these settings.

Normally selected, which allows NTPServer to regulate the time on the PC.

Driver and settings being used.

Select to provide internal debug informationif needed. These settings do not affect theNTP Server's normal operation.

Select one or both boxes (Unicast andBroadcast Server selected here).

Adjust broadcast rate as needed.

(Refer to the NTP Server manual for more detailed information and for information regardingconfiguration when the ARCNET driver is used in place of the Network Time Protocol Driver.)

Select to provide external debuginformation if needed. These settings do notaffect the NTP Server's normal operation.

3. The driver settings dialog box (shown in the next figure) should be configured tomatch the hardware installed in the pc. Refer to the NTP Server manual for moredetailed information and for information regarding configuration when theARCNET driver is used in place of the Network Time Protocol driver.

4. Select OK when settings are completed. This returns you to the previous screen.

5. Select the Finish button to save and activate the new configuration


OperationNormal operation of NTP and NTP Server is monitored with the NTP StatusIndicator program discussed below. For more detailed information about the status ofNTP or NTP Server running on the local pc or a remote pc, use the NTP Diagnosticsprogram described below.

Event Viewer (NTP Only)The NTP service (but not NTP Server) writes status messages to the Windows EventLog. These messages are viewed with the Windows Event Viewer program.

Or double-click the icon. .�� To view the Event Viewer messages:1. From Programs, select the Administrative Tools program group/folder.

2. Click the Event Viewer icon. The Event Viewer�Application displays.

3. From the Log menu, select Application. The Application Log events aredisplayed.

4. Under the Source column, click the latest NTP entry to highlight it.

5. Double-click the entry. The following Event Detail dialog box displays with atext message that describes that event.

Source Column

Log Menu


Multiple entries can occurbefore synchronization occurs.

After some time, synchronization to the time Master occurs. The text message inEvent Detail indicates that this pc is synchronized to the time Master.

Note If there is a time difference of more than a minute between the Client and theMaster node, a delay can occur before time synchronization is achieved. This delaycan be minimized by stopping the NTP from the Service program and setting theClient time to the current value of the Master node.

�� To set the local time to the same value as the Master node� From the command prompt window on the client pc, type the command ntpdate<master> (<master> is the current Master pc). The NTP service must be stoppedon this pc before running this command.

NTP Server Hardware InterfaceChapter 6 provides informationfor installing and configuringpc time cards.

NTP Server requires a satellite time card installed in the pc. The NTP Server productalso includes a driver that is used by the service to communicate with the time card.The NTP Driver is configured from the NTP Configuration Utility as in theexamples above.

Chapter 3 provides informationfor configuring the ARCNETdriver to provide HighResolution time card support.

The NTP Driver is not used if an ARCNET card is installed in the pc and theARCNET driver is configured for High Resolution time card support. Instead, NTPServer uses the ARCNET driver with the NTP Driver disabled.


Synchronization of Mark VI and EX2100 ControllersBoth the MarkVI and EX2100 controller�s time is synchronized over Ethernet usingNTP. The NTP software is part of the controller�s runtime code, so no installation isrequired. You configure the controller�s NTP using the GE Control System Toolbox,then download the configuration to the controller.

Both the MarkVI and EX2100 controllers are configured using the GE ControlSystems Toolbox. The following figure shows a MarkVI device named mkvi1 as itappears in toolbox. For the EX2100, a similar display would show a device namedEX2.

�� To edit Mark VI or EX2100 controller properties1. Highlight the device name at the top of the tree (mkiv1 for Mark VI, EX2 for

EX2100). You can also right click to the device name in the tree structure at theright of the screen.

2. Select Edit/Modify from the toolbox menu.

The MarkVI or EX2100 (Innovation Series) Controller Properties dialog boxdisplays.

3. Select the NTP tab to view or edit the existing configuration.

Note The following figure shows a Mark IV NTP tab dialog box. For the EX2100,the tab display contains the same options.


Mark VI controllers can only beconfigured as a time client usingeither Broadcast or Unicast mode.

Selection causes the controller tomonitor for periodic broadcastson the Ethernet (UDH).

Selection allows specification ofup to 2 time sources: a primaryand a backup.

With Unicast selected, this servermust be specified.

With Unicast selected, this serveris optional.

Or select the Validate icon on Toolbox toolbar.

Or select the Save icon onthe Toolbox toolbar

Or select the Build icon .

Or select the Download icon

.

4. When you�ve made all changes, validate them by selectingDevice/Validate/Selected from the Toolbox menu.

5. If the validation is successful, save the new configuration by selecting File/Savefrom the Toolbox menu.

6. Convert the new configuration into a form that can be downloaded to the MarkVI or EX2100 controller by selecting Device/Build from the Toolbox Menu.

7. If the build is successful, download the new configuration to the controller byselecting Device/Download/Application Code from the Toolbox Menu.


NTP Status IndicatorThe icon displays in thelower right of the Windowstaskbar.

The NTP Status Indicator displays the synchronization status of the NTP service onthe local pc through a clock icon. The icon has associated tool tips. The tool tipsdisplay the machine�s synchronization status, including the name or IP address of thenode that the local machine is synchronized to.

NTP Status Indicator is installed with the NTP product installation as part of theTurbine Control System CD. It also provides convenient access to NTP Diagnostics.

Note The NTP Status Indicator is not compatible with versions of Windows NTprior to 4.0 (these earlier versions did not implement the taskbar functionality).

Starting the Status Indicator�� To start the NTP Status Indicator

Or from the command promptwindow, change to thedirectory where NTP isinstalled. This is usuallyC:\Program Files\GE ControlSystem Solutions\NTPSTAT\or C:\Program Files\GEControl System Solutions\NTPDIAG-S\.

� From the GE Control Systems Solutions program group, select NTPStatus Indicator.

The NTP Status Indicator starts. An icon displays in the lower right of theWindows taskbar. Refer to the section Operation for icon status definitions.

The NTP Status Indicator queries the NTP service running on the local computerapproximately every 15 seconds and updates the clock icon in the Windows taskbar.The icon graphically displays the NTP synchronization status of the computer.

Note Hold the cursor over the clock icon to generate a tool tip that displays thesynchronization status of the machine and the name or IP address of the node that thelocal machine is synchronized to.


Menu CommandsThe NTP Status Indicator menu commands:

• Close the application

• Start the application automatically whenever the computer is logged on

• Create NTP Diagnostic window(s) to display NTP data

• Access online Help

�� To operate the menu command� Click on the icon with the right mouse button. The following pop-up menu

displays:

Click for online help.

Click to toggle auto start. A checkmarkshows that auto start is on.

Click to close the window. The icondisappears. (To bring back the icon,rerun the application.)

Click to create a new window andview specific NTP data.

Icon StatusWhen the NTP Status Indicator starts, the clock icon displays in the Windowstaskbar (right side). The icon status reflects the synchronization:

Icon Status Color of clock

NTP Service is not running white with red X

Initializing (displays when application starts) white

Waiting for feedback from the NTP service gray

NTP service is not synchronized red

NTP service is not synchronized, but has located atleast one potential time source

yellow

NTP service is synchronized green

The NTP Status Indicator iconis a clock symbol to signify thatit is related to the system time.The icon does not show theactual system time.

The NTP Status Indicator icon is animated to indicate that the application isactively receiving data from the NTP service. Every time the NTP service returnsdata to the application, the minute hand of the clock icon moves one position. Thehour hand of the clock icon always remains at the horizontal (3 o'clock) position.

Note Only one instance of the NTP Status Indicator can run on the computer. Thisavoids wasting system resources that display redundant information. Do not attemptto start the application when another instance of the application is already running.


NTP DiagnosticsThe NTP Diagnostics program is a utility used to monitor the operation of both NTPand NTP Server on the local pc or on any specified computer on the network. Theutility periodically polls the NTP or NTP Server service on the specified hostcomputer and then displays that data.

Starting and Closing the Program� To start NTP Diagnostics from the GE Control Systems Solutionsprogram group� Select NTP Diagnostic.

� To start NTP Diagnostics in Windows NT 4.0 and later

1. Either right double-cllick the icon , located on the right side of the taskbar, orselect NTP Status Indicator and right single-click the icon.

2. From the pop-up menu, click Create a new NTP Diagnostics window.

The NTP Diagnostics application starts and displays the NTP Diagnosticswindow.

Select to configurehost name (seeConfiguration)

Displays when NTPDiagnostics starts orwhen the user selectsa new host.

Host name. Default islocalhost, which displays datafor the NTP service running onthe local computer.

Window size and font areautomatically selected basedon the active video mode.The user cannot select them.

Or click in the top right ofthe window

�� To close the NTP Diagnostics program� From the NTP Diagnostics window, select the File menu and Exit.


ConfigurationThe NTP host name is the only configurable item for this application. The defaulthost name is localhost, which displays data for the NTP service running on the localcomputer.

�� To display data on a remote computer1. From the Configure menu, select Specify Remote Computer.

2. Enter the name or IP address of the remote computer.

Data DisplayThe program displays data, as follows:

• It periodically (about every 5 to 10 seconds) updates the data as it is receivedfrom the specified host as follows:

• Data that corresponds to the node that the computer is synchronized to displaysagainst a green background.

• Data that corresponds to any potential time source displays against a yellowbackground.

• All other data displays against a white background.


Green

White

Yellow

Data Field Description

remote The name or IP address of each remote time source. The asterisk character (*) indicates the currentMaster node, which shows that synchronization with this node has occurred. The plus character (+)indicates that the host is a potential time source.

refid Shows the current source of synchronization for the remote time source.

St Shows the stratum level of the remote time source. The stratum level is a declaration of the quality of thetime source. Lower stratum numbers indicate a more accurate time source.

t Shows the data gathering method used, such as u = unicast, b = broadcast.

when The time in seconds since the last broadcast from the time source (Broadcast mode) or since the timesource was polled by the client (Unicast mode).

poll The broadcast frequency of the time source or the polling rate of the client node (defined in the ntp.inifile by the minpoll parameter (2^minpoll)).

reach An indication of the responsiveness of the time source.

delay The communication delay between the time source and the local node in milliseconds.

offset The time difference between the time source and the local node in milliseconds.

disp Dispersion is a measure of how well the local time is tracking the remote time source. Smaller numbersindicate better tracking accuracy.


Monitoring NTP

The local pc issynchronizedto host NS01.

NS01 is actingas a stratum 4time source.

NTP is pollingNS01 every128 seconds.

NTP last heardfrom NS01 125seconds ago.

NS01 time is-5.98 ms aheadof local PC time.

Highestreachabilitylevel possible.

Low dispersionno., indicating avery reliabletime source.

Example of NTP configured as a Unicast Client.

Local clockis timesource.

Local clock astratum 12time source.

NTP is pollinglocal clockevery 16 sec.

NTP last heardfrom local clock10 sec. ago.

No network delay(data gatheredinternally).

High reachability.377 (octal) is thehighest.

Example of NTP configured as a Unicast Master using only the local clock as a time source.

No offset whenlocal clock istime source


Monitoring NTP Server

Entry for thetime card.

Entry for thePC's local clock.

Difference (ms) between pc'slocal time and time card.

The first (green) line of datashows that NTP Server isacting as a stratum 1 timesource based on the time card.

st* Description

1 Locked onto satellite time.

2 Timecard is Flywheeling but has been locked to satellite time within the past hour.

5 Timecard is Flywheeling but has been locked to satellite time more than an hour ago.

8 Timecard is Flywheeling and has not been locked since NTP Server began, but time has past reasonablenesschecks, thus indicating a previous time lock.

11 Timecard is Flywheeling and has not been locked since NTP Server started up. Time has not passedreasonableness checks, thus indicating invalid tome on the timecard. NTP Server is using the local NTP clock tocompensate the timecard time value.

* Stratum level used by NTP Server.


Notes

GEI-100513 HMI Time Synchronization Chapter 3 Time Synchronization Over Stagelink •••• 3-1

Chapter 3 Time Synchronization OverStagelink

IntroductionTimesync provides the time synchronization capabilities of the HMI on Stagelink(ARCNET) networks. The Timesync software is automatically installed as part ofthe TCI product installation. The Timesync program starts automatically when theTCI service starts.

A Stagelink network generally consists of one or more HMI PCs connected to one ormore Mark V or Mark V LM controllers. The controllers automatically listen forbroadcasts from the available Stagelink Time Masters and synchronize to theselected Stagelink Time Master. One HMI acts as the Stagelink Time Master and theother HMIs and controllers synchronize their time to it. The HMIs can be set toreceive time from a satellite time card or use the internal pc clock.

The Stagelink Time Master selection is periodically re-evaluated. If its statuschanges in such a way that it is no longer the best source of time on the Stagelinknetwork, a different HMI is chosen as Stagelink Time Master.

This chapter is organized as follows:

Section Page

Configuration............................................................................................................3-2Hardware ...........................................................................................................3-2ARCNET Driver ...............................................................................................3-2Timesync Software (Timesync.dat file) ............................................................3-4

Timesync Operation .................................................................................................3-7Time Card Initialization ....................................................................................3-8Timesync Startup and Initialization...................................................................3-9GTS Tracking..................................................................................................3-10Flywheel Operation .........................................................................................3-11Low Resolution Operation ..............................................................................3-11

Timesync Diagnostics and Monitoring...................................................................3-12Enable or Disable Timesync............................................................................3-12Load Major Time into the Time Card .............................................................3-13Obtain Timesync Status Information...............................................................3-13Obtain Timesync Trace Information ...............................................................3-20Timesync Log File...........................................................................................3-21

Connecting the PC Time Card to a Satellite Time Source (GTS) ..........................3-22Validating GTS Signal Reception ...................................................................3-22

System Configuration Issues ..................................................................................3-22Sample Topologies (Timesync only)......................................................................3-23

3-2 •••• Chapter 3 Time Synchronization Over Stagelink SPEEDTRONIC Turbine Control GEI-100513

ConfigurationHardwareIf a time card is installed in the pc, the High Resolution Time SynchronizationOption is used and the time card must be configured correctly. See the PC TimeCard Installation section of this document for more information. If the LowResolution Time Synchronization option is used the pc does not require a time card.

ARCNET DriverThe ARCNET driver interfaces to two cards:

• The ARCNET card and, therefore, the Stagelink network

• The time card if it is installed in the pc

The ARCNET driver is configured with the Turbine Control Interface (TCI) appletunder the Windows Control Panel.

To activate the TCI UtilityIn Windows 3.51, go toProgram Manager and double-click Control Panel.


2. Double-click

3. Select the ARCNET Time Sync tab to view the current settings or make changes.

Select to configure the driver to interface with thetime card installed in the computer.

When selected, the ARCNET driver will notinterface with the time card. These selections donot disable the High Resolution Time Card.

Used by the driver to correctly communicate withthe time card. These settings should alwaysmatch the installed time card, no matter whatthe Time Acquisition Hardware setting is.

If the pc does not have a time card, set to<No card installed> to disable the HighResolution and Base I/O Address fields.

When None is selected, Timesync cannot run onthe PC.

When Low Resolution is selected, Timesync usesthe PC's CMOS clock as a time source.

See the PC Time Card Installation section of this document for more information onsupported card types and base I/O settings.

The ARCNET driver can also be affected by settings in the timesync.dat file. Thetimesync.dat file parameters are discussed in the Timesync Software(Timesync.dat file) section below.


For configuration changes to take effect, you must stop and restart the TurbineARCNET driver in coordination with the TCI service. This must take place afterchanging the ARCNET Time Sync parameters from the TCI applet or after makingchanges to the timesync.dat file.

� To restart the TCI service in coordination with the ARCNET driverIn Windows NT 3.51, go toProgram Manager and double-click Control Panel.


2. Double-click Services.

The following dialog box displays:

3. Click on TCI (Turbine Control Interface) to select it.

4. Click Stop to shut down the TCI service.


6. Double-click .

The following dialog box displays:

7. Click on ARCNET to select it.

8. Click Stop to shut down the ARCNET driver.


9. Repeat steps 1-3 above to select the TCI service.

10. Click Start to restart the TCI service. The ARCNET driver restartsautomatically.

Note stopping and restarting the TCI service in coordination with the ARCNETdriver can also be accomplished by bringing up a command prompt window andissuing the following commands in the following order:Net stop TCI

Net stop ARCNET

Net start TCI

Timesync Software (Timesync.dat file)The Timesync process running on the HMI pc is configured via the F:\Timesync.datfile. The file is modified using any text editor. Lines beginning with a semicolon (;)are comments and are ignored by the Timesync process. The key lines of the file are:----------------------------------------------------------TIMESYNC [<controller> MODE <mode> [LEVEL_SHIFT] | LOWRES | SLAVE]LOCAL_TIMESET [ENABLED | DISABLED]I_TIME [LOCAL | UTC]MARKV_TIME [LOCAL | UTC]TIME_SOURCE [LOCAL | UTC]TIME_LOAD [MANUAL | LOCAL |NETWORK]----------------------------------------------------------

Note A template for the timesync.dat file is located under G:\Data\Timesync.dat.This file can be copied to F:\Timesync.dat and edited as required.

The parameters are discussed below:

TIMESYNC

This line is defines the time source the first Timesync will use. It must always beincluded.

The line will be in the following form if a time card is installed in the pc:

TIMESYNC <controller> MODE <mode> [LEVEL_SHIFT]

Note These settings correspond to the High Resolution setting in the TCI dialog�sARCNET Time Sync page. The High Resolution Time Acquisition Hardware optionmust be selected when specifying this line in the timesync.dat file. The <controller>setting must match the Card Type specified in the TCI dialog.

The parameters are defined as follows:

<controller> specifies the type of time card installed in the pc. One of thefollowing values will be specified:

BC620AT

BC627AT

TPRO_PC

Note The <controller> setting must match the Card Type specified in the TCIdialog.


<mode> specifies the hardware interface to the Global Time Source (GTS). Thefollowing values are allowed:

IRIG-B Modulated IRIG-B Time Code Signal

IRIG-A Modulated IRIG-A Time Code Signal (N/A forTPRO_PC)

NASA-36 Modulated NASA-36 Time Code Signal

2137 Modulated 2137 Time Code Signal (N/A for TPRO_PC)

1PPS One pulse per second time input

1PPM One pulse per minute time input

1PPH One pulse per hour time input

GPS GPS Reference Signal via satellite antenna (bc627AT only)

FLYWHEEL Use the Time Processing Board�s on board lowdrift clock as the GTS.

LEVEL_SHIFT is used if IRIG-x, NASA-36, or 2137 timecodes are DClevel shifted instead of modulated. This applies to bc620AT time cardsonly.

If a time card is not installed in the pc, the TIMESYNC line can be specified asfollows to enable the low resolution software implementation which allows the pc toact as a Stagelink Time Master using the pc�s local (internal) clock as the GTS

TIMESYNC LOWRES

Note This setting corresponds to the Low Resolution setting in the TCI dialog�sARCNET Time Sync page- do not use this option if the Low Resolution setting isnot selected.

If a time card is not installed in the pc, the TIMESYNC line can be specified asfollows to enable the low resolution software implementation as a time client only.Specifying slave operation ensures that this pc will never act as a time master.

TIMESYNC SLAVE

Note This setting corresponds to the Low Resolution setting in the TCI dialog�sARCNET Time Sync page- do not use this option if the Low Resolution setting isnot selected.

LOCAL_TIMESET [ENABLED | DISABLED]

This line is used to enable or disable updates to the pc�s internal clock by theTimesync program. The ENABLED option allows the Timesync program to forcethe pc�s internal clock to track the Stagelink time. The DISABLED option preventsthe Timesync program from updating the pc�s internal clock. The default behavior ifthis line is not specified in the timesync.dat file is disabled.

I_TIME [LOCAL | UTC]

This line is valid only if LOCAL_TIMESET is enabled. This parameter specifieswhether the pc�s operating system is based on UTC or local time. This is a legacyparameter from the IDP system and will be ignored in a TCI system. TCI isWindows based which uses UTC as the base time- Timesync will automatically useUTC as the time base on a TCI system.


MARKV_TIME [LOCAL | UTC]

This line defines whether the Mark V controller(s) is UTC or local time based.Default value if not specified is LOCAL.

Note Mark VLM controllers always use a UTC time base- this parameter has noeffect on Mark VLM time synchronization.

TIME_SOURCE [LOCAL | UTC]

This line specifies whether the GTS is UTC or local time based. This parameter onlyapplies to timecode GTS sources, it does not apply to pulse input time sources.Default value if not specified is UTC.

TIME_LOAD [MANUAL | LOCAL | NETWORK]

This line specifies how the major time elements are initially loaded into the time cardregisters. This line is ignored if no time card is installed. Default value if notspecified is MANUAL.

LOCAL specifies that the major time elements are loaded automaticallyupon bootup from the pc�s CMOS clock.

NETWORK specifies that the major time elements are loadedautomatically upon bootup from another Stagelink Time Master.

MANUAL specifies that the major time elements must be loaded manuallyupon bootup. The HMI pc cannot act as a Stagelink Time Master until themajor time elements are manually loaded. See the TIMEUTIL descriptionunder the Programs/Monitoring section for details on manually setting themajor time elements.

Note TIME_LOAD LOCAL is not recommended for 1 PPS Global Time Sources,since the CMOS clock may have errors in time on the order of several seconds.


Timesync OperationA Stagelink Time Master can be:

• Any HMI pc (Operator Interface) with a time card installed and configured forHigh Resolution time mode

• Any pc without a time card configured for Low Resolution time mode

All nodes on the Stagelink network synchronize to the same master based on thefollowing criteria:

• Tracking Status: HMIs tracking the Global Time Source (GTS) are given thehighest priority. HMIs that are in Flywheel or Low Resolution mode will begiven lower priority.

• Lowest Stagelink (ARCNET) address: the HMI with the lowest Stagelinkaddress is given priority over HMIs with higher Stagelink addresses. The HMIwith the lowest Stagelink address on the lowest numbered Stagelink will beselected if multiple Stagelink networks are connected.

If the current master is lost, all of the nodes pick another common time master basedon the above criteria.

If the GTS is lost, the time card(s) goes to flywheel mode (uses its onboard low driftclock as the time reference) with a maximum drift of +-2ms per hour, which allowsthe GTS to be repaired in most cases before a severe disruption in the plant�s systemtime occurs.

The following figure shows a typical Stagelink network time synchronization layout:

HMI HMI HMI HMI

Note As implied by the selection criteria, the ARCNET link address assigned toeach HMI pc provides the mechanism for controlling which HMI will serve as theprimary time master and the priority given to the secondary masters in the event theprimary time master is lost. The ARCNET link address is adjusted from theARCNET tab of the TCI applet and by the switch setting on the ARCNET board.Remember that the ARCNET address for each pc must be unique on the Stagelinknetwork- use care when modifying this value.


The detailed sequence of time synchronization events over the Stagelink network isas follows:

• Every 20 seconds each available Stagelink Time Master broadcasts anidentification message announcing its availability.

• Approx. twice a minute each turbine controller asks the Stagelink Time Masterfor the current time and the controller steps or slews its time accordingly.

• All nodes re-evaluate the master selection based on the tracking status andStagelink address of each available time master at the rate of once per minute.

• Every HMI with the LOCAL_TIMESET ENABLED option set in F:\timesync.datsets its time according to the Stagelink Time Master approx. once every 20minutes.

Time Card InitializationWhenever the HMI pc is rebooted, the major time elements must be loaded into thetime card�s registers. The source of these values can be CMOS, another StagelinkTime Master, or manual entry as specified by the TIME_LOAD parameter in theF:/Timesync.dat file. The TIME_LOAD parameter options are summarized below.See Timesync Software under the Configuration section above for a more detaileddescription of these parameters.

• LOCAL specifies that the major time elements are loaded automatically uponbootup from the pc�s CMOS clock.

• NETWORK specifies that the major time elements are loaded automaticallyupon bootup from another Stagelink Time Master.

• MANUAL specifies that the major time elements must be loaded manually uponbootup. The HMI pc cannot as a Stagelink Time Master until the major timeelements are manually loaded. See the TIMEUTIL description under thePrograms/Monitoring section for details on manually setting the major timeelements.


The LOCAL and NETWORK options allow the major time elements to be loadedautomatically upon bootup, while the MANUAL option requires manually enteringthe major time elements every time the pc is rebooted. The HMI pc cannot act as aStagelink Time Master until the major time elements are loaded, so specifying theMANUAL option will disable the pc as a Stagelink Time Master until the major timeelements are manually loaded following a bootup.

Timesync Startup and InitializationThe Timesync program is started by the TCI service whenever the TCI service isstarted. The TCI service must be running for the pc to act as a Stagelink time masteror to synchronize to another Stagelink time master. The Windows NT Task Managercan be used to verify that the Timesync program is running by locating theTIMESYNC.EXE entry on the Processes tab. (Right click on the Windows task barand select Task Manager from the popup menu to start task manager).

Timesync does not run if it has been disabled from the TCI Control Panel applet. Ifthe None option for the Time Acquisition Hardware setting on the ARCNET TimeSync tab of the TCI Control Panel applet is selected, Timesync terminates when theTCI service is started. Timesync writes the following message to theG:\Log\Timesync.log file:

ARCNET Driver is not setup for TIMESYNC (Check RegistryEntries). TIMESYNC Program is terminating.

If Timesync is not disabled and fails to start when the TCI service is started, aconfiguration or hardware problem may exist. If an error occurs, the Timesyncprogram generates the G:\Log\Timesync.log file, which indicates the nature of theproblem. If the log file does not exist, an error was not recorded by the Timesyncprogram.


GTS TrackingAfter the major time elements are loaded into the time card, it attempts tosynchronize to the satellite time reference (GTS or Global Time Source) that it hasbeen configured for. (See the Flywheel Operation section below for cases where asatellite time reference is not available). After a sufficient amount of data is collectedfrom the GTS, the time card sets its tracking bit to indicate that it has locked on tothe external time source.

The time card also maintains a Global Time Acquired (GTA) status bit that is set thefirst time the card begins tracking the time source and remains set until the card isreinitialized. Once the Global Time Acquired bit is set, the Timesync program on theHMI pc can act as a valid Stagelink Time Master. The Global Time Acquired bitindicates that the time card has been able to set its time based on the external timesource.

If the external time source is lost, the card still has valid time subject to the effects ofthe drift of the time card�s internal clock. If the external time source has never beenavailable during the time since the card was initialized the Global Time Acquired bitremains cleared and the pc cannot act as a Stagelink time master. If the external timesource is lost while the time card is tracking it, the tracking bit is cleared but theGlobal Time Acquired bit remains set. The pc can still serve as a Stagelink master.However, since it is now Flywheeling instead of tracking an external time source, itis regarded as a lower quality time master. It then will not be selected as the timemaster if other time masters on the network are tracking an external time sourcewhen time master selection is re-evaluated.

The delay associated with tracking the different types of time card interfaces follows:

• When using a timecode reference, there is typically a delay of a few seconds fromthe time that the timecode signals begin to be received or the card is initializeduntil the tracking bit is set in the time card.

• The tracking bit will not be set until at least one reference pulse has beenrecorded after the card was initialized in situations where a pulse time source isused. This implies that tracking a 1PPS time source may take several secondsafter card initialization, tracking a 1PPM time source may take several minutesafter the time card initialization, and tracking a 1PPH may take an hour or moreafter time card initialization.

• For GPS time sources (bc627AT card using a satellite antenna) the tracking bitwill not be set until at least 4 satellites have been found and their positionscalculated, which may take up to 20 minutes.

Note Disconnecting a pulse time source will generate false pulse readings whichmay �confuse� the Timesync software. The TCI service should be restarted after thepulse signal is re-connected to the time card to avoid misoperation.


Flywheel OperationThe Timesync Flywheel option enables the use of the time card�s low drift onboardclock as the Stagelink time reference if a satellite time reference is not available. Thetime card flywheels when it is running without an external time reference.

Without an external time reference, the card uses its onboard low drift clock as thetime reference. The card maintains a Global Time Acquired bit that is set the firsttime the card sets its time according to an external time source. Normally, this bitwill never be set if an external time source is not available. The card can beconfigured using the Flywheel option to set the Global Time Acquired bit in theabsence of an external time source.

After the major time elements have been loaded, there will be a 3-minute delaybefore the Global Time Acquired bit is set and the pc is available as a time master.This allows initialization and selection of any masters using an external timereference before making the pc available as a time master.

The tracking bit will not be set without an external time reference, so the pc will beconsidered a lower quality time source than any time master that is tracking anexternal time source. The Timesync parameter in the F:/Timesync.dat file can beused to specify Flywheel operation mode. See Timesync Software under theConfiguration section above for a more detailed description of the Timesyncparameter.

Low Resolution OperationThe Timesync LOWRES option enables the pc to serve as a Stagelink Time Masterwithout having a time card installed. The LOWRES option uses the pc�s internalclock as the time source. The Timesync program emulates the behavior of a timecard when this option is specified.

When the Timesync program starts, the tracking bit and Global Time Acquired bitsare cleared. There will be a 3-minute delay before the Global Time Acquired bit isset and the pc is available as a time master. This allows initialization and selection ofany masters using an external time reference before making the pc available as atime master.

The tracking bit will not be set without an external time reference, so the pc will beconsidered a lower quality time source than any time master that is tracking anexternal time source. The Timesync parameter in the F:/Timesync.dat file can beused to specify LOWRES operation mode. See Timesync Software under theConfiguration section above for a more detailed description of the Timesyncparameter.


Timesync Diagnostics and MonitoringTimesync cannot be monitored directly in the Mark V or Mark V LM controller.However, the controller�s status can be determined from the Stagelink Time Master�sTimesync trace information.

If there are multiple HMIs on the Stagelink network, the HMI that is currently actingas the Stagelink Time Master can be determined by running the TIMEUTIL programon any of the HMIs on the target Stagelink network. The status option of theTIMEUTIL program displays the address of the currently selected Stagelink TimeMaster.

Note If the Stagelink Time Master PC cannot be easily identified by its Stagelinkaddress, the time master pc can be identified by bringing up the TCI Control Panelapplet on each HMI until the ARCNET Link Address value on the ARCNET tabmatches the address of the Stagelink Time Master. The HMI where the matchingaddress was found is the current Stagelink Time Master.

TIMEUTIL ProgramThe TIMEUTIL program provides the mechanism for monitoring andtroubleshooting the Stagelink time synchronization activity. The program is acommand line based utility that is run from the command prompt window. It isautomatically installed as part of the TCI software distribution. The TIMEUTILprogram can be used for three functions:

• Enable or disable the Timesync function on the local pc

• Load the major time elements into the time card

• Obtain Timesync status information

The functions are described in the following sections.

Enable or Disable TimesyncTo temporarily disable the Timesync function, enter the following command at thecommand prompt window:

G:\EXEC\TIMEUTIL TIMESYNC DISABLE

To restore the Timesync function, enter the following command at the commandprompt window:

G:\EXEC\TIMEUTIL TIMESYNC ENABLE

The Timesync function is automatically re-enabled if the TCI service is restarted.


Load Major Time into the Time CardThe TIMEUTIL program can be used to manually load the major time elements intothe time card by entering the following command at the command prompt window,followed by the date and time, as follows:

G:\EXEC\TIMEUTIL TIMELOAD DD-MMM-YYYY HH:MM:SS:CCCC

Note The time entered should correspond to the time base of the GTS. If the GTS isUTC-based, enter the current UTC time. If the GTS is local time-based, enter thecurrent local time.

Obtain Timesync Status InformationThe TIMEUTIL program can be used to obtain status information regarding the stateof the Timesync process by entering the following command at the command promptwindow:

G:\EXEC\TIMEUTIL STATUS

If the Timesync program is not running on the pc, the message Failed to connect toTimeSync Program. Program exiting is displayed. This can be caused by one of thefollowing problems:

• The TCI service has not been started on the pc: The TCI service isresponsible for starting Timesync. Start the TCI service if it is not alreadyrunning on the pc and run the TIMEUTIL program again. There may be a delayof a minute or so while the Timesync program completes its initialization beforeTIMEUTIL will begin working so allow some time after TCI has started beforeassuming that Timesync is not functioning properly.

• The Timesync process has not been configured to run on this pc: If the�None� option has been selected for the Time Acquisition Hardware parameteron the ARCNET Time Sync tab of the TCI Control Panel Applet the Timesyncprogram will terminate when the TCI service is started. TheG:\Log\Timesync.log file will contain the following message in this case:

ARCNET Driver is not setup for TIMESYNC (Check Registry Entries)TIMESYNC Program is terminating.

• The Tymesync process has shut down due to an error: If the Timesyncprocess fails to start up when TCI is restarted it may be terminating on an errorcondition. This could be caused by a configuration error that prevents Timesyncfrom operating correctly, or it could be caused by a hardware problem with thetime card. The Timesync program will write an entry to theG:\Log\Timesync.Log file when an error occurs. The source of the problem cannormally be determined from the log file. The log file is deleted wheneverTimesync is restarted- if the Timesync.log file does not exist, a Timesync errorhas not occurred.

If the Timesync program is running, the TIMEUTIL program displays the statusinformation for the program. The following figure shows the output for an IRIG-BGTS on November 30, 2000, the 335th day of the year.


---------------------------------------------------------------------------------------- TIMESYNC STATUS (NT Version)Overall TIMESYNC Function: ENABLEDTIMESYNC Controller: Bancomm bc620ATTIMESYNC Mode: IRIG-B (Modulated) Status: TRACKINGGlobal Time Acquired: YES Year: 2000 Days: 335Pulse Correction in Use: N/AMajor Time Load Flag: LOCAL CMOS

Global Time Source: UTCMark V Panel Time: LOCALMark V LM Panel Time: UTC<I> / <G> CPU Time: UTC Local Windows NT Timeset: ENABLEDNumber of Stagelink Time Masters: 1Network Address Status Selected 1 0x1F 0x1903 x 1 0x3F 0x1903

Network #1, Local ARCNET address: 0x1F-----------------------------------------------------------------------------------------

Overall TIMESYNC Function: This field indicates whether the Timesync functionis enabled on this pc.

TIMESYNC Controller: This field shows the time card type specified in thetimesync.dat file. If the Low resolution option (TIMESYNC LOWRES orTIMESYNC SLAVE) is selected in the timesync.dat file �Low resolution� isdisplayed in this field. In the figure above, the controller is a Bancomm bc620ATtime card.

TIMESYNC Mode: Indicates the type of interface used to communicate with theGTS. This field corresponds to the <mode> parameter in the TIMESYNC line of thetimesync.dat file and will be one of the values enumerated above if a time card isinstalled in the pc. If TIMESYNC LOWRES is specified in the timesync.dat file, thisfield will display �Low Resolution�. If TIMESYNC SLAVE is specified in thetimesync.dat file, this field will display �Time Slave only. Not a time master.� If themode is specified as FLYWHEEL, this field will display �FLYWHEELING�.

Note If the mode is IRIG-x, NASA-36 or 2137 and the LEVEL_SHIFT parameteris not specified in the TIMESYNC line of the timesync.dat file the timecode signal isassumed to be modulated and (Modulated) will appear after the mode designation. Ifthe LEVEL_SHIFT parameter is specified with the above modes the timecode signalis DC level shifted and (DC Level Shift) will appear after the mode designation.

Status: This field indicates whether or not Timesync on this pc is receiving signalsfrom and is locked on to the GTS. If the GTS is present, this field normally displays�TRACKING�. If the GTS is not available, this field will display�FLYWHEELING�.

Global Time Acquired: This value indicates whether the GTS signal has beendetected by the time card. YES implies that the signal was present at some time sincethe card has been initialized. NO indicates that the GTS has never been detected andthat the pc cannot serve as a time master. FLYWHEEL and LOWRES modestransition Global Time Acquired from NO to YES after a 3 minute delay following areboot of the pc or a restart of the TCI service. During this time the following linedisplays under the Global Time Acquired field:* Delay in progress. 180 seconds before time master is enabled.

Year: this field displays the GTS year value. If the value is 0, the major timeelements have not been loaded. The pc cannot serve as a Stagelink Time Master untilthe major time elements have been loaded.


Day: This field displays the GTS day of the year value. If the value is 0, the majortime elements have not been loaded. The pc cannot serve as a Stagelink Time Masteruntil the major time elements have been loaded.

Pulse Correction in Use: This field will display a time correction value if the cardis configured to receive 1 PPM or 1 PPH pulse input signals, or N/A if a the card isconfigured for a 1 PPS signal or a non-pulse based time signal. In the case of a 1PPM (pulse-per-minute) or 1 PPH (pulse-per-hour) signal, the value displayed is thevalue added to the time card�s time registers to correct for the time delta between thetime card�s time registers and the time that the pulse input was received. Theresulting value is the correction factor that is used by the Timesync program to adjustthe local pc clock and to report to the slave nodes if it is the selected master. Thefollowing additional fields are displayed if a 1 PPM or 1 PPH signal is in use:

Expected Pulse Frequency: The value displayed in this field correspondsto the period of the configured pulse mode. The value will be 60 seconds fora 1 PPM time source and 3600 seconds for a 1 PPH time source.

Seconds until pulse death: The value displayed in this field indicateswhether the last expected pulse was received. A value equal to the value inthe Expected Pulse Frequency field indicates that the last pulse wasreceived. If the last pulse was not received, the value counts down until thetime of the next expected pulse. If the second consecutive pulse is notreceived the time source will be declared dead and the time card Status willtransition from TRACKING to FLYWHEELING.

Pulse mask in use: The value shown indicates which elements of the timedelta are considered in determining the error. The pulse mask will be +000000:01:00.000000 for a 1 PPM time source, which indicates that the timeelements from minutes and above are ignored. When a pulse is received, thetime card�s seconds and subsecond registers are captured and the other timeelements are ignored. A 1-pulse-per-minute signal can be used to adjust thetime in increments smaller than a minute, so the time elements other thanseconds and subseconds are ignored. A 1 PPH time source will use +000001:00:00.000000 as the time mask, which indicates that time registers ofhours and above will be ignored.

Major Time Load Flag: This field indicates the source of the major time elementswhen the time card is initialized. The value corresponds to the TIME_LOADparameter in the timesync.dat file.

TIME_LOAD LOCAL displays �LOCAL CMOS�

TIME_LOAD MANUAL displays: �MANUAL only�

TIME_LOAD NETWORK displays: �NETWORK or MANUAL�

Global Time Source: This field displays the time base of the GTS. The valuecorresponds to the value of the TIME_SOURCE parameter in the timesync.dat file.The value displayed will be either UTC or LOCAL.

Mark V Panel Time: This field displays the time base of the Mark V controllers onthe Stagelink network. The value corresponds to the value of the MARKV_TIMEparameter in the timesync.dat file. The value displayed will be either UTC orLOCAL.

Mark V LM Panel Time: This field displays the time base of the Mark V LMcontrollers on the Stagelink network. This value is always UTC for Mark V LMcontrollers.

(I)/(G) CPU Time: This field displays the time base of the pc. The value is alwaysUTC for TCI systems because TCI is Windows-based and uses UTC as the timebase.


Local Windows NT Timeset: This field indicates whether the pc�s internal time isbeing adjusted by Timesync. The value corresponds to the LOCAL_TIMESETparameter in the timesync.dat file. The value displayed will be either ENABLED orDISABLED.

Number of Stagelink Time Masters: the value shown indicates the total number ofavailable time masters on the Stagelink network.

Status Table: The table shows the location (Stagelink Network Number), StagelinkAddress, time master status, and selected status of each available time master on theStagelink Network. The status word is a hexadecimal value with the following bitassignments:

Bit 0: 1 ==> Stagelink Timemaster is tracking the GTS.

Bit 0: 0 ==> Stagelink Timemaster is flywheeling.

Bit 1: Reserved. Normally has a value of 1.

Bits 2-7: Reserved. Normally has a value of 0.

Bit 8*: 1 ==> GTS is UTC based.

Bit 8*: 0 ==> GTS is LOCAL.

*This bit corresponds to the TIME_SOURCE parameter setting in thetimesync.dat file of the pc.

Bit 9: This bit will always be set to 1 in a TCI system since Windows isUTC based.

Bit 10*: 1 ==> Mark V�s time is UTC based.

Bit 10*: 0 ==> Mark V�s time is LOCAL.

*This bit corresponds to the MARKV_TIME parameter setting in thetimesync.dat file of the pc.



Reserved bit definitions are subject to change.

The status word can be used to determine at a glance which time masters are trackingan external time source- any status word ending in an odd number is TRACKINGand any status word ending in an even number is FLYWHEELING.

Note The two most significant digits of the status word should be identical in alltime masters on the Stagelink Network. If they do not match, shifts in the timereference may occur when a new master is selected. Resolve any differences bysetting the TIME_SOURCE and MARKV_TIME parameters to the same values inthe timesync.dat file on all of the PCs in the system.

Network number, LOCAL ARCNET Address: this field indicates whichStagelink networks the pc is connected to and gives the Stagelink address ofthe pc on each network.


Timesync Status ExamplesTime Card using IRIG-B: The TIMEUTIL output example (refer to the ObtainTimesync Status Information section) shows the status of a system using a bc620ATtime card using modulated IRIG-B signals from the GTS. The time card is trackingthe GTS, which implies that the time signals are actively being received from theGTS. Global time has been acquired and the non-zero Year and Day values showthat the major time elements have been loaded.

The pc is an available Timesync master since it is tracking the GTS, global time hasbeen acquired and the major time elements have been loaded. The chart at the bottomshows that this node is the selected time master, which can be seen by the fact thatthe node with address 0x1F is selected and the last line in the display indicates thatthis node�s Stagelink address is 0x1F.

Time Card using 1Pulse Per Minute time signal: The following figure shows theoutput for an 1 pulse-per-minute GTS on December 6, 2000, the 341st day of theyear.

--------------------------------------------------------------- TIMESYNC STATUS (NT Version)Overall TIMESYNC Function: ENABLED

TIMESYNC Controller: Bancomm bc620ATTIMESYNC Mode: 1 PPM Status: TRACKING

Global Time Acquired: YES Year: 2000 Days: 341

Pulse Correction in Use: -0000 00:00:13.133037Expected Pulse Frequency: 0060 seconds. Seconds until pulse death: 0060Pulse mask in use: +0000 00:01:00.000000

Major Time Load Flag: LOCAL CMOS

Global Time Source: UTCMark V Panel Time: LOCALMark V LM Panel Time: UTC<I> / <G> CPU Time: UTC Local Windows NT Timeset: ENABLED

Number of Stagelink Time Masters: 1Network Address Status Selected 1 0x1F 0x1F03 x

Network #1, Local ARCNET address: 0x1F-----------------------------------------------------------------------------------------


The output above shows that the bc620AT card is configured to receive a 1Pulse Per Minute signal, and the TRACKING value in the Status fieldindicates that the pulses are being received. Global Time Acquired displaysYES which indicates that at least one pulse has been received and the timecorrection value has been calculated. The value shown in the PulseCorrection in Use field is the value added to the time card�s time registersto correct for the time delta between the time card�s time registers and thetime that the pulse input was received. The resulting value is the value thatis used by the Timesync program to adjust the local pc clock and to reportto the slave nodes. The Expected Pulse Frequency field is 60 secondssince this is a 1 pulse per minute time source. The Seconds until pulsedeath is 60 which indicates that the last pulse was received. If a pulse ismissed, the Seconds until pulse death number will count down to zero. Iftwo consecutive pulses are lost the connection is declared dead, the statuswill transition from TRACKING to FLYWHEELING. The Seconds untilpulse death field will display 0000. If the pulse following the dropped pulseis received the transition will not occur. The pulse correction value cannotbe calculated in the absence of the pulse signals, so the pulse correctionvalue will remain unchanged until the pulse signal is restored. The Pulsemask in use field indicates that only the seconds and subseconds are beingused in the pulse correction value.

Time Card in Flywheel Mode: The following figure shows the output fora bc620AT time card configured for Flywheel operation on December 6,2000, the 341st day of the year.

----------------------------------------------------------------------------------------- TIMESYNC STATUS (NT Version)Overall TIMESYNC Function: ENABLEDTIMESYNC Controller: Bancomm bc620ATTIMESYNC Mode: FLYWHEELING Status: FLYWHEELING

Global Time Acquired: NO * Year: 2000 Days: 341* Delay in progress. 180 seconds before time master is enabled.

Pulse Correction in Use: N/A


Global Time Source: UTC Mark V Panel Time: LOCALMark V LM Panel Time: UTC<I> / <G> CPU Time: UTC Local Windows NT Timeset: ENABLEDNo Stagelink Time Masters exist.Network #1, Local ARCNET Address: 0x3F-----------------------------------------------------------------------------------------

The output above shows that the bc620AT card is configured forFLYWHEEL mode, which causes the card to use its on-board clock as thetime source. The Status field always indicates FLYWHEELING (neverTRACKING) in this mode because an external time signal is not beingreceived. The data above was taken when the system was first restarted-notice that the Global Time Acquired field displays NO, and beneath it isthe note that there will be a 180 second delay (3 minutes) before the timemaster is enabled. After the 180 seconds elapse, the Global Time Acquiredfield will indicate YES and the pc is available as a time master on theStagelink.


Low Resolution Mode: The following figure shows the output for an HMIpc running the Timesync software configured as a LowRes time master.

----------------------------------------------------------------------------------------- TIMESYNC STATUS (NT Version)Overall TIMESYNC Function: ENABLEDTIMESYNC Controller: Low resolutionTIMESYNC Mode: Low Resolution Status: FLYWHEELING

Global Time Acquired: NO * Year: 2000 Days: 341* Delay in progress. 180 seconds before time master is enabled.

Pulse Correction in Use: N/A


Global Time Source: UTC Mark V Panel Time: LOCALMark V LM Panel Time: UTC<I> / <G> CPU Time: UTC Local Windows NT Timeset: ENABLEDNo Stagelink Time Masters exist.Network #1, Local ARCNET Address: 0x3F-----------------------------------------------------------------------------------------

The output above shows that the Timesync Controller is the Low resolution timecard emulator � there is no time card in this pc. Low Resolution mode uses the pc�sclock as the time source, so the field will always indicate FLYWHEELING (neverTRACKING) in this mode because an external time signal is not being received. Thedata above was taken when the system was first restarted- notice that the GlobalTime Acquired field displays NO, and beneath it is the note that there will be a 180second delay (3 minutes) before the time master is enabled. After the 180 secondselapse, the Global Time Acquired field will indicate YES and the pc is available as atime master on the Stagelink.


Obtain Timesync Trace InformationThe Timesync program maintains a trace buffer in memory while it is running. Thetrace buffer contains a log of the internal Timesync activity on the pc. If the pc is thecurrently selected Stagelink Time Master, the messages between the slave nodes andthe time master are also displayed. Timesync trace information is retrieved using theGBL2FILE.EXE program as follows:

G:\Exec\GBL2FILE timesync_trace <output file>

<output file> specifies the path (optional) and the name of the file to where the resultswill be written. If a path is not specified ,the results will be written to the G:\Execdirectory. The timesync_trace argument must be entered in lowercase. Following isa sample output from the timesync_trace buffer:

000131CC, E1 --> 00 (OUT) Msg.Type: 1(Timesync Master ID)Sequence #32DD Highest Time Format: 4, Timesync Master Status: 1903 Packet recorded at: 22-MAY-1997 18:59:02.214 (NT Time)

000131CD, 59 --> E1 (IN) Msg. Type: 2 (Request For Time Sequence #B560 Raw Time: 01 42 18 59 12 52 39 69 Time Format: 3, Timeboard Time: 142 18:59:12.523969 Packet recorded at: 22-MAY-1997 18:59:12.379 (NT Time)

000131CE, E1 --> 59 (OUT) Msg. Type: 3 (Time Response) Sequence #B560 Time Format: 3, Local Correction: -0240, Response Status: 0000 Raw Time: 80 97 84 33 C1 FE 07 00 Time Returned: 22-MAY-1997 18:59:12.523969 Packet recorded at: 22-MAY-1997 18:59:12.389 (NT Time)

000131CF, 59 --> E1 (IN) Msg. Type: 4 (Time Diagnostic) Sequence #B560 Raw Time: 00 00 00 00 85 09 00 00 Time Format: 3, Delta-Time: -0000 00:00:00.000437 Packet recorded at: 22-MAY-1997 18:59:12.389 (NT Time)

000131D0, E1 --> 00 (OUT) Msg.Type:1 (Timesync Master ID)Sequence #32DE Highest Time Format: 4, Timesync Master Status: 1903 Packet recorded at: 22-MAY-1997 18:59:22.223 (NT Time)

000131D1, Doing LOCAL TIMESET Function. Old Time: 22-MAY-1997 18:59:22.223 New Time: 22-MAY-1997 18:59:22.360000131D2, 59 --> E1 (IN) Msg. Type: 2 (Request For Time)Sequence #B561 Raw Time: 01 42 18 59 32 52 15 32 Time Format: 3, Timeboard Time: 142 18:59:32.521532 Packet recorded at: 22-MAY-1997 18:59:32.514 (NT Time)

000131D3, E1 --> 59 (OUT) Msg. Type: 3 (Time Response) Sequence #B561 Time Format: 3, Local Correction: -0240, Response Status: 0000 Raw Time: 94 97 84 33 3C F5 07 00 Time Returned: 22-MAY-1997 18:59:32.521532 Packet recorded at: 22-MAY-1997 18:59:32.514 (NT Time)

000131D4, 59 --> E1 (IN) Msg. Type: 4 (Time Diagnostic)Sequence #B561 Raw Time: 00 00 00 00 80 09 00 00 Time Format: 3, Delta-Time: -0000 00:00:00.000432 Packet recorded at: 22-MAY-1997 18:59:32.514 (NT Time)

000131D5, E1 --> 00 (OUT) Msg.Type:1 (Timesync Master ID)Sequence #32DF Highest Time Format: 4, Timesync Master Status: 1903 Packet recorded at: 22-MAY-1997 18:59:42.368 (NT Time)

The output above shows the typical Timesync message traffic. Each message has aunique hexadecimal ID number, followed by a designation of the source anddestination nodes� Stagelink addresses.


In the example above, E1 is the address of the master node and there is a slave nodewith address 59 requesting time from it. The (IN) and (OUT) designations showwhether the message is being received (IN) by the time master or sent (OUT) by it.The message type information shows the type of message that was sent or received,as follows:

• Type 1 messages (Timesync Master ID) are generated when the master nodesends out the message of who he is and what his status is, signaling to the slavenodes that he is alive and available.

• Type 2 messages (Request for time) are generated when the slave nodes requestthe time from the master node.

• Type 3 messages (Time Response) are generated when the master responds tothe client�s (slave�s) request for time. Message types 1-3 are useful fordevelopment purposes but generally are not useful to the average user.

• Type 4 messages (Time Diagnostic) are the main item of interest whenevaluating the state of the system. These messages show the error correctionsbetween the Stagelink Time Master and the slave node(s), which are indicated bythe Delta-Time value.

Timesync Log FileThe G:\Log\Timesync.log file is created by the Timesync process if a configuration orhardware error is encountered. If the file does not exist an error was not reported bythe Timesync process.


Connecting to a Satellite Time Source (GTS)The time signal is usually supplied from a satellite receiver or other device via anRG-58 coaxial cable. T-connectors are used to parallel the signal between devices ifmultiple devices require the time signal. IRIG-B or other timecode signals areconnected to the Timecode Input BNC connector of the time card. Pulse signals (1pulse-per-minute and 1 pulse-per-hour) are connected to the Event Input BNCconnector of the time card. See the PC Time Card Installation section of thisdocument for detailed information about the connections supplied by the differenttime cards.

Validating GTS Signal ReceptionFailure of the Timesync process to track the GTS may indicate that the time card isnot receiving the time signals. Refer to Testing the Cards under the PC Time CardInstallation section of this document for a description of the TEST_620.EXEprogram. That section includes the procedure to verify that the time card is receivingtimecode or pulse input signals.

System Configuration IssuesThe previous sections showed how to configure an individual HMI pc, this sectiondiscusses the issues involved in configuring the HMIs from a system perspective.This section assumes Stagelink time synchronization only. Topologies thatincorporate both Ethernet synchronization via NTP and Stagelink synchronizationvia Timesync are discussed in a later section.

The HMI with the lowest numbered Stagelink address will be considered the PrimaryStagelink Master and HMIs with higher Stagelink addresses are referred to as thesecondary operator interfaces. The primary master will always be selected by defaultunless a problem prevents it from receiving its time reference or it is unable tocommunicate on the Stagelink network.

If an HMI is connected to multiple Stagelink networks, it will synchronize to theselected master on the lowest numbered network. An HMI connected to multipleStagelink networks can simultaneously act as master on all of the networks it isconnected to.

The TIME_SOURCE and MARKV_TIME parameters in the timesync.dat file of allof the HMIs in the system must agree to avoid shifts in system time when a newStagelink Time Master is selected. The I_TIME parameter, if specified, has noeffect.

The easiest way to verify that these parameters agree is to run the TIMEUTILprogram with the �status� argument and verify that the 2 most significant digits ofthe status word are the same for all of the available Stagelink Masters. See theObtain Timesync Status Information section under the Synchronization OverStagelink section of this document for additional information and examples.


Sample Topologies (Timesync only)Single Time Master on a Single Stagelink

HMI Stagelink

MarkV MarkV

IRIG-B(optional)

The figure above shows an example of a single HMI with a bc620AT time cardacting as the time master on a Stagelink network. The ARCNET Time Sync tab ofthe TCI control panel applet would have the following settings:

The timesync.dat file would have the following entries, with the boldfaced entriesbeing the only allowed values and the other entries being set according to thespecifics of the requisition:

TIMESYNC BC620AT MODE IRIG-B

TIME_SOURCE UTC

LOCAL_TIMESET ENABLED

MARKV_TIME LOCAL

TIME_LOAD LOCAL

The IRIG-B time signal is optional- if there is no satellite time source available thetime card can be configured to run in Flywheel mode by leaving everything else thesame and using the following TIMESYNC line in the timesync.dat file:

TIMESYNC BC620AT MODE FLYWHEEL


Multiple Stagelinks Following The Same Satellite TimeSourceThe previous example can be expanded to provide a common time reference tomultiple Stagelink networks as in the following figure where each HMI has abc620AT time card installed:

Stagelink 1

MarkV MarkV

HMI Stagelink 2

MarkV MarkV

IRIG-B fromsatellite receiveror other device

RG-62CoaxialCable

HMI

Timecodein BNC

RG-58CoaxialCable

Timecodein BNC

IRIG-B timecode toother plant equipment

Timecodein BNC

HMI Stagelink 3

MarkV MarkV

The time card in each HMI is connected to a common IRIG-B signal from a satellitereceiver or other device via RG-58 coaxial cable. This signal may also be routed toother devices in the plant. Each HMI acts as the time master on the Stagelinknetwork that it is connected to, and all Stagelink networks are now following thesame time reference.

The configuration of each HMI is identical to the single Stagelink example above.The ARCNET Time Sync settings in the TCI control panel applet are set for HighResolution and bc620AT. The timesync.dat file in each HMI specifies TIMESYNCBC620AT MODE IRIG-B in the first line and the other lines are specified asappropriate to the specifics of the system. Remember that the TIME_SOURCE andMARKV_TIME parameters should be identical in all of the time master HMIs.

Note a pulse input can be used instead of an IRIG-B timecode by connecting thepulse signal RG-58 coax cable to the Event In BNC connector and specifying 1PPM(or 1PPH) for the TIMESYNC MODE parameter in the timesync.dat file asfollows: TIMESYNC BC620AT MODE 1PPM


Multiple Stagelinks Following a Single HMI Configured asthe GTSMultiple Stagelink networks can be synchronized to a common time reference in theabsence of a satellite time source by allowing one time card to act as the GTS for thesite by running one time card in Flywheel mode and feeding the other time cardswith the output of the flywheeling card as shown in the following figure where eachHMI has a bc620AT time card installed:

Stagelink 1

MarkV MarkV

HMI2 Stagelink 2

MarkV MarkV

IRIG-B timecode toother plant equipment

RG-62CoaxialCable

Timecodeout BNC

HMI1(GTS)

Timecodein BNC

Timecodein BNC

HMI3 Stagelink 3

MarkV MarkV

RG-58CoaxialCable

Note the 1PPS output from the flywheeling time card can also be used to feed DCSequipment or any other 1PPS based equipment.

An RG-58 coaxial cable is connected from the timecode output BNC connector ofthe HMI configured as the GTS to the timecode input BNC connectors on the timecard in each of the other HMIs using T-connectors. The configuration for all of theHMIs in the TCI control panel applet specifies High Resolution and bc620AT for theARCNET Time Sync parameters. The timesync.dat file in the HMI acting as theGTS must specify Flywheel mode.

TIMESYNC BC620AT MODE FLYWHEEL

TIME_SOURCE UTC


MARKV_TIME UTC [G1]

TIME_LOAD LOCAL

Specifies "Flywheel" mode for the HMIacting as a GTS.Specifies "IRIG-B" for the other HMIswith time cards installed.

Example of aTimesync.dat file


Redundant Masters on the Same StagelinkMultiple HMIs can be configured as time masters on the same Stagelink to provideredundancy. Each HMI that will act as a Stagelink time master will have a timecardinstalled. The HMI with the lowest Stagelink address will be given priority over theother time masters and is referred to as the primary time master. The other HMIswith time cards are the secondary time masters and will only be selected if theprimary time master is shut down or loses its connection to the time source. Thefollowing figure shows a system where the same IRIG-B time signal is fed to all ofthe time cards.

HMI(Primary)

MarkV

MarkV

HMI(Secondary)

HMI(Secondary)

IRIG-B timecode to other plant equipment

RG-58CoaxialCable

RG-62 Coaxial CableTimecode

in BNC

Timecodein BNC

Timecodein BNC

MarkV

Stagelink

IRIG-B from satellitereceiver or other device

The time card in each HMI is connected to a common IRIG-B signal from a satellitereceiver or other device via RG-58 coaxial cable. This signal may also be routed toother devices in the plant. The primary time master is the HMI with the lowestARCNET Link Address specified on the ARCNET tab of the TCI Control Panelapplet, as shown in the following figure:


The primary time master can be re-assigned by giving one of the other HMIs a lowerARCNET address than the current primary time master HMI, or by giving thecurrent primary time master HMI a higher address than one of the other time masterHMIs. Remember that the Stagelink address (ARCNET Link Address) must beunique on the Stagelink network, do not assign an address that is already used byanother device on the Stagelink.

The configuration for all of the HMIs on the TCI Control Panel applet ARCNETTime Sync tab specifies High Resolution and bc620AT for the card type.

The timesync.dat file will be identical in all of the HMIs with time cards installed.The timesync.dat file in this example would have the TIMESYNC line specified asshown with appropriate values for the other settings:


TIME_SOURCE UTC


MARKV_TIME LOCAL

TIME_LOAD LOCAL

Note a pulse input can be used instead of an IRIG-B timecode by connecting thepulse signal RG-58 coaxial cable to the Event In BNC connector and specifying1PPM (or 1PPH) for the TIMESYNC MODE parameter in the timesync.dat file asfollows: TIMESYNC BC620AT MODE 1PPM


Single High Resolution Time Master with Several TimeSlaves on a Single StagelinkThe following figure shows a system where one HMI has a bc620AT time cardinstalled receiving an IRIG-B time signal and the remaining HMIs are either LowResolution time masters or Time Slaves, or a combination of the two:

HMI1

MarkV

MarkV

RG-58CoaxialCable

RG-62 Coaxial CableTimecode

in BNC

MarkV

Stagelink

IRIG-B from satellitereceiver or other device

HMI2

HMI3

The configuration for HMI1 on the TCI Control Panel applet ARCNET Time Synctab specifies High Resolution and bc620AT for the card type. The timesync.dat filefor HMI1 would typically be configured as follows:


TIME_SOURCE UTC


MARKV_TIME LOCAL

TIME_LOAD LOCAL

HMI2 and HMI3 do not have time cards installed, so they would specify LowResolution or None for Time Acquisition Hardware and <No card installed> in theCard Type field. If None is selected, the Timesync program terminates when the TCIservice is started, so no time correction will occur on the HMI and the entries in thetimesync.dat file have no effect.

If Low Resolution is selected for Time Acquisition Hardware, TIMESYNC LOWRESor TIMESYNC SLAVE should be specified in the timesync.dat file for HMI2 andHMI3. A typical timesync.dat file follows:

TIMESYNC SLAVE

TIME_SOURCE UTC


MARKV_TIME LOCAL

TIME_LOAD LOCAL


The selection of LOWRES or SLAVE determines whether the HMI can act as anavailable time master. If LOWRES is selected, the HMI advertises itself as anavailable time master on the ARCNET. It can act as the selected time master if theHigh Resolution time master is lost. If SLAVE is selected, the HMI uses its internalLow Resolution time source to set its local time if there are no available masters onthe Stagelink. It does not advertise itself as an available master, so the other nodeswill not attempt to use it as a time master.


Notes

GEI-100513 HMI Time Synchronization Chapter 4 Mixed Network Topology Guidelines •••• 4-1

Chapter 4 Mixed Network TopologyGuidelines

IntroductionSystems may include both Stagelink-based devices, such as Mark V controllers, andEthernet-based devices, such as Mark VI controllers. These systems require carefulcoordination between the HMI PCs to achieve the same time reference over theEthernet and Stagelink networks. System topology must be carefully considered inthese situations.

This chapter defines requirements for time synchronization on the different types ofsystem configurations.

Section Page

Overview of HMI Types...........................................................................................4-2Type 1: HMIs with a Time Card Supplying Time to the Ethernet and At Least OneStagelink Network ....................................................................................................4-2

Timesync Configuration....................................................................................4-3NTP Server Configuration.................................................................................4-3

Type 2: HMI Synchronized to and/or Supplying Time to Only One Network Type(Ethernet or Stagelink) .............................................................................................4-4Type 3: HMI Synchronized to Ethernet Time and Supplying Time to at Least OneStagelink Network ....................................................................................................4-5

Timesync Configuration....................................................................................4-5NTP Configuration............................................................................................4-5

Type 4: HMI Synchronized to Stagelink Time and Supplying Time to the Ethernet4-6Timesync Configuration....................................................................................4-6NTP Configuration............................................................................................4-6

Example Topologies.................................................................................................4-7

4-2 •••• Chapter 4 Mixed Network Topology Guidelines SPEEDTRONIC Turbine Control, GEI-100513

Overview of HMI TypesEach HMI in the turbine control system falls into one of the following categories:

Type 1: HMI with a time card supplying time to the Ethernet and at least oneStagelink Network

Type 2: HMI synchronized to and/or supplying time to only one network type(Ethernet or Stagelink)

Type 3: HMI synchronized to Ethernet time and supplying time to at least oneStagelink network

Type 4: HMI synchronized to Stagelink time and supplying time to the Ethernet

In general, the HMI and Historian PCs are synchronized over Ethernet using NTPand NTP Server.

In a mixed system with both Mark VI controllers (Ethernet) and Mark V controllers(Stagelink), the HMI PCs and Mark VI controllers are synchronized over Ethernetusing NTP, and Timesync is used to synchronize the Mark V controllers.

Type 1: HMIs with a Time Card Supplying Time to theEthernet and At Least One Stagelink Network

An HMI with a time card can supply time to both the Ethernet and Stagelinknetworks. NTP Server is used to interface with the time card to supply time to theEthernet and it is configured to regulate the local time on the pc. Timesync isconfigured to interface with the time card and act as a Stagelink Time Master, but itsability to set the local pc�s time is disabled to avoid conflicts with NTP Server�sregulation of the pc�s time.

The following figure illustrates the implementation within the HMI pc.

NTPServer

Timesync

Time Card

Ethernet

Stagelink


Timesync ConfigurationChapter 3 provides configurationdetails.

Configure TCI: The High Resolution hardware option must be selected and theCard Type and Base IO Address must be properly specified on the ARCNET TimeSync tab of the TCI Windows Control Panel applet.

Edit the Timesync.dat file: The TIMESYNC line must be configured to allowTimesync to receive time from the time card, and the adjustments to the local clockmust be disabled using the LOCAL_TIMESET line. The following example showshow these two lines would be configured in a pc using a bc620AT time card usingIRIG-B timecode signals.


LOCAL_TIMESET DISABLED

Stop and restart the TCI service and the ARCNET driver to activate thechanges.

NTP Server ConfigurationNTP Server must be configured to enable Internal Regulation. The Unicast Serverand Broadcast Server options should be set according to the requirements of the NTPclients in the system. Enable the Broadcast Server option to broadcast the time toBroadcast Clients on the Ethernet and enable the Unicast Server option to supportany Unicast Clients on the Ethernet. The following is an example where NTP Serveris configured to regulate the local pc clock and to act as a Unicast Server.


Type 2: HMI Synchronized to and/or Supplying Time toOnly One Network Type (Ethernet or Stagelink)Chapters 2 and 3 provideconfiguration details.

System topology dictates whether each HMI is configured to implement Ethernet orStagelink time synchronization or a combination of the two. An HMI in a systemwith at least one Stagelink network implements time synchronization over a singlenetwork type in the following cases:

• The HMI is not connected to a Stagelink network.

• The HMI is connected to a Stagelink network, but it will not synchronize to it oract as a master on it.

• The HMI is synchronized to a Stagelink network and it will not be used as a timesource on the Ethernet.


Type 3: HMI Synchronized to Ethernet Time andSupplying Time to at Least One Stagelink Network

An HMI without a time card can be configured to synchronize to an Ethernet timesource. It can also supply time to any Stagelink networks it is connected to. NTP isconfigured to synchronize the local pc�s time to the Ethernet time source. Timesyncis configured as a Low Resolution time master with its ability to regulate the pc�slocal clock disabled. This allows Timesync to track the pc�s time, which is regulatedby NTP. This allows Timesync to supply this time to the Stagelink networks towhich it is connected.

The following figure illustrates implementation within the HMI pc.

NTP

Timesync

Local Clock

Ethernet

Stagelink

Timesync ConfigurationChapter 3 providesconfiguration details.

Configure TCI: The Low Resolution hardware option must be selected and theCard Type and Base IO Address must be properly specified on the ARCNET TimeSync tab of the TCI Windows Control Panel applet.

Edit the Timesync.dat file: The TIMESYNC and LOCAL_TIMESET lines must beconfigured as follows:

TIMESYNC LOWRES

LOCAL_TIMESET DISABLED

Stop and restart the TCI service to activate the changes.

NTP ConfigurationChapter2 providesconfiguration details.

NTP can be configured as either a Master or Client. Configuring it as a Masterallows it to act as a redundant Time Master in the event that the primary TimeMaster is lost, or as the primary Time Master if a better time source does not exist onthe Ethernet.


Type 4: HMI Synchronized to Stagelink Time andSupplying Time to the Ethernet

An HMI without a time card can be configured to synchronize to the Stagelink TimeMaster using Timesync. It can also act as a time source on the Ethernet using NTP.Timesync is configured as a Low Resolution time source to allow it to operate as anavailable time master if the current time master is lost. It can also be specified as aslave to prevent it from ever becoming a time master. This configuration should onlybe used in cases where a high quality time source exists in the Stagelink network andthere is no high quality source on Ethernet.

Timesync is configured to regulate the time on the local pc. NTP is configured as aTime Master using only the local clock as the time source. This allows NTP to trackthe pc�s time, which is regulated by Timesync and allows NTP to supply this time tothe Ethernet. This configuration is useful if either a better time source does not existon the Ethernet, or redundancy of Ethernet time sources is desired.

The following figure illustrates implementation within the HMI pc.

NTP

Timesync

Local Clock

Ethernet

Stagelink

Timesync ConfigurationChapter 3 providesconfiguration details.

Configure TCI: The Low Resolution hardware option must be selected and theCard Type and Base IO Address must be properly specified on the ARCNET TimeSync tab of the TCI Windows Control Panel applet. (See the Configuration sectionof Chapter 3, Synchronization Over Stagelink Configuring.)

Edit the Timesync.dat file: The TIMESYNC and LOCAL_TIMESET lines mustbe configured as follows:

TIMESYNC LOWRES (or TIMESYNC SLAVE)


Stop and restart the TCI service to activate the changes.

NTP ConfigurationChapter 2 providesconfiguration details.

NTP must be configured as a Broadcast or Unicast Master using only the local clockas a time source.


Example TopologiesThis section provides examples of some mixed topologies using NTP and Timesync.Although not every variation in system topologies can be included in this document,the following examples illustrate the uses of each configuration type.

Example 1

HMI 1 Type 2

NTPServer

Time Card HMI 2Type 3

NTP

TimesyncSt

agel

ink

1

IRIG-B signal

Mark VI Mark VIMark VI

Ethernet (UDH)

Mark V

Mark V

HMI 3Type 3

NTP

Timesync

Stag

elin

k 2

Mark V

Mark V

HMI 4Type 3

NTP

Timesync

Stag

elin

k 3

Mark V

Mark V

HMI1 connects to a satellite time source and acts as a Time Master on the Ethernetonly. It does not connect to any of the Stagelink networks. All Mark VI controllersand HMIs are synchronized to HMI1 over Ethernet via NTP.

NTP in each HMI can be configured in one of two ways:

• As a Time Master to allow the HMI to act as a backup time source if HMI1 islost

• Or as a Time Client only

Each HMI connects to an isolated Stagelink network. Therefore, each HMI isconfigured as a Type 3 to allow it to synchronize the Stagelink network to the sametime as the Ethernet Time Master. Timesync in each HMI is configured as a LowResolution Stagelink Time Master.


Example 2

HMI 1 Type 1

NTPServer

Timesync

Time Card HMI 2Type 3

NTP

Timesync

HMI4Type 2

NTP

HMI3Type 3

Timesync

IRIG-B signal

Mark VI Mark VIMark VI

Ethernet (UDH)

Stagelink

Mark V Mark V Mark V

NTP

HMI1 is configured as a Type 1 time node because it has a time card and connects toboth the Ethernet and the Stagelink networks. NTP Server is regulating HMI1�s localclock and also acting as a Broadcast Server, Unicast Server, or both on the Ethernet(depending on the configuration of the Mark VI controllers and HMI4). HMI1 is alsoacting as the Stagelink Time Master.

Both HMI2 and HMI3, which are connected to the Stagelink, are synchronizing toHMI1 using NTP Type 3 configuration This means that it is synchronized toEthernet. Additionally, it may also act as a time master on the Ethernet. ConfiguringTimesync on HMI2 as a Low Resolution Time Master on the Stagelink with NTP asa time master allows HMI2 to act as a backup time source on both the Ethernet andthe Stagelink if HMI1 is lost.

HMI4 is not connected to the Stagelink network, so it is a Type 2 configuration.HMI4 can be configured as an NTP Time Master to provide a redundant time sourceon the Ethernet, or it can be configured as an NTP Time Client only. The Mark VIdevices can be configured as either Broadcast or Unicast clients on the Ethernet. TheMark V devices automatically synchronize to the selected Stagelink Time Master.

GEI-100513 HMI Time Synchronization Chapter 5 PC Time Card Installation •••• 5-1

Chapter 5 PC Time Card Installation

IntroductionThe HMI pc can be equipped with a satellite interface card to allow the pc to act aseither of two time sources:

• A universal time source when connected to a satellite signal

• Or as a low drift time source without the satellite connection

The NTP Server product or the Timesync software can access the time card via anappropriate hardware driver. They can then serve as an NTP time server in the caseof NTP Server or as an ARCNET time server in the case of Timesync.

The HMI supports the following time cards:

• Bancomm: bc620AT

• Bancomm: bc627AT

• KSI Odetics: tPRO-pc

The NTP Server product includes the Network Time Protocol Driver, which cansupport only the bc620AT and bc627AT time cards. NTP Server requires theTurbine ARCNET driver (which is installed as part of TCI) to communicate with thetPRO-PC card.

Systems that do not require ARCNET communications (MarkVI and serial Mark IV)normally use NTP Server and either the bc620AT or bc627AT card to synchronize toa satellite time source.

This chapter provides installation and configuration for the HMI time cards. It isorganized as follows:

Section Page

Bancomm bc620AT or bc627AT Time Card ...........................................................5-2Setting the Base I/O Address.............................................................................5-2Setting the IRQ..................................................................................................5-3Card Installation ................................................................................................5-3Connecting to the Global Time Source (GTS) ..................................................5-3Testing the Cards...............................................................................................5-4

KSI Odetics tPRO-PC Installation and Configuration............................................5-11Setting the Base I/O Address...........................................................................5-11Setting the IRQ................................................................................................5-12Card Installation ..............................................................................................5-12Connecting the Global Time Source (GTS) ....................................................5-12

5-2 •••• Chapter 5 PC Time Card Installation SPEEDTRONIC Turbine Control GEI-100513

Bancomm bc620AT or bc627AT Time CardThe following illustration shows a typical bc620AT/bc627AT Time and FrequencyModule, which is one of the time cards used in the HMI. Installation andconfiguration is described below.

JP1

SW1

J1

J2

BANCOMM bc620AT

I/O ADDRESS

IRQ JUMPERS

Setting the Base I/O AddressThe bc620AT or bc627AT card is shipped from the Bancomm factory with a baseI/O address of 0x0300. Always set the base I/O address to 0x0280 per the switchselections shown in the following illustration.

Address Bit A9 A8 A7 A6 A5 A4

1 2 3 4 5 6

OPEN

ON

OFF

SW1

A9 A8 A7 A6 A5 A0A1A2A3A4

1 0 1 0 0 0 000 0 = 0x0280

ONOFF

= 0= 1

INDICATES DIRECTION OF TOGGLE


Setting the IRQAdjust the bc620AT and bc627AT cards� IRQ setting to No IRQ, as shown in thefollowing illustration.

1 3 5 7 9 11 13 15 17 19 21 23Pin

IRQIR15

IR14

IR12

IR11

IR10 IR

9IR7

IR6

IR4

IR5

IR3

NOIRQ

JP1

Card InstallationThe bc620AT or bc627AT card can be placed in any spare ISA (Industry StandardArchitecture) slot of an operator interface. Refer to pc vendor user documentation forcard installation procedures. Refer to the card manufacturer�s documentation for softswitch settings.

Connecting to the Global Time Source (GTS)

bc620AT Time CardThe bc620At card has two connectors:

• J1 is a 15-pin receptacle D-connector and is used to connect the GTS

• J2 is not used for this application

The type of GTS determines how J1 is interfaced. For most GTSs, a 15-pin to BNCadapter is used for this connection. This adaptor consists of a 15-pin plug D-connector and five BNC receptacle connectors, as illustrated in the following figure.

1 PPS Output

1 PPS Input

Timecode Output

Event Input

Timecode Input(Modulated)

ReceptacleBNC's (GTS Source)

(Flywheel Mode Out)

(1 PPS)

(Optional External Use)

(1 PPM or 1 PPH)

(IRIG-A, IRIG-B,NASA36, or 2137)

Adapter

15-pinD Plug

Tobc620AT

J1


bc627AT Time CardThe bc627AT has two connectors, J1 and J2. J1 is not used for this application. J2 isa 12-pin receptacle and is used to connect to a GPS receiver core module. Thebc627At card has two connectors:

• J1 is not used for this application

• J2 is a 12-pin receptacle used to connect to a GPS (global positioning satellite)receiver core module

Refer to card manufacturer�s documentation for information about placement of theGPS antenna.

Testing the CardsThe G:\EXEC\TEST_620.EXE program is supplied as part of the TCI productsoftware. This program provides bc620AT/bc627AT testing capability.

This program can be used to verify that the GTS interface (pulse or timecode) ispresent and operational. This section describes how to use this program.

!Warning

This program can interfere with the normal timesyncoperation of the operator interface. This is especiallytrue for pulse input GTSs. This program should onlybe run when the TCI system service is not running.The ARCNET device driver must be running in orderto use this test program. Restart the TCI system serviceafter running this test program.

�� To run the test program:1. Open a Command Prompt window

2. Enter TEST_620

A menu of available commands is displayed, as shown in the figure below. Alsolisted below is a number of different tests that can be run.

-----------------------------------------------------------------------

Main bc620AT/bc627AT TestProgram Menu.

bc620AT Time & Frequency Processor Test Program (NT Version)1. Read Time2. Read Event Time (Pos. Edge) I. Read Event Time (Neg. Edge)3. Request bc620AT Programmable Data4. Request Model Number & Firmware Version5. Request D/A Value6. Request RTC Time7. Select Operational Mode8. Select Time Code Format and Type9. Program Control Register (CRO)A. Program Heartbeats (82C54)B. Preset D/AC. Send Path ByteD. Send Command ** bc627AT COMMANDS ONLY **E. Load Major Time Registers J. Request YearF. Load RTC Time Registers K. Request GPS Leap SecondsG. Load Strobe Time L. Load GPS Leap SecondsH. Program Propagation Delay Offset M. Load GPS Time OffsetEnter Selection: x. Exit-----------------------------------------------------------------------


3. To test the bc620 times registers and/or to test timecode GTSs, go to the Test 1section that follows.

4. To test the bc620 event recording registers and/or to test 1PPS, 1PPM or 1PPHGTSs, go to the Test 2 section that follows.

5. To test 1PPS GTSs and/or the bc620 time registers, go to the Test 3 section thatfollows.

6. To test the bc620AT FIFO command/response registers, go to the Test 4 and Test5 sections that follow.

7. When tests are completed, select option x at the program menu. Restart the TCISystem Service.

Card Test 1This test validates the existence of a timecode GTS (if used) and the time recordingregisters of the bc620AT.

1. To begin the test, select 1 at the program menu. Press any key to terminate thetest.

This test reads the bc620 time registers as rapidly as possible. All of the bc620 timeregisters are BCD registers. If any digit displays as ":", ";", "<", "=", ">", or "?", thenthe bc620 time registers are defective or the I/O Port Base Address in the WindowsNT registry is wrong.

If a timecode GTS is in use and is operational, then each line should show Trackingstatus. Otherwise, each line shows Flywheeling status.

A sample read time register output is shown in the following example:

-----------------------------------------------------------------TIME: 143 14:19:48.859419 Status: 0 (TRACKING)TIME: 143 14:19:48.859710 Status: 0 (TRACKING)TIME: 143 14:19:48.859980 Status: 0 (TRACKING)TIME: 143 14:19:48.860256 Status: 0 (TRACKING)TIME: 143 14:19:48.860524 Status: 0 (TRACKING)TIME: 143 14:19:48.860794 Status: 0 (TRACKING)TIME: 143 14:19:48.861067 Status: 0 (TRACKING)TIME: 143 14:19:48.861336 Status: 0 (TRACKING)TIME: 143 14:19:48.861604 Status: 0 (TRACKING)TIME: 143 14:19:48.861878 Status: 0 (TRACKING)TIME: 143 14:19:48.862147 Status: 0 (TRACKING)TIME: 143 14:19:48.862423 Status: 0 (TRACKING)TIME: 143 14:19:48.862698 Status: 0 (TRACKING)TIME: 143 14:19:48.862967 Status: 0 (TRACKING)TIME: 143 14:19:48.863237 Status: 0 (TRACKING)TIME: 143 14:19:48.863511 Status: 0 (TRACKING)TIME: 143 14:19:48.863779 Status: 0 (TRACKING)TIME: 143 14:19:48.864120 Status: 0 (TRACKING)TIME: 143 14:19:48.864396 Status: 0 (TRACKING)TIME: 143 14:19:48.864665 Status: 0 (TRACKING)TIME: 143 14:19:48.864934 Status: 0 (TRACKING)TIME: 143 14:19:48.865207 Status: 0 (TRACKING)TIME: 143 14:19:48.865476 Status: 0 (TRACKING)TIME: 143 14:19:48.865744 Status: 0 (TRACKING)TIME: 143 14:19:48.866017 Status: 0 (TRACKING)TIME: 143 14:19:48.866287 Status: 0 (TRACKING)------------------------------------------------------------------


Card Test 2This test is used to validate the bc620 card�s event recorder registers, and can beused to validate pulse input GTSs. This test consists of several steps:

1. Program Control Register 0 to enable event recording while disabling eventlockout. Do this by selecting option 9 at the program menu, and then enter 08 forthe value of CR0. For an example, refer to the Sample Read Event RegisterOutput on the following page.

2. Select option 2 at the program menu. This starts event register recording, asshown by the Sample Read Event Register Output on the following page. (Thisexample was created by connecting the 1PPS Output BNC to the Event InputBNC.)

3. To test the bc620AT�s event recording capability, place a short circuit on theEvent Input BNC using a jumper wire. Every time the short circuit is removed, anew event time should be shown. All of the bc620 event registers are BCDregisters. Only digits 0-9 should be in these registers. If any digit displays as ":",";","<", "=", ">" or "?", then the bc620 event registers are defective or the I/OPort Base Address in the Windows NT registry is wrong. If a timecode GTS isattached to the "Timecode In" BNC, each line should show "Tracking" status.Otherwise, "Flywheeling" status will be shown.

4. To test 1PPS, 1PPM or 1PPH pulse input GTSs, attach the signal to the EventInput BNC.

For 1PPS, this is a temporary connection. 1PPS GTSs are normally connected to the1PPS Input BNC. Each time the pulse input changes from logic 0 to logic 1, a newevent time should be shown. All of the bc620 event registers are BCD registers. Onlydigits 0-9 should be in these registers.

If any digit displays as ":", ";","<", "=", ">" or "?", then the bc620 event registers aredefective or the I/O Port Base Address in the Windows NT registry is wrong. If atimecode GTS is attached to the Timecode In BNC, each line should show Trackingstatus. Otherwise, Flywheeling status is shown.


--------------------------------------------------------------------

Sample Read Event RegisterOutput.

3. Request bc620AT Programmable Data 4. Request Model Number & Firmware Version 5. Request D/A Value 6. Request RTC Time 7. Select Operational Mode 8. Select Time Code Format and Type 9. Program Control Register (CR0) A. Program Heartbeats (82C54) B. Preset D/A C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT

Enter selection: 9 Current CR0 value: 0x00 Enter new value (hex): 0x08 New value of CR0 written.

Press any key to continue:--------------------------------------------------------------------

--------------------------------------------------------------------

Programming Control Register0.

C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT

Enter selection: 2

Waiting for an event input pulse...hit any key to return

Event Time: 143 14:20:52.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:53.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:54.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:55.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:56.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:57.0000001 Status: 0 (TRACKING) Event Time: 143 14:20:58.0000001 Status: 0 (TRACKING) Event Time: 143 14:20:59.0000001 Status: 2 (TRACKING)------------------------------------------------------------------


Card Test 3This test will validate the existence of a 1PPS GTS and the time recording registersof the bc620AT.

�� To set up Test 31. Select 7 at the program's menu to select the operational mode of the bc620AT.

2. Select 2 to choose 1PPS synchronization.

3. Press any key to return to the program's menu.

4. See the sample below for an example of selecting the operational mode.

5. To begin the test, select 1 at the program's menu. Press any key to terminate thetest.

The program reads the bc620 time registers as rapidly as possible. All of the bc620time registers are BCD registers. Only digits 0-9 should be in these registers. If anydigit displays as ":", ";", "<", "=", ">" or "?", then the bc620 time registers aredefective or the I/O Port Base Address in the Windows NT registry is wrong.

If the 1PPS GTS is connected to the 1PPS Input BNC and is operational, then eachline should show Tracking status. Otherwise, each line shows Flywheeling status.

A sample output is shown in the example below:

Programming bc620AT to use1PPS GT (Test 3).

------------------------------------------------------------------ B. Preset D/A C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS LeapSeconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT

Enter selection: 7

Possible bc620AT Operating Modes: 0 - Time Code Mode (default bc620AT) 1 - Free Running Mode 2 - Synchronize of external 1PPS input 3 - Real Time Clock Mode 4 - GPS - Acutime Mode (default bc627AT) Current bc620AT Operating Mode: 0 - Time Code Decoder Mode Enter new operating mode (0-4): 2 REQUEST SENT TO bc620AT: 01 41 32 17

Press any key to continue:----------------------------------------------------------------------


Card Tests 4 and 5Tests 4 and 5 validate the bc620AT's FIFO command and response registers.

1. For Test 4, enter 3 at the program's menu prompt. An output similar to theexample below should be displayed.

Note If Test 3 was completed, the output will be slightly different.

2. To run Test 5, enter 4 at the program's menu prompt. An output similar to theexample below should be displayed.

If either test fails, then probably either the bc620AT is defective or the I/O PortBase Address in the Windows NT Registry is wrong.


-------------------------------------------------------------

Sample Request bc620ATProgrammable Data Output(Test 4).

G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT Enter selection: 3 REQUEST: 01 4F 33 17 REPLY: 01 6F 33 30 42 4D 42 30 31 2B 30 30 2B 30 30 30 REPLY: 30 30 30 30 30 30 30 30 30 30 30 30 30 17

bc620AT Programmable Data Mode: : 0 - Time Code Decoder Mode Time Code Format : B - IRIG B Time Code Type : M - Modulated Time Code Generator : B - IRIG B Path Byte : 0x01 Local Time Offset : +00 Propagation Delay Offset : +0.0000000 seconds Heartbeat (82C54) : Mode = 0 : Cnt1 = 0000 : Cnt2 = 0000

Press any key to continue:--------------------------------------------------------------

Sample Request Model Numberand Firmware Version Output(Test 5).

5. Request D/A Value 6. Request RTC Time 7. Select Operational Mode 8. Select Time Code Format and Type 9. Program Control Register (CR0) A. Program Heartbeats (82C54) B. Preset D/A

C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT

Enter selection: 4 REQUEST: 01 4F 34 17 REPLY: 01 6F 34 62 63 36 32 30 41 54 20 39 35 30 31 31 REPLY: 35 35 17

Model: bc620AT 9501155

Press any key to continue:


KSI Odetics tPRO-PC Installation and ConfigurationThe illustration below shows the general layout of the TPRO_PC card.

P2J3

J2

P4

P3

J1

IRQ JUMPERS

I/O ADDRESS

Setting the Base I/O AddressThe TPRO_PC card is shipped from KSI Odectics with a base I/O address of0x0300. Always set the base I/O address to 0x0280, as shown in the figure below.

11 10 9 78 5 46Pin

I/O ADDR JP=0

P3

Connected Pins = 0

Open Pins = 1

0 2 8 00000 0010 1000 0000

1110 9 8 7 6 5 4

Event Input

The TPRO_PC card is shipped from KSI Odectics with Event Input disabled. EventInput is used for 1 PPM and 1 PPH references. To enable Event Input, adjust thecard�s settings as shown in the figure below:

P4

E X D


Setting the IRQAdjust the card's IRQ setting pm the TPRO-PC board to No IRQ, as shown in thefigure below:

234567 10111214 15

IRQNO IRQ

P2

Card InstallationThe TPRO_PC card can be placed in any in any spare ISA (Industry StandardArchitecture) slot of an operator interface. Refer to pc vendor user documentation forcard installation procedures

Connecting the Global Time Source (GTS)The TPROC_PC has one panel connector, J1 and two BNC connectors, J2 and J3.J1 is a 15-pin receptacle D-connector and is used to connect the GTS. The type ofGTS determines how J1 is interfaced. For most GTSs, a 15-pin to BNC adapter isused. This connector consists of a 15-pin plug D-connector, and five BNC receptacleconnectors.

The figure below shows a diagram of this adapter. J2 can be connected to a timecodeinput and J3 can used as a timecode output.

1 PPS Output

1 PPS Input

Timecode Output

Event Input

Timecode Input(Modulated)

ReceptacleBNCs

(GTS Source)

(Flywheel Mode Out)

(1 PPS)

(Optional External Use)

(1 PPM or 1 PPH)

(IRIG-B or NASA36)

Adapter

15-pin D Plug

ToTPRO_PC

J1

GEI-100513 HMI Time Synchronization Appendix A IRIG Nomenclature and Codes •••• A -1

Appendix A IRIG Nomenclature andCodes

IRIG NomenclatureIRIG Time Codes have alphabetical as well as numerical designations, as defined inthis appendix.

Rate DesignationA: 1000 pps

B: 100 pps

D: 1 ppm

E: 10 pps

G: 10000 pps

H: 1 pps

Form Designation0: Pulse, width-coded

1: Sine wave, amplitude-modulated

Carrier/Resolution0: No carrier/index count interval

1: 100 Hz/10 ms

2: 1000 Hz/1 ms

3: 10000 Hz/0.1 ms

4: 100000 Hz/0.01 ms

A -2 •••• Appendix A IRIG Nomenclature and Codes SPEEDTRONIC Turbine Control GEI-100513

Coded Expressions0: BCD, CF, SBS

1: BCD, CF

2: BCD

3: BCD, SBS

IRIG CodesThe following is a list of recognized standard IRIG codes:

* Format A: A000, A003, A130, A133

* Format B: B000, B003, B120, B123

Format D: D001, D002, D111, D112, D121, D122

Format E: E001, E002, E111, E112, E121, E122

Format G: G001, G002, G141, G142

Format H: H001, H002, H111, H112, H121, H122

* Supported by Turbine Control Time Synchronization

GEI-100513 HMI Time Synchronization Glossary 1

Glossaryapplication codeSoftware that controls the machine or process, specific to the application.

ARCNETAttached Resource Computer Network, a LAN communications protocol developedby Datapoint Corporation. ARCNET defines the physical (coax and chip) anddatalink (token ring and board interface) layer of a 2.5 MHz communicationnetwork.

boardPrinted wiring board, or circuit board, used for electronic circuits.

configureSelect specific options, either by editing disk files, or by setting the location ofhardware jumpers, or by loading software parameters into memory.

coaxial cable (coax)A type of wire cable with a solid metal core surrounded by an insulator, acombination shield and ground wire, and an outer protective jacket.

connectorA device, either a plug or receptacle, used to terminate or connect cables.

control system(Industrial.) A means of governing the starting, stopping, direction of motion,acceleration, speed, and retardation of a moving member of any electrical apparatus,machine, or system.

control system toolboxSee GE Control System Toolbox.

CSFControl System Freeway, a token passing communication network, typically usingTWINAX cabling, running at 2.3 MHz. CSF is also called Control Signal Freeway.

EthernetLAN with a 10 or 100 megabaud data rate, used to link one or more computersand/or controllers together. It features a collision avoidance/collision detectionsystem. It uses TCP/IP and I/O services layers that conform to the IEEE 802.3standard, developed by Xerox, Digital Equipment Corporation, and Intel.

eventDiscrete signal generated by a change in a status of a logic signal in a controller.

Glossary 2 SPEEDTRONIC Turbine Control GEI-100513

EX2100GE generator exciter control. It regulates the generator field current to control thegenerator output voltage.

Global Time Source (GTS)Worldwide system supplying UTC (Coordinated Universal Time) using a network ofsatellites.

heartbeatSignal emitted at regular intervals by software to demonstrate that it is still active.

hexadecimal (hex)Base 16 numbering system using the digits 0-9 and letters A-F to represent thedecimal numbers 0-15. Two hex digits represent 1 byte.

Historian Client ToolsetSoftware package that allows a PC to become a client for the Historian data. This islicensed software consisting of components from both GE and OSI Software, Inc.

HMIHuman-Machine Interface. The GE HMI is a Windows NT-based operator interfaceto the turbine controllers and auxiliary power plant equipment. The HMI uses GEFanuc�s CIMPLICITY as the operator interface, and supports the Historian ClientToolset for viewing Historian data.

I/OInput/output interfaces that allow the flow of data into and out of a device.

logicalStatement of a true/false sense, such as a Boolean.

Mark IVSPEEDTRONIC gas turbine control system, introduced in 1983. The first GE TripleModular Redundant (TMR) control for fault-tolerant operation.

Mark VAll-digital SPEEDTRONIC gas and steam turbine control system, introduced in1991, available in Simplex and TMR control versions. At first equipped with aDOS-based PC operator interface, later upgraded to use the NT-based CIMPLICITYHMI.

Mark V LMSPEEDTRONIC gas turbine control system, introduced in 1995, designedspecifically to support the aeroderivative Dry Low Emissions (DLE) technologydeveloped by GE Aircraft Engines. Equipped to use the NT-based CIMPLICITYHMI.

GEI-100513 HMI Time Synchronization Glossary 3

Mark VIVME-based SPEEDTRONIC gas and steam turbine control system, introduced in1998, available in Simplex and TMR control versions. Equipped to use the NT-based Cimplicity HMI and Innovation Series Toolbox.

MSPMessage Service Protocol, a communication protocol used by many GE devices.

networkA data communication system that links two or more computers and peripheraldevices.

NTP (network time protocol)A communications protocol designed to synchronize clocks on servers and clients.You can have NTP servers and NTP clients. Clients receive time data from the NTPserver and can adjust their clocks as necessary.

pcPersonal computer.

StagelinkARCNET-based communication link used by many controllers.

TCITurbine Control Interface. It is the GE supplied software package on the HMI thatinterfaces to the turbine control.

time accuracyHow close a given time is to a known standard. Lack of time accuracy results in driftin the same way that a wristwatch can deviate over time without human intervention.GE has chosen the Global Time Standard called UTC. GE systems that have accessto this time standard using the high resolution option are accurate ±1 ms.

time coherencyHow close is the time reported by two different controllers for an event that happenssimultaneously for both.

time resolutionHow small a time increment a given controller can discriminate.

toolbox (Control System Toolbox)Windows-based software package used to configure the Mark VI controllers,exciters, and drives.

UTCCoordinated Universal Time, an international time reference standard.

Windows NTWindows New Technology, a 32-bit operating system from Microsoft Corporation.

Glossary 4 SPEEDTRONIC Turbine Control GEI-100513

Notes

GEI-100513 HMI Time Synchronization Index •••• 1

Index

AARCNET, 3-1, 3-2, 3-9, 3-13

BBancomm bc620AT Time Card, 5-1, 5-2Bancomm bc627AT Time Card, 5-1, 5-2bc620AT Time Card, 5-1, 5-2bc627AT Time Card, 5-1, 5-2Broadcast

Client, Standard Configuration Option, 2-1,2-6

Master, Custom Configuration Option, 2-1Broadcast and Unicast

Master, Custom Configuration Option, 2-1Server, 2-1, 2-13

CConfiguration

CustomBroadcast and Unicast Master, 2-1Broadcast Master, 2-1

NTP, 2-1, 2-2, 2-4, 2-5, 2-16, 4-1, 4-5, 4-6NTP Server, 2-1, 2-3, 2-11, 4-1, 4-3Standard

Broadcast Client, 2-1, 2-6Unicast Client, 2-1

Time Synchronization, 3-1, 3-22, 3-23, 4-1,4-3, 4-5, 4-6

CSFSynchronization, MSP_TSET, 1-1, 1-3

EEthernet

HMI, 4-4, 4-5, 4-6Network Topology, Mixed

Type 1, 4-2Type 2, 4-4Type 3, 4-5Type 4, 4-6

NTP and NTP Server, 1-1, 1-3NTP Server, 1-1, 1-3

FFlywheel Operation, 3-1, 3-10, 3-11

GGlobal Time Source (GTS), 5-1, 5-3

Time Card, Connecting to, 3-1Tracking, 3-1, 3-10

HHelp, 1-4HMI, 4-1, 4-2

Network Topology, MixedType 1, 4-2Type 2, 4-4Type 3, 4-5Type 4, 4-6

IIRIG, 1-1, 5-10

KKSI Odetics tPRO-PC Time Card, 5-1, 5-11

LLow Resolution Operation, 3-1, 3-11

NNetwork Topology, Mixed

Type 1, 4-2Type 2, 4-4Type 3, 4-5Type 4, 4-6

NTPConfiguration, 2-1, 2-2, 2-4, 2-5, 2-16, 4-1, 4-5, 4-6

Screen Examples, 2-1, 2-5Utility, 2-1, 2-2, 2-4, 2-16

Diagnostics, 2-1, 2-15, 2-19, 2-21Data Display, 2-1, 2-22Monitoring, 2-1, 2-24, 2-25Starting, Closing Program, 2-1, 2-21

Event Viewer, 2-1, 2-15Monitoring, 2-1, 2-24, 2-25

2 •••• Index SPEEDTRONIC Turbine Control GEI-100513

Status Indicator, 2-1, 2-15, 2-19 � 2-21Icon Status, 2-1, 2-20Menu Commands, 2-1, 2-20

Synchronization, Ethernet, 1-1, 1-3Time Acquisition Modes, 2-1, 2-2

NTP ServerConfiguration, 2-1, 2-3, 2-11, 4-1, 4-3Diagnostics

Monitoring, 2-1, 2-25Hardware Interface, 2-1, 2-16Synchronization, Ethernet, 1-1, 1-3

SSerial Network

Synchronization, MSP_TSET, 1-1, 1-3Setting the IRQ, 5-1, 5-3, 5-12SPEEDTRONIC Turbine Control, 1-1, 1-4, 1-5Stagelink

Network Topology, MixedType 1, 4-2Type 2, 4-4Type 3, 4-5Type 4, 4-6

Synchronization, 1-1,1-3, 3-1, 3-22, 4-6Synchronization

CSF and Serial Network, MSP_TSET, 1-1,1-3

Ethernet, NTP and NTP Server, 1-1, 1-3EX2100 Controllers, 2-1, 2-17Mark VI Controllers, 2-1, 2-17Stagelink, 1-1, 1-3, 3-1, 3-22, 4-6

TTime Card

Bancomm bc620AT, 5-1, 5-2Bancomm bc627AT, 5-1, 5-2Initialization, 3-1, 3-8Installation, 1-1, 3-2, 3-22, 5-1KSI Odetics tPRO-PC, 5-1, 5-11

Time SynchronizationConfiguration, 3-1, 3-22, 4-1, 4-3, 4-5, 4-6Diagnostics and Monitoring, 3-1, 3-12Disable, 3-1, 3-12Enable, 3-1, 3-12Flywheel Operation, 3-1, 3-10, 3-11

GTS, 3-1, 3-10Log File, 3-1, 3-21Low Resolution Operation, 3-1, 3-11Operation, 3-1, 3-7Software, 3-1, 3-2, 3-4, 3-8, 3-11, 4-3, 4-5, 4-6Startup and Initialization, 3-1, 3-9Status, 3-1, 3-13, 3-17, 3-22Time Card, 3-1

Initialization, 3-1, 3-8Load Time, 3-1, 3-13

Timesync.dat, 3-1, 3-2, 3-4, 3-8, 3-11, 4-3, 4-5, 4-6Trace Information, 3-1, 3-20

Topologies, 4-1, 4-7tPRO-PC Time Card, 5-1, 5-11

UUnicast

Client, Standard Configuration Option, 2-1Server, 2-1, 2-11, 2-13, 4-3, 4-8

�*(�,QGXVWULDO�6\VWHPV

*HQHUDO�(OHFWULF�&RPSDQ\�� 5RDQRNH�%OYG�ZZZ�*(LQGXVWULDO�FRP 6DOHP��9$��86$