Jump to content

Disconnect battery for CAI install

Luckyfd

By Luckyfd
in Modifications, Wheels & Tires

 Share

Recommended Posts

Luckyfd Enthusiast

Luckyfd

Posted
Posted

I just want to make sure I understand this... if the intake was installed without disconnecting the battery and there is NO CEL or problems of any kind the MAF sensor sent the new readings to the ECU and the ECU made adjustments and is benefiting from the upgraded CAI. The truck runs and sounds amazing! 2019 5.3 Chevy Silverado S&B CAI. The MAF isn’t Artificial intelligence It’s a sensor that cannot be reset. It’s just a sensor right? So when sensing a new environment it will send the new reading to the ECU and if it’s in the acceptable parameters the truck will adjust fuel to mix with the increase in air flow. 

TNTSierra Senior Enthusiast

TNTSierra

Posted
Posted

You are supposed to unhook the battery for 2 hours when installing an S&B CAI per instructions.  I installed mine and have over 8k miles on it without throwing an codes or any other issues.  ????
 

Hopefully you have no issues. You could always unhook it for a few hours. Hook it back up and make sure your air filter monitor life is turned off. 

Luckyfd Enthusiast

Luckyfd

Posted
  • Author
Posted
17 minutes ago, TNTSilverado said:

You are supposed to unhook the battery for 2 hours when installing an S&B CAI per instructions.  I installed mine and have over 8k miles on it without throwing an codes or any other issues.  ????
 

Hopefully you have no issues. You could always unhook it for a few hours. Hook it back up and make sure your air filter monitor life is turned off. 

Thanks! I’ve always heard you need to disconnect but I just can’t follow the logic. 

Thejet07 Enthusiast

Thejet07

Posted
Posted

I’ve almost pulled the trigger on this intake countless times. I really want it but I’ve had the dreaded P0300 code twice in the last 2-3k miles and the dealership refuses to dive into it calling it random. I’m afraid that if I install this and something does come up they’ll just blame it on the intake. Ohh what to do?


Sent from my iPhone using Tapatalk

lapoolboy Senior Enthusiast

lapoolboy

Posted
Posted (edited)
1 hour ago, Thejet07 said:

I’ve almost pulled the trigger on this intake countless times. I really want it but I’ve had the dreaded P0300 code twice in the last 2-3k miles and the dealership refuses to dive into it calling it random. I’m afraid that if I install this and something does come up they’ll just blame it on the intake. Ohh what to do?


Sent from my iPhone using Tapatalk

Your truck will be out of warranty before the intake comes in.

Edited by lapoolboy
  • Like 1
  • Haha 1
CamGTP Senior Enthusiast

CamGTP

Posted
Posted
2 hours ago, lapoolboy said:

Disconnecting the battery resets the short-term fuel trims so it can rebuild the tables.

I will correct you on this incase someone in the future reads this.

 

Short term trims reset back to zero when the engine turns off and come back alive the within a few seconds of the engine running, they are always active no matter what unless otherwise programmed to be turned off.

 

Long term fuel trims don't reset and will be remembered when the engine starts again. They take "longer" to make changes to real time fuel changes but disconnecting the battery really isn't even needed anymore. Long term trims learn quicker than most think, I'm talking like 30 seconds to a minute and they can completely change course.

 

Someone could have a vacuum leak for 1,000 miles with the fuel trims pegged at the maximum 25%. That someone could fix the vacuum leak and within a minute the computer would have already started bring the fuel trims back down to normal again. O2 sensors and fuel trims work very fast when everything is up to par.

 

 

Like the OP said, the MAF is just a sensor and all it does it read what is happening. It's the same way with "tables", those are preset and do no change. All the airflow and fueling tables are set in stone and the computer will do it's best to achieve the set values in the calibration based upon sensor feedback. It's the main reason why things are so lenient in the calibration, things can be horribly wrong with mechanical parts or sensor and the engine will still run. The calibrations have such a huge swing in the good or bad portion that it can still be made to run with tons of background computer correction.

 

Okay, long winded late night reply over.

  • Like 2
  • Thanks 1
  • 2 years later...
Flag26 New Member

Flag26

Posted
Posted

So did you disconnect for 2 hours? I just bought an S&B Cai for my 2021 2500 hd and wondering about that. Also will it remember filter disable if I do it before disconnecting?

Thanks 

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...