Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Understanding host managed and auto Daylight Savings Time (DST) configuration for hourly gas history upload

Understanding host managed and auto Daylight Savings Time (DST) configuration for hourly gas history upload

  • Last UpdatedApr 24, 2025
  • 1 minute read

Understanding host managed and auto Daylight Savings Time (DST) configuration for hourly gas history upload

An auto Daylight Savings Time (DST) Remote Terminal Unit (RTU) automatically changes its clock from 1:59:59 am to 3:00:00 am in the Spring DST transition, and 1:59:59 am to 1:00:00 am the Fall DST transition. In the fall, the hourly gas Historical records are expected to have two records with the same local time stamps at 1:00 am.

A host-managed DST RTU does not change its clock until it is forced to time sync by the AVEVA Enterprise SCADA host. In the fall, the hourly gas Historical records are expected to have two records with the same local time stamp at any hour of the clock as a result of the forced time sync.

A DST enabled AVEVA Enterprise SCADA protocol driver is capable of logging each gas record with their corresponding Coordinated Universal Time (UTC). As part of its logic, the protocol driver requires an Auto Lock Out / Resume of Hourly History Upload to allow the two duplicated local time records be uploaded in a single session.