The "Initiated Outstation Set Clock" event is logged for a channel when a driver sets the clocks of all the outstations that are using that channel for communications.  The "Initiated Outstation Set Clock" event is logged:

  • Periodically, for example, once an hour, according to the interval and offset that is configured in the channel's scan parameters. The driver sets the outstation clocks periodically to correct any difference ('drift') between the master station clock and the outstation clocks.
  • When the master station's clock changes.  If the time on the server is changed, each driver will automatically update the clocks in all of the outstations with the new time in order to ensure that the master station and outstations are synchronized.
This functionality does not apply to PSTN channels and outstations and is only supported by certain drivers and protocols.

If your system is frequently logging "Initiated Outstation Set Clock" event messages, there is probably an issue with the PC clock.  Some PCs suffer from 'jitter' in their real-time clock which can make it appear as though the master station clock is repeatedly changing (causing the "Initiated Outstation Set Clock" message to be logged each time). 

A common cause of this issue is machines that utilize "Speed Step" technology.  If you can disable "Speed Step", this may resolve the issue.

Alternatively, you could increase the threshold at which ClearSCADA will respond to a change in clock.  This will then prevent an excessive number of "Initiated Outstation Set Clock" event messages being logged.  You can use the Server Configuration Tool to change the "Maximum Clock Jump" setting. 

For more information, see Detecting a Change to the Server's Clock in the Server Administration Guide in ClearSCADA Help.