Overview
This guide covers the most common Franklin Fueling gateway failures Chipkin is likely to see: incomplete tank and sensor schedules, serial setup mistakes, Veeder Root function gaps on Franklin EVO projects, and cases where the source-side definition is sound but the downstream exposure still needs work. Use it with the Franklin Fueling when exposing tank-monitoring data into BACnet or another supervisory platform.
Diagnostic Flow
- Confirm the exact panel or console model.
- Confirm the tank and sensor schedule.
- Confirm the source-side connection and protocol path.
- Validate one known-good tank or sensor value.
- Check whether the required point family is actually available through that protocol path.
- Only then review downstream supervisory mapping.
Symptoms & Solutions
| Symptom | Likely Cause | Action | Related Page |
|---|---|---|---|
| The gateway is installed but no meaningful points can be mapped | Tank and sensor inventory is incomplete | Stop and collect the real site schedule | Franklin Fueling |
| The team cannot log into the gateway during commissioning | The wrong GUI path is being used | Recheck the gateway access URL and commissioning procedure | QuickServer |
| Relay or status values never update even though other points work | The Franklin EVO does not expose those points cleanly through the Veeder Root path | Verify whether the job needs a Modbus fallback for those points | Modbus |
| One tank value is visible but the full site view is not | The source schedule was only partially collected | Rebuild the point map from the full tank and sensor list | Franklin Fueling |
| Source-side setup looks fine but BACnet values are still wrong | Target-side mapping now needs review | Recheck BACnet exposure after source validation | BACnet |
| Replacement work causes downstream mismatch | The previous point scope was not preserved | Compare the new map to the old site expectations | Veeder Root |
The Tank Schedule Is Missing
This is the first thing to correct in most Franklin Fueling jobs.
Confirm The Real Site Inventory
Confirm:
- Tank count
- Tank addresses
- Sensor count
- Sensor addresses and types
[!WARNING] If the tank and sensor schedule is incomplete, the gateway map is not ready.
Commissioning Is Blocked By Access Confusion
Some Franklin Fueling jobs fail on the setup path rather than the source protocol itself.
Recheck The Access Method
Look again at:
- Gateway GUI URL or access path
- Whether the team is using the correct page for commissioning
- Whether the source-side panel details are already known before changing login assumptions
The Veeder Root Path Does Not Expose Every Required Point
Franklin EVO projects can show partial success: tank data works, but relay or status data does not.
Separate Partial Success From Total Failure
Confirm:
- Which specific point family is failing
- Whether tank values are already proven
- Whether the installed EVO model supports that request path cleanly
- Whether a Modbus fallback is acceptable for the missing points
[!WARNING] If tank values work but relay status does not, do not keep rewriting the whole map blindly. First confirm whether the missing points are a protocol-path limitation on the source device.
The Source Is Fine But The Supervisory View Is Wrong
Once source-side values are proven, treat target mapping as a separate step.
Validate The Downstream Model
Confirm:
- Which points the supervisory system expects
- Whether one known-good value is present
- Whether the site is comparing against the original point scope from an older installation
Quick Diagnostic Decision Tree
- Start by confirming the panel model and the full tank and sensor schedule.
- If that is unclear: stop and collect it first.
- If it is clear: continue to access-path validation.
- Check whether the gateway access path is correct during commissioning.
- If not: fix that before deeper troubleshooting.
- If yes: continue to source-value validation.
- Check whether one known-good tank or sensor value is correct.
- If not: recheck the source inventory and mapping.
- If yes: continue to point-family validation.
- Check whether the missing data is limited to a specific point family such as relays or status values.
- If yes: validate the source protocol path and consider Modbus fallback.
- If no: continue to target-side validation.
- Check whether the downstream view is still wrong after source validation.
- If yes: recheck BACnet or other target mapping.
- If no: the main fault was on the source-definition or commissioning-access side.