Field reference for fuel system and underground storage tank technicians. 93 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 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.
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
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.
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.
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.
Data transfer errors occurred in the System Bus. — Action: Upgrade to the latest version of firmware available at: www.franklinfueling.com
[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.
[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.
[Tank] The density of the product is not within specifications. — Action: Enter setup and verify the information under density in the probe programming.
[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.
[Tank] Product level exceeds tank diameter due to an error in console of programming. — Action: Verify tank, offset, and probe programming.
[Tank] Backup battery is low. — Action: See Installation Guide for replacement instructions.
[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.
[Sensor] The specified TSP-DMS has detected product. — Action: Inspect the sump for the presence of product.
[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.
[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.
[Sensor] The specified TSP-DMS was not properly learned. — Action: Enter into the Control > Mag Sensor screen and have the console learn the sensor.
[Sensor] The specified TSP-DMS has detected water. — Action: Inspect the sump for water.
[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.
[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.
[Any] The device listed has gone out of compliance — Action: Pass a test or clear the alarm on the device.
[Tank] Product net levels exceed tank diameter — Action: Verify tank, product offset and probe programming
[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.
[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.
[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.
[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.
[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.
[SCM] An error has been detected in the containment programming.
[SCM] An error has been detected in the containment programming
[Engineering] The containment called for the STP to turn on but has not seen an increase in vacuum level.
[SCM] The rate of vacuum decay faster than the learned rate.
[SCM] 6”hg could not be reached in the learned time.
[SCM] The vacuum level has dropped below 1”hg.
[Engineering] Low vacuum level due to Pump Request Ignored.
[SCM] Containment programming has not been completed
[SCM] Vacuum level is fluctuating at a rate that is inconsistent with the learned parameters.
[SCM] The 4-20mA vacuum transducer has failed and is no longer detected
[SCM] The vacuum level has reached above 10”hg
[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.
[ChannelSN3] Brine solution has tripped high level brine sensor. — Action: Verify actual level of solution and sensor installed location.
[ChannelSN3] Discriminating sensor is given an improper ID. — Action: Verify sensor programming and Auto configuration.
[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.
[ChannelSN3] 3-wire discriminate sensor detecting water at location. — Action: Visually inspect area for water presence.
[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.
[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.
[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.
[Line] An error has been detected in the programming of the specified line. — Action: Verify programming of line under the setup menu.
[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.
[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.
[TPI] The STP controller is reporting an extended run condition. — Action: Refer to the applicable Smart Controller Installation guide for details.
[TPI] The STP controller is reporting a high temperature condition.
[TPI] The STP controller is reporting that it has not been calibrated.
[TPI] The STP controller is reporting an over speed condition. — Action: Refer to the applicable Smart Controller Installation guide for details
[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.
[TPI] The STP controller is reporting a relay fault error. — Action: Refer to the applicable Smart Controller Installation guide for details.
[TPI] The STP controller is reporting an unbalanced load condition.
[TPI] The STP controller is reporting a voltage level under 200VAC.
[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
[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.
[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.