Veeder-Root · TLS-350
Maintenance Tracker
A scheduled maintenance interval has elapsed. Action: perform the due maintenance and reset the tracker.
Field reference for fuel system and underground storage tank technicians. 48 entries, taken from the DropTubeBuilder app.
Reference notes from DropTubeBuilder, the offline field tool for fuel system technicians who cut overfill drop tubes, build tank charts and chase dispenser faults. It works with no cell signal, because the sites do not have any.
Get DropTubeBuilder on the App StoreConfiguration data was lost or changed (often after a battery/power issue). Action: review and re-enter System/In-Tank/Sensor setup; print a setup report and confirm against records.
Integrated printer is out of paper or the door is open. Action: reload paper roll, close door, clear the warning.
Printer mechanism fault or paper jam. Action: clear jam, reseat paper, cycle power to the console if it persists.
Console backup battery is low; setup/data may not survive a power loss. Action: schedule battery replacement (board-mounted lithium).
Console lost AC power and is running on backup or has shut down. Action: check breaker/UPS feeding the console; confirm dedicated circuit is on.
Non-volatile memory (setup storage) failed its self-test. Action: cycle power; if it returns, the CPU/memory board needs service.
Working memory failed its self-test. Action: cycle power; persistent fault means CPU board replacement.
A software/feature module mismatch or expired feature was detected. Action: verify installed features/licensing and firmware version.
Console lost communication with a device (probe, sensor, module, or remote display). Action: check the device wiring, module seating, and address/setup.
Scheduled modem/network report-out to the host failed. Action: verify phone line/Ethernet, host number/IP, and comm settings.
A scheduled maintenance interval has elapsed. Action: perform the due maintenance and reset the tracker.
Product level dropped below the delivery-needed limit. Action: schedule a fuel delivery; informational.
Product volume is below the configured low limit. Action: order fuel; verify limit is set correctly for the site.
Product volume is above the high limit (approaching capacity). Action: stop/observe deliveries; verify the high limit and tank chart.
Tank exceeded the overfill limit (typically 90%) during/after a delivery. Action: stop delivery immediately; investigate delivery practices and overfill setpoint.
Level reached the maximum (≈95%) limit. Action: cease filling; confirm overfill-prevention valve and setpoints.
Water in the tank exceeds the high-water limit. Action: pump out water; inspect fill cap, spill bucket, and gaskets for intrusion; check for phase separation.
Water has reached the warning limit. Action: monitor; schedule water removal and find the source.
Product temperature is below the low limit (waxing/gel risk for diesel). Action: informational; monitor in cold weather.
Probe is reporting an implausible level (floats stuck or product/water floats crossed). Action: pull and inspect the probe and floats for fouling or sticking.
Console is not seeing the probe. Action: check probe wiring/connections at the probe and module; verify probe address and canister.
Static (gross 3.0 gph) leak test failed. Action: re-run when quiet/idle; if it fails again, investigate the tank for leaks.
Periodic (0.2 gph) leak test failed. Action: ensure adequate idle time and product level; investigate if it repeats.
Annual (0.1 gph) precision test failed. Action: review test conditions; arrange tightness testing/leak investigation.
No passing periodic leak test within the required window. Action: ensure the tank gets quiet idle time to complete a test.
No passing annual (0.1 gph) test within the window. Action: schedule conditions for a valid test.
Statistical leak detection declared a leak. Action: treat as a release indication; investigate per regulations.
An unexpected sudden drop in volume (not a sale/delivery) was detected. Action: check for theft, siphoning, or a leak.
Volume decreased without an authorized dispense. Action: investigate unauthorized removal.
Water exceeds limit but the water float is missing/stuck. Action: inspect probe water float assembly.
A liquid sensor (sump/interstitial/dispenser pan) detected hydrocarbons. Action: locate and stop the leak; remove product from the containment.
A liquid sensor detected water in containment. Action: remove water; find intrusion source (covers, seals, groundwater).
Liquid in containment reached the upper sensor threshold. Action: pump out and identify whether fuel or water; inspect for leaks.
Liquid in an interstitial/brine sensor fell below limit (possible breach of double wall). Action: inspect interstitial integrity and brine level.
Liquid detected at the warning level. Action: investigate containment; monitor for escalation to alarm.
A discriminating sensor lost its expected water reference. Action: inspect the sensor and its position.
Console is not seeing the sensor (open/short or disconnected). Action: check sensor wiring and module; verify the sensor type/setup.
Sensor wiring is shorted. Action: inspect for pinched/wet wiring and connector corrosion; megger if needed.
Sensor configuration was lost/changed. Action: re-enter sensor type and thresholds.
Pressurized line leak detector failed the gross (3.0 gph) test. Action: line is disabled; inspect piping/fittings before returning to service.
Line failed the monthly (0.2 gph) test. Action: investigate piping integrity; verify functional element/leak detector.
Line failed the annual (0.1 gph) test. Action: schedule line tightness testing/repair.
PLLD/WPLLD detected a hardware/handling fault (e.g., relay, pressure sensor). Action: inspect line leak module, transducer, and STP relay wiring.
The line pressure/turbine sensor reading is out of range. Action: check the pressure transducer and its wiring at the STP.
Vapor/ullage pressure sensor not communicating. Action: check the pressure sensor and its module/wiring.
Ullage pressure is outside the normal range (Stage II/ORVR/PV monitoring). Action: inspect P/V vents and vapor lines for blockage or leaks.
A vapor-well sensor detected liquid hydrocarbons. Action: investigate vapor recovery piping and well.
Membrane/vapor processor reported a fault or degraded performance. Action: review processor diagnostics and maintenance.
Reference notes from DropTubeBuilder, the offline field tool for fuel system technicians who cut overfill drop tubes, build tank charts and chase dispenser faults. It works with no cell signal, because the sites do not have any.
Get DropTubeBuilder on the App StoreThese notes are a field aid, not a substitute for the governing codes, the stamped drawings, the authority having jurisdiction, or manufacturer manuals. Verify against the current documentation for your installed equipment.