Workflow
60-Second Triage
Do this first
- Active vs. history (Is it happening now?)
- Identify object: Tank # / Line # / Sensor ID / Input
- Capture evidence: alarm screen + detail screen
- Classify: Containment/Sensor • Line/PLLD • Tank • System/Setup
- Go physical: verify in the field (don’t diagnose from the screen only)
Minimum documentation
- Site + date/time
- Tank/Line/Sensor ID (exact)
- What you found (facts)
- What you did (actions)
- Final status (normal? still alarm?)
- Before/after photos (screen + physical location)
Quick Reference
Common Alarms (Meaning + First Moves)
These are the alarms you meet most often, with the first moves for each. For a console alarm that is not on this page, the full Veeder Root reference covering the TLS-300, TLS-350, TLS-450, TLS-450 PLUS and TLS4 is at thrasherapps.com/droptubebuilder/reference, with the likely cause and the checks to make in order for each alarm. It is kept current there.
Keep your response consistent: confirm the device, go physical, document evidence, and recheck status.
Fuel Alarm
Meaning: Fuel/liquid detected in a space it’s not allowed (sump, dispenser pan, interstice, etc.).
- Use sensor ID + location label + site map to go to the correct containment area.
- Verify: active leak vs spill vs intrusion vs residual product.
- Clean/contain per Petro Plus procedure and check likely entry points (fittings, boots, conduit, lids, seals).
- Document: what was present, suspected cause, and what was corrected.
Safety: If you suspect an active leak, treat it as a hazard. Make safe, escalate, document.
Low Pressure Alarm
Meaning: Dispense pressure is below expected during dispensing (often line/hydraulics/power related).
- Determine scope: one dispenser/position, one line, or multiple.
- Check obvious causes: STP performance/power, filters, line restrictions, leaks, air, dispenser symptoms.
- Pull PLLD/line diagnostics history for that line before repeating tests.
- Document observed symptoms at the dispenser (slow flow, no flow, cycling, etc.).
Gross Line Fail (3.0) / Line Leak Shutdown
Meaning: Gross leak test category failure (3.0) or related shutdown condition for a line.
- Pull PLLD diagnostics for the affected line (recent pass/fail timestamps).
- Confirm the line and affected dispensers match the site map.
- Verify physical conditions: obvious leaks, STP issues, dispenser symptoms.
- Document clearly and follow company escalation if shutdown/critical.
0.2 / 0.1 Test Fail (Periodic / Annual)
Meaning: Precision line test category fail (0.2 periodic / 0.1 annual).
- Pull 0.2/0.1 diagnostics history first; confirm which line is failing and when.
- Consider traffic reality: precision tests need stable conditions; repeated interruptions create confusion.
- Verify physically: leaks, seepage, check valves, fittings, dispenser symptoms.
- Document: what the console reported + what you verified onsite.
Sensor Out Alarm
Meaning: Sensor not reporting correctly (disconnected, damaged, wiring issue, or setup mismatch).
- Confirm the sensor exists at that location (site map) and is the correct type for that spot.
- Inspect: wiring/conduit, water intrusion, physical damage, loose connections.
- Document before touching anything; fix physical issues if safe/authorized.
Setup Data Warning
Meaning: Configuration/setup issue or mismatch (device/tank/line/sensor setup integrity).
- Capture screenshots showing exactly what it references.
- Verify console labels match the physical site map (wrong mapping causes bad troubleshooting).
- Do not change programming unless authorized; document and escalate with evidence.
High Water Alarm (Tank Water)
Meaning: Water in the tank has exceeded the high-water limit setting.
- Screenshot water/tank status screens and note tank number.
- Verify the correct tank/probe association (mapping errors happen).
- Follow Petro Plus tank water procedure (removal/containment/escalation) and document before/after.
Important: Treat tank water alarms as serious. Document clearly for the office and the customer.
Field Skill
Locate the Correct Sensor (Fast Method)
Console → Field (always)
- From the alarm, identify Sensor ID and any location label.
- Use the site map to walk directly to that sump/pan/spill bucket/interstice.
- Verify physically: liquid present, water intrusion, damage, sensor placement, float condition.
- Correct the issue per procedure; avoid “random changes.”
- Recheck sensor status/alarm on the console and capture the “after” screen.
Best practices
- If the location label is wrong, note it and keep the call focused on the actual problem.
- Take a wide photo (to prove location) and a close-up (to prove condition).
- When recurring alarms happen at the same spot, treat it as a pattern and document the likely root cause.
Tip: A clean site map + consistent naming reduces bad troubleshooting more than any “advanced” console work.
Diagnostics
PLLD / Line Tests (3.0 / 0.2 / 0.1)
Field rule: pull diagnostics/history first, then decide if you should run tests or inspect hardware.
PLLD workflow (quick)
- Identify the line number referenced by the alarm.
- Check PLLD status/diagnostics for that line (recent pass/fail + timestamps).
- Confirm conditions (dispensing/traffic can interfere with clean test completion).
- Inspect physically based on the symptom (leak, restriction, power/STP, dispenser behavior).
- Document and recheck status after any change.
TLS-450PLUS (touchscreen) — where to look
- Menu → Diagnostics → PLLD → 0.2 GPH TESTS
- Menu → Diagnostics → PLLD → 3.0 GPH TESTS
Best practice: Screenshot the diagnostics page for the affected line (it’s the fastest way to explain what happened).
TLS-350 (keypad) — common diagnostic steps
- Press MODE for DIAG MODE
- FUNCTION to PRESSURE LINE LEAK DIAG
- STEP to the screen you need (0.2 / 0.1 / 3.0)
- Press PRINT (if available)
What each test means (one line each)
- 3.0 = gross leak category (big problem / high risk)
- 0.2 = periodic precision category
- 0.1 = annual precision category
Best Practice
Site Mapping (Tanks, Lines, Sensors)
Goal: any tech can arrive and find the right tank/line/sensor without guessing.
What every site map must include
- Tanks: Tank #, product, probe type, notes (water history, known issues)
- Lines: Line # to dispenser group (rough mapping is fine at first)
- Sensors: Sensor ID + physical location name (STP sump, dispenser pan, spill bucket, interstice)
- Emergency stops: locations + what they affect
- Photos: 1–2 wide shots + inside each sump/pan you service
Mapping method (field)
- Start with tank numbers and probe locations (confirm each physically where possible).
- List every sensor by console ID; walk and confirm each physical location.
- Name locations consistently (example: “Disp 3 Pan”, “STP Sump”, “Tank 2 Interstice”).
- Update the map immediately when equipment is moved/replaced.
Dispensing Issue
Slow Flow (Manual Leak Detector) — Field Troubleshooting
Slow flow is commonly triggered when a manual leak detector senses a pressure drop and restricts flow to alert the site that there is a problem.
Quick workflow
- Determine scope: one fueling point vs all fueling points.
- Install a pressure gauge on the line at a shear valve.
- Verify running pressure, seating pressure, and hold time.
- Based on scope + readings, troubleshoot dispenser-side vs pump/line-side causes.
- Document readings and final outcome (before/after).
Pressure check (gauge at shear valve)
- Running pressure: should be above 25 psi.
- Seating pressure: should settle above 20 psi.
- Hold test: should hold that seating pressure for more than 30 minutes.
Best practice: Write the numbers down (running, seating, and time held). Photos of the gauge help reduce disputes later.
If slow flow affects ONE fueling point
Most likely: dispenser-side restriction or component issue.
- Clogged filter
- Bad meter
- Bad proportional valve
Best practice: Don’t jump to STP parts if only one position is affected.
If slow flow affects ALL fueling points
Possible causes: line-side issue or pump-side pressure loss.
- Actual leak (customer may need a line leak test performed)
- Internal pressure loss in pump head (commonly a bad functional element on a Red Jacket STP)
- Bad check valve
- Bad packer o-rings
- Bad motor or capacitor
Safety: If you suspect an actual leak, treat it as a hazard. Make safe and follow Petro Plus escalation/testing procedure.
Closeout (required documentation)
- Which dispenser(s) / fueling points were affected
- Where the gauge was installed (which shear valve)
- Running PSI, seating PSI, and time held
- What was repaired/replaced
- Final result (normal flow restored? still slow flow?)
Franklin / INCON
EVO™ 550 / 5000 (TS-550/5000 evo) Alarms
Franklin Fueling's EVO consoles group alarms by device: system/modules, tank, sensor, line leak (LS500), and TPI (the Turbine Pump Interface that reports STP-controller faults). Source: TS-550/5000 evo Operator's Guide, FFS doc 000-2171.
Working an EVO alarm
- Read the alarm banner — EVO alarms are plain-English names tied to a device (Tank, Sensor, Line, TPI, module slot).
- Print or view Alarm History — patterns matter more than single events.
- If the site has TPI — the console mirrors STP-controller faults (under/over voltage, pump faults). Check the Smart Controller display too; the same fault shows both places.
- Verify before you clear — an alarm that matches reality (real high water, real low product) is information, not a nuisance.
Common in-tank & line alarms (from the operator's guide)
| Alarm | Meaning | First actions |
|---|---|---|
| High product level | Product exceeded the High limit — possible near-overfill. | Get an accurate stick/level; if it doesn't match the console, verify probe programming. |
| High water level | Water exceeded the High limit. | Verify the programmed level; if water is truly high, follow site procedure and remove water. |
| Low low product volume | Tank (or manifold) near empty. | Verify volume vs. programming; schedule delivery. |
| Tank Delivery Detected | A delivery was detected. | Only a concern if there was no delivery at that date/time. |
| Tank Theft Detected | Product left the tank in Sentinel Mode beyond the theft limit. | Verify the theft limit and get an accurate level vs. inventory. |
| Gross Leak Detected (Line) | Line leak greater than 3 GPH detected. | Inspect all sumps for product immediately; see the LS500 guide (FFS 000-2145). |
| Marginal Pass of Gross Leak Test | Last gross test passed just under the 3 GPH threshold. | Check sumps for any sign of leaks and run additional tests. |
| Pump Communication Fail (TPI) | TPI lost comms with the STP controller. | Check wiring and confirm the Smart Controller has power. |
| Under Voltage (TPI) | STP controller reporting supply under 200 VAC. | Meter the controller supply; correct the feed. |
Full library: the complete EVO alarm list (97 alarms with recommended actions — modules, relays, sensors, LLD, and TPI) is searchable in the
DropTubeBuilder app under Dispenser Error Codes → Franklin / INCON.
Standard
Closeout (Before You Leave)
- Recheck the console status for the tank/line/sensor you worked.
- Capture “after” evidence (screen + physical area photo).
- Confirm the site is left clean and safe (no open sumps/pans, no tools, no trip hazards).
- Write clear notes: what was found, what was done, and the final status.
Goal: the next tech can understand the situation in 30 seconds from your photos and notes.