Time Synchronization

Time syncing is needed to keep all the workstations at the same time and for accurate time based functions like timed recordings and branch events.

Time syncing can be done either within the DAD program or by external 3^rd party programs. 

Time syncing outside of DAD.

There are several time sync programs available on the Internet. The two we commonly use are Dimension 4 (D4) and Tardis.

D4 is available at: http://www.thinkman.com/dimension4/index.html

The Tardis Home Page can be found at: http://www.kaska.demon.co.uk

D4 is the "client" software and Tardis is the "timeserver" software. In this model, one workstation will receive the time sync setting its time. This workstation running Tardis will act as the timeserver for the network. The other workstation on the network will run Dimension 4 getting their time from the timeserver. 

For example:

A station could receive a GPI Closure from a Satellite provider setting the time of that workstation. That same workstation also runs Tardis. Tardis is configured to ‘look’ to it’s own IP Address. This will force Tardis to rebroadcast the time set by the closure from DAD across the network. The other workstations on the network then use D4. D4 is configured to ‘look’ to the IP Address of the workstation that is running Tardis.

Tardis

When the application Tardis is installed and run, it will automatically configured to use an Internet Server. Tardis can also be configured to use it’s own IP Address for reference. This is desirable for most stations. 

Users should ‘Clear All’ of the current timeservers set within the default setup of Tardis. Next select Add and add the proper information for the workstation’s IP Address. Simple Network Time Protocol (SNTP) is the most commonly used time protocol.

There are several other options available to the user if they desire. These are available from the Options button on the main screen. Here users can have Tardis start minimized and hide itself in the workstations system tray.

Once Tardis has been configured, you should consider placing a shortcut in that workstation’s STARTUP folder.

Dimension 4 (D4)

Dimension 4 can be configured with the SERVER and LOCATION of your workstation running Tardis. This is done through the ADD feature. This program is very configurable to fit your needs.

Users can quickly remove all timeservers by editing the C:\Program Files\D4\Server.dat file.

Select ADD and enter the proper information for the IP Address and Protocol of the workstation running the Tardis program.

Users should also set the Maximum correction time to two hours. This allows for DST time changes. Users can have D4 start and hide in the workstations system tray upon startup.  

Time syncing within DAD:

Time syncing within DAD can be handled by using satellite closures and proper configuration. If you are receiving a satellite closure at the same time each day then you could use this as a "reference" time. For example, if your satellite program provider sends a Legal ID pulse each hour at :59:50, you can sync to that pulse. You should keep in mind that some providers use the same closure for multiple reasons. (Legal ID and other liners)  You should also review the times you will actually be "listening" for that closure from the provider. Will you only be on satellite during evening hours or will you change from provider to provider?  You should try to use a source that will be consistent throughout the day.

After determining, wiring and testing the GPI you wish to use, add the following line to that workstations' GPI file.  (SETUP > README > GPI)

SYNC 5950

This DCL will sync the workstations time to the time of :59:50 for the current hour when it receives the closure. If you are using this closure for other relays in the hour you should add a limit to the time before and after 59:50 in which it may sync. This is done by adding MAX 60.

SYNC 5950 MAX 60

This will sync the workstations time to the time of :59:50 of the current hour when it receives the closure only if the time of the workstation is within 60 seconds of :59:50. It will not perform the sync if it is outside of the time limit.

Time syncing with Novell NetWare 

If a Novell NetWare server is being used, edit the workstations' configuration file. (SETUP > README > CFI) Near the bottom of the file find the line: TIMESYNC = OFF LOCAL. For the workstation receiving the closure, you will add the following:

TIMESYNC = 337 SERVER

This will allow this workstation to set the time of the server every 5.61 hours. You should not set the time (337) to less then one hour and on even values like 60 or 120 minutes.

You will also need to make this workstation a Console Operator on the server. This allows the workstation the proper "rights" to set the server's time. To do this, login to the server as ADMIN. Find the F:\PUBLIC folder and run the NWADMIN4x.exe program.

Double (or right) Click on the server icon in your tree: to view the properties. On the right side of the details screen, select the OPERATOR button. Press ADD and select the desired user (workstation) from the list. This will add that user as a console operator. Exit and login back into the server normally.

Finally, you will need to configure the remaining workstations configuration file. (SETUP > README > CFG) The other workstations will sync to the server. Changing the TIMESYNC line to something like the following does this.

TIMESYNC = 20 LOCAL

This will sync the workstations' local time every twenty minutes.

The workstation receiving the time pulse will now set its time and the servers' time. The rest of the workstations will in turn sync themselves to the servers' time. 

Peer to Peer 

If you are using a peer-to-peer configuration, you can use the DCL: SEND COMMAND to send a workstation a sync command.

SEND COMMAND PROD 'SYNC 5950'

You can place this line in the GPI file along with the sync command.

One can also utilize the Tardis and D4 applications.