Field reference for fuel system and underground storage tank technicians. 93 entries, taken from the DropTubeBuilder app.
These notes are the web copy of the DropTubeBuilder reference, built for fuel system and underground storage tank technicians. The same library is free inside the app, with no time limit and no account, and it works with no signal.
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 StoreProgramming errors made during setup of the 2-Wire Sensor Module. — Action: Verify 2-Wire Sensor Module programming parameters. If the condition still exists, contact Franklin Fueling Systems’ Technical Services Dept. for support on this issue.
3-Wire Sensor Module is offline due to unknown causes. — Action: Follow safety procedures before working inside of the console. Visually verify a steady, green “Run” light. If a red “Err” light is flashing or steady, try to reboot the system. If the condition still exists, contact Franklin Fueling Systems’ Technical Services Dept. for support on this issue.
3-Wire Sensor Modules detected does not match the number programmed. — Action: At startup check that the number of 3-Wire Sensor Modules installed matches the number programmed under System Configuration > Modules Expected. On machines that are in service: Check for a flashing green light or no light at all on the 3-Wire Sensor Module and contact FFS Technical Services for support.
4-20 mA Modules detected does not match the number programmed. — Action: Check that the number of 4-20mA Modules installed matches the number programmed under System Configuration > Modules Expected. Check for a flashing green light or no light at all on the 4-20mA Module and contact FFS Technical Services for support
Errors have been detected in the an analog input channel — Action: If the input is not being used, set the programming to reflect proper input type. If the input is being used as an analog signal, inspect the wiring and redo connections.
AC Input Modules detected does not match the number programmed. — Action: Check that the number of AC Input Modules installed matches the number programmed under System Configuration > Modules Expected. Check for a flashing green light or no light at all on the AC Input Module and contact FFS Technical Services for support.
An input on the AC input module has been configured as an alarm and is active. — Action: Check the programming and voltage inputs for the specified Input channel on the AC Input module; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
DIM modules detected does not match the number programmed. — Action: Check that the number of DIM Modules installed matches the number programmed under System Configuration > Modules Expected. If problem persists, contact FFS Technical Services for support
The configuration that has been loaded is not valid. — Action: Verify the file type of the configuration which is being uploaded; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
An input on the Input/Output module has been configured as an alarm and is active. — Action: Check the programming and voltage inputs for the specified Input channel on the IO module; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
IO Modules detected does not match the number programmed. — Action: Check that the number of IO Modules installed matches the num- ber programmed under System Configuration > Modules Expected. Check for a flashing green light or no light at all on the IO Module and contact FFS Technical Services for support.
Lon Modules detected does not match the number of Lon Modules programmed. — Action: Check that the number of LON Modules installed matches the number programmed under System Configuration > Modules Expected. If problem persists, contact FFS Technical Services for support. Also check that the Node ID does not conflict with another Node ID in the network
Power Supply Modules detected does not match the number programmed. — Action: Check that the number of Power Supply Modules installed matches the number programmed under System Configuration > Modules Ex- pected. Check for a flashing green light or no light at all on the Power Supply Module and contact FFS Technical Services for support
Errors in the setup of the listed module. — Action: The console may need to be reprogrammed; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
Probe Module is not communicating with the console. — Action: Follow safety procedures before working inside the console. Visually verify a steady green “Run” light. If red “Err” light is flashing or steady, re-seat module and reboot system. If the condition still exists, contact Franklin Fueling Systems’ Technical Support for help on this issue.
Programming errors made during setup of the Probe Module. — Action: Verify Probe Module programming parameters. If the condition still exists, contact Franklin Fueling Systems’ Technical Support for help on this issue.
[slot] Relay Modules detected does not match the number programmed. — Action: Check that the number of Relay Modules installed matches the num- ber programmed under System Configuration > Modules Expected. Check for a flashing green light or no light at all on the AC Input Module and contact FFS Technical Services for support.
An error exists in the configuration of the Secondary Containment Monitoring Setup. — Action: Inspect the Secondary Containment Monitor setup configuration for possible errors; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
Data transfer errors occurred in the System Bus. — Action: Upgrade to the latest version of firmware available at: www.franklinfueling.com; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Tank] This error is caused by a programming mistake in the Special Products section. — Action: Verify Special Product Alpha volume correction program parameters. Contact FFS Technical Services Department for assistance.
[Any] The device listed has 7 days before it will go into a compliance alarm — Action: Pass a test or clear the alarm on the device; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Tank] Level and Volume mismatch detected in Correction table programming. — Action: Verify that all levels and volumes are entered accurately into the Correction Table programming; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] The density of the product is not within specifications. — Action: Enter setup and verify the information under density in the probe programming; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] Probe detects a lesser number of floats than programmed. — Action: Review probe programming for correct number of floats. If correct then inspect probe shaft, floats, and float magnets. With the probes out of the tank, this would be an idea time to clean the probe and floats. If pressures meets requirements specified, contact Franklin Fueling Systems’ Technical Services Dept. for support on this issue.
[Tank] Product level exceeded High limit set. Possible close to tank overfill condition — Action: Acquire an accurate product level. If actual product level in tank does not match the consoles displayed current level, verify programming is correct.
[Tank] The specified tank has reached the programmed High Product Volume. — Action: Check product volume and compare to the programmed High Volume alarm Limit in the setup menu. Acquire an accurate product level and compare to the ATG. If levels differ, verify programming is correct. If alarm persists, contact FFS Technical Services for support.
[Tank] Water level exceeded High limit set. — Action: Verify programmed level. If water is too high consult you local site policy procedures for corrective actions; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Tank] Product level exceeds tank diameter due to an error in console of programming. — Action: Verify tank, offset, and probe programming; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] Backup battery is low. — Action: See Installation Guide for replacement instructions; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Tank/ Manifold] Product volume below Low Low limit. The tank or manifold specified may be near empty. — Action: Acquire an accurate product volume, and if does not match the consoles displayed current volume, verify programming; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Sensor] The specified TSP-DMS has detected product. — Action: Inspect the sump for the presence of product; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Sensor] There is an error with the reported data from the specified TSP-DMS — Action: Inspect wire connections at the Mag sensor. If the problem persists, contact FFS Technical Services for support; before escalating, check the module has power and that its status light behaves normally; check the module is fully seated and its connectors are clean and dry; check for water ingress and corrosion inside the console, which is a common cause of module faults; power cycle the console and note whether the fault returns immediately or after a delay; have the console model, software version and the exact alarm text ready before you call
[Sensor] The specified TSP-DMS is not reporting the level information for one or more float. — Action: Inspect the Mag sensor for damage and redo the connections. If the Problem persists, contact FFS Technical Services; before escalating, check the module has power and that its status light behaves normally; check the module is fully seated and its connectors are clean and dry; check for water ingress and corrosion inside the console, which is a common cause of module faults; power cycle the console and note whether the fault returns immediately or after a delay; have the console model, software version and the exact alarm text ready before you call
[Sensor] The specified TSP-DMS was not properly learned. — Action: Enter into the Control > Mag Sensor screen and have the console learn the sensor; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Sensor] The specified TSP-DMS has detected water. — Action: Inspect the sump for water; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Tank] A delivery has been detected on the specified manifold. — Action: This is not an alarm and should only be a concern if there was not a delivery to the site at the specified date and time.
[Tank] A leak in the specified manifolded tanks has been detected via a SCALD test. Suspect possible leak — Action: Review Tank Leak Test History and programming. Refer to page 22 for instructions on manually starting line leak tests; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] The specified manifold has reached the programmed Low Low Product Volume — Action: Check product volume and compare to the programmed Low Low Volume alarm Limit in the setup menu. Acquire an accurate product volume and compare to the ATG. If levels differ, verify programming is correct. If alarm persists, contact FFS Technical Services for support.
[Tank] The specified manifold has entered Sentinel Mode and detects product leaving the tank that exceeds the programmed theft limits. — Action: Verify programming and accurate level / volume readings; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Any] The device listed has gone out of compliance — Action: Pass a test or clear the alarm on the device; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Tank] Product net levels exceed tank diameter — Action: Verify tank, product offset and probe programming; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] The Console is not receiving any communication from the probe. — Action: Check for proper probe programming at the console and inspect wire connections at the probe. If the problem persists, contact FFS Technical Services for support.
[Tank] The Product Volume as reported by the probe has exceeded the limits of the tank. — Action: Check for proper probe and tank programming at the console. If programming is correct, inspect the probe to ensure that the float is not stuck in the riser or is otherwise obstructed.
[System] The system has detected a low memory situation. — Action: Contact FFS Technical Services for support; before escalating, check the module has power and that its status light behaves normally; check the module is fully seated and its connectors are clean and dry; check for water ingress and corrosion inside the console, which is a common cause of module faults; power cycle the console and note whether the fault returns immediately or after a delay; have the console model, software version and the exact alarm text ready before you call
[Tank] Tank leak detected. Suspect possible leak. — Action: Review tank leak test history and programming. Refer to page 22 for instructions on manually starting line leak tests; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] The Product Density has exceeded the programmed low limit. — Action: Verify programming if correct this alarm may be an indication of improper density of the fuel; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] A delivery has been detected on the specified tank. — Action: This is not an alarm and should only be a concern if there was not a delivery to the site at the specified date and time.
[Tank] Product used in Sentinel Mode exceeds theft limit set. Suspect theft, and then verify theft limit in programming. — Action: Verify theft limit in programming. Also obtain an accurate product level and compare to inventory; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Tank] Ullage reported has exceeded tank capacity. — Action: Check for proper probe and tank programming at the console. If programming is correct, inspect the probe to ensure that the float is not stuck in the riser or obstructed. Bring the probe inside and wire directly to the gauge to eliminate possible problems with the field wiring.
[Tank] Water volume has exceeded tank capacity. — Action: Check for proper probe and tank programming at the console. If programming is correct, inspect the probe to ensure that the colored water float is on the bottom.
[SCM] The learning process has not been completed. — Action: Refer to Secondary Containment Monitoring Installation and User’s Guide 000-0528 for more information; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[SCM] An error has been detected in the containment programming. Vacuum based containment monitoring is not valid while this is present. Action: review the containment programming against what is physically installed, tank by tank and line by line; check each monitored containment is assigned to the correct sensor and transducer; check the learned parameters have been established, since an unlearned system reports programming errors; check whether recent work added or removed a containment without the programming following; re enter and save the configuration, then let the system relearn; confirm monitoring is actually running afterwards rather than assuming the error clearing means it is
[SCM] An error has been detected in the containment programming. This is the warning stage of the same condition. Action: review the containment programming against the physical installation before it escalates; check sensor and transducer assignments for each containment; check the learned parameters are present and sensible; check for recent work that changed the installation without the programming following; correct and save, then confirm monitoring resumes
[Engineering] The containment called for the STP to turn on but saw no increase in vacuum level. Either the pump did not run, or it ran and the vacuum did not build. Action: check whether the STP actually ran when requested, which splits this immediately into a pump problem or a vacuum path problem; check the STP control wiring and the relay; check the STP is not locked out by a tank or line leak alarm; if the pump ran, check the vacuum path for a large leak that prevents any vacuum building; check the vacuum line, fittings and the transducer connection; check the interstitial space is actually sealed, including sump penetrations and test ports left open after service; check the transducer is reading, since a dead transducer reports no increase even when vacuum is building
[SCM] Vacuum is decaying faster than the learned rate. The containment is leaking somewhere, though not necessarily through the tank wall. Action: check the accessible fittings, test ports and vacuum line connections first, since these are the common leak points and are far more likely than a tank breach; check any port opened during recent service was properly resealed; check the vacuum line for damage and for crushing under a sump lid; check the transducer connection and its seal; check sump penetrations and boots on the interstitial path; if the accessible points are sound, the interstice itself is suspect, which makes this a potential breach requiring investigation; a confirmed containment breach is a suspected release the owner must report to the implementing agency within 24 hours
[SCM] Six inches of mercury could not be reached in the learned time. The system is pulling but not getting there. Action: check for a leak in the vacuum path, working the accessible fittings, test ports and line connections first; check any service port left open or poorly resealed; check the vacuum pump or generator is running and making its rated performance; check the vacuum line for restriction, crushing or blockage; check the transducer is reading correctly against a known gauge, since a drifting transducer reports a target never reached; check whether the learned time is still appropriate, because a changed installation invalidates the learned parameters; if the path is sound and the pump performs, treat the interstice as suspect and investigate
[SCM] The vacuum level has dropped below one inch of mercury. At this level the containment is effectively unmonitored. Action: check the vacuum source is running; check the accessible fittings, test ports and vacuum line connections for leaks; check any port disturbed by recent service; check the vacuum line for damage or disconnection; check the transducer and its connection; check whether other containments on the same system are also low, which points at the vacuum source rather than one interstice; if no leak is found in the accessible path, treat the interstice as suspect and investigate, reporting within 24 hours if a breach is confirmed
[Engineering] Low vacuum together with a pump request that produced no response. Two related failures at once, which usually means one cause. Action: check whether the STP ran when requested, which separates a control fault from a vacuum path fault; check the STP control wiring, relay and any lockout from a tank or line alarm; check the vacuum path for a leak large enough to prevent vacuum building at all, starting at accessible fittings and test ports; check the vacuum line for disconnection or major damage; check the transducer is reading; treat a large unexplained leak as a potential containment breach and investigate rather than simply restarting the pump
[SCM] Containment programming has not been completed, so nothing is being monitored. Action: complete the containment configuration for every monitored space; assign each containment to its correct sensor and transducer; let the system establish its learned parameters, which it needs before it can judge normal from abnormal; check whether the configuration was lost rather than never entered, since loss points at a power or memory problem that will recur; confirm monitoring is running and reporting sensible values before leaving site; record the period during which containment was unmonitored
[SCM] The vacuum level is fluctuating inconsistently with the learned parameters. An intermittent leak or a measurement problem. Action: check for an intermittent leak at fittings, test ports and the vacuum line, including anything that moves or flexes; check for a loose or partly seated cap or port cover, which is the classic cause of unstable rather than steady loss; check the transducer and its wiring for an intermittent connection; check for temperature driven fluctuation, since a shallow interstice can swing with ambient conditions; check whether the learned parameters were established under different conditions and need relearning; trend the readings rather than judging on a single sample
[SCM] The 4-20 mA vacuum transducer has failed and is no longer detected. Containment monitoring is out until it is restored. Action: check the transducer wiring and terminations, since a 4-20 mA loop reports as failed on an open circuit; check for water and corrosion at the connector, which is the usual cause; check loop power is present; measure the loop current to distinguish a dead transducer from a broken loop; check the transducer itself for damage; replace and verify the reading against a known gauge; record the outage, since the containment was unmonitored
[SCM] The vacuum level has risen above ten inches of mercury. Excessive vacuum can damage the tank or the interstice. Action: check the vacuum source is not running continuously when it should have cut out; check the control and the pressure switch or setpoint; check the transducer is reading correctly against a known gauge, since a drifting transducer is a common cause of a false high reading; check the relief arrangement is functioning; stop the vacuum source if the reading is genuine and excessive, since over vacuum can collapse an interstice; verify the setpoints against the manufacturer specification for the tank
[ChannelSN2] 2-Wire Sensor Module fuse blown due to unknown causes. — Action: The fuses on the Sensor boards are non-serviceable per UL listing standards. The module must be replaced if the fuse is blown.
[ChannelSN3] Monitoring well is dry. — Action: Visually verify that the alarm is correct; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[ChannelSN3] Brine solution has tripped high level brine sensor. — Action: Verify actual level of solution and sensor installed location; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[ChannelSN3] Discriminating sensor is given an improper ID. — Action: Verify sensor programming and Auto configuration; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[ChannelSN3] Discriminating sensor has detected product present at location. — Action: Visually inspect location carefully for presence of liquid. In the case of a leak, follow site policy procedures. If no liquid is present, and alarm still exists, sensor may be tripped on error. Check wiring continuity from sensor to console.
[ChannelSN3] Discriminating sensor shows alarm status. — Action: Inspect location for presence of liquid. In the case of a leak, follow site policy procedures. If no liquid is present, and alarm still exists, sensor may be tripped on error. Check wiring continuity from sensor to console. Test sensor at console, trip sensor on purpose. Verify console terminal wiring. If issue still exists, inspect wiring to probe. If the condition still exists, contact Franklin Fueling Systems’ Technical Services for support.
[ChannelSN3] 3-wire sensor data signals not in sync with module. — Action: Verify correct wiring and re-make the connections. Verify sensor type; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[ChannelSN3] 3-wire discriminate sensor detecting water at location. — Action: Visually inspect area for water presence; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Line] A 0.1 gph test has not been completed within the last 365 days. — Action: Verify that no pertinent alarm conditions have been reoccurring. Ensure that there is enough time to pass the test; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Line] The required daily 3 GPH test has not been completed. — Action: Check for continuous pump on conditions that could be caused by a sticky handle switch or relay; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Line] Pressure during dispensing dropped below 7.5 psi. This is seen as a catastrophic leak during dispensing. — Action: Inspect all sumps for product. Use a pressure gauge to test line pressure during dispensing. See “LS500 Auto Learn Line Leak Detection Installation & User’s Guide” FFS 000-2145. Contact Franklin Fueling Systems’ Technical Services Dept. for support.
[Line] The pump OFF pressure has dropped below 7 psi within 1 second after the pump was turned off — Action: Inspect all sumps for product. Refer to “LS500 Auto Learn Line Leak Detection Installation & User’s Guide” FFS 000-2145 for more information.
[Line] The console has detected a line leak greater than 3 gph. — Action: Inspect all sumps for product. Refer to “LS500 Auto Learn Line Leak Detection Installation & User’s Guide” FFS 000-2145 for more information.
[Line] Specified line is not configured, therefore line leak test will not be performed. — Action: Verify line programming. If necessary configure line; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Line] An error has been detected in the programming of the specified line. — Action: Verify programming of line under the setup menu; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[Line] The last passed gross test detected a leak just under the 3 gph threshold. — Action: Verify there is no sign of leaks within any of the sumps. Run additional tests. Refer to “LS500 Auto Learn Line Leak Detection Installation & User’s Guide” FFS 000-2145 for more information.
[Line] Line testing has not been enabled. — Action: Verify no other alarm is present then enter the line control menu and enable the line testing feature; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Line] The transducer is not being detected by the console. — Action: Inspect the wiring to the specified transducer and the channel it terminates at. Refer to “LS500 Auto Learn Line Leak Detection Installation & User’s Guide” FFS 000-2145 for more information.
[TPI] The STP controller has reported a dry run condition but the associated tank shows a product level above the intake. — Action: Ensure proper programming of the TPI and calibration of the Smart Controller. If correct, check for an obstruction on the PMA.
[TPI] The programmed controller type does not match what the console is detecting. — Action: Verify proper programming of the TPI as well as the Smart controller type and address; compare the programming against what is physically installed rather than against what you expect; check whether recent work changed the installation without the programming following; check whether the setting was lost rather than never entered, since loss points at a power or memory fault that will recur; save and power cycle, then confirm the fault clears rather than assuming it
[TPI] The STP controller is reporting an extended run condition. — Action: Refer to the applicable Smart Controller Installation guide for details; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[TPI] The STP controller is reporting a high temperature condition. Action: check the controller enclosure for blocked ventilation and accumulated debris; check ambient conditions at the controller, including direct sun on the enclosure; check the motor is not drawing excessive current, since a loaded or failing motor heats the controller; check for a restriction in the line raising motor load; check the supply voltage, since low voltage raises current and heat; check the connections at the controller for looseness, because a loose termination heats badly; let it cool and monitor whether it recurs, rather than only clearing the alarm
[TPI] The STP controller reports it has not been calibrated. Action: establish whether calibration was lost or never performed, since lost calibration points at a problem that will recur; check whether a recent controller replacement or firmware update cleared it; calibrate following the Franklin procedure for this controller; verify the pump operates and makes normal pressure after calibration; check the backup and power arrangements if the calibration was lost rather than absent
[TPI] The STP controller is reporting an over speed condition. — Action: Refer to the applicable Smart Controller Installation guide for details; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[TPI] Communication from the TPI to the STP controller has failed. — Action: Check all wiring connections and ensure that there is power supplied to the Smart Controller; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[TPI] The STP controller is reporting a relay fault error. — Action: Refer to the applicable Smart Controller Installation guide for details; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[TPI] The STP controller is reporting an unbalanced load. On a three phase motor this damages the motor if left. Action: measure the current on each phase at the controller and compare them; measure the voltage on each phase, since a supply imbalance causes a current imbalance; check all terminations at the controller and the motor for looseness and corrosion, which is the most common cause; check the motor windings for resistance imbalance; check for a failing contactor with a pitted or open pole; do not simply reset and leave it, because running a motor on an unbalanced supply will destroy it; involve the utility if the imbalance is on the incoming supply
[TPI] The STP controller is reporting a supply below 200 VAC. Low voltage raises motor current and causes overheating. Action: measure the incoming voltage at the controller under load, not at rest, since the drop only appears when the motor starts; check all terminations from the panel to the controller for looseness and corrosion; check the breaker and any disconnect for a poor contact; check the conductor size against the run length, since voltage drop on a long undersized run causes this; check whether other equipment on the same supply drops at the same time, which points upstream; check with the utility if the supply itself is low; do not run the pump on low voltage, because it will overheat and fail
[TPI] The STP controller is reporting an unknown fault code. — Action: Check fault condition on Smart controller and contact FFS Technical Services for more information; before escalating, check the module has power and that its status light behaves normally; check the module is fully seated and its connectors are clean and dry; check for water ingress and corrosion inside the console, which is a common cause of module faults; power cycle the console and note whether the fault returns immediately or after a delay; have the console model, software version and the exact alarm text ready before you call
[Printer] Printer is out of paper, or the printer door is open. — Action: Make sure the printer has paper, and the printer door is closed completely; check the wiring and terminations for the affected device before replacing anything; check for water and corrosion at connectors, which causes most field faults; power cycle and confirm the fault genuinely clears rather than just acknowledging it; record the alarm and its time, since the pattern often identifies the cause faster than the single event
[Printer] Printer motor has exceeded temperature limit — Action: Allow printer to cool. Keep the console area cool and ventilated. If the alarm does not clear, contact FFS Technical Support.
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.