User manual

Masterclock www.masterclock.com

Clock does not respond to configuration changes and/or status display is intermittent

Device was found using WinDiscovery, but the status display is intermittent or not updating

and/or the clock does not appear to be responding to configuration changes under the current

WinDiscovery session.

Clock(s) previously found during a recent session of WinDiscovery do not show up during the

current session.

The clock status or settings displayed under WinDiscovery show garbled characters.

Possible reasons and solutions:

1. The WinDiscovery application has been open for too long and the clock configuration(s)

have changed. For example, this can occur if the DHCP server has issued a new/ refreshed

address. Close the WinDiscovery application and restart.

2. The discovery process was not complete before selecting began. After clicking [Discover]

wait until the discovery status indicates 100% completion.

3. Verify that the physical network cables and equipment are configured for UDP.

4. Verify that you are currently the only user accessing the device via WinDiscovery.

5. The network may currently be experiencing heavy traffic which is reducing bandwidth

and/or causing collisions with the UDP packets between the device(s) and WinDiscovery.

Since delivery of UDP messages are not guaranteed, this can cause WinDiscovery to not

receive the latest configuration or status packets and thus show outdated or garbled

information.

6. In some cases, the device may not be discovered and displayed in the WinDiscovery device

tree. In others, previously discovered devices may no longer be accessible or responding.

Click [Discover] again and wait until the discovery process to complete. Close the current

WinDiscovery session and restart the WinDiscovery application. Take steps to increase the

bandwidth and reduce network traffic.

If these continue to be ongoing problems, remove the device to an isolated LAN.

Clock periodically resets itself

Clock appears in red text under

WinDiscovery device tree

Clock is being assigned an IP address of 169.254.xxx.xxx

Clock is showing an “Error” field under the status window in WinDiscovery

Possible reasons and solutions:

1. Incorrect network configuration may be causing the device to receive a fallback IP address

and or perform soft restarts. Verify that the IP address configured for the device is correct.

If you manually enter (or DHCP assigns) an IP address that already exists on the network,

this will create an IP address conflict. The device will reset its address (fallback) to one

within the link-local address space. Determine the cause of fallback IP address and resolve

issue. View the error status field under the status window to help determine the cause of

why the device received a “169.254.xxx.xxx”. Near the bottom of the status window the

error will be displayed. (If there is no error the text box will not be displayed.)

2. If static IP addressing is being used the original conflicting static IP address can be

restored. Perform a soft restart of the network device using WinDiscovery prior to

changing any other configuration parameters.