What is ATG Configuration Auto-Sync?

ATG Configuration Auto-Sync is a new facility-level feature currently in beta-testing that automatically pulls configuration data from a site's ATG (Automatic Tank Gauge) and keeps it in sync with Titan Cloud Edge. 

When enabled, a daily process runs at 9:15 AM Eastern to retrieve current values from the ATG. This timing applies to both the Baseline sync and the Fields sync.

The feature has two independent toggles:

1. Automatically Update Baseline

Enables automatic synchronization of baseline tank configuration values from the ATG. This monitors and updates all fields available from configuration management — a broader set than the individual fields listed under “Automatically Update Fields” below. Baseline updates flow into the facility's Configuration Management page.

2. Automatically Update Fields

Enables automatic synchronization of specific tank, probe, piping, line, and sensor data from the ATG into the corresponding Edge UI fields. When this is turned on, each field below can be individually toggled to control whether it's kept in sync.

Fields Available for Automatic Update

Enable Tanks Sync

A separate Enable Tanks Sync section governs whether Titan Cloud Edge automatically adjusts which tanks exist / are active based on what it sees from the ATG:

• Detect new tanks from ATG: Automatically adds new tanks in Edge when the ATG reports a tank that doesn't exist yet.
• Detect tanks turned off in ATG: Automatically flags tanks that have been disabled. 

New tanks can populate automatically as long as “Detect new tanks from ATG” and the relevant field-sync settings are enabled together.

Known Differences Between Veeder-Root and Franklin

Veeder-Root (TLS-350) and Franklin (550 EVO) expose configuration data differently, so some fields don't map one-to-one:

• Tank Overfill Limit: 
  • Veeder-Root has a dedicated OverfillLimit register (62300) 
  • Franklin's equivalent field, HIGH_LEVEL_LIMIT, is often not present on the device, so Overfill Limit is frequently missing for Franklin sites. 
    • This is a device/data availability limitation, not a bug.
• Tank Tilt: 
  • Veeder-Root provides a direct TankTilt register. 
  • Franklin has no separate tilt field; instead, Franklin's PRODUCT_OFFSET is documented by Franklin as tank tilt compensation. 
  • Titan Cloud Edge does not currently map PRODUCT_OFFSET → Tank Tilt.
• Probe Offset: 
  • Veeder-Root provides a direct ProbeOffset register. 
  • Franklin has no single equivalent. It splits this into separate PRODUCT_OFFSET and WATER_OFFSET values, so there's no clean one-field mapping today.