Jump to content

Titan Replacment Fuel Tank, 2020 Diesel HD

Major Tom

By Major Tom
in Modifications & Accessories

 Share

Recommended Posts

cdh7917 Enthusiast

cdh7917

Posted
Posted

Glad to hear this has turned into a worthwhile modification. 
 

I’ve been trying to decide on the S&B 62 gal tank or the Titan 56 gal tank for my soon to arrive 3500. 
 

Either one seems like a great option once you get past the cost. I found a local shop that will do the install, but I’m also considering doing it myself. 
 

Thanks for all your feedback on the upgrade. Much appreciated. 

Major Tom Enthusiast

Major Tom

Posted
  • Author
Posted

On thing I failed to note in earlier post is the first fill-up warning.  Air gets trapped when the tank is nearly full, pause the pump for a few seconds before topping off or you will get some  fuel blow back!

hotairgypsy Enthusiast

hotairgypsy

Posted
Posted

in my 2015 i had the 57 gallon titan tank and liked it...i considered doing the 56 gallon in my 2020 but I went a different route personally.  for less money i am installing a 45 gallon L shaped tank that hugs my retractable cover canister in the bed of the truck...So now i have 36 plus 45 gallons for a few hundred less dollars...So if fully loaded up i will have onboard 80 gallons of diesel instead of 56 with the titan tank..I know that kills bed space but the retractable cover committed me that way.  I wanted to have a way to secure stuff in my bed of the truck...less crap i have to carry in the cab or the trailer

cdh7917 Enthusiast

cdh7917

Posted
Posted

I've ordered the S&B Filters replacement fuel tank.  It's a 62 gallon tank.  Up until the past day or two, it was about $100 more than Titan.  Today I noticed that the Titan tank is now $20 more than S&B for a smaller tank.

  • 1 month later...
Geobrian Enthusiast

Geobrian

Posted
Posted

@Major TomAny updates on tank performance? Looking at getting this tank soon. What type of shop did you get to install it?

Major Tom Enthusiast

Major Tom

Posted
  • Author
Posted

The tank was installed by a dealer that sells Titan products.  They do diesel repairs and upgrades.  I didn't know this until I visited their shop.  I took it as a good sign that they were very busy; it took them three days to work my job into their schedule.  No problems with the tank other than the blow back on fill-up.  Just slow the pump as you approach full.  Listen and you can hear a chance the fuel and air flow sound as the tank gets near full.  I did not have the blowback problem with the original equipment tank.

  • 1 year later...
Major Tom Enthusiast

Major Tom

Posted
  • Author
Posted

Talk to Titan yourself, but I believe they are diesel only tanks.  They have since released a 62 gallon version of this replacment tank.

Agargano98 Enthusiast

Agargano98

Posted
Posted

Has anyone had issues of the fuel guage dropping to empty like they say on the titan website?  Thinking of going this route as well.  Will also be doing a 45 gal aux tank in the bed along with the titan.  S&B voids their warranty if you add an aux tank.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...