Issue
3:15am Time Sync error in AMT
Product Line
TAC INET
Environment
- I/NET site with DCU Time Sync enabled
- Daylight Savings Time
Cause
- Outdated SAV file
- No DST observed
- Enabled DCU Time Sync from Host PC
Resolution
- Make sure versions of Bin Files are up to date with current revision of I/NET across all controllers. For how to do this read How to upgrade bin and SAV files in I/NET controllers.
- Make sure SAV files are backed up and current. For how to do this read How to upgrade bin and SAV files in I/NET controllers.
As the host workstation synchronizes the daylight savings time settings in a controller, it will also check for the existence of a corresponding SAV file. If a SAV file for the controller is found, the host workstation processes it as follows SAV file is current If the controller's SAV file is current, the host automatically updates it with the daylight savings settings from this editor. This ensures that if you later restore the controller using this SAV file, the correct daylight savings time settings will be downloaded.
SAV file is old If the controller's SAV file is out-of-date, the host does not change it. In this case, you can manually update the controller's SAV file or use the Automatic DCU Save function in order to create an up-to-date SAV file for the controller. Refer to Station Save and Restore for more information. - Beginning with I/NET revision 2.41, I/NET allows the DCU Time Sync and no observance of DST.
- Work around is to remove DCU Time Sync if your time zone does not observe DST.