Ultimate Veeder-Root TLS Alarm Codes: ATG Troubleshooting Guide

EPA fines for underground storage tank violations can hit $37,500 per day. When a Veeder-Root TLS console starts flashing an alarm at 2 a.m., the clock is already ticking.

Most fuel site operators can recognize an alarm on the console display. Fewer can tell whether that alarm demands an immediate pump shutdown or just a note in the logbook. Existing references from Veeder-Root's own blog list alarm names without troubleshooting steps. ManualsLib serves up raw tables with zero interpretation. Gas Station Compliance Hub covers only seven alarm types.

This guide fills the gap. Every Veeder-Root TLS alarm code below includes four data points: the exact console display string, the cause, the urgency level, and the first-response action. It also covers something no other resource addresses: how ATG alarms propagate through BIR, DIM, and TDIM interfaces to reach the forecourt controller and POS.

What Are ATG Alarm Categories and Why Do They Matter?

Veeder-Root TLS alarm codes fall into three severity tiers: alarms requiring immediate shutdown, warnings with a 24-hour investigation window, and system faults pointing to equipment problems.

Each tier triggers a different response. The first bucket, alarms, means "stop what you're doing and deal with this now." Warnings give a 24-hour window to investigate. System faults point to equipment problems rather than tank problems.

Alarms are the red-alert tier. They mean something is actively wrong: a potential leak, an overfill event, or a sensor detecting fuel in a space where fuel shouldn't be. Overfill, Sudden Loss, Gross Test Fail, and Sensor Fuel all fall into this tier. These demand immediate operator response, which often means shutting down dispensing from the affected tank and documenting the event per 40 CFR Part 280.

Warnings flag conditions trending toward a threshold. High Product, Low Liquid, Probe Out, and High Water are typical examples. Operators have a response window, but the EPA still requires documented investigation within 24 hours of the event.

System faults indicate equipment malfunction rather than a tank condition. Communication failures, sensor opens, and mag sensor errors fall here. A system fault doesn't mean fuel is going anywhere it shouldn't. But it does mean the ATG has a blind spot, and until someone fixes that blind spot, the site is running with incomplete monitoring coverage.

Getting the tier right determines everything else. Can dispensing continue? Does the state need a call? Is this a "get someone here today" situation, or can it wait until next Tuesday? The answer depends entirely on which category that console display string falls into.

What Are the TLS-350 Alarm Codes and How Do You Respond to Each One?

TLS-350 alarms fall into four groups: PLLD leak detection, tank level, sensor, and line equipment. Each group carries a different urgency profile and demands a specific first response.

PLLD (Leak Detection) Alarms

A Gross Test Fail is one of the most serious Veeder-Root TLS alarm codes an operator can encounter. It means the console ran its periodic leak detection test and found product loss exceeding the allowable threshold (typically 0.2 gallons per hour for a gross test). Do not resume dispensing until a certified technician confirms tank integrity.

PLLD Shutdown means the console has effectively given up on periodic testing because conditions keep preventing valid results. This is not the same as a confirmed leak, but it does mean leak detection coverage is offline. Regulatory agencies treat an offline PLLD system as a compliance gap.

Tank Level Alarms

Sudden Loss is the alarm that keeps operators up at night. It triggers when the TLS-350 detects a product level drop faster than normal dispensing activity explains. However, temperature plays a role here. A delivery of cold fuel into a warm tank causes contraction that can mimic a sudden loss. Wait 30 to 60 minutes after a delivery, then recheck the level before escalating.

Sensor and Communication Alarms

Sensor Fuel is a high-stakes alarm. It means a sensor physically detected liquid fuel where fuel should not be (an interstitial space or containment sump). Even if the fuel turns out to be condensation mixed with residual vapor, treat the alarm as real until visual inspection confirms otherwise. For more on leak detection systems and line leak testing, Allied's dedicated leak detection guide covers the full diagnostic process.

What TLS-450PLUS Alarm Codes Differ from the TLS-350?

The TLS-450PLUS generates alarm codes for CSLD leak detection, temperature sensors, vapor monitoring, and TCP/IP communication that don't exist on TLS-350 consoles.

Here's what catches people off guard: if the site just upgraded from a TLS-350, the operator is going to see Veeder-Root TLS alarm codes on the display that weren't there before. Here's what each one means:

The CSLD codes represent a significant upgrade over the TLS-350's periodic testing approach. The TLS-350 waits for a quiet window (usually overnight when nobody's dispensing) to run its periodic leak test. The TLS-450PLUS doesn't wait. It's crunching numbers on product levels all day, every day, using statistical analysis to spot trends. That means it catches slow leaks faster, but it also means operators see CSLD-specific alarm codes that older consoles never generated.

BIR COMM ERROR deserves special attention. This alarm means the TLS-450PLUS has lost its connection to the forecourt controller. While tank monitoring continues locally on the console, alarm data is no longer forwarding to the POS. Operators relying on POS-level alarm notifications will have a blind spot until the BIR connection is restored.

How Do ATG Alarms Reach the Forecourt Controller and POS?

ATG alarms propagate from the TLS console to the forecourt controller through BIR protocol and DIM hardware modules, then forward to the POS for centralized monitoring.

This signal chain is something no other Veeder-Root TLS alarm codes reference explains. Here is how the path works, step by step:

The BIR Protocol

Veeder-Root's BIR (Bulletin Information Report) protocol is the standard communication method between TLS consoles and forecourt controllers. BIR carries three categories of data back and forth: tank inventory levels, alarm status, and delivery reports. It works on a polling cycle. The forecourt controller asks the TLS console for an update, the console responds, and the cycle repeats on a configurable interval. Want the full picture? Allied published a separate ATG forecourt controller integration guide that covers BIR message formats, polling interval settings, and every step of getting the TLS console and controller to communicate.

DIM Hardware Modules

So how does the TLS console physically talk to the forecourt controller? Through a DIM module. There are three options, and the choice usually comes down to how far apart the two boxes are and whether Ethernet is available:

• EDIM (Ethernet DIM): Connects the TLS console's serial output to an Ethernet network, allowing TCP/IP-based communication with the forecourt controller.
• CDIM (COM DIM): A straight serial-to-serial link. Works well when the TLS console and forecourt controller sit in the same equipment room or within a short cable run.
• LVDIM (Low Voltage DIM): Built for the long haul. When the TLS console and controller are separated by hundreds or thousands of feet of cable, the LVDIM handles voltage drop across runs up to 4,000 feet.

TDIM for TCP/IP Installations

For TLS-450PLUS sites, the TDIM (TCP/IP DIM) enables native Ethernet alarm forwarding without serial-to-Ethernet conversion. That takes the CDIM and LVDIM completely out of the picture, which means fewer boxes in the equipment room, less wiring to run, and fewer things that can break.

The Complete Signal Chain

Here's the full path, end to end. A tank condition triggers the TLS console to generate an alarm. The console packages that alarm into a BIR message. A DIM or TDIM module grabs the message and hauls it over to the forecourt controller. Once the NeXGen PRIME or AEGIS gets it, the alarm pops up on the POS screen where it's actually visible to staff.

Without this integration, operators must physically walk to the TLS console (often located in a back room or equipment closet) to check for active alarms. With a properly configured DIM or TDIM interface, every alarm appears at the POS register the moment it fires. For sites with multiple tanks and high transaction volume, this is the difference between catching an alarm in seconds and missing it for hours.

What Causes False ATG Alarms and How Do You Fix Them?

False ATG alarms usually trace back to four causes: float calibration drift, aging sensors, seasonal water table shifts, or temperature changes after fuel delivery.

A good ASP can recalibrate and fix most of them on-site, but there's a point where the component is simply worn out and needs to be swapped.

Float Calibration Drift

Over months and years, fuel residue and contaminants coat the surface of magnetostrictive probe floats. That gunk changes the float's buoyancy just enough to shift the product level reading. The result? Phantom High Product or Low Liquid Veeder-Root TLS alarm codes that fire with no actual level change in the tank.

An authorized service provider can recalibrate the float on-site, and that fixes it most of the time. But here's the rule of thumb: if the drift comes back within six months of recalibration, the float is done. It's past its service life, and throwing another recalibration at it is throwing money away. Time for a new one.

Sensor Aging

Interstitial and sump sensors don't last forever. After 10 to 15 years in the ground, the sensor's resistance characteristics drift with age. That's when operators start getting intermittent Sensor Open or Sensor Fuel alarms with nothing actually leaking. If a sensor is past the 10-year mark and keeps triggering false alarms, every service call to "investigate" costs more than just replacing the sensor would.

Water Table Fluctuations

Sites in coastal areas or regions with high seasonal groundwater see High Water alarms triggered by external water table changes rather than actual water intrusion. What's actually happening: the water detection float picks up pressure changes from groundwater pushing against the tank walls from outside. The tank could be perfectly sealed, and the float still registers a shift.

Keeping a log of when these alarms fire makes the pattern obvious after a year or two. If the High Water pattern lines up with rainy seasons and clears on its own every time, that's a strong sign the tank itself is watertight. It's the water table pushing on the outside, not water getting inside.

Temperature-Induced False Positives

Picture this: a tanker truck sits in direct sun for 200 miles, then drops 8,000 gallons of warm fuel into a cool underground tank. As that fuel cools down to ground temperature, it contracts. The TLS console sees the level dropping and does exactly what it's supposed to do: it fires a Sudden Loss alarm. Nothing is leaking. The fuel is just shrinking as it cools.

The practical response: wait 30 to 60 minutes after a delivery before treating a Sudden Loss alarm as confirmed. If the level stabilizes after temperature equalization, the alarm was a false positive.

What Are the Regulatory Requirements After an ATG Alarm?

The federal rules are straightforward, even if following them isn't always fun. 40 CFR Part 280 says: investigate within 24 hours of any alarm event, and keep the paperwork for at least 3 years.

The 24-Hour Investigation Window

The EPA requires documented investigation within 24 hours of any alarm event. "Investigation" does not necessarily mean the problem is fixed within 24 hours. It means the operator has identified the alarm, determined the probable cause, and documented the findings. A Probe Out alarm investigated and logged as "probe cable reconnected, alarm cleared" satisfies the requirement. A Sudden Loss alarm investigated and escalated to an ASP for tank tightness testing also satisfies it.

Documentation Retention

All alarm events, investigation records, and corrective actions must be kept on file for at least 3 years under federal rules. Plenty of state programs push that to 5 years or even longer. Best practice: organize records by tank number and date so they're easy to pull up when an inspector walks in. Fumbling through a filing cabinet during an audit isn't a good look.

State-Level Variations

This is where things get complicated, because every state has its own spin on the federal rules. Three states illustrate just how different the requirements can be:

• California (SWRCB): The toughest in the country. Electronic monitoring is mandatory, monthly alarm event reports are due to the state, and sites can't self-monitor. A certified UST service provider has to be involved.
• Texas (TCEQ): Folds alarm documentation into the facility's annual compliance self-certification. Operators have to show that every single alarm got investigated and closed out.
• Florida (DEP): Wants an annual ATG operability certification. That means proving the monitoring system works and that all alarms from the past year have been addressed.

Every state agency publishes its own UST compliance requirements online. The bottom line: don't assume the federal 3-year minimum is the whole picture. Pull up the state environmental agency's website and check the actual reporting and documentation deadlines for that jurisdiction.

What Parts Are Commonly Needed After ATG Alarms?

The most commonly replaced ATG components after alarm events are magnetostrictive probes, water detection floats, interstitial sensors, sump sensors, and line leak detectors.

Figuring out what the alarm means is only half the job. The other half is getting the right replacement part on-site before the next shift starts. Here's a quick-reference breakdown showing which Veeder-Root TLS alarm codes point to which component:

Allied's Parts Superstore stocks ATG-adjacent components from Veeder-Root, Red Jacket, Franklin Fueling Systems, and other major manufacturers across 57,455+ SKUs. For hard-to-find or legacy ATG parts not listed in the online catalog, operators can submit a request through Allied's part request form and a specialist will source the component.

Frequently Asked Questions About Veeder-Root TLS Alarm Codes