Jump to content

Water-Meth

L8T

By L8T
in 6.6L Gas V8 (L8T)

 Share

Recommended Posts

L8T Enthusiast

L8T

Posted
Posted (edited)

Anyone tried running water meth as a power adder/mileage improver on their gasser yet? I ran it years ago on a Duramax but have never tried it on an NA engine. I feel with the higher compression and direct injection intake valve build up issues it might be very beneficial at a 30 to 50% meth mixture. 

Edited by L8T
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

I see no point on a NA engine.

 

It's already a DI engine, the fuel spray cools the air charge down inside the cylinder.

  • Like 1
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

I'm well aware of what water/meth does and I see no point on these engines when NA.

 

You are adding in extra fuel as well with the meth, which you don't need. You can't compensate for it with a tune either. Every engine is different but when I took the intake manifold off my DI 5.3 truck with 104,000 miles I was not concerned at all with the build up on my intake valves.

 

At cruising speeds the intake air temp is going be within 5-10 degrees of ambient, then it's going to get cooled by the fuel spray of the injector in the cylinder. What gains do you think you will see if you cool the air down just a smidge further? How will adding water/meth improve fuel mileage in closed loop fuel control?

Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted

We use to use water as detonation suppression on NA motors when gasoline octane started tanking after TEL was taken from gasoline. Water was quite effective as a charge coolant. It wasn't run continuously but triggered by manifold vacuum. Alcohol was added mostly to prevent freezing but also as an octane booster for stubborn cases.  Yes we have knock sensors but the point of this exercise it to prevent removing timing. 

 

Point of note. A motor with fuel before the valve at part throttle (high vacuum) vaporizes fuel by lowing the boiling point based on absolute pressure in the manifold. Near full throttle this effect is diminished as pressure rises reducing it's effectiveness. Water and alcohol both have lower boiling points than gasoline so it's more effective. 

 

GDI motors inject fuel under crazy high pressure into a cylinder under compression pressure several times higher than atmospheric. The gasoline is atomized not vaporized and does not contribute to charge cooling. Even it's temperature at the injector is quite a bit above its temperature in the tank the result of over 2K pressure.

 

Personally I don't see an advantage in a NA GDI motor and can see a few issues that may arise. For example the sensor that we call the MAP in the GM setup also measures humidity and temperature and adjust fuel accordingly. Adding moisture that is unaccounted for between the sensor and the valve will have an effect on fuel delivery rate. 

 

Anyway my 2 cents of which only one may have any value. 😉 

 

 

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

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...